Re: Loading kernel issues
I thought that, by default, the NOR bootloader was setting it's config files in NOR as well. But it seems that both bootloader are getting the same config file. I will switch to NOR, short the two right data lines, short them, start the mini board. And at that point I will change back the /env/config file. After that will re build barebox with that lines you told me, commented out. And re flash barebox to NOR! Thank you very much guys, will tell you my advance. 2016-10-21 10:07 GMT+02:00 Sascha Hauer : > On Fri, Oct 21, 2016 at 09:53:45AM +0200, Juergen Borleis wrote: >> Hi Javier, >> >> On Friday 21 October 2016 09:41:15 Javier Fileiv wrote: >> > I was looking to buy an ARM9 Jtag because it's what I >> > though... I would need a JTAG. >> > >> > Regarding shorting the data lines... do you know exactly what would I >> > need to do? >> >> Reading the datasheet of the used NAND device, find its datalines, find them >> on >> the Mini2440, configure the board to boot from NOR, short two of the eight >> datalines and power the board. > > The best would be to find two which are exactly next to each other so > you can short circuit them with a knitting needle or similar. > > When you flash a new barebox to NOR flash make sure you flash one that > doesn't get its environment from NAND, so comment out the following > lines in the board file: > > devfs_del_partition("env_raw"); > devfs_add_partition("nand0", 0x4, 0x2, DEVFS_PARTITION_FIXED, > "env_raw"); > dev_add_bb_dev("env_raw", "env0"); > > Sascha > > -- > Pengutronix e.K. | | > Industrial Linux Solutions | http://www.pengutronix.de/ | > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Loading kernel issues
On Fri, Oct 21, 2016 at 09:53:45AM +0200, Juergen Borleis wrote: > Hi Javier, > > On Friday 21 October 2016 09:41:15 Javier Fileiv wrote: > > I was looking to buy an ARM9 Jtag because it's what I > > though... I would need a JTAG. > > > > Regarding shorting the data lines... do you know exactly what would I > > need to do? > > Reading the datasheet of the used NAND device, find its datalines, find them > on > the Mini2440, configure the board to boot from NOR, short two of the eight > datalines and power the board. The best would be to find two which are exactly next to each other so you can short circuit them with a knitting needle or similar. When you flash a new barebox to NOR flash make sure you flash one that doesn't get its environment from NAND, so comment out the following lines in the board file: devfs_del_partition("env_raw"); devfs_add_partition("nand0", 0x4, 0x2, DEVFS_PARTITION_FIXED, "env_raw"); dev_add_bb_dev("env_raw", "env0"); Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Loading kernel issues
Hi Javier, On Friday 21 October 2016 09:54:04 Javier Fileiv wrote: > shoul I short them between them, short them to GND or > short them to VDD? "short two of them" means between them. D2 and D3 for example... Cheers, Juergen -- Pengutronix e.K. | Juergen Borleis | Industrial Linux Solutions | http://www.pengutronix.de/ | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Loading kernel issues
On 10/21/2016 09:54 AM, Javier Fileiv wrote: Thanks Juergen, shoul I short them between them, short them to GND or short them to VDD? Short them together. Does not care if they are tied to GND or VCC, the results are surely invalid. ;-) Best regards, -- Eurek s.r.l. | Electronic Engineering| http://www.eurek.it via Celletta 8/B, 40026 Imola, Italy | Phone: +39-(0)542-609120 p.iva 00690621206 - c.f. 04020030377 | Fax: +39-(0)542-609212 ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Loading kernel issues
Thanks Juergen, shoul I short them between them, short them to GND or short them to VDD? Thank you again 2016-10-21 9:53 GMT+02:00 Juergen Borleis : > Hi Javier, > > On Friday 21 October 2016 09:41:15 Javier Fileiv wrote: >> I was looking to buy an ARM9 Jtag because it's what I >> though... I would need a JTAG. >> >> Regarding shorting the data lines... do you know exactly what would I >> need to do? > > Reading the datasheet of the used NAND device, find its datalines, find them > on > the Mini2440, configure the board to boot from NOR, short two of the eight > datalines and power the board. > >> Regarding JTAG, which ones are the steps? > > Sorry, no idea. Never used it on Mini2440. > > Cheers, > Juergen > > -- > Pengutronix e.K. | Juergen Borleis | > Industrial Linux Solutions| http://www.pengutronix.de/ | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Loading kernel issues
Hi Javier, On Friday 21 October 2016 09:41:15 Javier Fileiv wrote: > I was looking to buy an ARM9 Jtag because it's what I > though... I would need a JTAG. > > Regarding shorting the data lines... do you know exactly what would I > need to do? Reading the datasheet of the used NAND device, find its datalines, find them on the Mini2440, configure the board to boot from NOR, short two of the eight datalines and power the board. > Regarding JTAG, which ones are the steps? Sorry, no idea. Never used it on Mini2440. Cheers, Juergen -- Pengutronix e.K. | Juergen Borleis | Industrial Linux Solutions | http://www.pengutronix.de/ | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Loading kernel issues
Hello Juerguen, I was looking to buy an ARM9 Jtag because it's what I though... I would need a JTAG. Regarding shorting the data lines... do you know exactly what would I need to do? Regarding JTAG, which ones are the steps? Thank you so much 2016-10-21 9:39 GMT+02:00 Juergen Borleis : > Hi Javier, > > On Thursday 20 October 2016 19:59:54 Javier Fileiv wrote: >> ups... I think Ive broken everything... I just put at the end of the >> env/config file "boot nand" and now is looping and at some point it >> says "ERROR: out of memory". >> Another thing... I changed vivibootloader in NOR for the barebox, and >> even if I change to NOR it's looping again and again... What do I do? >> HELP! > > Seems you configured your board into a brick. You now can boot from NOR and > short some data lines pins at the NAND device to make barebox fail to read its > environment from NAND and fall back to the built-in default environment > without that loop. > Or you need some JTAG equipment to make the SoC working again. > > Cheers, > Juergen > > -- > Pengutronix e.K. | Juergen Borleis | > Industrial Linux Solutions| http://www.pengutronix.de/ | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Loading kernel issues
Hi Javier, On Thursday 20 October 2016 19:59:54 Javier Fileiv wrote: > ups... I think Ive broken everything... I just put at the end of the > env/config file "boot nand" and now is looping and at some point it > says "ERROR: out of memory". > Another thing... I changed vivibootloader in NOR for the barebox, and > even if I change to NOR it's looping again and again... What do I do? > HELP! Seems you configured your board into a brick. You now can boot from NOR and short some data lines pins at the NAND device to make barebox fail to read its environment from NAND and fall back to the built-in default environment without that loop. Or you need some JTAG equipment to make the SoC working again. Cheers, Juergen -- Pengutronix e.K. | Juergen Borleis | Industrial Linux Solutions | http://www.pengutronix.de/ | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Loading kernel issues
ups... I think Ive broken everything... I just put at the end of the env/config file "boot nand" and now is looping and at some point it says "ERROR: out of memory". Another thing... I changed vivibootloader in NOR for the barebox, and even if I change to NOR it's looping again and again... What do I do? HELP! 2016-10-20 11:17 GMT+02:00 Javier Fileiv : > Thank you very much maybe I just to put on /env/config a "boot nand" > line... > > I'll try it. > > Regards > > 2016-10-20 11:13 GMT+02:00 Juergen Borleis : >> Hi Javier, >> >> On Wednesday 19 October 2016 20:18:38 Javier Fileiv wrote: >>> just in case...my /env/config as well >>> [...] >> >> Sorry, no idea. I do not even have the hardware anymore, so I cannot test it. >> >> Keep a look into the "env/bin/boot" script, what it tries to do with the >> configuration from your "env/config". Maybe it could help you to make it work >> again. >> >> Cheers, >> Juergen >> >> -- >> Pengutronix e.K. | Juergen Borleis | >> Industrial Linux Solutions| http://www.pengutronix.de/ | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Loading kernel issues
Thank you very much maybe I just to put on /env/config a "boot nand" line... I'll try it. Regards 2016-10-20 11:13 GMT+02:00 Juergen Borleis : > Hi Javier, > > On Wednesday 19 October 2016 20:18:38 Javier Fileiv wrote: >> just in case...my /env/config as well >> [...] > > Sorry, no idea. I do not even have the hardware anymore, so I cannot test it. > > Keep a look into the "env/bin/boot" script, what it tries to do with the > configuration from your "env/config". Maybe it could help you to make it work > again. > > Cheers, > Juergen > > -- > Pengutronix e.K. | Juergen Borleis | > Industrial Linux Solutions| http://www.pengutronix.de/ | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Loading kernel issues
Hi Javier, On Wednesday 19 October 2016 20:18:38 Javier Fileiv wrote: > just in case...my /env/config as well > [...] Sorry, no idea. I do not even have the hardware anymore, so I cannot test it. Keep a look into the "env/bin/boot" script, what it tries to do with the configuration from your "env/config". Maybe it could help you to make it work again. Cheers, Juergen -- Pengutronix e.K. | Juergen Borleis | Industrial Linux Solutions | http://www.pengutronix.de/ | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Loading kernel issues
just in case...my /env/config as well mini2440:/ cat /env/config #!/bin/sh machine=mini2440 user= # use 'dhcp' to do dhcp in barebox and in kernel # use 'none' if you want to skip kernel ip autoconfiguration ip=dhcp # or set your networking parameters here #eth0.ipaddr=a.b.c.d #eth0.netmask=a.b.c.d #eth0.gateway=a.b.c.d eth0.serverip=192.168.0.10 #eth0.ethaddr=a:b:b:d:e:f # autoboot settings # can be either 'tftp', 'nfs', 'nand' or 'mmc' kernel_loc=nand # can be either 'net', 'nand', 'initrd' or 'mmc' rootfs_loc=nand # can be either 'jffs2' or 'ubifs' for flash or 'ext3' for mmc rootfs_type=jffs2 rootfsimage=root-${machine}.${rootfs_type} # The image type of the kernel. Can be uimage, zimage, raw, or raw_lzo #kernelimage_type=zimage #kernelimage=zImage-${machine} kernelimage_type=uimage kernelimage=uImage-$machine #kernelimage_type=raw #kernelimage=Image-$machine #kernelimage_type=raw_lzo #kernelimage=Image-$machine.lzo # the name of the barebox image used by the update script bareboximage=barebox-$machine # the name of the barebox default environment used by the update script bareboxenvimage=barebox-environment-$machine if [ -n $user ]; then kernelimage="${user}"-"${kernelimage}" nfsroot="${eth0.serverip}:/home/${user}/nfsroot/${machine}" rootfsimage="${user}"-"${rootfsimage}" else nfsroot="/path/to/nfs/root" fi autoboot_timeout=3 if [ -e /dev/nor0 ]; then nor_parts="512k(barebox)" # Skip autoboot if not booting from NAND autoboot_disable=1 fi # # "mini2440" kernel parameter # 0 .. 9 = screen type # b = backlight enabled # t = touch enabled # c = camera enabled # Note: can be "mini2440= " if nothing of these components are connected # bootargs="console=ttySAC0,115200 mini2440=0tbc rootdelay=5" # NAND boot settings # Device name used by the kernel nand_device="nand" # partition definition in the NAND nand_parts="512k(barebox),384k(bareboxenv),2048k(kernel),-(root)" # rootfs's partition number in the NAND rootfs_mtdblock_nand=3 # used when manually booting with "boot nand" command rootfs_mtdblock_type=jffs2 # MMC/SD boot settings # partition number to read the kernel from # (starting with # 0, Barebox's counting scheme) kernel_mmc_part=0 # rootfs's partition number # (starting with # 1, Kernel's counting scheme) rootfs_mmc_part=2 # used when manually booting with "boot mmc" command rootfs_mmc_type=ext2 2016-10-19 20:17 GMT+02:00 Javier Fileiv : > Hello Juergen, > > Here is my power up output, thanks you very much > > Terminal ready > > > barebox 2011.05.0-ptx-2014.11.0 (Oct 13 2016 - 21:53:08) > > Board: Mini 2440 > NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V > 8-bit) > Bad block table found at page 524224, version 0x01 > Bad block table found at page 524160, version 0x01 > nand_read_bbt: Bad block at 0x255a > dm9000 i/o: 0x2300, id: 0x9a46 > eth@eth0: got MAC address from EEPROM: 00:00:00:00:00:00 > cfi_probe: cfi_flash base: 0x size: 0x0020 > ## Unknown FLASH on Bank at 0x - Size = 0x = 0 MB > refclk:12000 kHz > mpll: 405000 kHz > upll: 48000 kHz > fclk: 405000 kHz > hclk: 101250 kHz > pclk: 50625 kHz > SDRAM1: CL2@101MHz > Malloc space: 0x33a0 -> 0x33e0 (size 4 MB) > Stack space : 0x339f8000 -> 0x33a0 (size 32 kB) > running /env/bin/init... > > 2016-10-19 9:53 GMT+02:00 Juergen Borleis : >> Hi Javier, >> >> On Tuesday 18 October 2016 18:56:03 Javier Fileiv wrote: >>> Trying to autoboot from nand, I set my /env/config file like that (and >>> after that a "saveenv"). Although it doesn't work automaGically! :) >> >> Can you also send the output of barebox from power on up to the point it >> falls >> into the prompt? >> >> Cheers, >> Juergen >> >> -- >> Pengutronix e.K. | Juergen Borleis | >> Industrial Linux Solutions| http://www.pengutronix.de/ | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Loading kernel issues
Hello Juergen, Here is my power up output, thanks you very much Terminal ready barebox 2011.05.0-ptx-2014.11.0 (Oct 13 2016 - 21:53:08) Board: Mini 2440 NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit) Bad block table found at page 524224, version 0x01 Bad block table found at page 524160, version 0x01 nand_read_bbt: Bad block at 0x255a dm9000 i/o: 0x2300, id: 0x9a46 eth@eth0: got MAC address from EEPROM: 00:00:00:00:00:00 cfi_probe: cfi_flash base: 0x size: 0x0020 ## Unknown FLASH on Bank at 0x - Size = 0x = 0 MB refclk:12000 kHz mpll: 405000 kHz upll: 48000 kHz fclk: 405000 kHz hclk: 101250 kHz pclk: 50625 kHz SDRAM1: CL2@101MHz Malloc space: 0x33a0 -> 0x33e0 (size 4 MB) Stack space : 0x339f8000 -> 0x33a0 (size 32 kB) running /env/bin/init... 2016-10-19 9:53 GMT+02:00 Juergen Borleis : > Hi Javier, > > On Tuesday 18 October 2016 18:56:03 Javier Fileiv wrote: >> Trying to autoboot from nand, I set my /env/config file like that (and >> after that a "saveenv"). Although it doesn't work automaGically! :) > > Can you also send the output of barebox from power on up to the point it falls > into the prompt? > > Cheers, > Juergen > > -- > Pengutronix e.K. | Juergen Borleis | > Industrial Linux Solutions| http://www.pengutronix.de/ | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Loading kernel issues
Hi Javier, On Tuesday 18 October 2016 18:56:03 Javier Fileiv wrote: > Trying to autoboot from nand, I set my /env/config file like that (and > after that a "saveenv"). Although it doesn't work automaGically! :) Can you also send the output of barebox from power on up to the point it falls into the prompt? Cheers, Juergen -- Pengutronix e.K. | Juergen Borleis | Industrial Linux Solutions | http://www.pengutronix.de/ | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Loading kernel issues
Hi all! Trying to autoboot from nand, I set my /env/config file like that (and after that a "saveenv"). Although it doesn't work automaGically! :) What do you think about this guys? Thanks a lot! (I'm gonna try the nfs mounting right now!) mini2440:/ cat env/config #!/bin/sh machine=mini2440 user= # use 'dhcp' to do dhcp in barebox and in kernel # use 'none' if you want to skip kernel ip autoconfiguration ip=dhcp # or set your networking parameters here #eth0.ipaddr=a.b.c.d #eth0.netmask=a.b.c.d #eth0.gateway=a.b.c.d eth0.serverip=192.168.0.10 #eth0.ethaddr=a:b:b:d:e:f # autoboot settings # can be either 'tftp', 'nfs', 'nand' or 'mmc' kernel_loc=nand # can be either 'net', 'nand', 'initrd' or 'mmc' rootfs_loc=nand # can be either 'jffs2' or 'ubifs' for flash or 'ext3' for mmc rootfs_type=jffs2 rootfsimage=root-${machine}.${rootfs_type} # The image type of the kernel. Can be uimage, zimage, raw, or raw_lzo #kernelimage_type=zimage #kernelimage=zImage-${machine} kernelimage_type=uimage kernelimage=uImage-$machine #kernelimage_type=raw #kernelimage=Image-$machine #kernelimage_type=raw_lzo #kernelimage=Image-$machine.lzo # the name of the barebox image used by the update script bareboximage=barebox-$machine # the name of the barebox default environment used by the update script bareboxenvimage=barebox-environment-$machine if [ -n $user ]; then kernelimage="${user}"-"${kernelimage}" nfsroot="${eth0.serverip}:/home/${user}/nfsroot/${machine}" rootfsimage="${user}"-"${rootfsimage}" else nfsroot="/path/to/nfs/root" fi autoboot_timeout=3 if [ -e /dev/nor0 ]; then nor_parts="512k(barebox)" # Skip autoboot if not booting from NAND autoboot_disable=1 fi # # "mini2440" kernel parameter # 0 .. 9 = screen type # b = backlight enabled # t = touch enabled # c = camera enabled # Note: can be "mini2440= " if nothing of these components are connected # bootargs="console=ttySAC0,115200 mini2440=0tbc rootdelay=5" # NAND boot settings # Device name used by the kernel nand_device="nand" # partition definition in the NAND nand_parts="512k(barebox),384k(bareboxenv),2048k(kernel),-(root)" # rootfs's partition number in the NAND rootfs_mtdblock_nand=3 # used when manually booting with "boot nand" command rootfs_mtdblock_type=jffs2 # MMC/SD boot settings # partition number to read the kernel from # (starting with # 0, Barebox's counting scheme) kernel_mmc_part=0 # rootfs's partition number # (starting with # 1, Kernel's counting scheme) rootfs_mmc_part=2 # used when manually booting with "boot mmc" command rootfs_mmc_type=ext2 2016-10-18 10:24 GMT+02:00 Javier Fileiv : > Yes I did it and the values are ok. When I get home I'll send my config file! > > Thanks > > 2016-10-18 10:17 GMT+02:00 Juergen Borleis : >> Hi Javier, >> >> On Sunday 16 October 2016 23:06:15 Javier Fileiv wrote: >>> I've just flashed barebox on my Mini2440. I have 2 questions/issues now >>> >>> 1) When trying to load the kernel from TFTP, everything is ok but when >>> it's trying to mount the rootfs something is not working, even though >>> I set the rootdelay param to 5 secs. >>> >>> 2) I tried also the boot from nand and is working just fine, but there >>> no is auto boot when reseting the board... it just give me the barebox >>> prompt each time, and if i run from there boot nand it works OK, but >>> no automaGically. :) >> >> Did you modify the "/env/config"[1] file to define the default boot source? >> >> Cheers, >> Juergen >> >> [1] "kernel_loc" and "rootfs_loc" >> >> -- >> Pengutronix e.K. | Juergen Borleis | >> Industrial Linux Solutions| http://www.pengutronix.de/ | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Loading kernel issues
Yes I did it and the values are ok. When I get home I'll send my config file! Thanks 2016-10-18 10:17 GMT+02:00 Juergen Borleis : > Hi Javier, > > On Sunday 16 October 2016 23:06:15 Javier Fileiv wrote: >> I've just flashed barebox on my Mini2440. I have 2 questions/issues now >> >> 1) When trying to load the kernel from TFTP, everything is ok but when >> it's trying to mount the rootfs something is not working, even though >> I set the rootdelay param to 5 secs. >> >> 2) I tried also the boot from nand and is working just fine, but there >> no is auto boot when reseting the board... it just give me the barebox >> prompt each time, and if i run from there boot nand it works OK, but >> no automaGically. :) > > Did you modify the "/env/config"[1] file to define the default boot source? > > Cheers, > Juergen > > [1] "kernel_loc" and "rootfs_loc" > > -- > Pengutronix e.K. | Juergen Borleis | > Industrial Linux Solutions| http://www.pengutronix.de/ | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Loading kernel issues
Hi Javier, On Sunday 16 October 2016 23:06:15 Javier Fileiv wrote: > I've just flashed barebox on my Mini2440. I have 2 questions/issues now > > 1) When trying to load the kernel from TFTP, everything is ok but when > it's trying to mount the rootfs something is not working, even though > I set the rootdelay param to 5 secs. > > 2) I tried also the boot from nand and is working just fine, but there > no is auto boot when reseting the board... it just give me the barebox > prompt each time, and if i run from there boot nand it works OK, but > no automaGically. :) Did you modify the "/env/config"[1] file to define the default boot source? Cheers, Juergen [1] "kernel_loc" and "rootfs_loc" -- Pengutronix e.K. | Juergen Borleis | Industrial Linux Solutions | http://www.pengutronix.de/ | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Loading kernel issues
Hi Javier, On Sun, Oct 16, 2016 at 11:06:15PM +0200, Javier Fileiv wrote: > Hi everyone, I've just flashed barebox on my Mini2440. I have 2 > questions/issues now > > 1) When trying to load the kernel from TFTP, everything is ok but when > it's trying to mount the rootfs something is not working, even though > I set the rootdelay param to 5 secs. > > 2) I tried also the boot from nand and is working just fine, but there > no is auto boot when reseting the board... it just give me the barebox > prompt each time, and if i run from there boot nand it works OK, but > no automaGically. :) > > Any suggestions? Thank you very much > > > LOG FOR TFTP BOOT: > > mini2440:/ boot tftp > warning: No MAC address set. Using random address A2:50:1F:24:DF:AB > phy0: Link is up - 100/Full > T DHCP client bound to address 192.168.0.15 > TFTP from server 192.168.0.10 ('uImage-mini2440' -> '/dev/ram0.kernel') > # > # > # > # > # > > booting kernel of type uimage from /dev/ram0.kernel >Verifying Checksum ... OK >Image Name: Linux-3.16.7-ptx-master >Created: 2016-10-13 20:23:14 UTC >Image Type: () >Data Size:1910288 Bytes = 1.8 MB >Load Address: 30008000 >Entry Point: 30008000 > OK > commandline: console=ttySAC0,115200 mini2440=0tbc rootdelay=5 ip=dhcp > root=/dev/nfs nfsroot=/path/to/nfs/root,v3,tcp noinitrd You have to replace nfsroot=/path/to/nfs/root with some valid path. Since your dhcp server does not pass a root server ip you'll have to add that aswell, so your nfsroot should look like nfsroot=192.168.x.y:/path/to/nfsroot. Try 'edit /env/config' to edit the parameter to your needs. Do not forget saveenv afterwards. To boot from Nand also edit /env/config and adjust the kernel_loc and rootfs_loc variables. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox