I tried programming (for the first time) a 12f675 with my Wisp628. The programmer can't read the target ID. IS this because I am not using the additional circuit (the 'dongle') ? http://www.voti.nl/wisp628/pics/dongle.gif Also, whats a TIP120? Is there an alternative to the Dongle ? Thanks, Shachar Weis. |
|
Problems with wisp628 and PIC12F675
Started by ●May 24, 2004
Reply by ●May 24, 20042004-05-24
> I tried programming (for the first time) a 12f675 with my Wisp628. > The programmer can't read the target ID. What is the exact error message? > IS this because I am not using the additional circuit (the 'dongle') ? > http://www.voti.nl/wisp628/pics/dongle.gif With a new (clear) 12F675 this should (in practice) not be needed. > Also, whats a TIP120? a very common NPN darlington power transistor > Is there an alternative to the Dongle ? if you need it (see Wisp628 page) you will have to switch the power to the target. a moer sophisticated alternative would be a series transistor instead of a shorter, but that would reuire a more complex circuit. Wouter van Ooijen -- ------- Van Ooijen Technische Informatica: www.voti.nl consultancy, development, PICmicro products |
|
Reply by ●May 24, 20042004-05-24
--- In , "Wouter van Ooijen" <wouter@v...> wrote: > > I tried programming (for the first time) a 12f675 with my Wisp628. > > The programmer can't read the target ID. > > What is the exact error message? > The error message is : target auto-detect ... Sorry, I can not determine the target chip type. Specify a target on the command line, or maybe the chip is defect? The Id that is read is 3FFF. Its a clean blank PIC, i tried both with an internal and external osciletor and I also tried replacing the PIC. |
|
Reply by ●May 24, 20042004-05-24
Ok, I found the problem. In the "Blink A led" schematics, when the Led+Resistor is connected, the wisp can't ID the PIC. When disconnected, it works but prints an error message : C:\Program Files\XWisp\serialwin32.py:88: DeprecationWarning: integer argument e xpected, got float win32file.SetCommTimeouts(self.hComPort, timeouts) C:\Program Files\XWisp\xwisp.py:2026: FutureWarning: %u/%o/%x/%X of negative int will return a signed string in Python 2.4 and up self.Log(( "__GoTo( %04X )" % Address ) + \ |
|
Reply by ●May 24, 20042004-05-24
> Ok, I found the problem. > In the "Blink A led" schematics, when the Led+Resistor is > connected, the wisp can't ID the PIC. You probably have a Wisp628 with 470 ohm series resistors? You can replace these with 47 ohm resistors (or simply keep the 470's and put 47's in parallel). > When disconnected, it works but prints an error message : > > C:\Program Files\XWisp\serialwin32.py:88: DeprecationWarning: integer > argument e > xpected, got float > win32file.SetCommTimeouts(self.hComPort, timeouts) > C:\Program Files\XWisp\xwisp.py:2026: FutureWarning: %u/%o/%x/%X of > negative int > will return a signed string in Python 2.4 and up > self.Log(( "__GoTo( %04X )" % Address ) + \ Yeh, those stupid deprecation warnings I have to get rid off. But I'm glad it does work! Wouter van Ooijen -- ------- Van Ooijen Technische Informatica: www.voti.nl consultancy, development, PICmicro products |