usbpicprog-technical

Re: [Usbpicprog-technical] Using the programmer with Windows 8 - problems

[Frans S. <fra...@gm...>]

Dear Marcelo Maggi,

The windows 8 version needs a different driver topology. It is currently in
development and it needs a lot more work. I am working on it but i am also
busy because i recently moved into a new house. I believe that the
bootloader works, but the normal operation still needs some debugging.

Kind regards,

Frans Schreuder
Op 11 mrt. 2013 20:14 schreef "Marcelo Maggi" <mm...@ho...> het
volgende:

> Dear all,
>
> I have been using the programmer with Windows 7 (64) for quite a while
> with no issues at all. I recently migrated to Windows 8 (64), and tried to
> reinstall the software.
>
> The new version (UsbPicProg-amd64-0.5.0-win8.exe<http://usbpicprog.org/downloads/UsbPicProg-amd64-0.5.0-win8.exe>)
> installs with no problems; however, Windows 8 will not recognize the
> hardware, since there are no drivers available. Using the drivers from the
> Windows 7 version (UsbPicProg-amd64-0.5.0.exe<http://usbpicprog.org/downloads/old/UsbPicProg-amd64-0.5.0.exe>),
> and performing a manual driver update, Windows 8 will indicate that the
> drivers are not signed, so they are not updated. In order to install these
> drivers, the validation of driver signature in Windows 8 must be temporary
> disabled, which will allow the driver update process to continue.
>
> Now the hardware will be recognized, no issues highlighted in the Windows
> Device Manager, and when the UsbPicProg software runs the programmer is
> identified (firmware version 0.5.0).
>
> The problem now arises when trying to Program, Read or Verify... clicking
> any of these options, the program will stop running, with the usual Windows
> message... "This program stopped working..."
>
> It happens all the time, and I have no solution so far... I tried
> uninstalling and reinstalling, with the same results. I also tried running
> the program in Compatibility Mode and as Administrator, without success.
>
> I would appreciate any help to solve this problem.
>
> Thank you.
>
> Best regards,
> Marcelo Maggi
>
>
> ------------------------------------------------------------------------------
> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> endpoint security space. For insight on selecting the right partner to
> tackle endpoint security challenges, access the full report.
> http://p.sf.net/sfu/symantec-dev2dev
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>
>

[Usbpicprog-technical] Using the programmer with Windows 8 - problems

[Marcelo M. <mm...@ho...>]

Dear all, I have been using the programmer with Windows 7 (64) for quite a while with no issues at all. I recently migrated to Windows 8 (64), and tried to reinstall the software. The new version (UsbPicProg-amd64-0.5.0-win8.exe) installs with no problems; however, Windows 8 will not recognize the hardware, since there are no drivers available. Using the drivers from the Windows 7 version (UsbPicProg-amd64-0.5.0.exe), and performing a manual driver update, Windows 8 will indicate that the drivers are not signed, so they are not updated. In order to install these drivers, the validation of driver signature in Windows 8 must be temporary disabled, which will allow the driver update process to continue. Now the hardware will be recognized, no issues highlighted in the Windows Device Manager, and when the UsbPicProg software runs the programmer is identified (firmware version 0.5.0). The problem now arises when trying to Program, Read or Verify... clicking any of these options, the program will stop running, with the usual Windows message... "This program stopped working..." It happens all the time, and I have no solution so far... I tried uninstalling and reinstalling, with the same results. I also tried running the program in Compatibility Mode and as Administrator, without success. I would appreciate any help to solve this problem. Thank you. Best regards,Marcelo Maggi   		 	   		  

Re: [Usbpicprog-technical] User ID memory

[Frans S. <fra...@gm...>]

Hi Trevor,

In that case I will just try to work on it. The xml files were taken 
from piklab, they have added the user id's.
I have never really cared about them but it seems that people are 
actually using them, so I am going to add it!

Frans
On 02/18/2013 01:42 PM, Trevor Hinkley wrote:
> Hi Frans,
>
> My hack is a horrible hack. I've hardcoded the user ID memory location
> for the 18F4685 (0x200000-0x200007) into the write routine (so its not
> something that should be committed). However, I can say that
> TYPE_CODE for the read/writeBlock works for these values (at least on
> the 18F4685).
>
> Since the values do seem to be stored in the XML files (memory
> name="user_ids"), I'm quite happy to code this up into something more
> general, since it will only take a few mods to the Hardware and HexFile
> classes. At the moment I only have this model of MCU to work
> with though, so I'm unable to do extensive testing.
>
> ------------------------------------------------------------------------------
> The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
> is your hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials, tech docs,
> whitepapers, evaluation guides, and opinion stories. Check out the most
> recent posts - join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical

Re: [Usbpicprog-technical] User ID memory

[Trevor H. <tre...@gl...>]

Hi Frans,

My hack is a horrible hack. I've hardcoded the user ID memory location
for the 18F4685 (0x200000-0x200007) into the write routine (so its not
something that should be committed). However, I can say that
TYPE_CODE for the read/writeBlock works for these values (at least on
the 18F4685).

Since the values do seem to be stored in the XML files (memory
name="user_ids"), I'm quite happy to code this up into something more
general, since it will only take a few mods to the Hardware and HexFile
classes. At the moment I only have this model of MCU to work
with though, so I'm unable to do extensive testing.

Re: [Usbpicprog-technical] User ID memory

[Frans S. <fra...@gm...>]

Dear Trevor,

You are right, user id memory is not implemented in usbpicprog. Would you
like to contribute your fix to the project? I can give you write access to
the github repository.
The change to the software won't be that big indeed, i will have a look at
it.

Frans
 Op 17 feb. 2013 23:41 schreef "Trevor Hinkley" <
Tre...@gl...> het volgende:

> I've just spent the weekend trying to burn an 18F4685 with the midibox
> firmware. It seems a minor omission (with regards to this project) in the
> usbpicprog software is that it ignores the User ID data, which this
> firmware uses. In addition, I've been completely unable to run version 0.5
> software on MacOS 10.8.2, having to fall back to the 0.45 software (which
> works perfectly apart from the missing feature). Since the ID memory
> locations ARE listed in the XML files for the PIC models, it seems this
> should be an easy fix (indeed I was able to put a simple hack in [just for
> this model] to get it to write the ID data, in about 15 minutes for the
> command-line).
>
> Cheers,
> Trev
>
> ------------------------------------------------------------------------------
> The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
> is your hub for all things parallel software development, from weekly
> thought
> leadership blogs to news, videos, case studies, tutorials, tech docs,
> whitepapers, evaluation guides, and opinion stories. Check out the most
> recent posts - join the conversation now.
> http://goparallel.sourceforge.net/
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>

[Usbpicprog-technical] User ID memory

[Trevor H. <Tre...@gl...>]

I've just spent the weekend trying to burn an 18F4685 with the midibox firmware. It seems a minor omission (with regards to this project) in the usbpicprog software is that it ignores the User ID data, which this firmware uses. In addition, I've been completely unable to run version 0.5 software on MacOS 10.8.2, having to fall back to the 0.45 software (which works perfectly apart from the missing feature). Since the ID memory locations ARE listed in the XML files for the PIC models, it seems this should be an easy fix (indeed I was able to put a simple hack in [just for this model] to get it to write the ID data, in about 15 minutes for the command-line).

Cheers,
Trev

Re: [Usbpicprog-technical] Different components of the usbpicprog

[Frans S. <fra...@gm...>]

Dear Juan Malero,

Don't worry too much about the capacitors. As long as they have the right
value and the right voltage rating they will work.
Good luck building usbpicprog!

Frans
Op 17 feb. 2013 02:20 schreef "Juan Molero" <jua...@gm...> het
volgende:

> Hello, I'm electronics engineering student from venezuela.
>
> I have some questions regarding the components for assembling the thorough
> hole version of usbpicprog.
>
> I have almost no knowledge about packages, types of compoments, I just
> need a simple pic programmer an this one looked like a good one but I'm
> kinda starting to get worried when i get to solder all the componens into
> the pcb, I have bought the 18f already so pretty much I dont want to give
> up now.
>
> My doubts are in the capacitors, I just went to my local electronics store
> and bought all the capacitors listed in the bill of materials but just
> asking for the capacitance, i bought some tiny ceramic ones, some
> electrolitic, but after checking the picture of the pcb hole posted on your
> website I noticed some unknown rectangular white capacitors which made me
> worry, will any kind of capacitor work?
>
> Maybe I'm thinking too much about it but I dont want to waste my money,
>
> Thanks for your responses
>
>
> ------------------------------------------------------------------------------
> The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
> is your hub for all things parallel software development, from weekly
> thought
> leadership blogs to news, videos, case studies, tutorials, tech docs,
> whitepapers, evaluation guides, and opinion stories. Check out the most
> recent posts - join the conversation now.
> http://goparallel.sourceforge.net/
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>
>

[Usbpicprog-technical] Different components of the usbpicprog

[Juan M. <jua...@gm...>]

Hello, I'm electronics engineering student from venezuela.

I have some questions regarding the components for assembling the thorough
hole version of usbpicprog.

I have almost no knowledge about packages, types of compoments, I just need
a simple pic programmer an this one looked like a good one but I'm kinda
starting to get worried when i get to solder all the componens into the
pcb, I have bought the 18f already so pretty much I dont want to give up
now.

My doubts are in the capacitors, I just went to my local electronics store
and bought all the capacitors listed in the bill of materials but just
asking for the capacitance, i bought some tiny ceramic ones, some
electrolitic, but after checking the picture of the pcb hole posted on your
website I noticed some unknown rectangular white capacitors which made me
worry, will any kind of capacitor work?

Maybe I'm thinking too much about it but I dont want to waste my money,

Thanks for your responses

Re: [Usbpicprog-technical] Raspberry Pi PIC Programmer Help?

[Will M. <wm-...@sw...>]

Hi Frans,

Thanks for you interest!

The raspberry Pi output is 3.3V (according to 
http://elinux.org/RPi_Low-level_peripherals, and confirmed with 
oscilloscope if I recall correctly)

 From my reading of the Programming spec, I can't find any mention of a 
12V VPP, just a 3.3V on 'VDD during programming' in the table in section 
7.0. The chip also has an internal voltage regulator to ramp the 3.3V on 
VDD to 2.5V needed on 'VDDcore' with an extra tantalum capacitor.

Programming Spec:
http://ww1.microchip.com/downloads/en/DeviceDoc/39934b.pdf

I'm quoting sources not because I want to prove my point, but because I 
don't know what's wrong and you may be able to explain - if one of my 
sources is inaccurate that would explain a lot!

Those two bits put together made me think it would be very easy to use a 
Pi for this project - almost no extra components required.

Will.

P.S. In case you want to read more, here is a link to the Microchip page 
for this Pic. ;)
http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en536119#documentation

P.P.S. If you would like me to try and compile USB PIC Prog on the Pi, I 
shall try it some evening this week, but unfortunately I don't have a 
programmer to test it with.




On 29/01/13 16:33, Frans Schreuder wrote:
> Hi Will McElderry,
>
> It sounds nice, but how do you plan to convert the voltages (5V -> 3.3V)
> and how do you supply the 12V programming voltage?
> I guess you will need some additional hardware.
> It is possible though to run usbpicprog on the raspberry pi.
>
> Regards,
>
> Frans
> On 01/29/2013 01:33 PM, Will McElderry wrote:
>> Hi All,
>>
>> I'm attempting to use the GPIO pins on the Raspberry Pi to program a
>> PIC24FJ32GB004, and struggling.
>>
>> I've had some success, but I can only clock out 0's from the Visi
>> register (see note below).
>>
>> I am hoping that someone on here may be interested in my goal enough to
>> lend me their knowledge and perhaps try running the code on their Pi to
>> program a chip?
>>
>> Any comments on what may be wrong or ways to test further would be
>> appreciated!
>>
>> The code is very basic and hacked together, it's C++ and easy enough to
>> read.  I've compared with the usbpicprog code and I can't see any
>> noticeable differences.
>>
>> I'll post more details if there's anyone interested.
>>
>> Thanks,
>>
>> Will McElderry.
>>
>> NB: I *believe* I am clocking out zeros from the register as PGD seems
>> to accept current when the PIC should be transmitting data - indicating
>> the PIC is intentionally holding the ping low.
>> This was a fortuitous discovery thanks to only having access to an
>> oscilloscope with one channel, and using a r/2r ladder to allow
>> monitoring 3 pins at the same time. When PGD is not connected to either
>> zero or one the output voltage on the channel changes noticeably, a
>> state I have been able to induce intentionally by sending invalid
>> commands to the PIC, or not requesting clocking out of the Visi
>> register, but asking the Pi to try and read from the PGD pin.
>>
>> ------------------------------------------------------------------------------
>> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
>> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
>> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
>> MVPs and experts. ON SALE this month only -- learn more at:
>> http://p.sf.net/sfu/learnnow-d2d
>> _______________________________________________
>> Usbpicprog-technical mailing list
>> Usb...@li...
>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnnow-d2d
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical

Re: [Usbpicprog-technical] Raspberry Pi PIC Programmer Help?

[Frans S. <fra...@gm...>]

Hi Will McElderry,

It sounds nice, but how do you plan to convert the voltages (5V -> 3.3V) 
and how do you supply the 12V programming voltage?
I guess you will need some additional hardware.
It is possible though to run usbpicprog on the raspberry pi.

Regards,

Frans
On 01/29/2013 01:33 PM, Will McElderry wrote:
> Hi All,
>
> I'm attempting to use the GPIO pins on the Raspberry Pi to program a
> PIC24FJ32GB004, and struggling.
>
> I've had some success, but I can only clock out 0's from the Visi
> register (see note below).
>
> I am hoping that someone on here may be interested in my goal enough to
> lend me their knowledge and perhaps try running the code on their Pi to
> program a chip?
>
> Any comments on what may be wrong or ways to test further would be
> appreciated!
>
> The code is very basic and hacked together, it's C++ and easy enough to
> read.  I've compared with the usbpicprog code and I can't see any
> noticeable differences.
>
> I'll post more details if there's anyone interested.
>
> Thanks,
>
> Will McElderry.
>
> NB: I *believe* I am clocking out zeros from the register as PGD seems
> to accept current when the PIC should be transmitting data - indicating
> the PIC is intentionally holding the ping low.
> This was a fortuitous discovery thanks to only having access to an
> oscilloscope with one channel, and using a r/2r ladder to allow
> monitoring 3 pins at the same time. When PGD is not connected to either
> zero or one the output voltage on the channel changes noticeably, a
> state I have been able to induce intentionally by sending invalid
> commands to the PIC, or not requesting clocking out of the Visi
> register, but asking the Pi to try and read from the PGD pin.
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnnow-d2d
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical

[Usbpicprog-technical] Raspberry Pi PIC Programmer Help?

[Will M. <wm-...@sw...>]

Hi All,

I'm attempting to use the GPIO pins on the Raspberry Pi to program a 
PIC24FJ32GB004, and struggling.

I've had some success, but I can only clock out 0's from the Visi 
register (see note below).

I am hoping that someone on here may be interested in my goal enough to 
lend me their knowledge and perhaps try running the code on their Pi to 
program a chip?

Any comments on what may be wrong or ways to test further would be 
appreciated!

The code is very basic and hacked together, it's C++ and easy enough to 
read.  I've compared with the usbpicprog code and I can't see any 
noticeable differences.

I'll post more details if there's anyone interested.

Thanks,

Will McElderry.

NB: I *believe* I am clocking out zeros from the register as PGD seems 
to accept current when the PIC should be transmitting data - indicating 
the PIC is intentionally holding the ping low.
This was a fortuitous discovery thanks to only having access to an 
oscilloscope with one channel, and using a r/2r ladder to allow 
monitoring 3 pins at the same time. When PGD is not connected to either 
zero or one the output voltage on the channel changes noticeably, a 
state I have been able to induce intentionally by sending invalid 
commands to the PIC, or not requesting clocking out of the Visi 
register, but asking the Pi to try and read from the PGD pin.

Re: [Usbpicprog-technical] cant program the PIC

[Frans S. <fra...@gm...>]

Hi Balint,

You could try a low voltage shottky diode for the VDD, in stead of 
1n4148. That should do the job.

Frans

Op 1/21/2013 11:39 AM, Bálint Gyenes schreef:
> Hi Frans,
>
> I have only a multimeter, the voltages on the VDD and VPP pins are
> about 4,4V and about 12,3V during the programming process.
> I found the VDD voltage low, so I drove the target PIC's VDD pin with
> a 5V supply. On this way the VPP voltage remained about 12,3V.
>
> Best Regards,
> Balint
>
> 2013/1/21, Frans Schreuder <fra...@gm...>:
>> Hi Balint,
>>
>> I have never tested the 16F628, because it is obsolete but it' s
>> follower the 16F628A should work. The 16F84A should also work but that
>> one is very critical about the voltages. Could you measure VPP and VDD
>> while programming? preferably with an oscilloscope, but if you don't
>> have it try using a multimeter while the programming is in progress.
>>
>> Kind regards,
>>
>> Frans
>>
>> Op 1/21/2013 10:01 AM, Bálint Gyenes schreef:
>>> Hi,
>>>
>>> I build the through-hole version of the usbpicprog. Everything looks
>>> fine, but when I try to program a PIC, I get this:
>>>
>>> Erasing before programming...
>>> Erase OK
>>> Write Code memory OK
>>> Programming the data area of the PIC...
>>> Write Data memory OK
>>> Verifying all areas of the PIC...
>>> Verify code failed at 0x0. Read: 0x00, Expected: 0x12
>>> Programming configuration area of the PIC...
>>> Error programming config memory
>>>
>>> I tried it with two PICs, a 16F628 and a 16F84A, the programmer
>>> detects both, but at programming the situation is the same.
>>> I checked the circuit, it looks correct and the I/O test gives the
>>> required voltages on every pins.
>>> Could it be the problem that some of the mounted transistors
>>> (bs170,bs250, bc547) can't provide enough current?
>>>
>>> Thanks for the reply.
>>>
>>> Best Regards,
>>> Balint
>>>
>>> ------------------------------------------------------------------------------
>>> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
>>> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
>>> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
>>> MVPs and experts. SALE $99.99 this month only -- learn more at:
>>> http://p.sf.net/sfu/learnmore_122412
>>> _______________________________________________
>>> Usbpicprog-technical mailing list
>>> Usb...@li...
>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>>
>> ------------------------------------------------------------------------------
>> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
>> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
>> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
>> MVPs and experts. SALE $99.99 this month only -- learn more at:
>> http://p.sf.net/sfu/learnmore_122412
>> _______________________________________________
>> Usbpicprog-technical mailing list
>> Usb...@li...
>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122412
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical

Re: [Usbpicprog-technical] cant program the PIC

[Bálint G. <gye...@gm...>]

Hi Frans,

I have only a multimeter, the voltages on the VDD and VPP pins are
about 4,4V and about 12,3V during the programming process.
I found the VDD voltage low, so I drove the target PIC's VDD pin with
a 5V supply. On this way the VPP voltage remained about 12,3V.

Best Regards,
Balint

2013/1/21, Frans Schreuder <fra...@gm...>:
> Hi Balint,
>
> I have never tested the 16F628, because it is obsolete but it' s
> follower the 16F628A should work. The 16F84A should also work but that
> one is very critical about the voltages. Could you measure VPP and VDD
> while programming? preferably with an oscilloscope, but if you don't
> have it try using a multimeter while the programming is in progress.
>
> Kind regards,
>
> Frans
>
> Op 1/21/2013 10:01 AM, Bálint Gyenes schreef:
>> Hi,
>>
>> I build the through-hole version of the usbpicprog. Everything looks
>> fine, but when I try to program a PIC, I get this:
>>
>> Erasing before programming...
>> Erase OK
>> Write Code memory OK
>> Programming the data area of the PIC...
>> Write Data memory OK
>> Verifying all areas of the PIC...
>> Verify code failed at 0x0. Read: 0x00, Expected: 0x12
>> Programming configuration area of the PIC...
>> Error programming config memory
>>
>> I tried it with two PICs, a 16F628 and a 16F84A, the programmer
>> detects both, but at programming the situation is the same.
>> I checked the circuit, it looks correct and the I/O test gives the
>> required voltages on every pins.
>> Could it be the problem that some of the mounted transistors
>> (bs170,bs250, bc547) can't provide enough current?
>>
>> Thanks for the reply.
>>
>> Best Regards,
>> Balint
>>
>> ------------------------------------------------------------------------------
>> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
>> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
>> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
>> MVPs and experts. SALE $99.99 this month only -- learn more at:
>> http://p.sf.net/sfu/learnmore_122412
>> _______________________________________________
>> Usbpicprog-technical mailing list
>> Usb...@li...
>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122412
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>

Re: [Usbpicprog-technical] cant program the PIC

[Frans S. <fra...@gm...>]

Hi Balint,

I have never tested the 16F628, because it is obsolete but it' s 
follower the 16F628A should work. The 16F84A should also work but that 
one is very critical about the voltages. Could you measure VPP and VDD 
while programming? preferably with an oscilloscope, but if you don't 
have it try using a multimeter while the programming is in progress.

Kind regards,

Frans

Op 1/21/2013 10:01 AM, Bálint Gyenes schreef:
> Hi,
>
> I build the through-hole version of the usbpicprog. Everything looks
> fine, but when I try to program a PIC, I get this:
>
> Erasing before programming...
> Erase OK
> Write Code memory OK
> Programming the data area of the PIC...
> Write Data memory OK
> Verifying all areas of the PIC...
> Verify code failed at 0x0. Read: 0x00, Expected: 0x12
> Programming configuration area of the PIC...
> Error programming config memory
>
> I tried it with two PICs, a 16F628 and a 16F84A, the programmer
> detects both, but at programming the situation is the same.
> I checked the circuit, it looks correct and the I/O test gives the
> required voltages on every pins.
> Could it be the problem that some of the mounted transistors
> (bs170,bs250, bc547) can't provide enough current?
>
> Thanks for the reply.
>
> Best Regards,
> Balint
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122412
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical

[Usbpicprog-technical] cant program the PIC

[Bálint G. <gye...@gm...>]

Hi,

I build the through-hole version of the usbpicprog. Everything looks
fine, but when I try to program a PIC, I get this:

Erasing before programming...
Erase OK
Write Code memory OK
Programming the data area of the PIC...
Write Data memory OK
Verifying all areas of the PIC...
Verify code failed at 0x0. Read: 0x00, Expected: 0x12
Programming configuration area of the PIC...
Error programming config memory

I tried it with two PICs, a 16F628 and a 16F84A, the programmer
detects both, but at programming the situation is the same.
I checked the circuit, it looks correct and the I/O test gives the
required voltages on every pins.
Could it be the problem that some of the mounted transistors
(bs170,bs250, bc547) can't provide enough current?

Thanks for the reply.

Best Regards,
Balint

Re: [Usbpicprog-technical] ubuntu 12.10

[Frans S. <fra...@gm...>]

Dear Nuno,

That's right, I have forgotten to compile a new development version of 
the firmware, that is because nothing has changed in the firmware since 
the latest release (0.5.0)
For now just ignore the warning, on the next upgrade I will put a devel 
version number in the firmware.

Regards,

Frans
On 10/28/2012 06:32 PM, Nuno Sucena Almeida wrote:
> On 10/28/2012 04:20 AM, Frans Schreuder wrote:
>> Please also upgrade your wxwidgets from that ppa
> Hi Frans,
>
> that did the trick, but now the software complains about the firmware
> not being up to date. I used the firmware.hex file in
> /usr/share/usbpicprog , but it doesn't seem to be the devel version.
>
> regards,
> Nuno
>
>
> ------------------------------------------------------------------------------
> WINDOWS 8 is here.
> Millions of people.  Your app in 30 days.
> Visit The Windows 8 Center at Sourceforge for all your go to resources.
> http://windows8center.sourceforge.net/
> join-generation-app-and-make-money-coding-fast/
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical

Re: [Usbpicprog-technical] ubuntu 12.10

[Nuno S. A. <nu...@ae...>]

On 10/28/2012 04:20 AM, Frans Schreuder wrote:
> Please also upgrade your wxwidgets from that ppa

Hi Frans,

that did the trick, but now the software complains about the firmware 
not being up to date. I used the firmware.hex file in 
/usr/share/usbpicprog , but it doesn't seem to be the devel version.

regards,
Nuno

Re: [Usbpicprog-technical] ubuntu 12.10

[Frans S. <fra...@gm...>]

Please also upgrade your wxwidgets from that ppa
Op 28 okt. 2012 02:02 schreef "Nuno Sucena Almeida" <nu...@ae...>
het volgende:

> On 10/27/2012 06:50 PM, Frans Schreuder wrote:
> > If you apt-get install the latest software from usbpicprog-devel it
> should
> > work now.
> >
> > Kind regards,
> >
> > Frans Schreuder
>
> Thanks Frans, but it seems I still have the same issue:
>
> ~$ l /etc/apt/sources.list.d/fransschreuder1-usbpicprog-*
> fransschreuder1-usbpicprog-devel-quantal.list
> fransschreuder1-usbpicprog-stable-precise.list.distUpgrade
> fransschreuder1-usbpicprog-stable-precise.list.save
>
> after a apt-get update && apt-get install usbpicprog i still get:
>
> ~$ usbpicprog
> usbpicprog: error while loading shared libraries:
> libwx_gtk2u_html-2.9.so.4: cannot open shared object file: No such file
> or directory
>
> cheers,
> Nuno
>
>
> ------------------------------------------------------------------------------
> WINDOWS 8 is here.
> Millions of people.  Your app in 30 days.
> Visit The Windows 8 Center at Sourceforge for all your go to resources.
> http://windows8center.sourceforge.net/
> join-generation-app-and-make-money-coding-fast/
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>

Re: [Usbpicprog-technical] ubuntu 12.10

[Nuno S. A. <nu...@ae...>]

On 10/27/2012 06:50 PM, Frans Schreuder wrote:
> If you apt-get install the latest software from usbpicprog-devel it should
> work now.
>
> Kind regards,
>
> Frans Schreuder

Thanks Frans, but it seems I still have the same issue:

~$ l /etc/apt/sources.list.d/fransschreuder1-usbpicprog-*
fransschreuder1-usbpicprog-devel-quantal.list
fransschreuder1-usbpicprog-stable-precise.list.distUpgrade
fransschreuder1-usbpicprog-stable-precise.list.save

after a apt-get update && apt-get install usbpicprog i still get:

~$ usbpicprog
usbpicprog: error while loading shared libraries: 
libwx_gtk2u_html-2.9.so.4: cannot open shared object file: No such file 
or directory

cheers,
Nuno

Re: [Usbpicprog-technical] ubuntu 12.10

[Frans S. <fra...@gm...>]

Dear Nuno,

Before trying to program it with the serial programmer, you can try to see
if it works if you remove the select jumper, that should launch the
bootloader mode.
If you apt-get install the latest software from usbpicprog-devel it should
work now.

Kind regards,

Frans Schreuder
Op 27 okt. 2012 22:38 schreef "Nuno Sucena Almeida" <nu...@ae...>
het volgende:

> Hi,
>
> after upgrading from ubuntu 12.04 to 12.10 and running the install
> script (ubuntu-install-script.sh) I get the following:
>
> ~$ usbpicprog
> usbpicprog: error while loading shared libraries:
> libwx_gtk2u_html-2.9.so.4: cannot open shared object file: No such file
> or directory
>
> I have so.3 though:
> ~$ dpkg -S libwx_gtk2u_html-2.9.so.3
> libwxgtk2.9-0: /usr/lib/libwx_gtk2u_html-2.9.so.3
> libwxgtk2.9-0: /usr/lib/libwx_gtk2u_html-2.9.so.3.0.0
>
> Also, before upgrading to 12.10 a few weeks ago, I tried to run the
> devel branch and update the firmware, without changing the jumpers, and
> now the programmer is no longer recognized, lsusb doesn't show it anymore
> :(
>
> At this precise moment I'm building the serial port programmer in
> pic-icsp.jpg to try to "unbrick" it.
>
> regards,
> Nuno
>
>
> ------------------------------------------------------------------------------
> WINDOWS 8 is here.
> Millions of people.  Your app in 30 days.
> Visit The Windows 8 Center at Sourceforge for all your go to resources.
> http://windows8center.sourceforge.net/
> join-generation-app-and-make-money-coding-fast/
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>

Re: [Usbpicprog-technical] ubuntu 12.10

[Nuno S. A. <nu...@ae...>]

On 10/27/2012 04:01 PM, Nuno Sucena Almeida wrote:
> now the programmer is no longer recognized, lsusb doesn't show it anymore:(
>
> At this precise moment I'm building the serial port programmer in
> pic-icsp.jpg to try to "unbrick" it.
>
> regards,
> Nuno

With respect to this, I recovered by going through the normal firmware 
upgrade, changing the pins this time, and the programmer is now working, 
although I had to manually install an older .deb file to be able to run 
the software.

[Usbpicprog-technical] ubuntu 12.10

[Nuno S. A. <nu...@ae...>]

Hi,

after upgrading from ubuntu 12.04 to 12.10 and running the install 
script (ubuntu-install-script.sh) I get the following:

~$ usbpicprog
usbpicprog: error while loading shared libraries: 
libwx_gtk2u_html-2.9.so.4: cannot open shared object file: No such file 
or directory

I have so.3 though:
~$ dpkg -S libwx_gtk2u_html-2.9.so.3
libwxgtk2.9-0: /usr/lib/libwx_gtk2u_html-2.9.so.3
libwxgtk2.9-0: /usr/lib/libwx_gtk2u_html-2.9.so.3.0.0

Also, before upgrading to 12.10 a few weeks ago, I tried to run the 
devel branch and update the firmware, without changing the jumpers, and 
now the programmer is no longer recognized, lsusb doesn't show it anymore :(

At this precise moment I'm building the serial port programmer in 
pic-icsp.jpg to try to "unbrick" it.

regards,
Nuno

Re: [Usbpicprog-technical] config word programming

[Gábor H. <gab...@gm...>]

Hi Frans.

Thanks for the hint, to check this, I will have to build a charge pump, as
you did in usbpicprog.

Regards,
Gabor

On Wed, Oct 17, 2012 at 10:47 AM, Frans Schreuder
<fra...@gm...>wrote:

>  Hi Gabor,
>
> It could also be the MCLRE bit, disabling the MCLR pin, this requires
> another programming mode entry.
>
> Regards,
>
> Frans
>
> On 10/17/2012 09:00 AM, Gábor Hornyák wrote:
>
> Hi,
>
>  I will check the specs, but I am afraid this is something different,
> because I can not even read the config words, including the device ID,
> which I assume should be readable even with code protection enabled.
>
>  Thanks,
> Gabor
>
> On Wed, Oct 17, 2012 at 8:07 AM, Frans Schreuder <fra...@gm...
> > wrote:
>
>> Hi,
>>
>> You probagbly haven't bricked the pic but programmed the code proteection
>> bits by accident. With these bits enabled it is also more difficult to eras
>> the pic, check the programming specification for the procedure.
>>
>> Regards,
>>
>> Frans
>>
>>  Op 16 okt. 2012 23:04 schreef "Gábor Hornyák" <gab...@gm...>
>> het volgende:
>>
>> >
>> > Hi Everyone,
>> >
>> > My question is not strictly related to usbpicprog, but I am hoping that
>> someone here has faced similar issue.
>> > As a 'side' project of an other project, I thought I create a simple
>> programmer to PIC18F46K22 (I have a demo board with PIC18F45K22 equipped
>> with bootloader, which I am using for programming). Everything went fine -
>> I was able to read/write program memory and read config words - until I
>> reached the point where config words had to be written. After I created it
>> and tested with a PIC, it seems that I bricked the mcu, because from that
>> point, I can not do anything with the PIC (always read zeroes for all
>> addresses).
>> > I don't know what could have went wrong, since config word programming
>> differs only in a few things from program memory programming (which works
>> fine, and the fact is that I actually seem to have bricked two PICs
>> already). My concrete question is: could this problem have been caused by
>> trying to write config BYTES separately (not as words)? Has anyone faced
>> similar problem?
>> >
>> > Thanks and Regards,
>> > Gabor
>> >
>>  >
>> ------------------------------------------------------------------------------
>> > Everyone hates slow websites. So do we.
>> > Make your web apps faster with AppDynamics
>> > Download AppDynamics Lite for free today:
>> > http://p.sf.net/sfu/appdyn_sfd2d_oct
>> > _______________________________________________
>> > Usbpicprog-technical mailing list
>> > Usb...@li...
>> > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_sfd2d_oct
>> _______________________________________________
>> Usbpicprog-technical mailing list
>> Usb...@li...
>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>>
>>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:http://p.sf.net/sfu/appdyn_sfd2d_oct
>
>
>
> _______________________________________________
> Usbpicprog-technical mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>
>

Re: [Usbpicprog-technical] config word programming

[Frans S. <fra...@gm...>]

Hi Gabor,

It could also be the MCLRE bit, disabling the MCLR pin, this requires 
another programming mode entry.

Regards,

Frans
On 10/17/2012 09:00 AM, Gábor Hornyák wrote:
> Hi,
>
> I will check the specs, but I am afraid this is something different, 
> because I can not even read the config words, including the device ID, 
> which I assume should be readable even with code protection enabled.
>
> Thanks,
> Gabor
>
> On Wed, Oct 17, 2012 at 8:07 AM, Frans Schreuder 
> <fra...@gm... <mailto:fra...@gm...>> wrote:
>
>     Hi,
>
>     You probagbly haven't bricked the pic but programmed the code
>     proteection bits by accident. With these bits enabled it is also
>     more difficult to eras the pic, check the programming
>     specification for the procedure.
>
>     Regards,
>
>     Frans
>
>     Op 16 okt. 2012 23:04 schreef "Gábor Hornyák"
>     <gab...@gm... <mailto:gab...@gm...>> het volgende:
>
>
>     >
>     > Hi Everyone,
>     >
>     > My question is not strictly related to usbpicprog, but I am
>     hoping that someone here has faced similar issue.
>     > As a 'side' project of an other project, I thought I create a
>     simple programmer to PIC18F46K22 (I have a demo board with
>     PIC18F45K22 equipped with bootloader, which I am using for
>     programming). Everything went fine - I was able to read/write
>     program memory and read config words - until I reached the point
>     where config words had to be written. After I created it and
>     tested with a PIC, it seems that I bricked the mcu, because from
>     that point, I can not do anything with the PIC (always read zeroes
>     for all addresses).
>     > I don't know what could have went wrong, since config word
>     programming differs only in a few things from program memory
>     programming (which works fine, and the fact is that I actually
>     seem to have bricked two PICs already). My concrete question is:
>     could this problem have been caused by trying to write config
>     BYTES separately (not as words)? Has anyone faced similar problem?
>     >
>     > Thanks and Regards,
>     > Gabor
>     >
>     >
>     ------------------------------------------------------------------------------
>     > Everyone hates slow websites. So do we.
>     > Make your web apps faster with AppDynamics
>     > Download AppDynamics Lite for free today:
>     > http://p.sf.net/sfu/appdyn_sfd2d_oct
>     > _______________________________________________
>     > Usbpicprog-technical mailing list
>     > Usb...@li...
>     <mailto:Usb...@li...>
>     > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>     >
>
>     ------------------------------------------------------------------------------
>     Everyone hates slow websites. So do we.
>     Make your web apps faster with AppDynamics
>     Download AppDynamics Lite for free today:
>     http://p.sf.net/sfu/appdyn_sfd2d_oct
>     _______________________________________________
>     Usbpicprog-technical mailing list
>     Usb...@li...
>     <mailto:Usb...@li...>
>     https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
>
>
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical

Re: [Usbpicprog-technical] config word programming

[Gábor H. <gab...@gm...>]

Hi,

I will check the specs, but I am afraid this is something different,
because I can not even read the config words, including the device ID,
which I assume should be readable even with code protection enabled.

Thanks,
Gabor

On Wed, Oct 17, 2012 at 8:07 AM, Frans Schreuder
<fra...@gm...>wrote:

> Hi,
>
> You probagbly haven't bricked the pic but programmed the code proteection
> bits by accident. With these bits enabled it is also more difficult to eras
> the pic, check the programming specification for the procedure.
>
> Regards,
>
> Frans
>
> Op 16 okt. 2012 23:04 schreef "Gábor Hornyák" <gab...@gm...> het
> volgende:
>
> >
> > Hi Everyone,
> >
> > My question is not strictly related to usbpicprog, but I am hoping that
> someone here has faced similar issue.
> > As a 'side' project of an other project, I thought I create a simple
> programmer to PIC18F46K22 (I have a demo board with PIC18F45K22 equipped
> with bootloader, which I am using for programming). Everything went fine -
> I was able to read/write program memory and read config words - until I
> reached the point where config words had to be written. After I created it
> and tested with a PIC, it seems that I bricked the mcu, because from that
> point, I can not do anything with the PIC (always read zeroes for all
> addresses).
> > I don't know what could have went wrong, since config word programming
> differs only in a few things from program memory programming (which works
> fine, and the fact is that I actually seem to have bricked two PICs
> already). My concrete question is: could this problem have been caused by
> trying to write config BYTES separately (not as words)? Has anyone faced
> similar problem?
> >
> > Thanks and Regards,
> > Gabor
> >
> >
> ------------------------------------------------------------------------------
> > Everyone hates slow websites. So do we.
> > Make your web apps faster with AppDynamics
> > Download AppDynamics Lite for free today:
> > http://p.sf.net/sfu/appdyn_sfd2d_oct
> > _______________________________________________
> > Usbpicprog-technical mailing list
> > Usb...@li...
> > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
> >
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>
>