From: Fred H. <bwc...@ya...> - 2004-11-19 13:34:44
|
I have just received my gumstix. Let me see if i have things correct. The Uimage it the kernel and the root_fs_arm is the whole image including all of the whole file system. So believing that is correct i created a new Uimage. Before I permentaly copy it over i want to boot it from the mmc. I have looked through the past posts and found the following: So, what I have done for my own kernel testing is: 1) create a "loadkernel" env variable: setenv loadkernel mmc\; sleep 1\; mmc\; fatload mmc 1 0xa2000000 uimage 2) create a "testkernel" env variable: setenv testkernel run loadkernel\;cp 0x140000 0xa2100000 0x40000\; bootm 0xa2000000 0xa2100000 3) you can check the list of env variables with "printenv" printenv 4) save it to flash save Thereafter, upon reset, you can 1) intervene within the 3 seconds by pressing any key, then 2)type "run testkernel" at the prompt. Which i do and i get errors of the following sort: GUM> printenv bootdelay=2 baudrate=115200 bootargs=console=ttyS0,115200n8 root=1f02 rootfstype=jffs2 reboot=cold,hard bootcmd=fsload a2000000 boot/uImage;bootm a2000000 stdin=serial stdout=serial stderr=serial Environment size: 196/131068 bytes GUM> setenv loadkernel mmc\; sleep 1\; mmc\; fatload mmc 1 0xa2000000 uimage GUM> setenv testkernel run loadkernel\;cp 0x140000 0xa2100000 0x40000\; bootm 0xa2000000 0xa2100000 GUM> run testkernel No MMC card found No MMC card found ** Unable to use mmc 1:1 for fatload ** ## Booting image at a2000000 ... Bad Header Checksum My MMC works fine, when started i can cd to /mnt/mmc and make and creat files and read exsisting files. Also once i get this straightened out am i correct in assuming the easiest way to update kernels is to replace the /boot/Uimage with the new one i have made? Thanks a lot __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com |