From: Kim H. <ki...@ki...> - 2004-07-23 22:03:32
|
After successfully writing a flash image, I cannot boot. I get a bad magic number error: GUM> reset resetting ... ***** Welcome to gumstix! ***** U-Boot 1.0.0 (Feb 12 2004 - 10:58:22) U-Boot code: A3F00000 -> A3F18120 BSS space: -> A3F497F8 DRAM Configuration: Bank #0: a0000000 64 MB Flash: 4 MB In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 ## Booting image at 00040000 ... Bad Magic Number GUM> I've received this error both times. First after installing the image downloaded from source forge. And secondly, when installing the image I compiled myself. This is for an original gumstix. I've both images in the download area and one I've compiled myself. Could this be related to the ram initialization problem? (I'm running Uboot 1.0.0). However inclined to want to get a successful flash of a linux image before erasing and flashing a new uboot image. I've done the following steps: GUM> loadb 0xa2000000 ## Ready for binary (kermit) download to 0xA2000000 at 115200 bps... (Back at machine) ---------------------------------------------------- (/usr/local/src/gumstix/gumstix-buildroot/) C-Kermit>send root_fs_arm (/usr/local/src/gumstix/gumstix-buildroot/) C-Kermit> (/usr/local/src/gumstix/gumstix-buildroot/) C-Kermit> (/usr/local/src/gumstix/gumstix-buildroot/) C-Kermit> (/usr/local/src/gumstix/gumstix-buildroot/) C-Kermit> (/usr/local/src/gumstix/gumstix-buildroot/) C-Kermit> (/usr/local/src/gumstix/gumstix-buildroot/) C-Kermit>bootm ?Not a command or macro name: "bootm" (/usr/local/src/gumstix/gumstix-buildroot/) C-Kermit>connect Connecting to /dev/ttyS0, speed 115200 Escape character: Ctrl-\ (ASCII 28, FS): enabled Type the escape character followed by C to get back, or followed by ? to see other options. ---------------------------------------------------- ## Total Size = 0x001e61c0 = 1991104 Bytes ## Start Addr = 0xA2000000 GUM> GUM> erase 1:2-31 Erase Flash Sectors 2-31 in Bank # 1 Erasing sector 2 ... done Erasing sector 3 ... done Erasing sector 4 ... done Erasing sector 5 ... done Erasing sector 6 ... done Erasing sector 7 ... done Erasing sector 8 ... done Erasing sector 9 ... done Erasing sector 10 ... done Erasing sector 11 ... done Erasing sector 12 ... done Erasing sector 13 ... done Erasing sector 14 ... done Erasing sector 15 ... done Erasing sector 16 ... done Erasing sector 17 ... done Erasing sector 18 ... done Erasing sector 19 ... done Erasing sector 20 ... done Erasing sector 21 ... done Erasing sector 22 ... done Erasing sector 23 ... done Erasing sector 24 ... done Erasing sector 25 ... done Erasing sector 26 ... done Erasing sector 27 ... done Erasing sector 28 ... done Erasing sector 29 ... done Erasing sector 30 ... done Erasing sector 31 ... done GUM> GUM> cp.b 0xa2000000 0x40000 $(filesize) Copy to Flash.../done GUM> GUM> reset resetting ... ***** Welcome to gumstix! ***** U-Boot 1.0.0 (Feb 12 2004 - 10:58:22) U-Boot code: A3F00000 -> A3F18120 BSS space: -> A3F497F8 DRAM Configuration: Bank #0: a0000000 64 MB Flash: 4 MB In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 ## Booting image at 00040000 ... Bad Magic Number GUM> - Kim |
From: Craig H. <cr...@hu...> - 2004-07-23 22:29:24
|
At the u-boot prompt, type set bootcmd fsload a2000000 boot/uImage\;bootm a2000000 set bootargs console=ttyS0,115200n8 root=1f02 rootfstype=jffs2 noinitrd reboot=cold,hard save then reboot -- you should be good now. The problem is that the boot process has changed from the original distribution shipped with the 'stix to the current one in buildroot -- you need to change u-boot's boot script to adjust. the "save" will save it for future boots, so you only need to do it once. C On Jul 23, 2004, at 3:03 PM, Kim Hendrikse wrote: > After successfully writing a flash image, I cannot boot. I get a bad > magic > number error: > > > GUM> reset > resetting ... > > ***** Welcome to gumstix! ***** > > U-Boot 1.0.0 (Feb 12 2004 - 10:58:22) > > U-Boot code: A3F00000 -> A3F18120 > BSS space: -> A3F497F8 > DRAM Configuration: > Bank #0: a0000000 64 MB > Flash: 4 MB > In: serial > Out: serial > Err: serial > Hit any key to stop autoboot: 0 > ## Booting image at 00040000 ... > Bad Magic Number > GUM> > > I've received this error both times. First after installing the image > downloaded from source forge. And secondly, when installing the image > I compiled myself. This is for an original gumstix. I've both > images in the download area and one I've compiled myself. Could this be > related to the ram initialization problem? (I'm running Uboot 1.0.0). > > However inclined to want to get a successful flash of a linux image > before erasing and flashing a new uboot image. > > I've done the following steps: > > GUM> loadb 0xa2000000 > ## Ready for binary (kermit) download to 0xA2000000 at 115200 bps... > > (Back at machine) > ---------------------------------------------------- > (/usr/local/src/gumstix/gumstix-buildroot/) C-Kermit>send root_fs_arm > (/usr/local/src/gumstix/gumstix-buildroot/) C-Kermit> > (/usr/local/src/gumstix/gumstix-buildroot/) C-Kermit> > (/usr/local/src/gumstix/gumstix-buildroot/) C-Kermit> > (/usr/local/src/gumstix/gumstix-buildroot/) C-Kermit> > (/usr/local/src/gumstix/gumstix-buildroot/) C-Kermit> > (/usr/local/src/gumstix/gumstix-buildroot/) C-Kermit>bootm ?Not a > command or macro name: "bootm" > (/usr/local/src/gumstix/gumstix-buildroot/) C-Kermit>connect > Connecting to /dev/ttyS0, speed 115200 > Escape character: Ctrl-\ (ASCII 28, FS): enabled > Type the escape character followed by C to get back, > or followed by ? to see other options. > ---------------------------------------------------- > ## Total Size = 0x001e61c0 = 1991104 Bytes > ## Start Addr = 0xA2000000 > GUM> > GUM> erase 1:2-31 > Erase Flash Sectors 2-31 in Bank # 1 > Erasing sector 2 ... done > Erasing sector 3 ... done > Erasing sector 4 ... done > Erasing sector 5 ... done > Erasing sector 6 ... done > Erasing sector 7 ... done > Erasing sector 8 ... done > Erasing sector 9 ... done > Erasing sector 10 ... done > Erasing sector 11 ... done > Erasing sector 12 ... done > Erasing sector 13 ... done > Erasing sector 14 ... done > Erasing sector 15 ... done > Erasing sector 16 ... done > Erasing sector 17 ... done > Erasing sector 18 ... done > Erasing sector 19 ... done > Erasing sector 20 ... done > Erasing sector 21 ... done > Erasing sector 22 ... done > Erasing sector 23 ... done > Erasing sector 24 ... done > Erasing sector 25 ... done > Erasing sector 26 ... done > Erasing sector 27 ... done > Erasing sector 28 ... done > Erasing sector 29 ... done > Erasing sector 30 ... done > Erasing sector 31 ... done > GUM> > GUM> cp.b 0xa2000000 0x40000 $(filesize) > Copy to Flash.../done > GUM> > GUM> reset > resetting ... > > ***** Welcome to gumstix! ***** > > U-Boot 1.0.0 (Feb 12 2004 - 10:58:22) > > U-Boot code: A3F00000 -> A3F18120 > BSS space: -> A3F497F8 > DRAM Configuration: > Bank #0: a0000000 64 MB > Flash: 4 MB > In: serial > Out: serial > Err: serial > Hit any key to stop autoboot: 0 > ## Booting image at 00040000 ... > Bad Magic Number > GUM> > > - Kim > > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click > _______________________________________________ > gumstix-users mailing list > gum...@li... |
From: Kim H. <ki...@ki...> - 2004-07-23 23:31:55
|
> At the u-boot prompt, type > > set bootcmd fsload a2000000 boot/uImage\;bootm a2000000 > set bootargs console=ttyS0,115200n8 root=1f02 rootfstype=jffs2 noinitrd > reboot=cold,hard > save > > then reboot -- you should be good now. The problem is that the boot > process has changed from the original distribution shipped with the > 'stix to the current one in buildroot -- you need to change u-boot's > boot script to adjust. the "save" will save it for future boots, so > you only need to do it once. Ok, this worked. However, it booted to a kernel that required a root password and I didn't put one on it. I figured I'd checkout the build_root setup to see if it puts a default password on it. I turned off the power and took out the mmc card to be able to write a new image onto it on another machine. Once I was done, I went back to the gumstix and now it doesn't work at all! No uboot prompt or anything. Occasionally I just get a letter "a" with a grave character above it appearing, that or a '.' character. That's all. I'm running this gumstix in a harness I build for it myself. I took this gumstix out of a waysmall so I put it back into the waysmall to see if the battery had dropped too low, but it doesn't work in there as well. What could be wrong? As I can't get a uboot prompt I'm quite worried that the stix may have died for some reason. However, all I was busy with were software issues. There's still 3.85V going into the gumstix into the correct pins. One of the last things I did however before booting it was to set the environment variables. - Kim |
From: Craig H. <cr...@hu...> - 2004-07-23 23:37:27
|
The default root password on the new gumstix images is "gumstix" with no quotes. There's docs on the wiki covering stuff that's in the buildroot images. As for the hanging gumstix, do you have a JTAG debugger? That's probably the only way you'll be able to tell what's going on with it if you're not reaching the u-boot prompt. It's possible that when you saved your new environment variables, it somehow trashed the contents of sector 1 and when u-boot tries to read that back in, it's crapping out. But hard to tell w/out jtag... C On Jul 23, 2004, at 4:31 PM, Kim Hendrikse wrote: > Ok, this worked. However, it booted to a kernel that required a root > password > and I didn't put one on it. I figured I'd checkout the build_root > setup to see > if it puts a default password on it. I turned off the power and took > out the > mmc card to be able to write a new image onto it on another machine. > Once I was > done, I went back to the gumstix and now it doesn't work at all! No > uboot > prompt or anything. Occasionally I just get a letter "a" with a grave > character > above it appearing, that or a '.' character. That's all. > > I'm running this gumstix in a harness I build for it myself. I took > this > gumstix out of a waysmall so I put it back into the waysmall to see if > the > battery had dropped too low, but it doesn't work in there as well. > What could > be wrong? As I can't get a uboot prompt I'm quite worried that the > stix may > have died for some reason. However, all I was busy with were software > issues. > There's still 3.85V going into the gumstix into the correct pins. One > of the > last things I did however before booting it was to set the environment > variables. |
From: Gordon K. <go...@gu...> - 2004-07-23 23:58:55
|
Try plugging it in at the power source (i.e with a transformer that levels the voltage ramp) and see if that works. Gordon -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Craig Hughes Sent: Friday, July 23, 2004 4:37 PM To: gum...@li... Subject: Re: [Gumstix-users] Bad magic number The default root password on the new gumstix images is "gumstix" with no quotes. There's docs on the wiki covering stuff that's in the buildroot images. As for the hanging gumstix, do you have a JTAG debugger? That's probably the only way you'll be able to tell what's going on with it if you're not reaching the u-boot prompt. It's possible that when you saved your new environment variables, it somehow trashed the contents of sector 1 and when u-boot tries to read that back in, it's crapping out. But hard to tell w/out jtag... C On Jul 23, 2004, at 4:31 PM, Kim Hendrikse wrote: > Ok, this worked. However, it booted to a kernel that required a root > password > and I didn't put one on it. I figured I'd checkout the build_root > setup to see > if it puts a default password on it. I turned off the power and took > out the > mmc card to be able to write a new image onto it on another machine. > Once I was > done, I went back to the gumstix and now it doesn't work at all! No > uboot > prompt or anything. Occasionally I just get a letter "a" with a grave > character > above it appearing, that or a '.' character. That's all. > > I'm running this gumstix in a harness I build for it myself. I took > this > gumstix out of a waysmall so I put it back into the waysmall to see if > the > battery had dropped too low, but it doesn't work in there as well. > What could > be wrong? As I can't get a uboot prompt I'm quite worried that the > stix may > have died for some reason. However, all I was busy with were software > issues. > There's still 3.85V going into the gumstix into the correct pins. One > of the > last things I did however before booting it was to set the environment > variables. ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Kim H. <ki...@ki...> - 2004-07-24 00:13:32
|
> Try plugging it in at the power source (i.e with a transformer that levels the voltage ramp) and see if that works. Well I plugged it back into the waysmall computer and I used the transformer shipped from you guys with that (With a 240 -> 220 transformer in front, being in Europe). I've also pressed the reset button a few times, with the battery firmly in place. I don't think it's a power issue, as the battery still had 3.85 volts on the pins. - Kim |
From: Kim H. <ki...@ki...> - 2004-07-24 00:26:16
|
> Try plugging it in at the power source (i.e with a transformer that levels the voltage ramp) and see if that works. Ok, now that I've figured out what you mean by that. I unplugged the power supply from the wall socket. But no change. Still dead. - Kim |
From: Kim H. <ki...@ki...> - 2004-07-24 00:10:25
|
> The default root password on the new gumstix images is "gumstix" with > no quotes. There's docs on the wiki covering stuff that's in the > buildroot images. Ah, ok. A little bit academic now though :( > As for the hanging gumstix, do you have a JTAG debugger? That's > probably the only way you'll be able to tell what's going on with it if > you're not reaching the u-boot prompt. It's possible that when you > saved your new environment variables, it somehow trashed the contents > of sector 1 and when u-boot tries to read that back in, it's crapping > out. But hard to tell w/out jtag... Unfortunately I don't have a jtag debugger. And your conclusion is the one that I think as well :( I've tried a whole range of different baud rates and parity settings in case that's all that had changed. But no luck. It's just dead. - Kim > C > > On Jul 23, 2004, at 4:31 PM, Kim Hendrikse wrote: > > >Ok, this worked. However, it booted to a kernel that required a root > >password > >and I didn't put one on it. I figured I'd checkout the build_root > >setup to see > >if it puts a default password on it. I turned off the power and took > >out the > >mmc card to be able to write a new image onto it on another machine. > >Once I was > >done, I went back to the gumstix and now it doesn't work at all! No > >uboot > >prompt or anything. Occasionally I just get a letter "a" with a grave > >character > >above it appearing, that or a '.' character. That's all. > > > >I'm running this gumstix in a harness I build for it myself. I took > >this > >gumstix out of a waysmall so I put it back into the waysmall to see if > >the > >battery had dropped too low, but it doesn't work in there as well. > >What could > >be wrong? As I can't get a uboot prompt I'm quite worried that the > >stix may > >have died for some reason. However, all I was busy with were software > >issues. > >There's still 3.85V going into the gumstix into the correct pins. One > >of the > >last things I did however before booting it was to set the environment > >variables. > > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Kim H. <ki...@ki...> - 2004-07-26 09:21:20
|
> As for the hanging gumstix, do you have a JTAG debugger? That's > probably the only way you'll be able to tell what's going on with it if > you're not reaching the u-boot prompt. It's possible that when you > saved your new environment variables, it somehow trashed the contents > of sector 1 and when u-boot tries to read that back in, it's crapping > out. But hard to tell w/out jtag... I'm going to try and build a wiggler compatible jtag cable to look into the thing. Can you please mail me the procedure to recover the gumstix with this? Oh and which pins on the old (200Mhz) gumstix correspond to which pins on a wiggler? - Kim |
From: Craig H. <cr...@hu...> - 2004-07-26 19:05:02
|
I'll add a JTAG page or two on the wiki to help with this, including the OCD Commander script to initialize things on the gumstix enough to load a u-boot.srec to RAM C On Jul 26, 2004, at 2:21 AM, Kim Hendrikse wrote: >> As for the hanging gumstix, do you have a JTAG debugger? That's >> probably the only way you'll be able to tell what's going on with it >> if >> you're not reaching the u-boot prompt. It's possible that when you >> saved your new environment variables, it somehow trashed the contents >> of sector 1 and when u-boot tries to read that back in, it's crapping >> out. But hard to tell w/out jtag... > > I'm going to try and build a wiggler compatible jtag cable to look > into the > thing. Can you please mail me the procedure to recover the gumstix > with this? > Oh and which pins on the old (200Mhz) gumstix correspond to which pins > on a > wiggler? |