Welcome! Log In Create A New Profile

Advanced

uBoot on Maxtor MSS2

Posted by Val532 
Val532
uBoot on Maxtor MSS2
January 04, 2012 01:33PM
Hi Jeff,

I know this is probably not the good place to ask it but what i whant to do is nearly the same thing you did with the seagate free agent dockstar with the oBoot on Maxtor MSS2 (maxtor shared storage 2) i.e create a custom uBoot and to intall debian on it.

The hardware of the MSS2:
CPU marvell orion 88 F5182,
2x16Mo,
NAND for uBoot is 256k0,
2 SATA ports,
Gb LAN,
2 USB ports,
and a serial port.

The currently implemantation of uBoot probably not integrate the net consol and probably not usbload neither.
UBoot can start a kermel named uImage(but probably not uInitrd) on /boot on the frist or second partition of Sata drive (configurable).

I want the posibility to boot on usb drive and netconsole.

I know the Debian kernel is able to work on Orion CPU (orion5x) but the kernel is with an uInitrd and curently i don't know if uboot could boot a kernel like this.

I have made a rootdir with debian on it (with debootstrap and your script (modified)) but for the moment it does not boot.

Can you help me to build a new uboot for my MSS2 (i searched on the net but nobody do this).

Thanks.
dpffan
Re: uBoot on Maxtor MSS2
January 04, 2012 08:37PM
Val532
Re: uBoot on Maxtor MSS2
January 05, 2012 09:33AM
Thanks,

I build a new Kernel (3.1) on my dockstar for my MSS2, i hop it's work.
Val532
Re: uBoot on Maxtor MSS2
January 05, 2012 09:20PM
Ok my kernel does not work, i don't understand how i can do this corectly.

I think the official debian kernel should work.

For the moment my Uboot bootcmd is : bootcmd=ide reset; ide reset; ext2load ide 0:1 0x00200000 /boot/uImage; setenv bootargs $(bootargs) $(bootargs_root); bootm 0x00200000

How i can made it to boot the kernel.

For the moment i have no serial cable (i buy a nokia ca 42 it will arrive in two or three day).

If i do this : bootcmd=ide reset; ide reset; ext2load ide 0:1 0x800000 /boot/uImage; setenv bootargs $(bootargs) $(bootargs_root); if ext2load ide 0:1 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi

It should work no ?
Val532
Re: uBoot on Maxtor MSS2
January 07, 2012 10:41AM
hi,

I have access to u-boot, thanks to my serial cable.

I can charge a kernel via tftp but right now I have a kernel panic when trying to load the file system.

I need help to rebuild the kernel correctly.

[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.1.6 (3.1.6) (root@debian) (gcc version 4.6.2 (Debian 4.6.2-9) ) #2 Sat Jan 7 00:01:16 UTC 2012
[    0.000000] CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Maxtor Shared Storage II
[    0.000000] Clearing invalid memory bank 0KB@0xffffffff
[    0.000000] Clearing invalid memory bank 0KB@0xffffffff
[    0.000000] Clearing invalid memory bank 0KB@0xffffffff
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x41000403
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rw
[    0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
[    0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Memory: 32MB = 32MB total
[    0.000000] Memory: 27208k/27208k available, 5560k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
[    0.000000]     vmalloc : 0xc2800000 - 0xfd800000   ( 944 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc2000000   (  32 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc045cb18   (4435 kB)
[    0.000000]       .init : 0xc045d000 - 0xc0480000   ( 140 kB)
[    0.000000]       .data : 0xc0480000 - 0xc04b83d8   ( 225 kB)
[    0.000000]        .bss : 0xc04b83fc - 0xc051dd5c   ( 407 kB)
[    0.000000] NR_IRQS:64
[    0.000000] sched_clock: 32 bits at 166MHz, resolution 5ns, wraps every 25769ms
[    0.000000] Console: colour dummy device 80x30
[    7.918911] Calibrating delay loop... 331.77 BogoMIPS (lpj=1658880)
[    7.978578] pid_max: default: 32768 minimum: 301
[    7.978902] Security Framework initialized
[    7.979080] Mount-cache hash table entries: 512
[    7.979786] Initializing cgroup subsys cpuacct
[    7.979831] Initializing cgroup subsys memory
[    7.979891] Initializing cgroup subsys devices
[    7.979920] Initializing cgroup subsys freezer
[    7.979946] Initializing cgroup subsys net_cls
[    7.979973] Initializing cgroup subsys blkio
[    7.980165] CPU: Testing write buffer coherency: ok
[    7.982841] devtmpfs: initialized
[    7.985893] print_constraints: dummy:
[    7.986382] NET: Registered protocol family 16
[    7.987636] Orion ID: MV88F5182-A2. TCLK=166666667.
[    7.990200] Applying Orion-1/Orion-NAS PCIe config read transaction workaround
[    7.990778] PCI: bus0: Fast back to back transfers disabled
[    7.991907] PCI: bus1: Fast back to back transfers enabled
[    7.998188] bio: create slab <bio-0> at 0
[    7.999305] vgaarb: loaded
[    8.000220] SCSI subsystem initialized
[    8.002163] Switching to clocksource orion_clocksource
[    8.008665] Switched to NOHz mode on CPU #0
[    8.054444] NET: Registered protocol family 2
[    8.054958] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    8.056528] TCP established hash table entries: 1024 (order: 1, 8192 bytes)
[    8.056605] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    8.056655] TCP: Hash tables configured (established 1024 bind 1024)
[    8.056681] TCP reno registered
[    8.056713] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    8.056768] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    8.057339] NET: Registered protocol family 1
[    8.057827] NetWinder Floating Point Emulator V0.97 (double precision)
[    8.058912] audit: initializing netlink socket (disabled)
[    8.059008] type=2000 audit(0.130:1): initialized
[    8.062311] VFS: Disk quotas dquot_6.5.2
[    8.062540] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    8.064087] msgmni has been set to 53
[    8.065571] alg: No test for stdrng (krng)
[    8.065865] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    8.065903] io scheduler noop registered
[    8.065926] io scheduler deadline registered
[    8.066068] io scheduler cfq registered (default)
[    8.066347] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
[    8.102332] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[    8.142335] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[    8.143261] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    8.164752] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A
[    8.598259] console [ttyS0] enabled
[    8.604015] sata_mv sata_mv.0: slots 32 ports 2
[    8.612305] scsi0 : sata_mv
[    8.615984] scsi1 : sata_mv
[    8.619294] ata1: SATA max UDMA/133 irq 29
[    8.623454] ata2: SATA max UDMA/133 irq 29
[    8.629615] physmap platform flash device: 00040000 at ff800000
[    8.635801] Found: SST 39LF020
[    8.638877] physmap-flash.0: Found 1 x8 devices at 0x0 in 8-bit bank
[    8.645357] number of JEDEC chips: 1
[    8.652826] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    8.659829] mv643xx_eth smi: probed
[    8.667139] mv643xx_eth_port mv643xx_eth_port.0: eth0: port 0 with MAC address 00:10:75:03:5f:16
[    8.676954] mousedev: PS/2 mouse device common for all mice
[    8.683401] i2c /dev entries driver
[    8.688106] rtc-m41t80 0-0068: chip found, driver version 0.05
[    8.697111] rtc-m41t80 0-0068: rtc core: registered m41t81 as rtc0
[    8.706393] TCP cubic registered
[    8.709629] NET: Registered protocol family 17
[    8.714154] Registering the dns_resolver key type
[    8.718928] VFP support v0.3: not present
[    8.724171] registered taskstats version 1
[    8.729563] rtc-m41t80 0-0068: setting system clock to 2012-01-06 23:58:54 UTC (1325894334)
[    8.738090] Initializing network drop monitor service
[    9.132301] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    9.152562] ata1.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
[    9.158569] ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    9.182567] ata1.00: configured for UDMA/133
[    9.187605] scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG HD501LJ  CR10 PQ: 0 ANSI: 5
[    9.542289] ata2: SATA link down (SStatus 0 SControl 300)
[    9.548072] VFS: Cannot open root device "sda1" or unknown-block(0,0)
[    9.554551] Please append a correct "root=" boot option; here are the available partitions:
[    9.562930] 1f00             256 mtdblock0  (driver?)
[    9.567989] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    9.576310] [<c0017c20>] (unwind_backtrace+0x0/0xe0) from [<c031d124>] (panic+0x50/0x194)
[    9.584544] [<c031d124>] (panic+0x50/0x194) from [<c045dbe8>] (mount_block_root+0x234/0x284)
[    9.593041] [<c045dbe8>] (mount_block_root+0x234/0x284) from [<c045ddc4>] (prepare_namespace+0x128/0x188)
[    9.602655] [<c045ddc4>] (prepare_namespace+0x128/0x188) from [<c045d880>] (kernel_init+0x100/0x130)
[    9.611813] [<c045d880>] (kernel_init+0x100/0x130) from [<c0012ff8>] (kernel_thread_exit+0x0/0x8)
Re: uBoot on Maxtor MSS2
January 07, 2012 01:08PM
Sorry i have made it too work now.
Re: uBoot on Maxtor MSS2
March 25, 2012 04:39AM
Hi

i have a mssii and i would like to install debian on my mssii. Can i get your kernel your rootfs and a small howto for the installation.

Florian
Re: uBoot on Maxtor MSS2
April 03, 2012 01:38PM
I've managed to boot Arch Linux ARM on the MSS2 - it should be a similar way with every ARM (orion) enabled distribution.

First you need a serial cable (3,3V !!) to see what is going on - a Nokia DKU-5 for example (4pin header beside the Marvell chip and the SATA header) - I connected the wires from my cable in direction from the Marvell chip to the border of the pcb as following:

white / blue / green / none


Next - the partition with the kernel must not be formatted with ext2 on an actual linux distribution - the uboot installed on the mss2 won't read this - maybe this has something to do with the inode size? ( ... http://lists.denx.de/pipermail/u-boot/2009-March/049766.html )


I do the following:

* copied the partition table and enough bytes for the complete first partition from the original disk to another one (same size - 320gb in my case)

* after this I deleted all partitions except the first one
* created a second one with a size of 4GB

* this second partition was formatted with mkfs.ext2

* mounted the second partition to /example

* mkdir /example/boot

* mounted the first partition to /example/boot

* deleted everything (use rm - not format!) in /example/boot (the complete old linux system from maxtor was located here)

* decompressed the Arch Linux ARM rootfs in /example

* chrooted to /example (from now it has to be a ARM-Box - no x86)

* installed the linux-orion kernel package (http://archlinuxarm.org/forum/viewtopic.php?f=27&t=1400&p=8110&hilit=maxtor#p8110) - add the repo to pacman / install devio / install linux-orion (choose the right device!) + linux-headers-orion


Now the disk is bootable from the MSS2 - but only with editing some variables on every boot time - and this is my problem for now ... (I will open a new thread for this problem).
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: