From: Chris S. <chr...@gm...> - 2006-03-10 20:30:25
|
"uisp --wr_fuse_l=3D0xbf --wr_fuse_h=3D0xc2 --wr_fuse_e=3D0xff" This has made it *much* worse. I can't download anything to the Atmel and I can't change the fuse settings at all. Now I get: ./uisp An error has occurred during the AVR initialization. * Target status: Vendor Code =3D 0xff, Part Family =3D 0xff, Part Number =3D 0xff Check if the programmer is properly connected. The wiring may be incorrect or target might be 'damaged'. Of course, I haven't touched the wiring (Hirose) and googling around it seems that: "Generally, the "target damaged" error is received when the fuses become stuck in a certain position or the .... is no longer making good contact with the programming board." Is my Robostix hosed? Is there anyway to get out of this situation? Really, I just want to use the Robostix as a peripheral controller. I'm content to access everything via i2c from the gumstix. I don't want to do *any* programming for it, just the minimal configuration= . |
From: Dave H. <dhy...@gm...> - 2006-03-10 22:10:41
|
Hi Chris, On 3/10/06, Chris Sears <chr...@gm...> wrote: > "uisp --wr_fuse_l=3D0xbf --wr_fuse_h=3D0xc2 --wr_fuse_e=3D0xff" > > This has made it *much* worse. I can't download anything to the Atmel > and I can't change the fuse settings at all. Now I get: > > ./uisp > An error has occurred during the AVR initialization. > * Target status: > Vendor Code =3D 0xff, Part Family =3D 0xff, Part Number =3D 0xff > > Check if the programmer is properly connected. > The wiring may be incorrect or target might be 'damaged'. I get that error if only one of the two jumpers is installed, in particular, if the left jumper of the ones in this photo: http://gumstix.org/tikiwiki/tiki-index.php?page=3DRobostix-Gumstix-ISP is installed then I get that error. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Chris S. <chr...@gm...> - 2006-03-11 04:53:16
|
I checked out the jumpers and they're good. But it couldn't have been the jumpers because the symptom showed up right after the "uisp -wr_fuse ..." command. I *was* able to get the flashing LED demo working. It seems that the fuses are now in an incorrect state. In any case, we missed our deadline. So we're punting on the robostix and back to working with the gumstix/breakout-gs trying to get i2c working. Magic numbers and other incantations should be hidden in scripts. I don't know what a fuse is much less what settings are which, but I did want to use the Robostix in a pretty vanilla fashion. Oh well. Chris On 3/10/06, Dave Hylands <dhy...@gm...> wrote: > Hi Chris, > > On 3/10/06, Chris Sears <chr...@gm...> wrote: > > "uisp --wr_fuse_l=3D0xbf --wr_fuse_h=3D0xc2 --wr_fuse_e=3D0xff" > > > > This has made it *much* worse. I can't download anything to the Atmel > > and I can't change the fuse settings at all. Now I get: > > > > ./uisp > > An error has occurred during the AVR initialization. > > * Target status: > > Vendor Code =3D 0xff, Part Family =3D 0xff, Part Number =3D 0xff > > > > Check if the programmer is properly connected. > > The wiring may be incorrect or target might be 'damaged'. > > I get that error if only one of the two jumpers is installed, in > particular, if the left jumper of the ones in this photo: > http://gumstix.org/tikiwiki/tiki-index.php?page=3DRobostix-Gumstix-ISP > is installed then I get that error. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting langua= ge > that extends applications into web and mobile media. Attend the live webc= ast > and join the prime developer group breaking into this new coding territor= y! > http://sel.as-us.falkag.net/sel?cmdlnk&kid=110944&bid$1720&dat=121642 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Dave H. <dhy...@gm...> - 2006-03-11 05:44:21
|
Hi Chris, > In any case, we missed our deadline. So we're punting on > the robostix and back to working with the gumstix/breakout-gs > trying to get i2c working. You didn't need the robostix to use i2c, unless you're trying to actually talk to the robostix via i2c. Sorry it didn't work out, > Magic numbers and other incantations should be hidden in scripts. > I don't know what a fuse is much less what settings are which, > but I did want to use the Robostix in a pretty vanilla fashion. Good point. I'll add a couple of scripts for setting the fuses, and downloading the bootloader, and i2c-io program. The fuse incantation was on the wiki where it could be copied and pasted, and that's how I've used it in the past. I think I'll also put all of the i2c stuff together in a single tarball to make it easier to install. Fuses are a part of using most modern microcontrollers. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Chris S. <chr...@gm...> - 2006-03-11 06:56:12
|
Dave thanks. Since I was/am having trouble getting my i2c chip recognized on the gumstix, and since I had to level shift anyways, I decided to give the robostix a try. It could have worked for the demo. I also wanted to see the robostix recognized on the gumstix i2c bus. BTW, on the subject of i2c, I just don't get why it isn't preinstalled into the kernel as modules. NFS and sound and IDE are configured. If you stack the gumstix with the Robostix, then the first thing you'll wan= t is that i2c line. On 3/10/06, Dave Hylands <dhy...@gm...> wrote: > Hi Chris, > > > In any case, we missed our deadline. So we're punting on > > the robostix and back to working with the gumstix/breakout-gs > > trying to get i2c working. > > You didn't need the robostix to use i2c, unless you're trying to > actually talk to the robostix via i2c. Sorry it didn't work out, > > > Magic numbers and other incantations should be hidden in scripts. > > I don't know what a fuse is much less what settings are which, > > but I did want to use the Robostix in a pretty vanilla fashion. > > Good point. I'll add a couple of scripts for setting the fuses, and > downloading the bootloader, and i2c-io program. The fuse incantation > was on the wiki where it could be copied and pasted, and that's how > I've used it in the past. I think I'll also put all of the i2c stuff > together in a single tarball to make it easier to install. > > Fuses are a part of using most modern microcontrollers. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting langua= ge > that extends applications into web and mobile media. Attend the live webc= ast > and join the prime developer group breaking into this new coding territor= y! > http://sel.as-us.falkag.net/sel?cmdlnk&kid=110944&bid$1720&dat=121642 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Dave H. <dhy...@gm...> - 2006-03-11 07:10:04
|
Hi Chris, > BTW, on the subject of i2c, I just don't get why it isn't preinstalled > into the kernel as modules. NFS and sound and IDE are configured. > If you stack the gumstix with the Robostix, then the first thing you'll w= ant > is that i2c line. Lobby Craig.... That's why I provide the precompiled modules - to make it easier for people to get started with i2c without having to build it themselves. I think that part of the reaon it hasn't been bundled in the past is that there wasn't any software to use it. Acutally, if I remember correctly, it was include a long time agao (around the time the 60 pin hirose came out), but it delayed the boot while it scanned the bus. Nowadays, the bus scan is virtually instantaneous. The i2c modules would add about 40K to the size of the buildroot (that was for Craig, just in case he was wondering :) Now that the bootloader and whatnot seems to be working, I think that the robostix should be shipped with the i2c-Bootloader and i2c-io.hex already loaded. I still need to do a bit of work to incorporate i2c-load, i2c-io and the i2c programs into the buildroot. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Craig H. <cr...@gu...> - 2006-03-12 02:15:10
|
On Mar 10, 2006, at 11:09 PM, Dave Hylands wrote: > Lobby Craig.... > > That's why I provide the precompiled modules - to make it easier for > people to get started with i2c without having to build it themselves. > > I think that part of the reaon it hasn't been bundled in the past is > that there wasn't any software to use it. Acutally, if I remember > correctly, it was include a long time agao (around the time the 60 pin > hirose came out), but it delayed the boot while it scanned the bus. > > Nowadays, the bus scan is virtually instantaneous. > > The i2c modules would add about 40K to the size of the buildroot (that > was for Craig, just in case he was wondering :) Ok, I'll turn them on -- just to make sure: is all I need to do enabble i2c in the kernel config? Or is there some special hidden option somewhere I need too that's not obvious? C |
From: Dave H. <dhy...@gm...> - 2006-03-12 02:33:06
|
Hi Craig, > > The i2c modules would add about 40K to the size of the buildroot (that > > was for Craig, just in case he was wondering :) > > Ok, I'll turn them on -- just to make sure: is all I need to do > enabble i2c in the kernel config? Or is there some special hidden > option somewhere I need too that's not obvious? There are 3 config options that need to be enabled: CONFIG_I2C=3Dm CONFIG_I2C_CHARDEV=3Dm CONFIG_I2C_PXA=3Dm The I2CQuickStart page describes where they are in menuconfig. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |