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...> - 2020-03-12 17:41:57
|
Dear Neil, Thanks for the message. Could you fork the github project and commit the changed xml file, then I can merge it back to the official repo. If that is too much work you can also send me the xml so I can commit the changes. Regards, Frans Op do 12 mrt. 2020 18:16 schreef Neil Darlow via Usbpicprog-technical < usb...@li...>: > Hi Frans, > > I browsed the source code and determined, as you did, that it was a > problem with the XML file. > > I reconciled the XML file with the PIC18LF26K22 Data Sheet and found a > number of errors and omissions (things like EEPROM size, missing protection > block settings etc.). > > I've managed to create a working XML file that should suit my needs. Given > the diversity of the PIC ecosystem, if you ever decide to revisit the > project, it would be an idea to create the XML files from Microchip header > files using an automated mechanism. > > Regards, > Neil Darlow > > On Thu, 2020-03-12 at 11:53 +0100, Frans Schreuder wrote: > > Dear Neil Darlow, > > It has been a long term since I worked on usbpicprog. I guess there is a > problem in the xml file for the PIC18LF26K22 or it's interpretation. > > I will certainly not harm to continue using the application, however I > can't guarantee that the programming of this device will be 100% successful. > > Regards, > > Frans > On 3/12/20 11:17 AM, Neil Darlow via Usbpicprog-technical wrote: > > Hi, > > I am using usbpicprog from the Ubuntu PPA at version 1.0.5-4 amd64. > > The device I am working with, a PIC18LF26K22, produces the following > assertion when the device is selected. > > > pictype.h(433): assert "acc <= nbits" failed in GetBitSize(). > > > Selecting a PIC18F26K22 (the 5V powered part) does not generate this > assertion. > > The assertion dialog presents the options to Stop or Continue so is this > assertion non-fatal and am I OK to continue using the program? > > Regards, > Neil Darlow > > -- > > > Sent with Evolution Mail on Linux Mint 19.3 Tricia. > > > > _______________________________________________ > > Usbpicprog-technical mailing list > > Usb...@li... > > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > > _______________________________________________ > > Usbpicprog-technical mailing list > > Usb...@li... > > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > > -- > > Sent with Evolution Mail on Linux Mint 19.3 Tricia. > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > |
|
From: Neil D. <ne...@da...> - 2020-03-12 17:16:04
|
Hi Frans, I browsed the source code and determined, as you did, that it was a problem with the XML file. I reconciled the XML file with the PIC18LF26K22 Data Sheet and found a number of errors and omissions (things like EEPROM size, missing protection block settings etc.). I've managed to create a working XML file that should suit my needs. Given the diversity of the PIC ecosystem, if you ever decide to revisit the project, it would be an idea to create the XML files from Microchip header files using an automated mechanism. Regards,Neil Darlow On Thu, 2020-03-12 at 11:53 +0100, Frans Schreuder wrote: > Dear Neil Darlow, > > It has been a long term since I worked on usbpicprog. I guess > there is a problem in the xml file for the PIC18LF26K22 or it's > interpretation. > > I will certainly not harm to continue using the application, > however I can't guarantee that the programming of this device > will > be 100% successful. > > Regards, > > Frans > > > > On 3/12/20 11:17 AM, Neil Darlow via > Usbpicprog-technical wrote: > > > > > > > > Hi, > > > > > > > > I am using usbpicprog from the Ubuntu PPA at version 1.0.5-4 > > amd64. > > > > > > > > The device I am working with, a PIC18LF26K22, produces the > > following assertion when the device is selected. > > > > > > > > > > > > > > pictype.h(433): assert "acc <= nbits" failed in > > GetBitSize(). > > > > > > > > > > > > > > Selecting a PIC18F26K22 (the 5V powered part) does not > > generate this assertion. > > > > > > > > The assertion dialog presents the options to Stop or Continue > > so is this assertion non-fatal and am I OK to continue > > using the > > program? > > > > > > > > Regards, > > Neil Darlow > > > > > > > > > > -- > > > > Sent with Evolution Mail on Linux > > Mint 19.3 Tricia. > > > > > > > > > > > > > > > > > > > > > > _______________________________________________Usbpicprog- > > technical mailing lis...@li... > > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > > > > > > > _______________________________________________Usbpicprog-technical > mailing lis...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical -- Sent with Evolution Mail on Linux Mint 19.3 Tricia. |
|
From: Frans S. <fra...@gm...> - 2020-03-12 10:53:32
|
Dear Neil Darlow, It has been a long term since I worked on usbpicprog. I guess there is a problem in the xml file for the PIC18LF26K22 or it's interpretation. I will certainly not harm to continue using the application, however I can't guarantee that the programming of this device will be 100% successful. Regards, Frans On 3/12/20 11:17 AM, Neil Darlow via Usbpicprog-technical wrote: > Hi, > > I am using usbpicprog from the Ubuntu PPA at version 1.0.5-4 amd64. > > The device I am working with, a PIC18LF26K22, produces the following > assertion when the device is selected. > > > pictype.h(433): assert "acc <= nbits" failed in GetBitSize(). > > > Selecting a PIC18F26K22 (the 5V powered part) does not generate this > assertion. > > The assertion dialog presents the options to Stop or Continue so is > this assertion non-fatal and am I OK to continue using the program? > > Regards, > Neil Darlow > > -- > Sent with Evolution Mail on Linux Mint 19.3 Tricia. > > > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: Neil D. <ne...@da...> - 2020-03-12 10:43:36
|
Hi, I am using usbpicprog from the Ubuntu PPA at version 1.0.5-4 amd64. The device I am working with, a PIC18LF26K22, produces the following assertion when the device is selected. pictype.h(433): assert "acc <= nbits" failed in GetBitSize(). Selecting a PIC18F26K22 (the 5V powered part) does not generate this assertion. The assertion dialog presents the options to Stop or Continue so is this assertion non-fatal and am I OK to continue using the program? Regards, Neil Darlow -- Sent with Evolution Mail on Linux Mint 19.3 Tricia. |
|
From: Neil D. <ne...@da...> - 2020-03-12 10:43:34
|
Hi, I am using usbpicprog from the Ubuntu PPA at version 1.0.5-4 amd64. The device I am working with, a PIC18LF26K22, produces the following assertion when the device is selected. pictype.h(433): assert "acc <= nbits" failed in GetBitSize(). Selecting a PIC18F26K22 (the 5V powered part) does not generate this assertion. The assertion dialog presents the options to Stop or Continue so is this assertion non-fatal and am I OK to continue using the program? Regards,Neil Darlow -- Sent with Evolution Mail on Linux Mint 19.3 Tricia. |
|
From: Mark G. <mar...@sp...> - 2019-02-15 08:56:08
|
Hi Frans, Thanks for your reply. Do you know where I could get a Linux driver for programming the dsPIC33F? Or, if one doesn't exist, do you know of anyone who could develop one for me? Regards, Mark From: Frans Schreuder [mailto:fra...@gm...] Sent: 14 February 2019 15:34 To: usb...@li... Subject: Re: [Usbpicprog-technical] Support for dsPIC33F Hello Mark, I started implementing dsPIC33F, but somehow I never got it to work completely. It has been a while since I worked on usbpicprog. Regards, Frans On 14-02-19 15:28, Mark Gardiner wrote: I am interested in programming a dsPIC33F using a Linux-based software platform and your recommended hardware. The problem is that I can't see from your website if this device is supported. In fact, from the "Supported Devices" page of your website (http://usbpicprog.org/?page_id=402) , no devices are listed. Please can you advise if this is possible? Mark Gardiner ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs Email Security System. ________________________________________________________________________ _______________________________________________ Usbpicprog-technical mailing list Usb...@li...<mailto:Usb...@li...> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs Email Security System. ________________________________________________________________________ |
|
From: Frans S. <fra...@gm...> - 2019-02-14 15:34:06
|
Hello Mark, I started implementing dsPIC33F, but somehow I never got it to work completely. It has been a while since I worked on usbpicprog. Regards, Frans On 14-02-19 15:28, Mark Gardiner wrote: > > I am interested in programming a dsPIC33F using a Linux-based software > platform and your recommended hardware. > > > > The problem is that I can’t see from your website if this device is > supported. In fact, from the “Supported Devices” page of your website > (http://usbpicprog.org/?page_id=402) , no devices are listed. > > > > Please can you advise if this is possible? > > > > > > Mark Gardiner > > > ________________________________________________________________________ > This email has been scanned for all viruses by the MessageLabs Email > Security System. > ________________________________________________________________________ > > > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: Mark G. <mar...@sp...> - 2019-02-14 14:42:34
|
I am interested in programming a dsPIC33F using a Linux-based software platform and your recommended hardware. The problem is that I can't see from your website if this device is supported. In fact, from the "Supported Devices" page of your website (http://usbpicprog.org/?page_id=402) , no devices are listed. Please can you advise if this is possible? Mark Gardiner ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs Email Security System. ________________________________________________________________________ |
|
From: Diego H. <die...@di...> - 2015-09-16 09:05:00
|
Hi Anthony, 16F84A is available in both 4 MHz and 20 MHz versions (not 10 MHz). Just in case you were looking for a 10MHz version which to my knowledge does not exist. Also, the 20 MHz version can be found on ebay (look for "PIC16F84A-20"). While not cheap, it's affordable for a single unit (less than 7€ including P&P). Cheers! On Tue, Sep 15, 2015 at 7:37 PM, anthony <aw...@io...> wrote: > Hello Frans > > Thanks for the reply. > > I would have used a 16F84A if I could have found a 10 Mhz version. None > of the suppliers I use list anything other than the 4 Mhz version, > unfortunately. Other suppliers wanted silly money for postage just for a > couple of PICs. > > The reason that I am using this PIC is that I have been playing around > with the "Engineer's Assistant" that I found on the Microchip website - > Application Note AN689. This does actually specify a PIC16F84A, but like > I said, I could not find a 10 MHz version. > > In the mean time I have built a JDM programmer - my computer does > actually have a functional serial port! I was not sure that it would be > successful, but it was. Happy days. > > Regards > > Anthony > > On 12/09/15 14:13, Frans Schreuder wrote: > > Hello Anthony, > > > > It would be very easy to implement code for the 16F84, however since the > > part has been obsolete for such a long time I am unable to test. > > If you are willing to test I can add the 16F84. > > May I ask why you need the 16F84, and not just replace it with the A? > > > > Kind regards, > > > > Frans Schreuder > > > > On 10-09-15 12:16, anthony wrote: > >> I know the device is now considered obsolete, but what changes/edits are > >> required to be able to program the PIC16F84? It is, after all, very > >> similar to the PIC16F84A. > >> > >> > ------------------------------------------------------------------------------ > >> Monitor Your Dynamic Infrastructure at Any Scale With Datadog! > >> Get real-time metrics from all of your servers, apps and tools > >> in one place. > >> SourceForge users - Click here to start your Free Trial of Datadog now! > >> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 > >> _______________________________________________ > >> Usbpicprog-technical mailing list > >> Usb...@li... > >> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Usbpicprog-technical mailing list > > Usb...@li... > > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > > > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > |
|
From: anthony <aw...@io...> - 2015-09-15 18:37:31
|
Hello Frans Thanks for the reply. I would have used a 16F84A if I could have found a 10 Mhz version. None of the suppliers I use list anything other than the 4 Mhz version, unfortunately. Other suppliers wanted silly money for postage just for a couple of PICs. The reason that I am using this PIC is that I have been playing around with the "Engineer's Assistant" that I found on the Microchip website - Application Note AN689. This does actually specify a PIC16F84A, but like I said, I could not find a 10 MHz version. In the mean time I have built a JDM programmer - my computer does actually have a functional serial port! I was not sure that it would be successful, but it was. Happy days. Regards Anthony On 12/09/15 14:13, Frans Schreuder wrote: > Hello Anthony, > > It would be very easy to implement code for the 16F84, however since the > part has been obsolete for such a long time I am unable to test. > If you are willing to test I can add the 16F84. > May I ask why you need the 16F84, and not just replace it with the A? > > Kind regards, > > Frans Schreuder > > On 10-09-15 12:16, anthony wrote: >> I know the device is now considered obsolete, but what changes/edits are >> required to be able to program the PIC16F84? It is, after all, very >> similar to the PIC16F84A. >> >> ------------------------------------------------------------------------------ >> Monitor Your Dynamic Infrastructure at Any Scale With Datadog! >> Get real-time metrics from all of your servers, apps and tools >> in one place. >> SourceForge users - Click here to start your Free Trial of Datadog now! >> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 >> _______________________________________________ >> Usbpicprog-technical mailing list >> Usb...@li... >> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > ------------------------------------------------------------------------------ > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > |
|
From: Frans S. <fra...@gm...> - 2015-09-12 13:13:49
|
Hello Anthony, It would be very easy to implement code for the 16F84, however since the part has been obsolete for such a long time I am unable to test. If you are willing to test I can add the 16F84. May I ask why you need the 16F84, and not just replace it with the A? Kind regards, Frans Schreuder On 10-09-15 12:16, anthony wrote: > I know the device is now considered obsolete, but what changes/edits are > required to be able to program the PIC16F84? It is, after all, very > similar to the PIC16F84A. > > ------------------------------------------------------------------------------ > Monitor Your Dynamic Infrastructure at Any Scale With Datadog! > Get real-time metrics from all of your servers, apps and tools > in one place. > SourceForge users - Click here to start your Free Trial of Datadog now! > http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: anthony <aw...@io...> - 2015-09-10 10:49:08
|
I know the device is now considered obsolete, but what changes/edits are required to be able to program the PIC16F84? It is, after all, very similar to the PIC16F84A. |
|
From: Krishnendu D. <dcs...@ya...> - 2014-07-11 15:41:42
|
I have recently make a Usb Pic Prog programmer and program the codeto 16F877A uc. But whenever I want to run the simple Blink code it won't work. pls. suggest whether any boot loader of 16F877A for Usb Pic Prog. or give a sample code. Thanking you, regards, K.Dutta. |
|
From: Ajit J. <aji...@gm...> - 2013-10-31 10:55:21
|
Hello, Contact form on your website doesn't appear anywhere on the contact page. Seems like some problem with the webpage Is there a different email id where I can write to about the order I placed via online shop? Regards, -Ajit |
|
From: Frans S. <fra...@gm...> - 2013-07-24 18:31:04
|
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Dear J,<br>
<br>
Thank you for reporting. I have included libexpat.1.dylib in the
.app, could you try the new installer?<br>
<a class="moz-txt-link-freetext" href="http://sourceforge.net/projects/usbpicprog/files/usbpicprog-software/usbpicprog-0.6.0-software/UsbPicProg-OSX-r0.6.0.dmg/download">http://sourceforge.net/projects/usbpicprog/files/usbpicprog-software/usbpicprog-0.6.0-software/UsbPicProg-OSX-r0.6.0.dmg/download</a><br>
<br>
Kind regards,<br>
<br>
Frans<br>
<br>
<div class="moz-cite-prefix">On 24-07-13 17:54, <a class="moz-txt-link-abbreviated" href="mailto:ds...@em...">ds...@em...</a>
wrote:<br>
</div>
<blockquote cite="mid:B3S.1GJ39.7X%7DBDSinHoR.1Hx%7D...@se..."
type="cite">
<div>Hello, I have problem with new version of usbpicprog in Mac
OSX (Lion 10.7.5). </div>
<div><br>
</div>
<div>dyld: Library not loaded: /opt/local/lib/libexpat.1.dylib</div>
<div> Referenced from:
/Applications/usbpicprog.app/Contents/MacOS/usbpicprog</div>
<div> Reason: Incompatible library version: usbpicprog requires
version 8.0.0 or later, but libexpat.1.dylib provides version
7.0.0</div>
<div>Trace/BPT trap: 5</div>
<div><br>
</div>
<div>I tried install last version of expat (from macports an then
from official source), but it return the same message.</div>
<div>What can I do to upgrade expat (ver. 8.0.0) ?</div>
<div><br>
</div>
<div> J.</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
<a class="moz-txt-link-freetext" href="http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk">http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Usbpicprog-technical mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Usb...@li...">Usb...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical">https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical</a>
</pre>
</blockquote>
<br>
</body>
</html>
|
|
From: <ds...@em...> - 2013-07-24 16:19:41
|
Hello, I have problem with new version of usbpicprog in Mac OSX (Lion 10.7. 5). dyld: Library not loaded: /opt/local/lib/libexpat.1.dylib Referenced from: /Applications/usbpicprog.app/Contents/MacOS/usbpicprog Reason: Incompatible library version: usbpicprog requires version 8.0.0 or later, but libexpat.1.dylib provides version 7.0.0 Trace/BPT trap: 5 I tried install last version of expat (from macports an then from official source), but it return the same message. What can I do to upgrade expat (ver. 8.0.0) ? J. |
|
From: Henrique B. <hba...@ya...> - 2013-06-20 14:37:39
|
Hi,
I've tried this before and after restoring the system (to a point before having the usbpicprog software installed). I tried to update the driver through the device manager, but Windows do not find any driver in usbpicprog folder and subfolders. Then I went to the driver folder and installed it as administrator... no effect.
Install the revision 130401 do not seem to have any effect, even after uninstalling the old driver (Win8 do not offer to delete the old files, could I do that manually?), restoring the system and so on =/
Att,
Henrique Baqueiro
>________________________________
> De: Frans Schreuder <fra...@gm...>
>Para: Henrique Baqueiro <hba...@ya...>; "usb...@li..." <usb...@li...>
>Enviadas: Quarta-feira, 19 de Junho de 2013 11:42
>Assunto: Re: UsbPicProg-amd64-0.5.0 not installing in Windows8
>
>
>
>Dear Henrique,
>
>The problem is now that you have installed the old driver. Windows
has an installed device driver which doesn't work and needs to be
removed.
>I will guide you in steps through the process:
>
> 1. plug in usbpicprog
> 2. open device manager, and find usbpicprog, click properties
> 3. click uninstall driver and tell windows to remove the driver files
> 4. now run the installer for usbpicprog 130401
> 5. in device manager usbpicprog should now be recognized as a working device
> 6. open usbpicprog and see if the status bar says "usbpicprog .... connected"
>Regards,
>
>Frans
>
>On 06/19/2013 01:45 PM, Henrique Baqueiro wrote:
>
>Hi,
>>
>>
>>This revision installs but still could not recognize the programmer...
>>
>>
>>
>>Att,
>>Henrique Baqueiro
>>
>>
>>>________________________________
>>> De: Frans Schreuder <fra...@gm...>
>>>Para: Henrique Baqueiro <hba...@gm...>
>>>Enviadas: Quarta-feira, 19 de Junho de 2013 3:30
>>>Assunto: Re: UsbPicProg-amd64-0.5.0 not installing in Windows8
>>>
>>>
>>>Dear Henrique,
>>>
>>>It is a known bug that usbpicprog 0.5.0 does not
install well on windows 8. This is due to the fact
that windows has made changes to their driver policy.
usbpicprog 0.5.0 was released before Windows 8.
>>>If you go to the download page, you will find a new
installer
>>>http://usbpicprog.org/?page_id=193 (r130401) which will soon be released as 0.6.0
>>>The mailing list is not read only, but you have to
subscribe yourself. That is a sourceforge policy.
>>>
>>>Kind regards,
>>>
>>>Frans Schreuder
>>>
>>>On 06/19/2013 03:40 AM, Henrique Baqueiro wrote:
>>>> Hi,
>>>>
>>>> I've got some problems when I tried to install
the UsbPicProg-amd64-0.5.0 (Windows 8). I attached the
print screen and the log file... Do you have some idea
of what happened? The driver could not be installed
and therefore the program doenst recognize the
programmer. I tried the mailling list but it was
reading only...
>>>> Thanks!
>>>>
>>>> Sincerely,
>>>> Henrique
>>>
>>>
>>>
>>>
>
>
> |
|
From: Frans S. <fra...@gm...> - 2013-06-19 14:42:34
|
Dear Henrique,
The problem is now that you have installed the old driver. Windows has
an installed device driver which doesn't work and needs to be removed.
I will guide you in steps through the process:
1. plug in usbpicprog
2. open device manager, and find usbpicprog, click properties
3. click uninstall driver and tell windows to remove the driver files
4. now run the installer for usbpicprog 130401
5. in device manager usbpicprog should now be recognized as a working
device
6. open usbpicprog and see if the status bar says "usbpicprog ....
connected"
Regards,
Frans
On 06/19/2013 01:45 PM, Henrique Baqueiro wrote:
> Hi,
>
> This revision installs but still could not recognize the programmer...
>
> Att,
> Henrique Baqueiro
>
> ------------------------------------------------------------------------
> *De:* Frans Schreuder <fra...@gm...>
> *Para:* Henrique Baqueiro <hba...@gm...>
> *Enviadas:* Quarta-feira, 19 de Junho de 2013 3:30
> *Assunto:* Re: UsbPicProg-amd64-0.5.0 not installing in Windows8
>
> Dear Henrique,
>
> It is a known bug that usbpicprog 0.5.0 does not install well on
> windows 8. This is due to the fact that windows has made changes
> to their driver policy. usbpicprog 0.5.0 was released before
> Windows 8.
> If you go to the download page, you will find a new installer
> http://usbpicprog.org/?page_id=193 (r130401) which will soon be
> released as 0.6.0
> The mailing list is not read only, but you have to subscribe
> yourself. That is a sourceforge policy.
>
> Kind regards,
>
> Frans Schreuder
>
> On 06/19/2013 03:40 AM, Henrique Baqueiro wrote:
> > Hi,
> >
> > I've got some problems when I tried to install the
> UsbPicProg-amd64-0.5.0 (Windows 8). I attached the print screen
> and the log file... Do you have some idea of what happened? The
> driver could not be installed and therefore the program doenst
> recognize the programmer. I tried the mailling list but it was
> reading only...
> > Thanks!
> >
> > Sincerely,
> > Henrique
>
>
>
|
|
From: Matt H. <mh...@me...> - 2013-06-02 04:43:27
|
Frans, I got a chance to try 130529. It seems like things are not quite working yet. The 16C622 isn't autodetected. I get this on the command line: ReadId: 00 ReadId: 00 ReadId: 00 ReadId: 00 ReadId: 00 ReadId: 3fff ReadId: 3fff ReadId: ffff Autodetected PIC ID: 0xffffffff Manually selecting the part and attempting to read it returns all 0x3fff. I also tried programming a part, but it fails on verify. Also, the GUI leaves the "erase before programming" flag checked when 16C622 is selected -- which doesn't make sense when a 16C part is selected. (It fails on the erase step without getting to the programming). I tested my programmer with the 130529 firmware on a few grab bag parts - 16f876 and 16f84, and both read and programmed successfully. Just to be sure I measured my VPP while connected to the chip, and it came it at 11.92V. I'm happy to help with any debugging info you might need, and I really appreciate your taking the time to implement support for this. However, if it's going to be a headache for you it's ok by me to drop it. Best, Matt On 05/29/2013 09:42 AM, Frans Schreuder wrote: > Hi Matt, > > I have implemented a bunch of 16C microcontrollers. Please test version > 130529. > I have built a binary for ubuntu, for Windows I will build a binary later. > > Regards, > > Frans > > On 05/28/2013 07:24 PM, Matt Hirsch wrote: >> Frans, >> >> Agreed - I typically don't use these. I have a UV erasable part - 16c622 >> - that's part of an old project, and I wanted to make a small change to >> it. I actually have piles of spares of these as well. Anyway, I used to >> use a picstart programmer to program these, but it has since died. I see >> there are plenty of drop in replacements for this part, so I can >> probably just use something else if it's a big deal to implement >> support, but I suppose it would be *nice* if its not too hard. >> >> Thanks for getting back to me! >> >> Matt >> >> On 05/28/2013 02:25 AM, Frans Schreuder wrote: >>> Dear Matt Hirch, >>> >>> Since 16C devices are a little outdated, I have never invested time in >>> implementing them. >>> If you need support for a certain PIC16C, I can implement it for you. >>> I think it is more useful though to invest time in the newer PIC families. >>> Those devices are often cheaper, have more features and can be >>> programmed more than once. >>> >>> Kind regards, >>> >>> Frans Schreuder >>> >>> On 05/28/2013 07:17 AM, Matt Hirsch wrote: >>>> What is the status of 16C devices? I noticed there are some commented >>>> enums in the firmware prog.h and pictype.h and device_table.h have >>>> 16CXXX listings, but there aren't any 16C devices in index.xml. >>>> >>>> Were these intended for the future, but never implemented, or were they >>>> disabled for some reason? >>>> >>>> Thanks, >>>> Matt >>>> >>>> ------------------------------------------------------------------------------ >>>> Try New Relic Now & We'll Send You this Cool Shirt >>>> New Relic is the only SaaS-based application performance monitoring service >>>> that delivers powerful full stack analytics. Optimize and monitor your >>>> browser, app, & servers with just a few lines of code. Try New Relic >>>> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may >>>> _______________________________________________ >>>> Usbpicprog-technical mailing list >>>> Usb...@li... >>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical >>> ------------------------------------------------------------------------------ >>> Try New Relic Now & We'll Send You this Cool Shirt >>> New Relic is the only SaaS-based application performance monitoring service >>> that delivers powerful full stack analytics. Optimize and monitor your >>> browser, app, & servers with just a few lines of code. Try New Relic >>> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may >>> _______________________________________________ >>> Usbpicprog-technical mailing list >>> Usb...@li... >>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical >> ------------------------------------------------------------------------------ >> Try New Relic Now & We'll Send You this Cool Shirt >> New Relic is the only SaaS-based application performance monitoring service >> that delivers powerful full stack analytics. Optimize and monitor your >> browser, app, & servers with just a few lines of code. Try New Relic >> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may >> _______________________________________________ >> Usbpicprog-technical mailing list >> Usb...@li... >> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > ------------------------------------------------------------------------------ > Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET > Get 100% visibility into your production application - at no cost. > Code-level diagnostics for performance bottlenecks with <2% overhead > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap1 > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: Frans S. <fra...@gm...> - 2013-05-29 13:42:52
|
Hi Matt, I have implemented a bunch of 16C microcontrollers. Please test version 130529. I have built a binary for ubuntu, for Windows I will build a binary later. Regards, Frans On 05/28/2013 07:24 PM, Matt Hirsch wrote: > Frans, > > Agreed - I typically don't use these. I have a UV erasable part - 16c622 > - that's part of an old project, and I wanted to make a small change to > it. I actually have piles of spares of these as well. Anyway, I used to > use a picstart programmer to program these, but it has since died. I see > there are plenty of drop in replacements for this part, so I can > probably just use something else if it's a big deal to implement > support, but I suppose it would be *nice* if its not too hard. > > Thanks for getting back to me! > > Matt > > On 05/28/2013 02:25 AM, Frans Schreuder wrote: >> Dear Matt Hirch, >> >> Since 16C devices are a little outdated, I have never invested time in >> implementing them. >> If you need support for a certain PIC16C, I can implement it for you. >> I think it is more useful though to invest time in the newer PIC families. >> Those devices are often cheaper, have more features and can be >> programmed more than once. >> >> Kind regards, >> >> Frans Schreuder >> >> On 05/28/2013 07:17 AM, Matt Hirsch wrote: >>> What is the status of 16C devices? I noticed there are some commented >>> enums in the firmware prog.h and pictype.h and device_table.h have >>> 16CXXX listings, but there aren't any 16C devices in index.xml. >>> >>> Were these intended for the future, but never implemented, or were they >>> disabled for some reason? >>> >>> Thanks, >>> Matt >>> >>> ------------------------------------------------------------------------------ >>> Try New Relic Now & We'll Send You this Cool Shirt >>> New Relic is the only SaaS-based application performance monitoring service >>> that delivers powerful full stack analytics. Optimize and monitor your >>> browser, app, & servers with just a few lines of code. Try New Relic >>> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may >>> _______________________________________________ >>> Usbpicprog-technical mailing list >>> Usb...@li... >>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical >> ------------------------------------------------------------------------------ >> Try New Relic Now & We'll Send You this Cool Shirt >> New Relic is the only SaaS-based application performance monitoring service >> that delivers powerful full stack analytics. Optimize and monitor your >> browser, app, & servers with just a few lines of code. Try New Relic >> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may >> _______________________________________________ >> Usbpicprog-technical mailing list >> Usb...@li... >> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: Alexandre R. <ale...@gm...> - 2013-05-28 19:20:46
|
Ok Frans this is very good news to me. Thanks a lot. On Tue, May 28, 2013 at 4:00 PM, Frans Schreuder <fra...@gm...>wrote: > Dear Alexandre Rosa, > > The PIC12F1822 is supported by the latest version of usbpicprog, only the > 1840 not yet. > It won't be a lot of work to implement it, I think it will be a matter of > writing the .xml file. > I just realized that I have never added the 12F1822 to the supported > devices section on usbpicprog.org. > > I did now. > > Kind regards, > > Frans Schreuder > > > On 28-05-13 13:07, Alexandre Rosa wrote: > > I am recently working on projects with PIC12F1822 and PIC12F1840. There is > some support to this devices in USBPICPROG ? Maybe a compatible device with > some program algorithm. > > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may > > > > _______________________________________________ > Usbpicprog-technical mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > > > > ------------------------------------------------------------------------------ > Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET > Get 100% visibility into your production application - at no cost. > Code-level diagnostics for performance bottlenecks with <2% overhead > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap1 > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > |
|
From: Frans S. <fra...@gm...> - 2013-05-28 19:00:15
|
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Dear Alexandre Rosa,<br>
<br>
The PIC12F1822 is supported by the latest version of usbpicprog,
only the 1840 not yet.<br>
It won't be a lot of work to implement it, I think it will be a
matter of writing the .xml file.<br>
I just realized that I have never added the 12F1822 to the supported
devices section on usbpicprog.org.<br>
<br>
I did now.<br>
<br>
Kind regards,<br>
<br>
Frans Schreuder<br>
<br>
On 28-05-13 13:07, Alexandre Rosa wrote:<br>
<blockquote
cite="mid:CAG...@ma..."
type="cite">
<div dir="ltr">I am recently working on projects with PIC12F1822
and PIC12F1840. There is some support to this devices in
USBPICPROG ? Maybe a compatible device with some program
algorithm.</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/newrelic_d2d_may">http://p.sf.net/sfu/newrelic_d2d_may</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Usbpicprog-technical mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Usb...@li...">Usb...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical">https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical</a>
</pre>
</blockquote>
<br>
</body>
</html>
|
|
From: Matt H. <mh...@me...> - 2013-05-28 17:24:30
|
Frans, Agreed - I typically don't use these. I have a UV erasable part - 16c622 - that's part of an old project, and I wanted to make a small change to it. I actually have piles of spares of these as well. Anyway, I used to use a picstart programmer to program these, but it has since died. I see there are plenty of drop in replacements for this part, so I can probably just use something else if it's a big deal to implement support, but I suppose it would be *nice* if its not too hard. Thanks for getting back to me! Matt On 05/28/2013 02:25 AM, Frans Schreuder wrote: > Dear Matt Hirch, > > Since 16C devices are a little outdated, I have never invested time in > implementing them. > If you need support for a certain PIC16C, I can implement it for you. > I think it is more useful though to invest time in the newer PIC families. > Those devices are often cheaper, have more features and can be > programmed more than once. > > Kind regards, > > Frans Schreuder > > On 05/28/2013 07:17 AM, Matt Hirsch wrote: >> What is the status of 16C devices? I noticed there are some commented >> enums in the firmware prog.h and pictype.h and device_table.h have >> 16CXXX listings, but there aren't any 16C devices in index.xml. >> >> Were these intended for the future, but never implemented, or were they >> disabled for some reason? >> >> Thanks, >> Matt >> >> ------------------------------------------------------------------------------ >> Try New Relic Now & We'll Send You this Cool Shirt >> New Relic is the only SaaS-based application performance monitoring service >> that delivers powerful full stack analytics. Optimize and monitor your >> browser, app, & servers with just a few lines of code. Try New Relic >> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may >> _______________________________________________ >> Usbpicprog-technical mailing list >> Usb...@li... >> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
|
From: Alexandre R. <ale...@gm...> - 2013-05-28 11:07:11
|
I am recently working on projects with PIC12F1822 and PIC12F1840. There is some support to this devices in USBPICPROG ? Maybe a compatible device with some program algorithm. |
|
From: Frans S. <fra...@gm...> - 2013-05-28 06:25:10
|
Dear Matt Hirch, Since 16C devices are a little outdated, I have never invested time in implementing them. If you need support for a certain PIC16C, I can implement it for you. I think it is more useful though to invest time in the newer PIC families. Those devices are often cheaper, have more features and can be programmed more than once. Kind regards, Frans Schreuder On 05/28/2013 07:17 AM, Matt Hirsch wrote: > What is the status of 16C devices? I noticed there are some commented > enums in the firmware prog.h and pictype.h and device_table.h have > 16CXXX listings, but there aren't any 16C devices in index.xml. > > Were these intended for the future, but never implemented, or were they > disabled for some reason? > > Thanks, > Matt > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may > _______________________________________________ > 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.
