[ARMedslack] Hello

[Davide]

Ok this is what I did:
partitioned a usb stick with 50Mb fat (first partition)
and the rest linux
made fat 32 filesystem on first partition and copied kirkwood kernel and initrd there
formatted second partition with ext2 and extracted miniroot to it
edited fstab to reflect the work I did with partitioning

then i but the stick in the dosckstar and boot to second uboot:
Marvell>> setenv x_bootcmd_kernel 'fatload usb 0:1 0x6400000 uImage'
Marvell>> setenv x_bootargs_root 'root=/dev/sda1 ro rootfstype=ext2'
Marvell>> printenv
bootcmd=${x_bootcmd_kernel}; setenv bootargs ${x_bootargs} ${x_bootargs_root}; ;
bootdelay=3
baudrate=115200
ipaddr=169.254.254.243
serverip=169.254.254.254
x_bootargs=console=ttyS0,115200 mtdparts=orion_nand:1M(u-boot),1M at 1M(second_staw
x_bootcmd_usb=usb start
stdin=serial
stdout=serial
stderr=serial
ethaddr=02:50:43:dd:a3:c7
ethact=egiga0
filesize=1FFE8C
x_bootcmd_kernel=fatload usb 0:1 0x6400000 uImage
x_bootargs_root=root=/dev/sda1 ro rootfstype=ext2

Environment size: 548/131068 bytes
Marvell>> boot
reading uImage
Invalid FAT entry

2096780 bytes read
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
## Booting kernel from Legacy Image at 06400000 ...
   Image Name:   Linux-2.6.33.5-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2096716 Bytes = 2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

That's the last line produced by the loaded kernel while booting.
I suspect that it's not correctly logging to serial console and that it's also in kernel panic dew to not mounting root.

One other thing: how do I get uboot to tell kernel to load initrd ?

Regards
David

--- Mer 16/3/11, Thorsten Mühlfelder <thenktor at gmx.de> ha scritto:

> Da: Thorsten Mühlfelder <thenktor at gmx.de>
> Oggetto: Re: [ARMedslack] Hello
> A: "Slackware ARM port" <armedslack at lists.armedslack.org>
> Data: Mercoledì 16 marzo 2011, 14:29
> Am Wednesday 16 March 2011 13:45:53
> schrieb Davide:
> > > Yes, that's possible. AFAIK you just have to
> place the
> > > second u-boot to the
> > > NAND address where originally the kernel can be
> found. If
> > > it fails to load
> > > the second u-boot the first u-boot must be able
> to boot
> > > from usb to recover
> > > things. Otherwise without JTAG you are stuck,
> too.
> >
> > Not really: you can use uboot to write to load via
> tftp and write to nand:
> > That's how I recovered from my dockstar invalid kernel
> CRC.
> > For anyone intrested insructions are quite clear on
> this on openwrt serial
> > console install.
> 
> Yes, forgot about the network method. Of course it has to
> be compiled in, 
> too ;)
> 
> > > IIRC on mikrocontroller.net the layout of the
> JTAG
> > > connector can be found.
> >
> > Yea I saw that but I'd still regard that as being more
> difficult then
> > plying with uboot from serial.
> 
> Indeed. As long as I can play with serial/netconsole and a
> working u-boot I 
> won't try JTAG.
> 
> > > > ext2load- load binary file from a Ext2
> filesystem
> > > > ext2ls  - list files in a directory
> (default /)
> >
> > I tryed that but got nothing. meybe because this uboot
> does not support usb
> > ... but then again where else would the dockstar have
> an ext2 filesystem ?
> > directly on flash without any ware levelling dedicated
> hardware would not
> > be a smart thing to do.
> 
> The included options are only a matter of configuration at
> compile time. And 
> you are right: ext2 support without usb support seems to be
> useless. At least 
> at the moment I canno imagine any useful scenario.
> 
> > I'll play with both uboot and see if I can boot
> armedslack in some way
> > other then using openwrt as an initrd to start
> armedslack. If that fails
> > I'll try jeff's enhanced uboot.
> 
> Some hints:
> Create first partition as fat on usb stick, second
> partition as ext4. The 
> first will be the boot partition and contain your uImage.
> usb start
> ext2load usb 0:1 0x6400000 /uImage
> setenv bootargs root=/dev/sda2 rootfstype=ext4
> run bootcmd
> 
> Something like this...
> 
> 
> -- 
> Thorsten Mühlfelder
> Salix OS: www.salixos.org
> _______________________________________________
> ARMedslack mailing list
> ARMedslack at lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
>