[U-Boot] problem running u-boot from RAM

I'm encountering a strange problem trying to run recent versions of u-boot from RAM on my DockStar.
I have version 2011.03 in NAND flash, and it boots OK and launches Linux OK. But if I use it to load u-boot.bin into RAM (at TEXT_BASE = 0x600000) and type "go 600000", it hangs soon after the relocation step. I've checked using crc32 that the image is correct in RAM, and I've used both tftpboot and fatload, with identical results.
But here's the strange part: if I use openocd to load the same image to the same location using JTAG, and do "resume 0x600000", it works correctly.
I'm not sure what the difference could be. Does anyone have any ideas? It's a lot more convenient to use TFTP to test out new images than JTAG, so I'd like to get this working.

Dear Eric Cooper,
In message 20110417014436.GD847@localhost you wrote:
I'm encountering a strange problem trying to run recent versions of u-boot from RAM on my DockStar.
http://www.denx.de/wiki/view/DULG/CanUBootBeConfiguredSuchThatItCanBeStarted...
Best regards,
Wolfgang Denk

On Sun, Apr 17, 2011 at 09:42:31AM +0200, Wolfgang Denk wrote:
http://www.denx.de/wiki/view/DULG/CanUBootBeConfiguredSuchThatItCanBeStarted...
OK, thanks. But I'd still like to figure out why it works fine when loaded into RAM via JTAG, after u-boot has already initialized the machine in the same way.
Cheers, Eric

Dear Eric Cooper,
In message 20110417143410.GA12566@localhost you wrote:
On Sun, Apr 17, 2011 at 09:42:31AM +0200, Wolfgang Denk wrote:
http://www.denx.de/wiki/view/DULG/CanUBootBeConfiguredSuchThatItCanBeStarted...
OK, thanks. But I'd still like to figure out why it works fine when loaded into RAM via JTAG, after u-boot has already initialized the machine in the same way.
Please re-read the FAQ. Your mistake is most probably in the "in the same way" part of your sentence.
Best regards,
Wolfgang Denk
participants (2)
-
Eric Cooper
-
Wolfgang Denk