Menu
▾
▴
usbpicprog-technical
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(13) |
Nov
(27) |
Dec
(23) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
|
Feb
(13) |
Mar
(24) |
Apr
(4) |
May
(11) |
Jun
(1) |
Jul
(4) |
Aug
(1) |
Sep
|
Oct
(6) |
Nov
(5) |
Dec
(2) |
| 2010 |
Jan
(1) |
Feb
(22) |
Mar
(52) |
Apr
(7) |
May
(19) |
Jun
(12) |
Jul
(9) |
Aug
(8) |
Sep
(7) |
Oct
|
Nov
(8) |
Dec
(7) |
| 2011 |
Jan
(12) |
Feb
(7) |
Mar
(10) |
Apr
(14) |
May
|
Jun
(1) |
Jul
|
Aug
(11) |
Sep
(5) |
Oct
(1) |
Nov
|
Dec
|
| 2012 |
Jan
(5) |
Feb
(2) |
Mar
(6) |
Apr
(12) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
(17) |
Nov
|
Dec
|
| 2013 |
Jan
(7) |
Feb
(6) |
Mar
(6) |
Apr
(21) |
May
(7) |
Jun
(3) |
Jul
(2) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Frans S. <fra...@gm...> - 2012-10-17 06:07:30
|
Hi, You probagbly haven't bricked the pic but programmed the code proteection bits by accident. With these bits enabled it is also more difficult to eras the pic, check the programming specification for the procedure. Regards, Frans Op 16 okt. 2012 23:04 schreef "Gábor Hornyák" <gab...@gm...> het volgende: > > Hi Everyone, > > My question is not strictly related to usbpicprog, but I am hoping that someone here has faced similar issue. > As a 'side' project of an other project, I thought I create a simple programmer to PIC18F46K22 (I have a demo board with PIC18F45K22 equipped with bootloader, which I am using for programming). Everything went fine - I was able to read/write program memory and read config words - until I reached the point where config words had to be written. After I created it and tested with a PIC, it seems that I bricked the mcu, because from that point, I can not do anything with the PIC (always read zeroes for all addresses). > I don't know what could have went wrong, since config word programming differs only in a few things from program memory programming (which works fine, and the fact is that I actually seem to have bricked two PICs already). My concrete question is: could this problem have been caused by trying to write config BYTES separately (not as words)? Has anyone faced similar problem? > > Thanks and Regards, > Gabor > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > |
|
From: Gábor H. <gab...@gm...> - 2012-10-16 21:03:56
|
Hi Everyone, My question is not strictly related to usbpicprog, but I am hoping that someone here has faced similar issue. As a 'side' project of an other project, I thought I create a simple programmer to PIC18F46K22 (I have a demo board with PIC18F45K22 equipped with bootloader, which I am using for programming). Everything went fine - I was able to read/write program memory and read config words - until I reached the point where config words had to be written. After I created it and tested with a PIC, it seems that I bricked the mcu, because from that point, I can not do anything with the PIC (always read zeroes for all addresses). I don't know what could have went wrong, since config word programming differs only in a few things from program memory programming (which works fine, and the fact is that I actually seem to have bricked two PICs already). My concrete question is: could this problem have been caused by trying to write config BYTES separately (not as words)? Has anyone faced similar problem? Thanks and Regards, Gabor |
|
From: Matt H. <mh...@me...> - 2012-10-11 15:30:22
|
I think its also possible to use the native MPLAB X and bundled C18 compiler provided by Microchip if you're on Linux and want to avoid running through wine: http://www.microchip.com/pagehandler/en-us/family/mplabx/ On 10/11/2012 03:34 AM, Frans Schreuder wrote: > The firmware contains a Makefile. If you run Linux and you have > installed the C18 compiler (wine) you can just run make from a console. > In Windows you could use mplab. Just create a new project with all the c > / h files and the rm18f4550.lkr. > > On 10/11/2012 04:54 AM, ti...@gm... wrote: >> Does anyone have information on how to compile the firmware? What IDE to use, settings, etc. I couldn't find a Read Me or information on the website. Thanks! >> ------------------------------------------------------------------------------ >> Don't let slow site performance ruin your business. Deploy New Relic APM >> Deploy New Relic app performance management and know exactly >> what is happening inside your Ruby, Python, PHP, Java, and .NET app >> Try New Relic at no cost today and get our sweet Data Nerd shirt too! >> http://p.sf.net/sfu/newrelic-dev2dev >> _______________________________________________ >> Usbpicprog-technical mailing list >> Usb...@li... >> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > ------------------------------------------------------------------------------ > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly > what is happening inside your Ruby, Python, PHP, Java, and .NET app > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: Frans S. <fra...@gm...> - 2012-10-11 07:34:39
|
The firmware contains a Makefile. If you run Linux and you have installed the C18 compiler (wine) you can just run make from a console. In Windows you could use mplab. Just create a new project with all the c / h files and the rm18f4550.lkr. On 10/11/2012 04:54 AM, ti...@gm... wrote: > Does anyone have information on how to compile the firmware? What IDE to use, settings, etc. I couldn't find a Read Me or information on the website. Thanks! > ------------------------------------------------------------------------------ > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly > what is happening inside your Ruby, Python, PHP, Java, and .NET app > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: Frans S. <fra...@gm...> - 2012-10-11 07:31:31
|
I don't know of anyone who has ever done such a thing. The biggest issue will be the PWM regulation for VPP and VDD, the other things are very straight forward. On 10/11/2012 04:53 AM, ti...@gm... wrote: > I noticed both the Usbpicprog and the PICKit 2 has the same PIC (PIC18F2550). Has anyone modified the firmware and get it working on the PICKit 2? In case anyone is wondering why anyone would do such a thing - I find it easier to modify Usbpicprog's C code over the assembly released by Microchip for their PICkit 2. > ------------------------------------------------------------------------------ > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly > what is happening inside your Ruby, Python, PHP, Java, and .NET app > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: <ti...@gm...> - 2012-10-11 02:55:06
|
Does anyone have information on how to compile the firmware? What IDE to use, settings, etc. I couldn't find a Read Me or information on the website. Thanks! |
|
From: <ti...@gm...> - 2012-10-11 02:53:52
|
I noticed both the Usbpicprog and the PICKit 2 has the same PIC (PIC18F2550). Has anyone modified the firmware and get it working on the PICKit 2? In case anyone is wondering why anyone would do such a thing - I find it easier to modify Usbpicprog's C code over the assembly released by Microchip for their PICkit 2. |
|
From: Kim R. <kro...@gm...> - 2012-06-29 22:05:48
|
Plus I noticed that when I connect the programmer with a target PIC24FJ256DA206 already connected the software tells me: 29.06.2012 23:46:59: Error setting configuration of the USB device: Pipe error 29.06.2012 23:46:59: Bootloader or programmer not found The same thing happens when I first connect the programmer without the target PIC (programmer is detected ok) and then connect the target a e.g. select "autodetect"... Am 29.06.2012 23:24, schrieb Kim Rosenbohm: > Hi All. > > I was naive when ordering the USBPICPROG hardware and though it > supported 24FJ256 -Types so it would support the DA206 version too, but > I only see -GA1xx and -GB1xx types in the software. > What can I do to flash that chip? It would suffice to flash the > bootloader... > > Best Regards, > > Kim > |
|
From: Kim R. <kro...@gm...> - 2012-06-29 21:24:11
|
Hi All. I was naive when ordering the USBPICPROG hardware and though it supported 24FJ256 -Types so it would support the DA206 version too, but I only see -GA1xx and -GB1xx types in the software. What can I do to flash that chip? It would suffice to flash the bootloader... Best Regards, Kim |
|
From: John G. <jo...@in...> - 2012-04-22 17:20:58
|
On 04/21/2012 11:21 AM, Frans Schreuder wrote: >> I see in the firmware that levels are already set for PIC24 family in subroutine >> > >> > set_vdd_vpp(PICTYPE pictype, PICFAMILY picfamily,char level) > Some PIC24 devices have been tested, but don't consider it stable. It > should only work in the restructure_code branch which will be mainstream > soon. Your schematic has lots of diodes even after the voltage doubler. Could some of those be left out? Are they there in case the code goes wild? What do you think of adding a third PWM voltage supply for VDD instead of regulators for supporting PIC24, PIC32? Especially since you have no stock of PCBs now, a hardware change would be easy. John |
|
From: Frans S. <fra...@gm...> - 2012-04-22 09:56:23
|
Dear Nuno, If the processors algorithm is already implemented in the firmware (picfamily) it is an easy task. In that case only an entry needs to be added to index.xml. Adding new families to the firmware is not that easy to do, for that i a affraid that you will need to read through the code. In that case it's better to check out the new restructure_code branch Kind regards, Frans Schreuder Op 21 apr. 2012 23:16 schreef "Nuno Sucena Almeida" <nu...@ae...> het volgende: > Hi, > what would be the way of adding support for a new processor? I > checked > the FAQ but didn't see it mentioned. I know that I can look at the > source, but some step-by-step guidelines would be nice. I'm particularly > interested in the 18F14K50 chip among others. > > Another thing, I tried to program the "blinking led" example on a > few > different processors and noticed that the oscillator settings/selection > seems to be somewhat wrong, although I didn't look at the source. I > tried with 16F648A, 16F628A, 12F615, 12F675 at least. > Writing my own simple C code within mplabx made it work flawlessly. > Cheers, > Nuno > > -- > http://aeminium.org/nuno/ > > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > |
|
From: Nuno S. A. <nu...@ae...> - 2012-04-21 21:16:10
|
Hi, what would be the way of adding support for a new processor? I checked the FAQ but didn't see it mentioned. I know that I can look at the source, but some step-by-step guidelines would be nice. I'm particularly interested in the 18F14K50 chip among others. Another thing, I tried to program the "blinking led" example on a few different processors and noticed that the oscillator settings/selection seems to be somewhat wrong, although I didn't look at the source. I tried with 16F648A, 16F628A, 12F615, 12F675 at least. Writing my own simple C code within mplabx made it work flawlessly. Cheers, Nuno -- http://aeminium.org/nuno/ |
|
From: Frans S. <fra...@gm...> - 2012-04-21 16:21:16
|
On 04/21/2012 02:34 PM, John Griessen wrote: > On 04/20/2012 11:22 PM, John Griessen wrote: >> Do these chips need different voltages? > I see in the firmware that levels are already set for PIC24 family in subroutine > > set_vdd_vpp(PICTYPE pictype, PICFAMILY picfamily,char level) Some PIC24 devices have been tested, but don't consider it stable. It should only work in the restructure_code branch which will be mainstream soon. > > Are PIC24 chips tested yet? Do they need more coding in the GUI app? > > Does usbpicprog.org sell and ship to USA? It does, but currently I didn't produce stock due to personal reasons. Hope to do so soon. > > Thanks, > > John Griessen > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: Frans S. <fra...@gm...> - 2012-04-21 16:14:17
|
The hardware does support the 3.3V chips (data and clock line) but the VDD needs a voltage regulator. There is some initial code for pic24 devices in the new code branch which can be found in the github repository: https://github.com/fransschreuder/usbpicprog/tree/restructure_code/ PIC32 has not been implemented yet. Kind regards, Frans Schreuder On 04/21/2012 06:22 AM, John Griessen wrote: > Do these chips need different voltages? > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: John G. <jo...@in...> - 2012-04-21 12:35:08
|
On 04/20/2012 11:22 PM, John Griessen wrote: > Do these chips need different voltages? I see in the firmware that levels are already set for PIC24 family in subroutine set_vdd_vpp(PICTYPE pictype, PICFAMILY picfamily,char level) Are PIC24 chips tested yet? Do they need more coding in the GUI app? Does usbpicprog.org sell and ship to USA? Thanks, John Griessen |
|
From: John G. <jo...@in...> - 2012-04-21 04:22:16
|
Do these chips need different voltages? |
|
From: Alexandre R. <ale...@gm...> - 2012-04-19 10:19:59
|
Ok Frans, this explain that resistors (470R and 1k) I where trying to figure out the function (a voltage divisor, I think). I will try the 100 Ohm resistor and give a feedback, thank you again. On Wed, Apr 18, 2012 at 11:25 AM, Frans Schreuder <fra...@gm...>wrote: > Ok, the difference is that the usbpicprog programmer has 470 Ohm > resistors in series. If you don't use 3.3V devices, you can replace them > with 100 Ohm. That will probably fix your problem. > > Kind regards, > > Frans Schreuder > > > On 04/18/2012 04:18 PM, Alexandre Rosa wrote: > > Thanks Frans, > > I figured out the problem, in 876A project PGD and PGC pins were shared > with an lcd bus lines so this should cause some interference in > programming. What is strange is that PICKIT3 do the job with no problem. > Any way thanks a lot. > > On Wed, Apr 18, 2012 at 5:12 AM, Frans Schreuder <fra...@gm... > > wrote: > >> Hello, >> >> The two devices use exactly the same algorithm and are also electrical >> identical. I have programmed the 876A many times and never experienced this >> behaviour. >> Have you checked: >> >> - your hardware voltages >> - all the connections to the 876A >> - that the PGM pin was connected to ground >> >> This could also be bad luck, you can try to request a free sample from >> microchip to get yourself a new 16F876A >> >> Kind regards, >> >> Frans Schreuder >> >> On 04/17/2012 04:24 PM, Alexandre Rosa wrote: >> >> Hey >> >> I have build a USBPICPROG through-hole version board and want to thank >> you for the good job in this project. >> >> I was able to program a 16F877A without any problem but with a 16F876A >> the programming has failed. >> >> 16/4/2012 13:50:32: Erasing before programming... >> 16/4/2012 13:50:32: Erase OK >> 16/4/2012 13:50:32: Programming the code area of the PIC... >> 16/4/2012 13:51:05: Write Code memory OK >> 16/4/2012 13:51:05: Programming the data area of the PIC... >> 16/4/2012 13:51:05: Write Data memory OK >> 16/4/2012 13:51:05: Verifying all areas of the PIC... >> 16/4/2012 13:51:06: Verify code failed at 0x0. Read: 0xFF, Expected: 0x0A >> 16/4/2012 13:51:06: Programming configuration area of the PIC... >> 16/4/2012 13:51:06: Error programming config memory >> 16/4/2012 13:51:06: Operations completed with errors/warnings >> >> In this case the 16F876A had been previous programmed with a PICKIT3 and >> was erased or bad programmed by USBPICPROG and did not work after this try. >> >> I try an external 5V power supply to do the job of USB BUS supply with no >> results. >> >> Any suggestions ? >> >> >> ------------------------------------------------------------------------------ >> Better than sec? Nothing is better than sec when it comes to >> monitoring Big Data applications. Try Boundary one-second >> resolution app monitoring today. Free.http://p.sf.net/sfu/Boundary-dev2dev >> >> >> >> _______________________________________________ >> Usbpicprog-technical mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical >> >> >> >> ------------------------------------------------------------------------------ >> Better than sec? Nothing is better than sec when it comes to >> monitoring Big Data applications. Try Boundary one-second >> resolution app monitoring today. Free. >> http://p.sf.net/sfu/Boundary-dev2dev >> _______________________________________________ >> Usbpicprog-technical mailing list >> Usb...@li... >> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical >> >> > > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free.http://p.sf.net/sfu/Boundary-dev2dev > > > > _______________________________________________ > Usbpicprog-technical mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > |
|
From: Frans S. <fra...@gm...> - 2012-04-18 14:26:00
|
Ok, the difference is that the usbpicprog programmer has 470 Ohm resistors in series. If you don't use 3.3V devices, you can replace them with 100 Ohm. That will probably fix your problem. Kind regards, Frans Schreuder On 04/18/2012 04:18 PM, Alexandre Rosa wrote: > Thanks Frans, > > I figured out the problem, in 876A project PGD and PGC pins were > shared with an lcd bus lines so this should cause some interference in > programming. What is strange is that PICKIT3 do the job with no > problem. Any way thanks a lot. > > On Wed, Apr 18, 2012 at 5:12 AM, Frans Schreuder > <fra...@gm... <mailto:fra...@gm...>> wrote: > > Hello, > > The two devices use exactly the same algorithm and are also > electrical identical. I have programmed the 876A many times and > never experienced this behaviour. > Have you checked: > > * your hardware voltages > * all the connections to the 876A > * that the PGM pin was connected to ground > > This could also be bad luck, you can try to request a free sample > from microchip to get yourself a new 16F876A > > Kind regards, > > Frans Schreuder > > > On 04/17/2012 04:24 PM, Alexandre Rosa wrote: >> Hey >> >> I have build a USBPICPROG through-hole version board and want to >> thank you for the good job in this project. >> >> I was able to program a 16F877A without any problem but with a >> 16F876A the programming has failed. >> >> 16/4/2012 13:50:32: Erasing before programming... >> 16/4/2012 13:50:32: Erase OK >> 16/4/2012 13:50:32: Programming the code area of the PIC... >> 16/4/2012 13:51:05: Write Code memory OK >> 16/4/2012 13:51:05: Programming the data area of the PIC... >> 16/4/2012 13:51:05: Write Data memory OK >> 16/4/2012 13:51:05: Verifying all areas of the PIC... >> 16/4/2012 13:51:06: Verify code failed at 0x0. Read: 0xFF, >> Expected: 0x0A >> 16/4/2012 13:51:06: Programming configuration area of the PIC... >> 16/4/2012 13:51:06: Error programming config memory >> 16/4/2012 13:51:06: Operations completed with errors/warnings >> >> In this case the 16F876A had been previous programmed with a >> PICKIT3 and was erased or bad programmed by USBPICPROG and did >> not work after this try. >> >> I try an external 5V power supply to do the job of USB BUS supply >> with no results. >> >> Any suggestions ? >> >> >> ------------------------------------------------------------------------------ >> Better than sec? Nothing is better than sec when it comes to >> monitoring Big Data applications. Try Boundary one-second >> resolution app monitoring today. Free. >> http://p.sf.net/sfu/Boundary-dev2dev >> >> >> _______________________________________________ >> Usbpicprog-technical mailing list >> Usb...@li... <mailto:Usb...@li...> >> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > <mailto:Usb...@li...> > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > > > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev > > > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: Alexandre R. <ale...@gm...> - 2012-04-18 14:18:45
|
Thanks Frans, I figured out the problem, in 876A project PGD and PGC pins were shared with an lcd bus lines so this should cause some interference in programming. What is strange is that PICKIT3 do the job with no problem. Any way thanks a lot. On Wed, Apr 18, 2012 at 5:12 AM, Frans Schreuder <fra...@gm...>wrote: > Hello, > > The two devices use exactly the same algorithm and are also electrical > identical. I have programmed the 876A many times and never experienced this > behaviour. > Have you checked: > > - your hardware voltages > - all the connections to the 876A > - that the PGM pin was connected to ground > > This could also be bad luck, you can try to request a free sample from > microchip to get yourself a new 16F876A > > Kind regards, > > Frans Schreuder > > On 04/17/2012 04:24 PM, Alexandre Rosa wrote: > > Hey > > I have build a USBPICPROG through-hole version board and want to thank you > for the good job in this project. > > I was able to program a 16F877A without any problem but with a 16F876A the > programming has failed. > > 16/4/2012 13:50:32: Erasing before programming... > 16/4/2012 13:50:32: Erase OK > 16/4/2012 13:50:32: Programming the code area of the PIC... > 16/4/2012 13:51:05: Write Code memory OK > 16/4/2012 13:51:05: Programming the data area of the PIC... > 16/4/2012 13:51:05: Write Data memory OK > 16/4/2012 13:51:05: Verifying all areas of the PIC... > 16/4/2012 13:51:06: Verify code failed at 0x0. Read: 0xFF, Expected: 0x0A > 16/4/2012 13:51:06: Programming configuration area of the PIC... > 16/4/2012 13:51:06: Error programming config memory > 16/4/2012 13:51:06: Operations completed with errors/warnings > > In this case the 16F876A had been previous programmed with a PICKIT3 and > was erased or bad programmed by USBPICPROG and did not work after this try. > > I try an external 5V power supply to do the job of USB BUS supply with no > results. > > Any suggestions ? > > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free.http://p.sf.net/sfu/Boundary-dev2dev > > > > _______________________________________________ > Usbpicprog-technical mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > |
|
From: Frans S. <fra...@gm...> - 2012-04-18 08:12:41
|
Hello, The two devices use exactly the same algorithm and are also electrical identical. I have programmed the 876A many times and never experienced this behaviour. Have you checked: * your hardware voltages * all the connections to the 876A * that the PGM pin was connected to ground This could also be bad luck, you can try to request a free sample from microchip to get yourself a new 16F876A Kind regards, Frans Schreuder On 04/17/2012 04:24 PM, Alexandre Rosa wrote: > Hey > > I have build a USBPICPROG through-hole version board and want to thank > you for the good job in this project. > > I was able to program a 16F877A without any problem but with a 16F876A > the programming has failed. > > 16/4/2012 13:50:32: Erasing before programming... > 16/4/2012 13:50:32: Erase OK > 16/4/2012 13:50:32: Programming the code area of the PIC... > 16/4/2012 13:51:05: Write Code memory OK > 16/4/2012 13:51:05: Programming the data area of the PIC... > 16/4/2012 13:51:05: Write Data memory OK > 16/4/2012 13:51:05: Verifying all areas of the PIC... > 16/4/2012 13:51:06: Verify code failed at 0x0. Read: 0xFF, Expected: 0x0A > 16/4/2012 13:51:06: Programming configuration area of the PIC... > 16/4/2012 13:51:06: Error programming config memory > 16/4/2012 13:51:06: Operations completed with errors/warnings > > In this case the 16F876A had been previous programmed with a PICKIT3 > and was erased or bad programmed by USBPICPROG and did not work after > this try. > > I try an external 5V power supply to do the job of USB BUS supply with > no results. > > Any suggestions ? > > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev > > > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: Alexandre R. <ale...@gm...> - 2012-04-17 14:24:22
|
Hey I have build a USBPICPROG through-hole version board and want to thank you for the good job in this project. I was able to program a 16F877A without any problem but with a 16F876A the programming has failed. 16/4/2012 13:50:32: Erasing before programming... 16/4/2012 13:50:32: Erase OK 16/4/2012 13:50:32: Programming the code area of the PIC... 16/4/2012 13:51:05: Write Code memory OK 16/4/2012 13:51:05: Programming the data area of the PIC... 16/4/2012 13:51:05: Write Data memory OK 16/4/2012 13:51:05: Verifying all areas of the PIC... 16/4/2012 13:51:06: Verify code failed at 0x0. Read: 0xFF, Expected: 0x0A 16/4/2012 13:51:06: Programming configuration area of the PIC... 16/4/2012 13:51:06: Error programming config memory 16/4/2012 13:51:06: Operations completed with errors/warnings In this case the 16F876A had been previous programmed with a PICKIT3 and was erased or bad programmed by USBPICPROG and did not work after this try. I try an external 5V power supply to do the job of USB BUS supply with no results. Any suggestions ? |
|
From: Phil E. <spa...@ch...> - 2012-03-17 19:23:30
|
Frans Schreuder wrote:
> Dear Phil,
>
> The configure script should check for libusb-1.0
OK, I now see:
checking for LIBUSB... yes
(I suppose that didn't show up when I grep'd for libusb due to case.)
Now when I build it does -I/usr/include/libusb-1.0 . Maybe I didn't
run configure again after installing libusb, or something; it didn't
have that before.
Anyway, I now seem to have a functioning program.
Regards, Phil.
|
|
From: Frans S. <fra...@gm...> - 2012-03-16 23:31:17
|
Dear Phil, The configure script should check for libusb-1.0 but indeed libusb-1.0-0-dev is the package you will need. /usr/include/usb.h is from usb 0.12, that is the older version of libusb which can't be used anymore with usbpicprog. Kind regards, Frans Schreuder On 03/16/2012 09:03 PM, Phil Endecott wrote: > Dear Experts, > > Does anyone understand the requirements for libusb, specifically on Debian? > > As far as I can see, the configure script doesn't check for anything > related to libusb; it probably should. When I compile I get > > main.cpp:32:20: fatal error: libusb.h: No such file or directory > hardware.cpp:31:20: fatal error: libusb.h: No such file or directory > > packages.debian.org can find /usr/include/libusb-1.0/libusb.h in > package libusb-1.0-0-dev. Is this the right file, in which case > usbpicprog would benefit from -I/usr/include/libusb-1.0, or should it > instead be using /usr/include/usb.h (there is a cryptic comment about > this in the source)? A quick hack to try usb.h didn't work. > > Sorry if I am missing something obvious... > > > Regards, Phil. > > > > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: Phil E. <spa...@ch...> - 2012-03-16 20:03:23
|
Dear Experts, Does anyone understand the requirements for libusb, specifically on Debian? As far as I can see, the configure script doesn't check for anything related to libusb; it probably should. When I compile I get main.cpp:32:20: fatal error: libusb.h: No such file or directory hardware.cpp:31:20: fatal error: libusb.h: No such file or directory packages.debian.org can find /usr/include/libusb-1.0/libusb.h in package libusb-1.0-0-dev. Is this the right file, in which case usbpicprog would benefit from -I/usr/include/libusb-1.0, or should it instead be using /usr/include/usb.h (there is a cryptic comment about this in the source)? A quick hack to try usb.h didn't work. Sorry if I am missing something obvious... Regards, Phil. |
|
From: Phil E. <spa...@ch...> - 2012-03-11 23:16:44
|
Frans Schreuder wrote: > Dear phil, > > Unfortunately the wxwidgets library is not just used for the gui, but also > for loading the xml files with pic information. Aargh. Is there an older version of usbpicprog that uses wxWidgets 2.8? Would that work with the firmware in my device? I've already spent hours downloading and installing dependencies (e.g. to get a sufficiently-new version of intltool, it replaced my entire Perl installation!). Would it be easier to install it on my Mac? > The same way as you can build usbpicprog, it is also easy to build > wxwidgets 2.9 along with 2.8, they won't harm each other. > Then you can build usbpicprog as well and start usbpicprog as a command > line application. > It is probably possible to load the xml files without wxwidgets but not in > the current code. I'm curious to know why you would choose wxWidgets as an XML reader for C++, compared to e.g. RapidXML or libxml++. Regards, Phil. |
6 messages has been excluded from this view by a project administrator.
