Wolfgang Denk <wd <at> denx.de> writes:
The ramdisk was recognized correctly. It's the content that did not match.
U-Boot has nothing to do with that.
I can see that my ramdisk was improperly made before, but I am still at a loss to understand why if I make a gzipped version of my filesystem, I get to this point:
VFS: Mounted root (ext2 filesystem). Mounted devfs on /dev Freeing unused kernel memory: 44k init
and the board reboots, bringing me back to the u-boot prompt. If I make an uncompressed version, it will boot and even bring me to a Busybox prompt, but if I try to execute an ls command, the board reboots.
This problem even occurs when I try to use the test ramdisk filesystem provided in the Wiki for u-boot; I get to:
VFS: Mounted root (ext2 filesystem). Mounted devfs on /dev Freeing unused kernel memory: 44k init
and the board reboots. I understand that this probably has nothing to do with u-boot, but I do not know where else to turn with this problem. Thank you for any help you can provide or any other list that might have a better handle on what is making the board reboot. Even if there is nothing that you can suggest, I thank you for at least taking the time to help me on my previous post.
Will Haines