From: VaibhavGhadiok <vai...@gm...> - 2009-12-02 20:49:36
|
hi I have a verdexpro attached with a netpro-vx and robostix. All thee boards are new. When I try to do a uisp I get a message stating Cannot identify device because it is locked. Device similar to the ATMEGA103-old is found. Device is locked. Address out of memory range. I have made the necessary modifications to the robostix. 1. The resistor pulling the RX pin high. 2. two pull ups for i2c 3. Power Modification as per robostix.pdf. (The entire one side of the IC is shorted when I short two pins on it) 4. Jumpers for programming With regards Vaibhav -- View this message in context: http://old.nabble.com/New-Robostix-not-recognized-%28after-modifications%29-tp26616171p26616171.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dave H. <dhy...@gm...> - 2009-12-03 06:14:43
|
Hi Vaibhav, On Wed, Dec 2, 2009 at 12:49 PM, VaibhavGhadiok <vai...@gm...> wrote: > > hi > > I have a verdexpro attached with a netpro-vx and robostix. All thee boards > are new. When I try to do a uisp I get a message stating > > Cannot identify device because it is locked. > Device similar to the ATMEGA103-old is found. > Device is locked. > Address out of memory range. Hmm. If it really is locked then I think you need to do a chip erase to reset the lock bits. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: VaibhavGhadiok <vai...@gm...> - 2009-12-03 07:07:34
|
If you are talking about uisp --erase I have done that. I have also tried various fuse settings for the high. c2 c9 ca. Dave Hylands wrote: > > Hi Vaibhav, > > On Wed, Dec 2, 2009 at 12:49 PM, VaibhavGhadiok > <vai...@gm...> wrote: >> >> hi >> >> I have a verdexpro attached with a netpro-vx and robostix. All thee >> boards >> are new. When I try to do a uisp I get a message stating >> >> Cannot identify device because it is locked. >> Device similar to the ATMEGA103-old is found. >> Device is locked. >> Address out of memory range. > > Hmm. If it really is locked then I think you need to do a chip erase > to reset the lock bits. > > -- > Dave Hylands > Shuswap, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------------ > Join us December 9, 2009 for the Red Hat Virtual Experience, > a free event focused on virtualization and cloud computing. > Attend in-depth sessions from your desk. Your couch. Anywhere. > http://p.sf.net/sfu/redhat-sfdev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/New-Robostix-not-recognized-%28after-modifications%29-tp26616171p26621712.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dave H. <dhy...@gm...> - 2009-12-03 07:35:07
|
Hi Vaibhav, I'm not sure what the problem is, On Wed, Dec 2, 2009 at 11:07 PM, VaibhavGhadiok <vai...@gm...> wrote: > > If you are talking about uisp --erase I have done that. > > I have also tried various fuse settings for the high. c2 c9 ca. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: Dave H. <dhy...@gm...> - 2009-12-03 16:50:16
|
Hi Vaibhav, > On Wed, Dec 2, 2009 at 11:07 PM, VaibhavGhadiok > <vai...@gm...> wrote: >> >> If you are talking about uisp --erase I have done that. >> >> I have also tried various fuse settings for the high. c2 c9 ca. Probably the next best thing to do, is to separate the robostix from the stack, remove the programming jumpers and see if you can program the robostix using an external programmer (through the 10 pin header) connected to your PC. And also double check all of your modifications to ensure that there aren't any solder bridges, etc. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |