Post by thread:[PIC] device identification 16f628a/wisp628 progra

As a beginner I loaded succesfully a blink-a-led program by means of the Wisp628 programmer and the Bumblebee programming software in a 16f628a PIC. Subsequently I played with multiple leds and timings, I also loaded a "hello world" display program, but after I loaded a 7-segment led driver I can't load and erase the 16f628a anymore. The Bumblebee can't identify the target, it says device code 0000, however it does identify the programmer correctly. Since I was afraid for damage by ESD, I carefully installed my second 16f628, loaded the program, which worked, but with the same effect that no erasing or loading is possible and the target cannot be identified. I have just no acces at all to the PIC. The simple Basic commands compiled by the Proton Lite compiler are given below, whereby I must note that initially I forgot the ALL_DIGITAL true statement. Device 16F628A ;Gebruik een 16F628A type Config INTRC_OSC_NOCLKOUT, WDT_OFF, PWRTE_ON, LVP_OFF, MCLRE_OFF ALL_DIGITAL true Dim CIJFER As Byte CIJFER= 4 Low PORTB If CIJFER=4 Then High PORTB.0 High PORTB.3 High PORTB.4 EndIf End I cannot believe that both PICs are destroyed, but can it be that code-protection is inadvertently set or is the device coding erased and how can that be restored ?. The voltage on the MCLR pin is initially 5.01 V, and stays at 12,75 V after unsuccesful loading , identifying or erasing. I would be grateful if someone can help me out.

> display program, but after I loaded a 7-segment led driver I > can't load and erase the 16f628a anymore. without any changes to the target circuit, or did you maybe connect the display to port B? Wouter van Ooijen -- ------------------------------------------- Van Ooijen Technische Informatica: http://www.voti.nl consultancy, development, PICmicro products docent Hogeschool van Utrecht: http://www.voti.nl/hvu

Thank you for your reply. I did connect the display to port B before loading. The problem persists with and without the display connected.----- Original Message ----- From: "Wouter van Ooijen" <spam_OUTwouterTakeThisOuTvoti.nl> To: "'Microcontroller discussion list - Public.'" <.....piclistKILLspam@spam@mit.edu> Sent: Friday, August 26, 2005 5:31 PM Subject: RE: [PIC] device identification 16f628a/wisp628 programmer/bumblebee prog software {Quote hidden}> > display program, but after I loaded a 7-segment led driver I > > can't load and erase the 16f628a anymore. > > without any changes to the target circuit, or did you maybe connect the > display to port B? > > Wouter van Ooijen > > -- ------------------------------------------- > Van Ooijen Technische Informatica: http://www.voti.nl > consultancy, development, PICmicro products > docent Hogeschool van Utrecht: http://www.voti.nl/hvu > > > -

Thank you for your reply. I did connect the display to port B before loading. The problem persists with and without the display connected.----- Original Message ----- From: "Wouter van Ooijen" <wouterKILLspamvoti.nl> To: "'Microcontroller discussion list - Public.'" <.....piclistKILLspam.....mit.edu> Sent: Friday, August 26, 2005 5:31 PM Subject: RE: [PIC] device identification 16f628a/wisp628 programmer/bumblebee prog software {Quote hidden}> > display program, but after I loaded a 7-segment led driver I > > can't load and erase the 16f628a anymore. > > without any changes to the target circuit, or did you maybe connect the > display to port B? > > Wouter van Ooijen > > -- ------------------------------------------- > Van Ooijen Technische Informatica: http://www.voti.nl > consultancy, development, PICmicro products > docent Hogeschool van Utrecht: http://www.voti.nl/hvu > > > -

Thank you for your reaction. MCLRE_OFF was in the header of the program all the time. I have not yet used XWISP. I have initially use WINWISP, but this does not properly recognise the a version of the 16f628. I could program a few times at random, but finally I could not get through anymore. WINWISP recognises only 4 models PIC: 16f84, 84a, 27 and 28. ----- Original Message ----- From: "Jan-Erik Soderholm" <EraseMEjan-erik.soderholmspam_OUTTakeThisOuTtelia.com> To: <piclistspam_OUTmit.edu> Sent: Friday, August 26, 2005 5:12 PM Subject: RE: [PIC] device identification 16f628a/wisp628 programmer/bumblebee prog software > Have you used MCLRE_OFF all the time ? > > Have you tried with XWisp (or > XWisp2) ? > > Jan-Erik. > > > > -

> Thank you for your reply. I did connect the display to port B before > loading. The problem persists with and without the display > connected. So summarise: you have a 16F628A that you can't reprogram with a Wisp628? Last step would be to try the extra circuit as shown on the Wisp628 webpage. Wouter van Ooijen -- ------------------------------------------- Van Ooijen Technische Informatica: http://www.voti.nl consultancy, development, PICmicro products docent Hogeschool van Utrecht: http://www.voti.nl/hvu

>>-----Original Message----- >>From: @spam@piclist-bouncesKILLspammit.edu >>[KILLspampiclist-bouncesKILLspammit.edu] On Behalf Of A.Schouten >>Sent: Friday, August 26, 2005 4:52 PM >>To: RemoveMEpiclistTakeThisOuTmit.edu >>Subject: [PIC] device identification 16f628a/wisp628 >>programmer/bumblebee prog software >> >>As a beginner I loaded succesfully a blink-a-led program by >>means of the Wisp628 programmer and the Bumblebee programming >>software in a 16f628a PIC. Subsequently I played with >>multiple leds and timings, I also loaded a "hello world" >>display program, but after I loaded a 7-segment led driver I >>can't load and erase the 16f628a anymore. The Bumblebee can't >>identify the target, it says device code 0000, however it ... I've had that happen when using too long wires from the Wisp628. /Hugo

xwisp2 (under Windows and OS/2) are the best software for Wisp628. It is a pity that it does not work under Linux now. http://www.robh.nl XWisp2 - by Rob Hamerling ================================= XWisp for OS/2 and Windows Copyright 2002,2004, R. Hamerling XWisp2 is a support program for the Wisp628 PIC programmer and WLoader. Basically it has the same purpose and functionality as the original programs Wisp and XWisp of Wouter van Ooijen (http://www.voti.nl/xwisp), but XWisp2 is written in C-language and directly executable, without having to install Python or any runtime libaries. The original documentation of XWisp should be used as reference for XWisp2. This file describes mainly differences. Regards, Xiaofan {Original Message removed}