In message 1096646639.10111.115.camel@mhpajh5c you wrote:
Today I was working on it and loaded a linux kernel image. When I 'loads' it, using the u-boot command line, into ram, the 'md' command at the loaded area shows
00010000: 27051956 d3232bea 415d1e66 0005ba2c '..V.#+.A].f..., 00010010: 7d8c5a14 3940ffff 914c0000 3bffffe0 }.Z.9@...L..;... 00010020: 4c696e75 782d322e 342e3138 00000000 Linux-2.4.18.... 00010030: 00000000 00000000 00000000 00000000 ................
while objdump shows
00000 27051956 d3232bea 415d1e66 0005ba2c '..V.#+.A].f..., 00010 00000000 00000000 82847f95 05070201 ................ 00020 4c696e75 782d322e 342e3138 00000000 Linux-2.4.18....
What's the result of "imi 00010000" on the target and "mkimage -l <your_image_file>" on the ost? I guess that "imi" reports a checksum error?
I've spoken with the board developer (who also wrote a bootloader for the board) and showed him the sdram initialization function, and he said it was correct. However, I've got the behavior shown above. Is there another reason why this sort of corruption would happen? (btw, using 'cu' to download the image into RAM).
There can be many reasons, ranging from a broken serial port on your host to RAM errors.
Best regards,
Wolfgang Denk