[U-Boot-Users] closer to nboot

I'm definitely getting closer so will answer part of my own question, but propose the next one.
The following is working (mostly)
uboot> tftp 0x1000000 uImage (its slightly smaller then 1Mbyte) uboot> nand write.jffs2 0x1000000 0x0 0x1000000 uboot> setenv bootdevice 0 uboot> nboot 0x1000000
At this point, I see:
Loading from NAND 256MiB 3.3V, 8-bit, offset 0x0 Image Name: Linux-2.6.17.11 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 937470 Bytes Load Address: 00000000 Entry Point: 00000000
And then I get the uboot prompt back.
I had thought that giving the address to the nboot command would get me a bit further, but apparently not. Also, I should note that I dont have mtdids or mtdparts defined at this stage. My assumption is that we are doing a raw write and read from the flash and that the .jffs2 argument just deals with the oob (out-of-band) bytes in a jffs2 manner.
Charles

In message A590D28B5042C041BCC880094CB6172E33DC68@mail1irv.inside.istor.com you wrote:
uboot> nboot 0x1000000
At this point, I see:
Loading from NAND 256MiB 3.3V, 8-bit, offset 0x0 Image Name: Linux-2.6.17.11 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 937470 Bytes Load Address: 00000000 Entry Point: 00000000
And then I get the uboot prompt back.
Looks goot to me (I guess "autostart" is not set to "yes", right?).
So what does "imi" show after this? A valid image, right?
I had thought that giving the address to the nboot command would get me a bit further, but apparently not. Also, I should note that I
You got all you asked for. What else did you expect?
[Please restrict your line leght to 70 characters or so when posting here.]
Best regards,
Wolfgang Denk
participants (2)
-
Charles Krinke
-
Wolfgang Denk