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-03-11 22:44:52
|
Dear phil, Unfortunately the wxwidgets library is not just used for the gui, but also for loading the xml files with pic information. 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. Kind regards, Frans Schreuder Op 11 mrt. 2012 23:38 schreef "Phil Endecott" < spa...@ch...> het volgende: > Dear Experts, > > I recently received my usbpicprog device and would like to use it with > my Debian system. After various snags I've now discovered that I need > wxWidgets version 2.9.0 or later. As far as I can tell, 2.9 is not > available on any Debian version, and even if they get around to > packaging it soon that won't help me on my "stable" system. > > I don't need the wxWidgets GUI. I'm a cmdline sort of person. I like > Makefiles and scripts, not GUIs. All that I want from this thing is a > simple command-line tool that will talk to the hardware to program a > chip. It seems that such a command-line tool is included, but I don't > immediately see a way to compile it separately from all the wx stuff. > I was hoping for e.g. "./configure --without-wxwidgets". Is there such > a thing? Is it just a case of extracting a few source files and > compiling them separately? > > Thanks for any suggestions. > > > Regards, Phil. > > > > > > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > |
|
From: Phil E. <spa...@ch...> - 2012-03-11 22:38:28
|
Dear Experts, I recently received my usbpicprog device and would like to use it with my Debian system. After various snags I've now discovered that I need wxWidgets version 2.9.0 or later. As far as I can tell, 2.9 is not available on any Debian version, and even if they get around to packaging it soon that won't help me on my "stable" system. I don't need the wxWidgets GUI. I'm a cmdline sort of person. I like Makefiles and scripts, not GUIs. All that I want from this thing is a simple command-line tool that will talk to the hardware to program a chip. It seems that such a command-line tool is included, but I don't immediately see a way to compile it separately from all the wx stuff. I was hoping for e.g. "./configure --without-wxwidgets". Is there such a thing? Is it just a case of extracting a few source files and compiling them separately? Thanks for any suggestions. Regards, Phil. |
|
From: Frans S. <fra...@gm...> - 2012-02-17 08:27:45
|
Hello Marcel, It's nice to hear that it works for you. Some computers just have less stable USB voltages. For those who suffer from unstable +5V, you can also add an external +5V to the target microcontroller's VDD pin, only make sure that you don't disable your MCLR pin in that case. Regards, Frans On 02/16/2012 10:52 PM, Marcel Konrad wrote: > Hello Frans, > > I just wanted to report back that adding a 470uF cap to VDD of P1, as > Marcelo suggested, did the trick. Now I was able to programm a 16F628A > just fine. For me the mentioned extra 100nF at the gate of Q1 was not > needed. > > Best > Marcel > > Am 11.04.2011 10:24, schrieb Marcel Konrad: >> Hello Frans, >> >> the verify step fails, as Marcelo pointed out in his mail today. >> ------------ >> Mo 11 Apr 2011 10:10:10 CEST: Löschen vor dem Programmieren >> Mo 11 Apr 2011 10:10:10 CEST: Löschen OK >> Mo 11 Apr 2011 10:10:10 CEST: Programmieren des Programmbereiches des PIC ... >> Mo 11 Apr 2011 10:10:16 CEST: Schreiben des Programmspeichers ist OK >> Mo 11 Apr 2011 10:10:16 CEST: Programmieren des Datenbereiches des PIC ... >> Mo 11 Apr 2011 10:10:16 CEST: Schreiben des Datenspeichers ist OK >> Mo 11 Apr 2011 10:10:16 CEST: Vergleiche alle Bereiche des PIC ... >> Mo 11 Apr 2011 10:10:17 CEST: Vergleiche den ProgrammcodeErfolglos bei 0x0. >> Gelesen: 0xFF, Erwartet: 0x55 >> Mo 11 Apr 2011 10:10:17 CEST: Programmieren des Konfigurationsspeichers des PIC >> Mo 11 Apr 2011 10:10:17 CEST: Fehler beim Programmieren des >> Konfigurationsspeichers >> Mo 11 Apr 2011 10:10:17 CEST: Ablauf ohne Fehler/Warnungen ausgeführt >> ------------ >> this is the log. Is it possible to switch the language to english from within >> the software? Did not find a option. Would be easier for troubleshooting... >> >> In english the sequence would be: >> Delete OK -> Programming the program memory OK -> Programming the data memory >> OK -> verify all areas of the pic -> Verify failed at 0x0, read: 0xFF, >> expected: 0x55. >> >> So my programming fails right at the beginning, whereas Marcelo's fails when >> programming large programs to the PIC, if I have understood that correctly. >> >> Also the last message is a bit weird, because ist say: "actions performed >> without errors/warnings". I will have a look at the translation files ... >> >> Best regards >> Marcel >> >> On Sunday 10 April 2011 17:06:00 Frans Schreuder wrote: >>> Dear Marcel Konrad, >>> >>> Could you tell me which error you are getting while programming? >>> >>> Kind regards, >>> >>> Frans Schreuder >>> >>> On 04/10/2011 04:33 PM, Marcel Konrad wrote: >>>> Hey, >>>> >>>> I have build the through-hole Version of usbpicprog successfully and want >>>> to thank you for the good and hard work you have invested so far. >>>> >>>> I was able to program a 18F4550 without problems, but when I have tried a >>>> 16F628A the programming has failed. Both chips are autodetected just >>>> fine. I am using the zif-board to mount the pics. >>>> >>>> I measured all pins with the Input/Output Test from the Options menu and >>>> they are as following: >>>> MCLR 4,96/13,7 >>>> VDD 5,04 >>>> PGD 3,52/5,32 >>>> PGC 3,52/5,31 >>>> Hardware rev. of usbpicprog is 0.3.2 firmware 0.4.2-beta (tried 0.4.1 as >>>> well) >>>> >>>> Any suggestions where to go from here? >>>> >>>> Kind regards >>>> Marcel Konrad >>>> >>>> ------------------------------------------------------------------------- >>>> ----- Xperia(TM) PLAY >>>> It's a major breakthrough. An authentic gaming >>>> smartphone on the nation's most reliable network. >>>> And it wants your games. >>>> http://p.sf.net/sfu/verizon-sfdev >>>> _______________________________________________ >>>> Usbpicprog-technical mailing list >>>> Usb...@li... >>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical >> ------------------------------------------------------------------------------ >> Xperia(TM) PLAY >> It's a major breakthrough. An authentic gaming >> smartphone on the nation's most reliable network. >> And it wants your games. >> http://p.sf.net/sfu/verizon-sfdev >> _______________________________________________ >> Usbpicprog-technical mailing list >> Usb...@li... >> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: Marcel K. <mak...@gm...> - 2012-02-16 21:52:45
|
Hello Frans, I just wanted to report back that adding a 470uF cap to VDD of P1, as Marcelo suggested, did the trick. Now I was able to programm a 16F628A just fine. For me the mentioned extra 100nF at the gate of Q1 was not needed. Best Marcel Am 11.04.2011 10:24, schrieb Marcel Konrad: > Hello Frans, > > the verify step fails, as Marcelo pointed out in his mail today. > ------------ > Mo 11 Apr 2011 10:10:10 CEST: Löschen vor dem Programmieren > Mo 11 Apr 2011 10:10:10 CEST: Löschen OK > Mo 11 Apr 2011 10:10:10 CEST: Programmieren des Programmbereiches des PIC ... > Mo 11 Apr 2011 10:10:16 CEST: Schreiben des Programmspeichers ist OK > Mo 11 Apr 2011 10:10:16 CEST: Programmieren des Datenbereiches des PIC ... > Mo 11 Apr 2011 10:10:16 CEST: Schreiben des Datenspeichers ist OK > Mo 11 Apr 2011 10:10:16 CEST: Vergleiche alle Bereiche des PIC ... > Mo 11 Apr 2011 10:10:17 CEST: Vergleiche den ProgrammcodeErfolglos bei 0x0. > Gelesen: 0xFF, Erwartet: 0x55 > Mo 11 Apr 2011 10:10:17 CEST: Programmieren des Konfigurationsspeichers des PIC > Mo 11 Apr 2011 10:10:17 CEST: Fehler beim Programmieren des > Konfigurationsspeichers > Mo 11 Apr 2011 10:10:17 CEST: Ablauf ohne Fehler/Warnungen ausgeführt > ------------ > this is the log. Is it possible to switch the language to english from within > the software? Did not find a option. Would be easier for troubleshooting... > > In english the sequence would be: > Delete OK -> Programming the program memory OK -> Programming the data memory > OK -> verify all areas of the pic -> Verify failed at 0x0, read: 0xFF, > expected: 0x55. > > So my programming fails right at the beginning, whereas Marcelo's fails when > programming large programs to the PIC, if I have understood that correctly. > > Also the last message is a bit weird, because ist say: "actions performed > without errors/warnings". I will have a look at the translation files ... > > Best regards > Marcel > > On Sunday 10 April 2011 17:06:00 Frans Schreuder wrote: >> Dear Marcel Konrad, >> >> Could you tell me which error you are getting while programming? >> >> Kind regards, >> >> Frans Schreuder >> >> On 04/10/2011 04:33 PM, Marcel Konrad wrote: >>> Hey, >>> >>> I have build the through-hole Version of usbpicprog successfully and want >>> to thank you for the good and hard work you have invested so far. >>> >>> I was able to program a 18F4550 without problems, but when I have tried a >>> 16F628A the programming has failed. Both chips are autodetected just >>> fine. I am using the zif-board to mount the pics. >>> >>> I measured all pins with the Input/Output Test from the Options menu and >>> they are as following: >>> MCLR 4,96/13,7 >>> VDD 5,04 >>> PGD 3,52/5,32 >>> PGC 3,52/5,31 >>> Hardware rev. of usbpicprog is 0.3.2 firmware 0.4.2-beta (tried 0.4.1 as >>> well) >>> >>> Any suggestions where to go from here? >>> >>> Kind regards >>> Marcel Konrad >>> >>> ------------------------------------------------------------------------- >>> ----- Xperia(TM) PLAY >>> It's a major breakthrough. An authentic gaming >>> smartphone on the nation's most reliable network. >>> And it wants your games. >>> http://p.sf.net/sfu/verizon-sfdev >>> _______________________________________________ >>> Usbpicprog-technical mailing list >>> Usb...@li... >>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > ------------------------------------------------------------------------------ > Xperia(TM) PLAY > It's a major breakthrough. An authentic gaming > smartphone on the nation's most reliable network. > And it wants your games. > http://p.sf.net/sfu/verizon-sfdev > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: Frans S. <fra...@gm...> - 2012-01-28 22:21:57
|
Dear charles, It's quite some project that you are propposing here. Maybe it would be good to put your changes to the hardware and software on github so that i can also link to it. The i2c eeprom code has never been tested thoroughly so it could be very possible that it doesn't work that stable. I think we need to debug a lot there. Of course for a stand alone programmer, a lot of things will have to be implemeented in firmware, right now the firmware only programs blocks of 32 bytes or so. The higher levels have to be implemented completely. I am now very busy on another project so i am willing to help, but i can't spend so many hours on programming usbpicprog. When you need help regarding the software i can do things, i can also fix bugs but big changes i simply have no time for right now. I would like to see your schematics on github though! Kind regards, Frans Op 28 jan. 2012 19:04 schreef "Charles Kerr" <cha...@fr...> het volgende: > Hi Frans > > My aim is to modify the usbpicprog into a portable programmer so that I > can download my code into an external eeprom, remove the usbpicprog from > the pc, then program my target using the usbpicprog as a stand alone > programmer. > > I have added an eeprom (24LC64) to the usbpicprog board (I did forget the > 2 x 10k pull up resistors on the SCL and SDA lines but have added them as a > mod on the board), a pushbutton switch and a 5v regulator. As you can see > from the schematic I used the pic sda and scl lines for the eeprom and > changed the pgd and pgc lines to pins 17 and 18 respectively. I changed the > firmware to use rc6 and rc7 and can program external pics with no problem. > > Unfortunately I can not seem to program an external eeprom (connected to > pgd and pgc) or the on board eeprom (using sda and scl). monitoring with a > scope I am getting activily on the clock and data lines but I suspect my > timing is out. I have tried software and hardware I2C routines with no luck. > > I was thinking that if the usbpic prog did not detect an external pic, (or > one could have an option in the pc programming software) it could dump the > program memory, data memory and config bits to the eeprom. when the > pushutton is pressed, to read the data from the eprom as though it were > coming from the usb port and program the target. > > Unfortunately I am stuck and not too sure how to proceed. > > Do you have any advise and could you help with the firmware modifications. > > Kind Regards > > > Charles Kerr > ch...@cr... > > Cape Town > South Africa > > > > > > > ------------------------------------------------------------------------------ > Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-dev2 > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > |
|
From: Charles K. <cha...@fr...> - 2012-01-26 09:15:52
|
Hi Frans My aim is to modify the usbpicprog into a portable programmer so that I can download my code into an external eeprom, remove the usbpicprog from the pc, then program my target using the usbpicprog as a stand alone programmer. I have added an eeprom (24LC64) to the usbpicprog board (I did forget the 2 x 10k pull up resistors on the SCL and SDA lines but have added them as a mod on the board), a pushbutton switch and a 5v regulator. As you can see from the schematic I used the pic sda and scl lines for the eeprom and changed the pgd and pgc lines to pins 17 and 18 respectively. I changed the firmware to use rc6 and rc7 and can program external pics with no problem. Unfortunately I can not seem to program an external eeprom (connected to pgd and pgc) or the on board eeprom (using sda and scl). monitoring with a scope I am getting activily on the clock and data lines but I suspect my timing is out. I have tried software and hardware I2C routines with no luck. I was thinking that if the usbpic prog did not detect an external pic, (or one could have an option in the pc programming software) it could dump the program memory, data memory and config bits to the eeprom. when the pushutton is pressed, to read the data from the eprom as though it were coming from the usb port and program the target. Unfortunately I am stuck and not too sure how to proceed. Do you have any advise and could you help with the firmware modifications. Kind Regards Charles Kerr ch...@cr... Cape Town South Africa |
|
From: Frans S. <fra...@gm...> - 2012-01-21 16:25:22
|
Dear Matt, Thanks for the comment! I will add it to the supported devices list. Kind regards, Frans Schreuder On 01/20/2012 06:44 PM, Matt Hirsch wrote: > I'm reporting that I tested the PIC18F46J50 successfully. I've been able > to program and read code and ID with a 3.3v regulator on VDD, using > usbpicprog 0.4.2 64-bit on Fedora Linux, and firmware-0.4.2. I haven't > tried the erase function. > > Thanks again for an awesome project. > > Best, > Matt > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: Matt H. <mh...@me...> - 2012-01-20 18:00:16
|
I'm reporting that I tested the PIC18F46J50 successfully. I've been able to program and read code and ID with a 3.3v regulator on VDD, using usbpicprog 0.4.2 64-bit on Fedora Linux, and firmware-0.4.2. I haven't tried the erase function. Thanks again for an awesome project. Best, Matt |
|
From: Frans S. <fra...@gm...> - 2011-09-10 13:06:36
|
Hi, Nothing, just replace them! Good luck, Frans Schreuder Op 10 sep 2011 04:45 schreef "Renan Pascoal" <re...@gm...>: Hi, Can you tell me what configuration i have to arrange to change those BS170 into BC547 and BS250 into BC557. Because in my city haven't these MOSFETs to sell. I wait your answer, Att, Renan de Farias Gomes Pascoal ------------------------------------------------------------------------------ Malware Security Report: Protecting Your Business, Customers, and the Bottom Line. Protect your business and customers by understanding the threat from malware and how it can impact your online business. http://www.accelacomm.com/jaw/sfnl/114/51427462/ _______________________________________________ Usbpicprog-technical mailing list Usb...@li... https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: Renan P. <re...@gm...> - 2011-09-10 02:45:01
|
Hi, Can you tell me what configuration i have to arrange to change those BS170 into BC547 and BS250 into BC557. Because in my city haven't these MOSFETs to sell. I wait your answer, Att, Renan de Farias Gomes Pascoal |
|
From: Michael M. <meh...@gm...> - 2011-09-05 21:19:23
|
Hello Frans Schreuder, Yes you are right, i am using the student version (lite edition). I guess i have to purchase the full edition or try it for 60 days inorder to compile usbpicprog project. And i am thankful to your response. kindly regards, michael |
|
From: Frans S. <fra...@gm...> - 2011-09-04 21:36:28
|
Hi,
Are you using the full version of c18?
It's a known issue that the student version can't compile the firmware.
Kind regards,
Frans Schreuder
Op 4 sep 2011 23:31 schreef "Michael Mehari" <meh...@gm...>:
Hello everyone,
i am fun of pic microcontrollers and the project usbpicprog took my breath
and i am looking deep into it.
Because i had experience on the microchip usb stack, i put focus on the
firmware part of the project (i.e. firmware-0.4.2), selectively the
usbpicprog part of the firmware.
As the project is made in piklab i tried building it but it was not
successful. Here is the output i get
*MPLINK 4.37, Linker *
*Copyright (c) 1998-2010 Microchip Technology Inc. *
*Error - section '.code_usb9.o' can not fit the section. Section
'.code_usb9.o' length=0x000002e6 *
*Errors : 1*
after that i looked in to the map file successfully created before error
occured and here is an excerpt from it
* page 0x082a 0x7fff .cinit 0x082a 0x001a
*
* .code_prog.o 0x0844
0x5d6a*
* .code_prog_lolvl.o 0x65ae
0x0dc6*
* .code_upp.o 0x7374
0x0ada*
* *
it seems the object file prog.o from source code prog.c was very large (i.e.
size 0x5d6a) and when the linker tried puting everything together, there was
no space left in memory
and it makes sence to understand the problem that way. For completness, here
are comand line compiler and linker arguments
*
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=main.o main.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=usbdsc.o
usbdsc.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=interrupt.o
interrupt.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=usbmmap.o
usbmmap.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=usbgen.o
usbgen.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=usb9.o usb9.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=usbctrltrf.o
usbctrltrf.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=usbdrv.o
usbdrv.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=upp.o upp.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=prog.o prog.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=prog_lolvl.o
prog_lolvl.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mplink
/k/home/michael/Desktop/firmware-0.4.2/ rm18f4550.lkr
/l/home/michael/.wine/dosdevices/c:/MCC18/lib/ /ouc_code.cof /muc_code.map
main.o usbdsc.o interrupt.o usbmmap.o usbgen.o usb9.o usbctrltrf.o usbdrv.o
upp.o prog.o prog_lolvl.o
*
*
*
Next i moved to the MPLAB IDE to see if the problem was with piklab and here
is the output result i get
**
*
MPLINK 4.37, Linker
*
*
Copyright (c) 1998-2010 Microchip Technology Inc.
Error - section '.code_upp.o' can not fit the section. Section '.code_upp.o'
length=0x00000ce0
Errors : 1
and an excerpt from the map file created before error occured is as follows
page 0x082a 0x7fff .cinit 0x082a 0x001a
.code_prog.o 0x0844 0x615a
.code_prog_lolvl.o 0x699e 0x0de6
The above listing shows that there is difference in content between
comparable files with in the two IDE's (Piklab and MPLAB).
For completness, here are comand line compiler and linker arguments
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "interrupt.c"
-fo="interrupt.o" -D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "main.c" -fo="main.o"
-D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "prog.c" -fo="prog.o"
-D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "prog_lolvl.c"
-fo="prog_lolvl.o" -D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "upp.c" -fo="upp.o" -D__DEBUG
-Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "usb9.c" -fo="usb9.o"
-D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "usbctrltrf.c"
-fo="usbctrltrf.o" -D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "usbdrv.c" -fo="usbdrv.o"
-D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "usbdsc.c" -fo="usbdsc.o"
-D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "usbgen.c" -fo="usbgen.o"
-D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "usbmmap.c" -fo="usbmmap.o"
-D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mplink.exe" /l"C:\MCC18\lib" "rm18f4550.lkr"
"interrupt.o" "main.o" "prog.o" "prog_lolvl.o" "upp.o" "usb9.o"
"usbctrltrf.o" "usbdrv.o" "usbdsc.o" "usbgen.o" "usbmmap.o" /u_CRUNTIME
/u_DEBUG /z__MPLAB_BUILD=1 /z__MPLAB_DEBUG=1 /o"picusbprog_custom.cof"
/M"picusbprog_custom.map" /W
My question is that i know this program is a working system and for some
reason which i don't understand now, it is not working. Making the program
small only for selective pic ranges could have solved the problem. But i
don't think that is the reason behind this. Could you please help me
understand why i am having such difficulty?
kindly regards,
michael
*
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Usbpicprog-technical mailing list
Usb...@li...
https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
|
|
From: Michael M. <meh...@gm...> - 2011-09-04 21:31:35
|
Hello everyone,
i am fun of pic microcontrollers and the project usbpicprog took my breath
and i am looking deep into it.
Because i had experience on the microchip usb stack, i put focus on the
firmware part of the project (i.e. firmware-0.4.2), selectively the
usbpicprog part of the firmware.
As the project is made in piklab i tried building it but it was not
successful. Here is the output i get
*MPLINK 4.37, Linker *
*Copyright (c) 1998-2010 Microchip Technology Inc. *
*Error - section '.code_usb9.o' can not fit the section. Section
'.code_usb9.o' length=0x000002e6 *
*Errors : 1*
after that i looked in to the map file successfully created before error
occured and here is an excerpt from it
* page 0x082a 0x7fff .cinit 0x082a 0x001a
*
* .code_prog.o 0x0844
0x5d6a*
* .code_prog_lolvl.o 0x65ae
0x0dc6*
* .code_upp.o 0x7374
0x0ada*
* *
it seems the object file prog.o from source code prog.c was very large (i.e.
size 0x5d6a) and when the linker tried puting everything together, there was
no space left in memory
and it makes sence to understand the problem that way. For completness, here
are comand line compiler and linker arguments
*
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=main.o main.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=usbdsc.o
usbdsc.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=interrupt.o
interrupt.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=usbmmap.o
usbmmap.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=usbgen.o
usbgen.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=usb9.o usb9.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=usbctrltrf.o
usbctrltrf.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=usbdrv.o
usbdrv.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=upp.o upp.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=prog.o prog.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mcc18
-I/home/michael/Desktop/firmware-0.4.2/
-I/home/michael/.wine/dosdevices/c:/MCC18/h/ -p 18f2550 -fo=prog_lolvl.o
prog_lolvl.c
wine /home/michael/.wine/dosdevices/c:/MCC18/bin/mplink
/k/home/michael/Desktop/firmware-0.4.2/ rm18f4550.lkr
/l/home/michael/.wine/dosdevices/c:/MCC18/lib/ /ouc_code.cof /muc_code.map
main.o usbdsc.o interrupt.o usbmmap.o usbgen.o usb9.o usbctrltrf.o usbdrv.o
upp.o prog.o prog_lolvl.o
*
*
*
Next i moved to the MPLAB IDE to see if the problem was with piklab and here
is the output result i get
**
*
MPLINK 4.37, Linker
*
*
Copyright (c) 1998-2010 Microchip Technology Inc.
Error - section '.code_upp.o' can not fit the section. Section '.code_upp.o'
length=0x00000ce0
Errors : 1
and an excerpt from the map file created before error occured is as follows
page 0x082a 0x7fff .cinit 0x082a 0x001a
.code_prog.o 0x0844 0x615a
.code_prog_lolvl.o 0x699e 0x0de6
The above listing shows that there is difference in content between
comparable files with in the two IDE's (Piklab and MPLAB).
For completness, here are comand line compiler and linker arguments
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "interrupt.c"
-fo="interrupt.o" -D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "main.c" -fo="main.o"
-D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "prog.c" -fo="prog.o"
-D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "prog_lolvl.c"
-fo="prog_lolvl.o" -D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "upp.c" -fo="upp.o" -D__DEBUG
-Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "usb9.c" -fo="usb9.o"
-D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "usbctrltrf.c"
-fo="usbctrltrf.o" -D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "usbdrv.c" -fo="usbdrv.o"
-D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "usbdsc.c" -fo="usbdsc.o"
-D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "usbgen.c" -fo="usbgen.o"
-D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F2550 "usbmmap.c" -fo="usbmmap.o"
-D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Executing: "C:\MCC18\bin\mplink.exe" /l"C:\MCC18\lib" "rm18f4550.lkr"
"interrupt.o" "main.o" "prog.o" "prog_lolvl.o" "upp.o" "usb9.o"
"usbctrltrf.o" "usbdrv.o" "usbdsc.o" "usbgen.o" "usbmmap.o" /u_CRUNTIME
/u_DEBUG /z__MPLAB_BUILD=1 /z__MPLAB_DEBUG=1 /o"picusbprog_custom.cof"
/M"picusbprog_custom.map" /W
My question is that i know this program is a working system and for some
reason which i don't understand now, it is not working. Making the program
small only for selective pic ranges could have solved the problem. But i
don't think that is the reason behind this. Could you please help me
understand why i am having such difficulty?
kindly regards,
michael
*
|
|
From: Frans S. <fra...@gm...> - 2011-08-23 17:14:39
|
Ok, good news! I was already thinking of a good answer. Kind regards, Frans schreuder Op 23 aug 2011 18:25 schreef "David Collins" <da...@in...>: Just to follow up on this ... On Tue, Aug 23, 2011 at 12:29:14AM +0100, David Collins wrote: > I'm trying to burn the bootloader ... It hadn't occured to me that I could use piklab itself to program the PIC. I didn't realise it supported JDM-style programmers. Selecting the "Direct programmer" option and programming, however, it seems to have succeeded (although I haven't verified this yet.) So, in retrospect, this was slightly off-topic - apologies. David Collins GPG id 646C8A43 ------------------------------------------------------... Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ Usbpicprog-technical mailing list Usbpicprog-technic... |
|
From: David C. <da...@in...> - 2011-08-23 16:25:27
|
Just to follow up on this ... On Tue, Aug 23, 2011 at 12:29:14AM +0100, David Collins wrote: > I'm trying to burn the bootloader to the PIC18F2550 using a JDM programmer and the picprog software (http://hyvatti.iki.fi/~jaakko/pic/picprog.html ) on Linux, but I am having problems. It hadn't occured to me that I could use piklab itself to program the PIC. I didn't realise it supported JDM-style programmers. Selecting the "Direct programmer" option and programming, however, it seems to have succeeded (although I haven't verified this yet.) So, in retrospect, this was slightly off-topic - apologies. David Collins GPG id 646C8A43 |
|
From: Frans S. <fra...@gm...> - 2011-08-23 10:22:46
|
Dear Virender Bangar, The PIC18F2550 has a reserved space (address 0 to 0x7FF) for the bootloader. This is the place where the bootloader is written the first time. Once this bootloader is in the flash of the pic, it can connect to usb and write the other code space (0x800 and beyond) for the actual firmware. The bootloader can be selected through the jumper settings. If you look at the firmware file, you will see (apart from some jump instructions which are ignored by the bootloader) no instructions in the area 0x000-0x7FF. I hope this explains it. Kind regards, Frans Schreuder On 08/23/2011 11:41 AM, virender bangar wrote: > Name: virender bangar > > Email: vir...@ya... > > Subject: boot loader and firmware > > Message: Hello Sir > I would like know that in 18f2550 weather we need to burn the boot > loader or firmware.As you said that boot loader has to be burnt once > then if after that i will try to burn the firmware , the boot loader > file will get replaced... > > please make the difference clear to me where to use boot loader and > where to use firmware > > > |
|
From: David C. <da...@in...> - 2011-08-22 21:58:33
|
I'm trying to burn the bootloader to the PIC18F2550 using a JDM programmer and the picprog software (http://hyvatti.iki.fi/~jaakko/pic/picprog.html ) on Linux, but I am having problems. Running picprog --burn -i Boot.hex -p /dev/ttyS0 I get "Boot.hex:146:invalid input line. Are you sure this is an 8 or 16 bit intel hex file?" This is an 32-bit hex format, right? My understanding is that picprog should be able to handle these files. I have tried the Boot.hex file in the latest SVN, as well as recompiling in piklab using the MCC18 libraries. Even though the project builds/compiles succesfully in piklab, I get the same error as above when I try to actually burn the bootloader to the PIC. I realise this is quite possibly a picprog program rather than a problem with the bootloader, but I thought someone here might be able to offer some input (+ picprog doesn't have a mailing list). David Collins GPG id 646C8A43 |
|
From: Frans S. <fra...@gm...> - 2011-08-05 06:38:10
|
If usbpicprog runs, it will probably also work with the programmer. If it doesn't connect to the programmer immediately, try running the program as root. In that case you will have to play around with udev rules, see http://usbpicprog.org/?page_id=13 Frans On 08/05/2011 03:13 AM, Matt Hirsch wrote: > I've used usbpicprog with fedora for quite awhile without problems. > > If you don't want to install multiple versions for wxWidgets (Fedora > 13/14/15 are still shipping 2.8.x) you can build wxWidgets without > installing it, and then specify the wxwidgets location in the > usbpicprog configure script. configure --help to find the option. > > Matt > > On 08/04/2011 11:35 PM, william estrada wrote: >> Hi group, >> >> I have installed usbpicprog on my laptop running Fedora 13. It was >> not quick! >> For the list here is what I did to get it installed: >> >> >> Yum install libusb\* >> Download current wxWidget (wxWidgets-2.9.1.tar.bz2 ) >> tar jxf wxWidgets-2.9.1.tar.bz2 >> cd tar jxf wxWidgets-2.9.1 >> configure >> make >> sudo make install >> sudo ldconfig >> Download usbpicprog source from SourceForge. >> configure >> make >> sudo make install >> export LD_LIBRARY_PATH=/usr/local/lib/:/usr/lib64/ >> >> now usbpicprog should run? >> >> I will know if it works when I get the hardware delivered. The >> program runs >> but I don't know if it works. >> >> >> >> >> >> -- >> William Estrada >> Mt Umunhum, CA, USA >> HTTP://64.124.13.3 ( Mt-Umunhum-Wireless.net ) >> Skype: MrUmunhum >> >> >> ------------------------------------------------------------------------------ >> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA >> The must-attend event for mobile developers. Connect with experts. >> Get tools for creating Super Apps. See the latest technologies. >> Sessions, hands-on labs, demos & much more. Register early & save! >> http://p.sf.net/sfu/rim-blackberry-1 >> >> >> _______________________________________________ >> Usbpicprog-technical mailing list >> Usb...@li... >> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > > > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: Matt H. <mh...@me...> - 2011-08-05 01:28:56
|
I've used usbpicprog with fedora for quite awhile without problems. If you don't want to install multiple versions for wxWidgets (Fedora 13/14/15 are still shipping 2.8.x) you can build wxWidgets without installing it, and then specify the wxwidgets location in the usbpicprog configure script. configure --help to find the option. Matt On 08/04/2011 11:35 PM, william estrada wrote: > Hi group, > > I have installed usbpicprog on my laptop running Fedora 13. It was > not quick! > For the list here is what I did to get it installed: > > > Yum install libusb\* > Download current wxWidget (wxWidgets-2.9.1.tar.bz2 ) > tar jxf wxWidgets-2.9.1.tar.bz2 > cd tar jxf wxWidgets-2.9.1 > configure > make > sudo make install > sudo ldconfig > Download usbpicprog source from SourceForge. > configure > make > sudo make install > export LD_LIBRARY_PATH=/usr/local/lib/:/usr/lib64/ > > now usbpicprog should run? > > I will know if it works when I get the hardware delivered. The > program runs > but I don't know if it works. > > > > > > -- > William Estrada > Mt Umunhum, CA, USA > HTTP://64.124.13.3 ( Mt-Umunhum-Wireless.net ) > Skype: MrUmunhum > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos& much more. Register early& save! > http://p.sf.net/sfu/rim-blackberry-1 > > > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: william e. <MrU...@cr...> - 2011-08-04 23:17:44
|
Hi group,
I have installed usbpicprog on my laptop running Fedora 13. It was
not quick!
For the list here is what I did to get it installed:
Yum install libusb\*
Download current wxWidget (wxWidgets-2.9.1.tar.bz2 )
tar jxf wxWidgets-2.9.1.tar.bz2
cd tar jxf wxWidgets-2.9.1
configure
make
sudo make install
sudo ldconfig
Download usbpicprog source from SourceForge.
configure
make
sudo make install
export LD_LIBRARY_PATH=/usr/local/lib/:/usr/lib64/
now usbpicprog should run?
I will know if it works when I get the hardware delivered. The program runs
but I don't know if it works.
--
William Estrada
Mt Umunhum, CA, USA
HTTP://64.124.13.3 ( Mt-Umunhum-Wireless.net )
Skype: MrUmunhum
|
|
From: Jovertson A. D. <jov...@gm...> - 2011-08-03 22:58:39
|
Dear sir Frans, Thank you very much for the very informative reply. Best Regards, Jovertson On Wed, Aug 3, 2011 at 2:42 PM, Frans Schreuder <fra...@gm...>wrote: > ** > Dear Jovertson, > > Once your usbpicprog is functioning, and it has the bootloader + firmware > loaded, it is able to program any other PIC using it's output connector. > Usually the 16F devices are programmed without a bootloader (you just write > the main program using usbpicprog) but of course if you have a bootloader > for the 877A you can program the bootloader using usbpicprog as well. > The bootloader from usbpicprog is of course not usable for the 16F877A > since it is a complete different processor and it doesn't have usb. > > Kind regards, > > Frans Schreuder > > > On 08/03/2011 03:17 AM, Jovertson A. Damo wrote: > > If i had already Done all the necessary procedures in creating and the > UsbPicProg is fucntioning. Now, I will then use this to program other PIC > models let say PIC16F877A but how can i download or load bootloader of the > PIC16F877A using USBPICPROG or Is it Possible to use UsbPICProg to download > the PIC16F877A Bootloader? > > Thank you in Advance. > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save!http://p.sf.net/sfu/rim-blackberry-1 > > > _______________________________________________ > Usbpicprog-technical mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > |
|
From: Frans S. <fra...@gm...> - 2011-08-03 06:43:13
|
Dear Jovertson, Once your usbpicprog is functioning, and it has the bootloader + firmware loaded, it is able to program any other PIC using it's output connector. Usually the 16F devices are programmed without a bootloader (you just write the main program using usbpicprog) but of course if you have a bootloader for the 877A you can program the bootloader using usbpicprog as well. The bootloader from usbpicprog is of course not usable for the 16F877A since it is a complete different processor and it doesn't have usb. Kind regards, Frans Schreuder On 08/03/2011 03:17 AM, Jovertson A. Damo wrote: > If i had already Done all the necessary procedures in creating and the > UsbPicProg is fucntioning. Now, I will then use this to program other > PIC models let say PIC16F877A but how can i download or load > bootloader of the PIC16F877A using USBPICPROG or Is it Possible to use > UsbPICProg to download the PIC16F877A Bootloader? > > Thank you in Advance. > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > > > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: Jovertson A. D. <jov...@gm...> - 2011-08-03 01:17:10
|
If i had already Done all the necessary procedures in creating and the UsbPicProg is fucntioning. Now, I will then use this to program other PIC models let say PIC16F877A but how can i download or load bootloader of the PIC16F877A using USBPICPROG or Is it Possible to use UsbPICProg to download the PIC16F877A Bootloader? Thank you in Advance. |
|
From: Joe W. <jwh...@ho...> - 2011-06-19 05:42:48
|
My current goal is to have a USB-based programmer that can handle as many serial protocols as possible for device programming or interfacing. That, or have a hand full of different cheaply-made programmers. This lead to researching the different boards and figuring out how they work which lead to both thinking of other ways and searching for parts sources. For example, I found the 'K105Z20Y5VF5TH5' number for a cheap 1 microfarad capacitor (13 cents even in singles...). It is 5mm tall so pretty small as well for a through-hole part. Anyone interested in alternate sources for parts? I'm trying to compile a list of the prices and sites that sell equivalent/compatible parts for projects like this one. The parts numbers from different manufactures that would also work are probably useful as well. It's is borderline advertising for the companies I find, so I'm asking if it's OK first. It's not like we haven't heard of more than half of them, though! ;) |
|
From: Marcelo M. <mm...@ho...> - 2011-04-15 22:47:48
|
Dear Frans:
I have tried your new firmware.
I still have errors when programming the PIC16F877A, at random locations each time. However, I noticed that the pattern changed.
Instead of FF 3F repeated 8 times and then 00 00 another 8 times, now I only see FF 3F repeated 8 times. No more 00 00.
I do not know if this may shed some light... just wanted to share my findings.
Thank you.
Best regards
Marcelo
Date: Fri, 15 Apr 2011 11:09:41 +0200
From: fra...@gm...
To: usb...@li...
Subject: Re: [Usbpicprog-technical] Unstability when programing large pieces of code
Dear Fatih,
It would be great if you would test this on your hardware.
If this doesn't help, the only other delay that can be causing the
error is the one in the erase procedure. Could you also try to make
that one longer?
Regards,
Frans
On 04/15/2011 10:50 AM, fatih gokce wrote:
Dear All,
Since our hardware is not usbpicprog hw i could not try Frans's
new firmware.
As far as i see, Frans changed two lines in prog.c in terms of
timing:
1- in
case P16F87X: //same as P16F62X
case P16F84A: //same as P16F62X
case P16F62XA: //same as P16F62X
case P16F62X:
case P12F629:
case P12F61X:
of write_code function
DelayMs(2); -> DelayMs(10);
2- in case P16F87XA: of write_code function DelayMs(8); ->
DelayMs(16);
Frans, if there is something that i missed please correct me.
I am planning to make these changes in our firmware without
touching original delayMs function
(while((tick-lasttick)<cnt)continue;) and test it with 16F877
(not 877A). But i hope i can do it in weekend.
All the best,
Fatih.
On Fri, Apr 15, 2011 at 9:56 AM, Frans
Schreuder <fra...@gm...>
wrote:
Dear Marcel,
It seems that Fatih solved the issue (at least for the 16F877)
by adding
more delay. I have now added more delay in the programming
routine only,
not doubled the delay-routine as Fatih did, but it should do
the same
trick. Maybe something went wrong during erase, I'll try and
see if
doubling the erase time could help.
Regards,
Frans
On 04/14/2011 11:45 PM, Marcel Konrad wrote:
> Dear Frans,
>
> I have tried your new firmware, but it didn't change
anything for me. Still the
> same error. I was hoping that this issue could be
solved in software, but now
> I think that I will try Marcelo's suggestion and add
a 470u cap. Will report
> back when I tried that.
>
> Kind regards
>
> Marcel
>
> Am Mittwoch, 13. April 2011, 16:32:28 schrieb Frans
Schreuder:
>> Dear Fatih,
>>
>> I have increased the delay for the given
processors in the current git
>> repository. Could you upgrade your firmware with
the file below?
>> https://github.com/fransschreuder/usbpicprog/raw/master/trunk/uc_code/uc_co
>> de.hex
>>
>> Kind regards,
>>
>> Frans Schreuder
>>
>> On 04/11/2011 08:17 PM, fatih gokce wrote:
>>> Dear all,
>>> We faced with the same problem for 16F877 and
it is solved by the
>>> following change in DelayMs routine of
interrupt.c (in firmware)
>>>
>>> while((tick-lasttick)<(2*cnt))continue;
>>>
>>> Since our hardware is not exactly the same
hardware of usbpicprog (it
>>> is compatible with gtp-usb lite and has a 12
Mhz xtal ), I thought
>>> that it was only our problem. But after
seeing last messages of Marcel
>>> and Marcelo I want to share our solution.
>>>
>>> Frans, you are saying that you have tried
more delays in programming
>>> sequence but I do not know the length of your
additional delays and
>>> maybe you can also try 2*cnt solution. You
will notice but I should
>>> also indicate that this change is
unnecessarily affecting the
>>> programming times of all PICs.
>>>
>>> I should also note that while compiling the
firmware with MPLAB we had
>>> to comment out some part of the code in
prog.c (related to the PICs we
>>> are not planning to use), since it was not
fitting into the program
>>> memory of 18F2550.
>>>
>>> Kindest regards,
>>> Fatih.
>>>
>>>
>>> On Mon, Apr 11, 2011 at 5:38 PM, Marcelo
Maggi <mm...@ho...
>>>
>>> <mailto:mm...@ho...>>
wrote:
>>> Thank you Frans for your prompt reply.
>>>
>>> I fully agree that the noise comes from
the USB power line, since
>>> I can see it even with the programmer
disconnected. What I also
>>> noticed is that the mosfet is somehow
amplifying the noise, that
>>> is the reason why I added a 100nF
capacitor at the gate, besides
>>> the large one directly on the Vdd line
after the mosfet. The large
>>> current as well as the time constant
introduced by this capacitor
>>> were the concerns I had at the beginning,
so I started testing
>>> with lower values until I reached 470 uF,
which seems a good
>>> compromise between noise reduction and
unwanted side effects.
>>>
>>> Unfortunately this is not a solution for
the PIC16F877A... it
>>> keeps showing the erratic behavior I
described in my previous
>>> message.
>>>
>>> I will appreciate if you could let me
know if you find a solution
>>> in the future... I will keep
experimenting from my side and let
>>> you know any progress.
>>>
>>> Thank you again.
>>>
>>> Best regards
>>>
>>> Marcelo Maggi
>>>
>>>
---------------------------------------------------------------------
>>> --- Date: Mon, 11 Apr 2011 08:58:30 +0200
>>> From: fra...@gm...
<mailto:fra...@gm...>
>>> To: usb...@li...
>>> <mailto:usb...@li...>
>>> Subject: Re: [Usbpicprog-technical]
Unstability when programing
>>> large pieces of code
>>>
>>>
>>> Dear Marcelo Maggi,
>>>
>>> I have indeed noticed this behaviour
before, but not for all pic
>>> devices. It seems to happen only on some
revisions of pics and it
>>> is very unpredictable. It also depends on
the computer you are
>>> using it on. I have been trying to add
more delays in the
>>> programming sequence, but that also
didn't seem to help much. At
>>> least it is good to hear that there is a
solution for the
>>> behaviour for the 628A.
>>> The funny thing is that the +5V is
directly obtained from the usb
>>> power line of the computer and is only
switched by one mosfet. The
>>> noise seems to come from the usb port in
most of the cases. Also
>>> on the programmer, the +5V is stabilized
with 4x 100nF and one
>>> time 100nF after the mosfet directly on
the VDD pin of the output
>>> port. A 470uF capacitor could do the job
but also introduces a
>>> large current while switching the VDD pin
on (there is no current
>>> limiter) but if it works, there is no
problem!
>>>
>>> Kind regards,
>>>
>>> Frans Schreuder
>>>
>>> On 04/11/2011 04:48 AM, Marcelo Maggi
wrote:
>>> Dear Frans:
>>>
>>> Thank you for this excellent
programmer; I built it and I am
>>> currently running the latest beta
version (0.4.2), both
>>> firmware and software (AMD64
version).
>>>
>>> I have been through a few issues;
while I solved some of them,
>>> I need your support with one.
>>>
>>> First thing I noticed was that I had
trouble when trying to
>>> program the PIF16F628A using more
than half of the program
>>> memory. The programming cycle goes
OK, but during the verify
>>> step there were problems reported
(byte read different from
>>> what was expected). It used to happen
at different parts of
>>> the code, and eventually I could have
a few successful
>>> attempts. Trying to find the cause of
the problem, I noticed
>>> that Vdd (5 volts) was very noisy; I
added a large capacitor
>>> (470 uF/16v) between Vdd and GND at
the connector to the ZIF
>>> board (P1), and a 0.1 uF at the gate
of Q3 (BS250). With Vdd
>>> now much cleaner, I can program the
PIC16F628A with no problem
>>> each and every time. This may help
reply the question from
>>> another user in this forum (posted on
April 10).
>>>
>>> Now, I am trying to program larger
PICs... I tried with the
>>> PIC16F877A, filling almost all of the
program memory. Now, I
>>> have the same problem again; while
verifying there are errors
>>> at different points of the program
each time, with a few
>>> successful attempts. Further
stabilization of Vdd does not
>>> help. What I noticed is that only a
small portion of the
>>> program is corrupted when it fails to
verify. It may happen at
>>> different parts of the code each
time, but the wrong sequence
>>> is always the same:
>>>
>>> FF 3F FF 3F FF 3F FF 3F FF 3F FF 3F
FF 3F FF 3F 00 00 00 00 00
>>> 00 00 00 00 00 00 00 00 00 00 00
>>>
>>> After this sequence, the program
continues with the right code.
>>>
>>> Have you experienced this before? Any
clue of what could be
>>> the reason with the information
given?
>>>
>>> Just for your reference, the same
happens with the latest
>>> stable version 0.4.1.
>>>
>>> Thank you in advance for your
ideas...
>>>
>>> Best regards
>>>
>>> Marcelo Maggi
>>>
>>>
>>>
-----------------------------------------------------------------
>>> ------------- Xperia(TM) PLAY
>>> It's a major breakthrough. An
authentic gaming
>>> smartphone on the nation's most
reliable network.
>>> And it wants your games.
>>> http://p.sf.net/sfu/verizon-sfdev
>>>
>>>
>>>
_______________________________________________
>>> Usbpicprog-technical mailing list
>>> Usb...@li...
>>> <mailto:Usb...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technica
>>> l
>>>
>>>
---------------------------------------------------------------------
>>> --------- Xperia(TM) PLAY It's a major
breakthrough. An authentic
>>> gaming smartphone on the nation's most
reliable network. And it
>>> wants your games. http://p.sf.net/sfu/verizon-sfdev
>>>
>>>
_______________________________________________
>>> Usbpicprog-technical mailing list
>>> Usb...@li...
>>> <mailto:Usb...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>>>
>>>
---------------------------------------------------------------------
>>> --------- Xperia(TM) PLAY
>>> It's a major breakthrough. An authentic
gaming
>>> smartphone on the nation's most reliable
network.
>>> And it wants your games.
>>> http://p.sf.net/sfu/verizon-sfdev
>>>
_______________________________________________
>>> Usbpicprog-technical mailing list
>>> Usb...@li...
>>> <mailto:Usb...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>>>
>>>
-------------------------------------------------------------------------
>>> ----- Xperia(TM) PLAY
>>> It's a major breakthrough. An authentic
gaming
>>> smartphone on the nation's most reliable
network.
>>> And it wants your games.
>>> http://p.sf.net/sfu/verizon-sfdev
>>>
>>>
>>>
_______________________________________________
>>> Usbpicprog-technical mailing list
>>> Usb...@li...
>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>
>
------------------------------------------------------------------------------
> Benefiting from Server Virtualization: Beyond Initial
Workload
> Consolidation -- Increasing the use of server
virtualization is a top
> priority.Virtualization can reduce costs, simplify
management, and improve
> application availability and disaster protection.
Learn more about boosting
> the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization
is a top
priority.Virtualization can reduce costs, simplify management,
and improve
application availability and disaster protection. Learn more
about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Usbpicprog-technical mailing list
Usb...@li...
https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Usbpicprog-technical mailing list
Usb...@li...
https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Usbpicprog-technical mailing list
Usb...@li...
https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
6 messages has been excluded from this view by a project administrator.
