Dear Martin,

please keep the ML on Cc:.

In message 001201c92a17$ee1381c0$4201a8c0@amil you wrote:

...

Is there by chance any watchdog on your system that mith have such a timeout / reset period?

...

Thank you for your quick reply. U-Boot appears to work properly apart from the "loop" command. I have not run Linux, but different versions of my application will normally fail in a similar way to what happens when using the loop command (but after different periods of time i.e 0 to 30 seconds).

If I type loop .b <SDRAM address> or loop .b <internal SRAM address> U-boot, after about 20 seconds, produces the dump copied below.

However if I type loop .b <Flash memory address> e.g. loop . 40000 the code appears to go into an infinate loop.

Would a dump be produced if the loop command was terminated by a watchdog?

No, not as you describe.

I think there are two likely reasons for your problem remaining: (1) incorrect initialization of your RAM (see FAQ # 1), and (2) a hardware problem.

Best regards,

Wolfgang Denk