From: Jonathan R. <jer...@ya...> - 2008-06-18 15:41:31
|
Hello - The script that I used to develop my product doesn't work on the latest connex boards that I bought. I keep getting the error "bad magic number" when I try to boot. I am using uBoot 1.2.0, and Linux Kernel 2.6.15gum. I followed both the connex and verdex instructions, but nothing works. When I follow the connex upload methodology, it will boot the first I upload the image, but will give me the "bad magic number" error on subsequent boots. Has anyone ever heard of this problem? Thanks, Jonathan |
From: Dave H. <dhy...@gm...> - 2008-06-18 17:41:49
|
Hi Jonathan, > The script that I used to develop my product doesn't work on the latest connex boards that I bought. I keep getting > the error "bad magic number" when I try to boot. I am using uBoot > 1.2.0, and Linux Kernel 2.6.15gum. I followed both the connex and verdex > instructions, but nothing works. When I follow the connex upload methodology, it will boot the first I upload the image, but will give me the "bad magic number" error on subsequent boots. Has anyone ever heard of this problem? This is typically caused by a mismatch of some type between the bootloader and the type of image being used. The newer bootloaders use the katload command, which expects the kernel to be in the upper megabyte of flash (and installed using the katinstall command). IIRC 2.6.15 would be using the kernel located in the file system, which means you'd need to use fsload, rather than katload. So try doing the following in uBoot: setenv bootcmd "icache on; fsload &&bootm" You may also need to change the root= portion of bootargs: setenv bootargs "console=ttyS0 root=1f01 rootfstype=jffs2 reboot=cold,hard" You can test it by just setting the bootargs, and manually entering the command: icache on; fsload &&bootm If it works, then you can do it again, but use saveenv to make the changes permanent (after setting bootargs and bootcmd) -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |