Before I jump in with the BDI and start debugging, has anyone else using
'nboot' and FIT images noticed that 'nboot' periodically fails where 'nand
read.i' of the SAME region of NAND succeeds?
=> echo $bootaddr
800000
=> echo $boot0
nboot ${bootaddr} 0 0 && setenv bootargs root=/dev/mtdblock9 && run
addjffs2 addtty && bootm ${bootaddr}
=> run boot0
Loading from NAND 64MiB 3,3V 8-bit, offset 0x0
** Bad FIT image format
=> nand read.i ${bootaddr} 0 400000
NAND read: device 0 offset 0x0, size 0x400000
Reading data from 0x3ffe00 -- 100% complete.
4194304 bytes read: OK
=> setenv bootargs root=/dev/mtdblock9
=> run addjffs2 addtty
=> bootm ${bootaddr}
## Booting kernel from FIT Image at 00800000 ...
Using '[EMAIL PROTECTED]' configuration
Trying '[EMAIL PROTECTED]' kernel subimage
...
Using Haleakala machine description
Linux version 2.6.25-rc3-00951-g6514352-dirty ([EMAIL PROTECTED])
(gcc version 4.0.0 (DENX ELDK 4.1 4.0.0)) #2 Wed May 28 22:49:36 PDT 2008
Zone PFN ranges:
DMA 0 -> 65536
Normal 65536 -> 65536
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
...
This is using AMCC's Haleakala board with Samsung K9F1208U0B NAND, though I
suspect that doesn't make any difference since nand read.i works fine.
Regards,
Grant
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users
