From: Benny S. (webmail) <ben...@ma...> - 2004-07-28 08:47:05
|
I did the same thing, but with my own build binary file so I thought there = were a problem with that file. Yesterday I managed to get my own build = JTAG and ODC Commander to execute the script from the Wiki and the 1.1.1 = bootloader did actually start, but I did unfortunately not stop the = bootloader before it tried to boot. Unfortunately it's almost impossible for me to start the stix and let the = Macraigor ODC Commander connect. I guess I used 3 houers where I got = "internal" errors from the Commander which according to the helpfile newer = should happen. I also got a log file which described errors internal in = the program. It does also look like a have my old problem to have the stix = power correctly up so that I can communicate with it over JTAG. Until Craig has confirmed that the bin image is working I will not = recommend that anyone try to update the u-boot unless they have a working = JTAG. Craig could you write the "md5sum" on the images you put on sourceforge so = it's possible to verify that nothing bad has happened during download. Best Regards Benny -----Oprindelig meddelelse----- Fra: gum...@li... Til: gum...@li... = <gum...@li...> Emne: [Gumstix-users] turned my stick into a doorstop Dato: 28-07-2004 03:34:08 > Well, I followed the steps I mapped out in my previous > post from last Friday and the stick is now dead. >=20 > I had downloaded the 400MHz binary imae from > sourceforge. One thing I didn't think about was > whether this binary is for older gumstix boards or > newer? I have an older one (waysmall), 400 MHz. >=20 > Anyway, all appeared to go correctly per the list of > commands I thought I needed to do: unprotect flash > (though uboot said the first sector was 1 and not 0) > erase flash, load binary, copy to flash, re-protect. >=20 > Issue reset command, board is dead. Cycle power and > board is dead. Oh well, looks like I'll need to get > JTAG up and running... >=20 > Craig, can you verify that the image on Sourceforge > really works? >=20 > Thanks, Jim >=20 >=20 >=20 >=20 > __________________________________ > Do you Yahoo!? > New and Improved Yahoo! Mail - 100MB free storage! > http://promotions.yahoo.com/new_mail >=20 >=20 > ------------------------------------------------------- > 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=3D4721&alloc_id=3D10040&op=3Dclick > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users >=20 >=20 |
From: Kim H. <ki...@ki...> - 2004-07-28 09:29:58
|
also look like a have my old problem to have the stix power correctly up so that I can communicate with it over JTAG. What are the symptoms of the above? Do you turn on the power and nothing happens? How would one tell the difference between broken uboot code and an incorrect power on reset? I ask, because my current stick does nothing. I'm assuming that it is a uboot problem, because it went that way after operations that write to bank 0, however if it was also a power on pulse problem I'm wondering how you can tell the difference? I suppose the difference is that you can't talk to the stick with jtag if it was a power on problem. Has there been any firm resolution to the power on pulse problem by those that experienced it? It may affect a decision to build in a power on pulse chip into my design or not. - Kim |
From: Craig H. <cr...@hu...> - 2004-07-28 17:15:38
|
We've gone back to all the boards we had which used to have the power-on problem that were in our "rejects" bin at gumstix, and with the new RAM refresh rate, all of them now behave correctly -- that is, the power-on problem seems to have been that some boards were more sensitive to the bad RAM refresh rate, and that this manifested itself particularly when power to the board was not switched on cleanly. C On Jul 28, 2004, at 2:29 AM, Kim Hendrikse wrote: > I suppose the difference is that you can't talk to the stick with jtag > if it > was a power on problem. Has there been any firm resolution to the power > on pulse problem by those that experienced it? It may affect a decision > to build in a power on pulse chip into my design or not. |
From: Craig H. <cr...@hu...> - 2004-07-28 17:09:04
|
I'll check and MD5 the images. Also, I've now got the linux mtd flash=20= utils compiling properly, so the uboot image can be written with a=20 simple command from linux instead of having to do it in u-boot, which=20 is a lot more error-prone. Requires upgrading the linux kernel first=20 though, since I had to make a minor change to the flash map in linux to=20= make the u-boot sectors writable. Please, nobody attempt to flash the new u-boot until I post again to=20 this list on the topic, when I'll provide instructions for how to do it=20= more safely under linux, as well as the MD5s Thanks, C On Jul 28, 2004, at 1:46 AM, Benny Simonsen (webmail) wrote: > I did the same thing, but with my own build binary file so I thought=20= > there were a problem with that file. Yesterday I managed to get my own=20= > build JTAG and ODC Commander to execute the script from the Wiki and=20= > the 1.1.1 bootloader did actually start, but I did unfortunately not=20= > stop the bootloader before it tried to boot. > Unfortunately it's almost impossible for me to start the stix and let=20= > the Macraigor ODC Commander connect. I guess I used 3 houers where I=20= > got "internal" errors from the Commander which according to the=20 > helpfile newer should happen. I also got a log file which described=20 > errors internal in the program. It does also look like a have my old=20= > problem to have the stix power correctly up so that I can communicate=20= > with it over JTAG. > > Until Craig has confirmed that the bin image is working I will not=20 > recommend that anyone try to update the u-boot unless they have a=20 > working JTAG. > > Craig could you write the "md5sum" on the images you put on=20 > sourceforge so it's possible to verify that nothing bad has happened=20= > during download. > > Best Regards > Benny > > -----Oprindelig meddelelse----- > Fra: gum...@li... > Til: gum...@li...=20 > <gum...@li...> > Emne: [Gumstix-users] turned my stick into a doorstop > Dato: 28-07-2004 03:34:08 > >> Well, I followed the steps I mapped out in my previous >> post from last Friday and the stick is now dead. >> >> I had downloaded the 400MHz binary imae from >> sourceforge. One thing I didn't think about was >> whether this binary is for older gumstix boards or >> newer? I have an older one (waysmall), 400 MHz. >> >> Anyway, all appeared to go correctly per the list of >> commands I thought I needed to do: unprotect flash >> (though uboot said the first sector was 1 and not 0) >> erase flash, load binary, copy to flash, re-protect. >> >> Issue reset command, board is dead. Cycle power and >> board is dead. Oh well, looks like I'll need to get >> JTAG up and running... >> >> Craig, can you verify that the image on Sourceforge >> really works? >> >> Thanks, Jim >> >> >> >> >> __________________________________ >> Do you Yahoo!? >> New and Improved Yahoo! Mail - 100MB free storage! >> http://promotions.yahoo.com/new_mail >> >> >> ------------------------------------------------------- >> 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=3D4721&alloc_id=3D10040&op=3Dclick >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > > > > ------------------------------------------------------- > 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_idG21&alloc_id=10040&op=3Dclick > _______________________________________________ > gumstix-users mailing list > gum...@li... |
From: Craig H. <cr...@hu...> - 2004-07-28 17:13:03
|
Benny, not sure how you're starting up. The way I do jtag with OCD commander is to connect the wiggler to the 'stix, then power up the 'stix and quickly hit the "reset" button in the OCD commander toolbar, which will reset the board and halt. Then I normally step an instruction at a time. What should happen is that the first instruction at address 0 in flash should be a branch to a little above 2k in flash, followed by the initialization code. I generally find it useful to be looking at a copy of the output of "arm-linux-objdump -S u-boot" from the buildroot/build_arm/u-boot-1.1.1 directory at the time, so I have a nice, commented, version of the u-boot source code side-by-side with what I'm looking at in OCD. C On Jul 28, 2004, at 1:46 AM, Benny Simonsen (webmail) wrote: > I did the same thing, but with my own build binary file so I thought > there were a problem with that file. Yesterday I managed to get my own > build JTAG and ODC Commander to execute the script from the Wiki and > the 1.1.1 bootloader did actually start, but I did unfortunately not > stop the bootloader before it tried to boot. > Unfortunately it's almost impossible for me to start the stix and let > the Macraigor ODC Commander connect. I guess I used 3 houers where I > got "internal" errors from the Commander which according to the > helpfile newer should happen. I also got a log file which described > errors internal in the program. It does also look like a have my old > problem to have the stix power correctly up so that I can communicate > with it over JTAG. |