usbpicprog-technical

Re: [Usbpicprog-technical] MacOSX tool open source?

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

Dear René v Amerongen,

The CLI for osx is somewhat difficult to access, since the binary is
inside an .app package.
If you realize that the .app is just a directory, you can access it and
find the executable in usbpicprog.app/Contents/MacOS
if you type:

export PATH=$PATH:/Applications/usbpicprog.app/Contents/MacOS/

You can access the cli by typing e.g.:

usbpicprog -h

Kind regards,

Frans Schreuder

On 11/03/2010 01:15 PM, René v Amerongen wrote:
> Hello, I could only find binaries, but is the tool also open source?
> Is the source available?
>
> Also if I understands well, the tool is connecting with the cli program to do its thing ( programming reading etc ). Plus it got a library to the device info?
>
> Greetz
>
> RvA
> ------------------------------------------------------------------------------
> Achieve Improved Network Security with IP and DNS Reputation.
> Defend against bad network traffic, including botnets, malware, 
> phishing sites, and compromised hosts - saving your company time, 
> money, and embarrassment.   Learn More! 
> http://p.sf.net/sfu/hpdev2dev-nov
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical

Re: [Usbpicprog-technical] MacOSX tool open source?

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

Dear René van Amerongen,

I wonder where you have looked if you couldn't find the source?
Of course usbpicprog is open source, else it wouldn't be on sourceforge!

Kind regards,

Frans Schreuder

On 11/03/2010 01:15 PM, René v Amerongen wrote:
> Hello, I could only find binaries, but is the tool also open source?
> Is the source available?
>
> Also if I understands well, the tool is connecting with the cli program to do its thing ( programming reading etc ). Plus it got a library to the device info?
>
> Greetz
>
> RvA
> ------------------------------------------------------------------------------
> Achieve Improved Network Security with IP and DNS Reputation.
> Defend against bad network traffic, including botnets, malware, 
> phishing sites, and compromised hosts - saving your company time, 
> money, and embarrassment.   Learn More! 
> http://p.sf.net/sfu/hpdev2dev-nov
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical

[Usbpicprog-technical] MacOSX tool open source?

[René v A. <app...@xs...>]

Hello, I could only find binaries, but is the tool also open source?
Is the source available?

Also if I understands well, the tool is connecting with the cli program to do its thing ( programming reading etc ). Plus it got a library to the device info?

Greetz

RvA

Re: [Usbpicprog-technical] dsPIC30F2020 question

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

Hi Ken,

The devices you are mentioning have now just been implemented like any
other dsPIC30F device, and this should indeed have a different protocol,
entering the programming mode. The protocol is more or less like the
18FXXJXXXX devices which have recently been implemented.
I have added the 3 devices as not working on the supported devices page.
I will soon try implementing the differences in those devices.
Thank you for letting me know.

Kind regards,

Frans Schreuder

On 11/02/2010 12:28 AM, Ken Sarkies wrote:
> Hi All
>
> Just a question about the supported devices. I'm looking to work with 
> the SMPS capable dsPIC30F devices (eg dsPIC30F2020), which appear to 
> differ from other dsPIC30F versions, in particular being low voltage 
> programmable and also appear to use somewhat different low level 
> programming protocols. Could someone please verify that the usbpicprog 
> firmware will handle these differences, and not apply high voltage 
> programming?
>
> cheers and thanks, Ken
>

[Usbpicprog-technical] dsPIC30F2020 question

[Ken S. <ksa...@tr...>]

Hi All

Just a question about the supported devices. I'm looking to work with 
the SMPS capable dsPIC30F devices (eg dsPIC30F2020), which appear to 
differ from other dsPIC30F versions, in particular being low voltage 
programmable and also appear to use somewhat different low level 
programming protocols. Could someone please verify that the usbpicprog 
firmware will handle these differences, and not apply high voltage 
programming?

cheers and thanks, Ken

-- 
Linux Error Message:
Font: "Helvetica" does not appear to be either a font file or registered with ImageMagick.
A similarly-named font was not found. Sorry! The font "Helvetica" will be used instead.

Re: [Usbpicprog-technical] [usbpicprog-technical] Re: New Pic controller...

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

Hi Patrick,

I have already put your code in the SVN tree, but I omitted the send_key
function, because it was the same anyway.
It is now also working for me!
I have also added your name in "developers" in the about usbpicprog
dialog :P

Frans

On 09/23/2010 10:31 AM, Patrick NIES wrote:
> OK, I'll try it.
>
> Anyway, only the prog_lolvl.c file has to be updated.
>
> Patrick
>
> Frans Schreuder a écrit :
>> Hi Patrick,
>>
>> It's just replying to usb...@li...
>> and there must be [usbpicprog-technical] in the subject.
>>
>> Did you know that you also have write access to subversion?
>>
>> Frans
>>
>> On 09/23/2010 09:39 AM, Patrick NIES wrote:
>>> Hi,
>>>
>>> How can I post something to the mailing list ? When I'm log in, I
>>> have nowhere to click.
>>>
>>> Maybe should I renew my account ?
>>>
>>> Patrick
>>>
>>> Frans Schreuder a écrit :
>>>> Hi Patrick,
>>>>
>>>> I also send this to the mailing list, because it might be
>>>> interesting for others to read as well.
>>>> Have you already tried the other code (28 in stead of 50)? This
>>>> code is really a bitshift of the other one, so I think you must
>>>> have looked wrong while measuring.
>>>> It could also be that the MCLR entry is alright, but that the code
>>>> for reading is different from other PIC18F devices.
>>>> It is always difficult to introduce a new PIC family. Microchip
>>>> likes it to put some slight differences in every programming
>>>> specification, probably just to make our life miserable!
>>>> I will have a look at the code more thoroughly.
>>>>
>>>> Frans
>>>>
>>>>
>>>> On 09/22/2010 01:00 AM, Patrick NIES wrote:
>>>>>
>>>>> Hi Frans,
>>>>>
>>>>> First, the piece of code I send last time was not good. For the
>>>>> delays to work I forget the ''lasttick=tick;'' before the
>>>>> ''while((tick-lasttick)<6)continue;'' line.
>>>>>
>>>>> I've replaced these lines by some ''DelayMs(6)'' but no response
>>>>> of the PIC. After five days of work, searching and testing
>>>>> everything I can or I think of, still no response.
>>>>>
>>>>> Tired of that, *I finally buy a PicKit3 !!!*
>>>>>
>>>>> Of course very nice thing, works without problems with MPLab and
>>>>> it permits to confirm that my 27j53 was not (yet) killed by my
>>>>> numerous tests, and of course no way to drive it on Linux, back to
>>>>> the very irritating Vi$ta 8-(.
>>>>>
>>>>> I've done some ''reverse engineering'' to try to understand what
>>>>> we do wrong on UPP.
>>>>>
>>>>> I'll try to describe what I find with my very old Tektronix 2236
>>>>> scope:
>>>>>
>>>>> The detection of the PicType is OK if I select the good device in
>>>>> the configuration menu in MPLab. Otherwise MPLab says the DevID do
>>>>> not match.
>>>>>
>>>>> The Pic is always supplied by the programmer (when choose in
>>>>> settings). I had doubts about that, thought that maybe the entry
>>>>> in programming mode was possible just after some VDD Off/ VDD On
>>>>> cycles.
>>>>>
>>>>> The delays: The MCLR ''high'' pulse have a duration of,
>>>>> approximately, 0.5Msec. Follow a MCLR ''low'' of 4Msec and the
>>>>> 32bits key. Not very new and conforms to the specs.
>>>>>
>>>>> More surprising: The 32 bits key is not the same as in the
>>>>> datasheet. Instead of 4D 43 48 50 I find 4D 43 24 28 !!! I must
>>>>> confirm that because I have just 5 seconds to read my scope screen
>>>>> during PicKit3 read the code memory of the Pic, and I'm not very
>>>>> certain...
>>>>>
>>>>> Still searching for the truth !!! ;-)
>>>>>
>>>>> Have a nice Week End,
>>>>>
>>>>> Patrick
>>>>>
>>>>>
>>>>>
>>>>> Frans Schreuder a écrit :
>>>>>> Hi Patrick,
>>>>>>
>>>>>> I have added your additions to the subversion repository.
>>>>>> Thanks!
>>>>>>
>>>>>> Frans
>>>>>>
>>>>>> On 09/17/2010 01:29 AM, Patrick NIES wrote:
>>>>>>>
>>>>>>> Hi Frans,
>>>>>>>
>>>>>>> Two things:
>>>>>>>
>>>>>>> The capacitor on the VDDCore Pin must be between 5.4 and 18MF. I
>>>>>>> put 10MF here.
>>>>>>>
>>>>>>> The P19 time is largely greater than the one you have write =>
>>>>>>> 4Msec. I have added a 6Msec time to be safe, and another 6Msec
>>>>>>> between Vdd rise and first MCLR rise.
>>>>>>>
>>>>>>> In prog_lolvl.c:/
>>>>>>> /
>>>>>>>
>>>>>>> /
>>>>>>> if(picfamily==PIC18J)/
>>>>>>>
>>>>>>> / {/
>>>>>>>
>>>>>>> / TRISPGD_LOW = 0;/
>>>>>>>
>>>>>>> / PGD_LOW = 0; //PGD and PGC to 3.3V mode (output)/
>>>>>>>
>>>>>>> / TRISPGC_LOW = 0;/
>>>>>>>
>>>>>>> / PGC_LOW = 0;/
>>>>>>>
>>>>>>> / VDD=0; //VDD high,/
>>>>>>>
>>>>>>> */while((tick-lasttick)<6)continue;/*
>>>>>>>
>>>>>>> / clock_delay(); //P13 = 100ns min/
>>>>>>>
>>>>>>> / VPP_RUN=1; //VPP to 4.5V/
>>>>>>>
>>>>>>> / VPP_RUN=0; //and immediately back to 0.../
>>>>>>>
>>>>>>> */while((tick-lasttick)<6)continue;/*
>>>>>>>
>>>>>>> / clock_delay(); //P19 = 40ns min/
>>>>>>>
>>>>>>> / //write 0x4D43, high to low, other than the rest of the
>>>>>>> commands which are low to high.../
>>>>>>>
>>>>>>> / //0x3D43 => 0100 1101 0100 0011/
>>>>>>>
>>>>>>> / //from low to high => 1100 0010 1011 0010/
>>>>>>>
>>>>>>> / //0xC2B2 /
>>>>>>>
>>>>>>> / pic_send_word(0xC2B2);/
>>>>>>>
>>>>>>> / //write 0x4850 => 0100 1000 0101 0000 => 0000 1010 0001 0010
>>>>>>> => 0x0A12/
>>>>>>>
>>>>>>> / pic_send_word(0x0A12);/
>>>>>>>
>>>>>>> / VPP_RUN=1; /
>>>>>>>
>>>>>>> / return;/
>>>>>>>
>>>>>>> / }/
>>>>>>>
>>>>>>> Not yet tested.
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Patrick
>>>>>>>
>>>>>>>
>>>>>>> Frans Schreuder a écrit :
>>>>>>>> Dear Patrick,
>>>>>>>>
>>>>>>>> This 32 bit key is implemented, however I have not gotten it to
>>>>>>>> work yet.
>>>>>>>> I will try to implement the X7J53 devices if you want to try
>>>>>>>> them out.
>>>>>>>>
>>>>>>>> Frans.
>>>>>>>>
>>>>>>>> On 09/16/2010 10:13 AM, Patrick NIES wrote:
>>>>>>>>>
>>>>>>>>> Yes,
>>>>>>>>>
>>>>>>>>> /Entry into ICSP modes for PIC18F2XJXX/4XJXX family
>>>>>>>>> devices is somewhat different than previous PIC18
>>>>>>>>> devices. As shown in Figure 2-6, entering ICSP
>>>>>>>>> Program/Verify mode requires three steps:
>>>>>>>>> 1.   Voltage is briefly applied to the MCLR pin.
>>>>>>>>> 2.   A 32-bit key sequence is presented on PGD.
>>>>>>>>> 3.   Voltage is reapplied to MCLR and held.
>>>>>>>>> *The programming voltage applied to MCLR is VIH, or
>>>>>>>>> essentially, VDD*. There is no minimum time requirement
>>>>>>>>> for holding at VIH. After VIH is removed, an interval of at
>>>>>>>>> least P19 must elapse before presenting the key
>>>>>>>>> sequence on PGD.
>>>>>>>>>
>>>>>>>>> /Although the MCLR pin is 5.5V tolerant, in the programing
>>>>>>>>> specs VIH must not exceed VDD.
>>>>>>>>>
>>>>>>>>> I'll try with a zener diode...
>>>>>>>>>
>>>>>>>>> Patrick
>>>>>>>>> /
>>>>>>>>>
>>>>>>>>> /
>>>>>>>>>
>>>>>>>>> Frans Schreuder a écrit :
>>>>>>>>>> Dear Patrick,
>>>>>>>>>>
>>>>>>>>>> It is not that easy, also the 24J10 is not yet recognized.
>>>>>>>>>> Please do not connect them yet as I am not even sure if they
>>>>>>>>>> might be destroyed by usbpicprog.
>>>>>>>>>> I am still considering if it might be necessary to implement
>>>>>>>>>> another 3.3V zener diode on VPP while programming the
>>>>>>>>>> 18FXXJXX devices.
>>>>>>>>>>
>>>>>>>>>> Kind regards,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Frans Schreuder
>>>>>>>>>>
>>>>>>>>>> On 09/16/2010 01:25 AM, Patrick NIES wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi Frans,
>>>>>>>>>>>
>>>>>>>>>>> Could you please implement the 18f27j53 and the 18f47j53 ?
>>>>>>>>>>>
>>>>>>>>>>> I begin today some tests with this devices and it would be
>>>>>>>>>>> nice if they be recognised by UPP.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> Patrick
>>>>>>>>>>>
>>>>>>>>>>> Frans Schreuder a écrit :
>>>>>>>>>>>> Hi Patrick,
>>>>>>>>>>>>
>>>>>>>>>>>> I will need some more time on the 24J10, but as soon as it
>>>>>>>>>>>> is working the 27j53 will be peanuts as well.
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>
>>>>>>>>>>>> Frans
>>>>>>>>>>>>
>>>>>>>>>>>> On 08/26/2010 01:14 AM, Patrick NIES wrote:
>>>>>>>>>>>>> Hi Frans,
>>>>>>>>>>>>>
>>>>>>>>>>>>> For a new project I would use a 18f27j53. I have seen that
>>>>>>>>>>>>> you have implemented and done some tests with 18f24j10
>>>>>>>>>>>>> (with same programming specs) apparently unsuccessful as
>>>>>>>>>>>>> you mark it as "not working".
>>>>>>>>>>>>>
>>>>>>>>>>>>> Do you think it needs a little more time to spend to make
>>>>>>>>>>>>> it work or it seems to bee very hard to find what's wrong
>>>>>>>>>>>>> with these controllers ???
>>>>>>>>>>>>>  
>>>>>>>>>>>>> Thanks for your response.
>>>>>>>>>>>>>  
>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>  
>>>>>>>>>>>>> Patrick
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>>

Re: [Usbpicprog-technical] [usbpicprog-technical] Re: New Pic controller...

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

Hi Patrick,

That's great news! I am going to try the new code right now!
I will put the new code in subversion (except of course the replacement
of the devid bits)
I have now added all the 2XJXX and 4XJXX to the upp_wx application.

Frans




On 09/23/2010 02:32 AM, Patrick NIES wrote:
> Hi Frans,
>
> Good news, I finally success !!!
>
> The 32 bits key 4D 43 48 50 was alright, I just misinterpreted my
> scope screen.
>
> All the other pieces of code (read, write, erase...) are the same as
> for the 18Fxxxx.
>
> The only thing that we forget was the P12 delay (0.4Msec) before
> sending commands.
>
> I have rewritten all this ICSP entry mode and add a more clear
> specific function to send the key in prog_lolvl.c. However it works
> the same with yours:
> /
> void set_vdd_vpp(PICTYPE pictype, PICFAMILY picfamily,char level)/
> /{/
> / unsigned int i;/
> /
> if(level==1)/
> / {/
>
> / TRISPGC =0; //PGC output/
>  
> / if(picfamily==PIC18J)/
> / {/
> / TRISPGD=0; //needed to refresh, sometimes.../
> / TRISPGC=0;/
> / VPP_RUN=0; //MCLR low/
> / VDD=0; //VDD high,/
> / DelayMs(10); //P13 = 100ns min => far more here for the supply to
> stabilize /
> / TRISPGD_LOW = 0;/
> / PGD_LOW = 0; //PGD and PGC to 3.3V mode (output)/
> / TRISPGC_LOW = 0;/
> / PGC_LOW = 0;/
> /
> /
> / VPP_RUN=1; //VPP to 4.5V/
> / for(i=0;i<300;i++)continue; //aprox 0.5ms/
> / VPP_RUN=0; //and back to 0.../
> / DelayMs(4); //P19 = 4ms min/
> / //write 0x4D43, high to low, other than the rest of the commands
> which are low to high.../
> / //0x3D43 => 0100 1101 0100 0011/
> / //from low to high => 1100 0010 1011 0010/
> / //0xC2B2 /
> ///// pic_send_word(0xC2B2);/
> / //write 0x4850 => 0100 1000 0101 0000 => 0000 1010 0001 0010 => 0x0A12/
> ///// pic_send_word(0x0A12);/
> / pic_send_key(0x4D43,0x4850);/
> /// clock_delay(); //P20 = 50ns min/
> / VPP_RUN=1; //MCLR released /
> / DelayMs(1); //P12 = 0.4Msec min/
>
> / return;/
> / }/
> …
> /
> void pic_send_key(unsigned int keyMsb, unsigned int keyLsb)
> {
> char i;
> for(i=0;i<16;i++)
> {
> if(keyMsb&0x8000)PGD=1;
> else PGD=0;
> PGC=1;
> keyMsb<<=1;
> PGC=0;
> }
> clock_delay();
> for(i=0;i<16;i++)
> {
> if(keyLsb&0x8000)PGD=1;
> else PGD=0;
> PGC=1;
> keyLsb<<=1;
> PGC=0;
> }
> clock_delay();
> } /
>
> I can send you the complete files.
>
> All is OK with a 18F27J53 except the verification of the configuration
> bits. It's normal as I had to replace the DevId of the 27J53 by the
> one of the 45J10 in upp.c:
>
> /case CMD_READ_ID:
> ...
> case PIC18:
> case PIC18J:
> read_code(picfamily,pictype,0x3FFFFE,(unsigned
> char*)output_buffer,2,3); //devid is at location 0x3ffffe for PIC18
> devices
> i*f (output_buffer[0] == 0x60) output_buffer[0] = 0x20;    //replace
> DevIds
> if (output_buffer[1] == 0x58) output_buffer[1] = 0x1C; *
>
> break;
> … /
>
> I have made some tries to add these PICs in the .xml files and
> recompile them but they are still not recognized by the UPP software.
> I don't know how to calculate or where to find the upp_devidmask and
> many other parameters.
>
> For these tests I also modified the hardware to be sure there was no
> 5V or 12V VPP applied to the target device... too long to expain now...
>
> Cheers,
>
> Patrick
>
>
>
>
>
> Frans Schreuder a écrit :
>> Hi Patrick,
>>
>> I also send this to the mailing list, because it might be interesting
>> for others to read as well.
>> Have you already tried the other code (28 in stead of 50)? This code
>> is really a bitshift of the other one, so I think you must have
>> looked wrong while measuring.
>> It could also be that the MCLR entry is alright, but that the code
>> for reading is different from other PIC18F devices.
>> It is always difficult to introduce a new PIC family. Microchip likes
>> it to put some slight differences in every programming specification,
>> probably just to make our life miserable!
>> I will have a look at the code more thoroughly.
>>
>> Frans
>>
>>
>> On 09/22/2010 01:00 AM, Patrick NIES wrote:
>>>
>>> Hi Frans,
>>>
>>> First, the piece of code I send last time was not good. For the
>>> delays to work I forget the ''lasttick=tick;'' before the
>>> ''while((tick-lasttick)<6)continue;'' line.
>>>
>>> I've replaced these lines by some ''DelayMs(6)'' but no response of
>>> the PIC. After five days of work, searching and testing everything I
>>> can or I think of, still no response.
>>>
>>> Tired of that, *I finally buy a PicKit3 !!!*
>>>
>>> Of course very nice thing, works without problems with MPLab and it
>>> permits to confirm that my 27j53 was not (yet) killed by my numerous
>>> tests, and of course no way to drive it on Linux, back to the very
>>> irritating Vi$ta 8-(.
>>>
>>> I've done some ''reverse engineering'' to try to understand what we
>>> do wrong on UPP.
>>>
>>> I'll try to describe what I find with my very old Tektronix 2236 scope:
>>>
>>> The detection of the PicType is OK if I select the good device in
>>> the configuration menu in MPLab. Otherwise MPLab says the DevID do
>>> not match.
>>>
>>> The Pic is always supplied by the programmer (when choose in
>>> settings). I had doubts about that, thought that maybe the entry in
>>> programming mode was possible just after some VDD Off/ VDD On cycles.
>>>
>>> The delays: The MCLR ''high'' pulse have a duration of,
>>> approximately, 0.5Msec. Follow a MCLR ''low'' of 4Msec and the
>>> 32bits key. Not very new and conforms to the specs.
>>>
>>> More surprising: The 32 bits key is not the same as in the
>>> datasheet. Instead of 4D 43 48 50 I find 4D 43 24 28 !!! I must
>>> confirm that because I have just 5 seconds to read my scope screen
>>> during PicKit3 read the code memory of the Pic, and I'm not very
>>> certain...
>>>
>>> Still searching for the truth !!! ;-)
>>>
>>> Have a nice Week End,
>>>
>>> Patrick
>>>
>>>
>>>
>>> Frans Schreuder a écrit :
>>>> Hi Patrick,
>>>>
>>>> I have added your additions to the subversion repository.
>>>> Thanks!
>>>>
>>>> Frans
>>>>
>>>> On 09/17/2010 01:29 AM, Patrick NIES wrote:
>>>>>
>>>>> Hi Frans,
>>>>>
>>>>> Two things:
>>>>>
>>>>> The capacitor on the VDDCore Pin must be between 5.4 and 18MF. I
>>>>> put 10MF here.
>>>>>
>>>>> The P19 time is largely greater than the one you have write =>
>>>>> 4Msec. I have added a 6Msec time to be safe, and another 6Msec
>>>>> between Vdd rise and first MCLR rise.
>>>>>
>>>>> In prog_lolvl.c:/
>>>>> /
>>>>>
>>>>> /
>>>>> if(picfamily==PIC18J)/
>>>>>
>>>>> / {/
>>>>>
>>>>> / TRISPGD_LOW = 0;/
>>>>>
>>>>> / PGD_LOW = 0; //PGD and PGC to 3.3V mode (output)/
>>>>>
>>>>> / TRISPGC_LOW = 0;/
>>>>>
>>>>> / PGC_LOW = 0;/
>>>>>
>>>>> / VDD=0; //VDD high,/
>>>>>
>>>>> */while((tick-lasttick)<6)continue;/*
>>>>>
>>>>> / clock_delay(); //P13 = 100ns min/
>>>>>
>>>>> / VPP_RUN=1; //VPP to 4.5V/
>>>>>
>>>>> / VPP_RUN=0; //and immediately back to 0.../
>>>>>
>>>>> */while((tick-lasttick)<6)continue;/*
>>>>>
>>>>> / clock_delay(); //P19 = 40ns min/
>>>>>
>>>>> / //write 0x4D43, high to low, other than the rest of the commands
>>>>> which are low to high.../
>>>>>
>>>>> / //0x3D43 => 0100 1101 0100 0011/
>>>>>
>>>>> / //from low to high => 1100 0010 1011 0010/
>>>>>
>>>>> / //0xC2B2 /
>>>>>
>>>>> / pic_send_word(0xC2B2);/
>>>>>
>>>>> / //write 0x4850 => 0100 1000 0101 0000 => 0000 1010 0001 0010 =>
>>>>> 0x0A12/
>>>>>
>>>>> / pic_send_word(0x0A12);/
>>>>>
>>>>> / VPP_RUN=1; /
>>>>>
>>>>> / return;/
>>>>>
>>>>> / }/
>>>>>
>>>>> Not yet tested.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Patrick
>>>>>
>>>>>
>>>>> Frans Schreuder a écrit :
>>>>>> Dear Patrick,
>>>>>>
>>>>>> This 32 bit key is implemented, however I have not gotten it to
>>>>>> work yet.
>>>>>> I will try to implement the X7J53 devices if you want to try them
>>>>>> out.
>>>>>>
>>>>>> Frans.
>>>>>>
>>>>>> On 09/16/2010 10:13 AM, Patrick NIES wrote:
>>>>>>>
>>>>>>> Yes,
>>>>>>>
>>>>>>> /Entry into ICSP modes for PIC18F2XJXX/4XJXX family
>>>>>>> devices is somewhat different than previous PIC18
>>>>>>> devices. As shown in Figure 2-6, entering ICSP
>>>>>>> Program/Verify mode requires three steps:
>>>>>>> 1.   Voltage is briefly applied to the MCLR pin.
>>>>>>> 2.   A 32-bit key sequence is presented on PGD.
>>>>>>> 3.   Voltage is reapplied to MCLR and held.
>>>>>>> *The programming voltage applied to MCLR is VIH, or
>>>>>>> essentially, VDD*. There is no minimum time requirement
>>>>>>> for holding at VIH. After VIH is removed, an interval of at
>>>>>>> least P19 must elapse before presenting the key
>>>>>>> sequence on PGD.
>>>>>>>
>>>>>>> /Although the MCLR pin is 5.5V tolerant, in the programing specs
>>>>>>> VIH must not exceed VDD.
>>>>>>>
>>>>>>> I'll try with a zener diode...
>>>>>>>
>>>>>>> Patrick
>>>>>>> /
>>>>>>>
>>>>>>> /
>>>>>>>
>>>>>>> Frans Schreuder a écrit :
>>>>>>>> Dear Patrick,
>>>>>>>>
>>>>>>>> It is not that easy, also the 24J10 is not yet recognized.
>>>>>>>> Please do not connect them yet as I am not even sure if they
>>>>>>>> might be destroyed by usbpicprog.
>>>>>>>> I am still considering if it might be necessary to implement
>>>>>>>> another 3.3V zener diode on VPP while programming the 18FXXJXX
>>>>>>>> devices.
>>>>>>>>
>>>>>>>> Kind regards,
>>>>>>>>
>>>>>>>>
>>>>>>>> Frans Schreuder
>>>>>>>>
>>>>>>>> On 09/16/2010 01:25 AM, Patrick NIES wrote:
>>>>>>>>>
>>>>>>>>> Hi Frans,
>>>>>>>>>
>>>>>>>>> Could you please implement the 18f27j53 and the 18f47j53 ?
>>>>>>>>>
>>>>>>>>> I begin today some tests with this devices and it would be
>>>>>>>>> nice if they be recognised by UPP.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> Patrick
>>>>>>>>>
>>>>>>>>> Frans Schreuder a écrit :
>>>>>>>>>> Hi Patrick,
>>>>>>>>>>
>>>>>>>>>> I will need some more time on the 24J10, but as soon as it is
>>>>>>>>>> working the 27j53 will be peanuts as well.
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>>
>>>>>>>>>> Frans
>>>>>>>>>>
>>>>>>>>>> On 08/26/2010 01:14 AM, Patrick NIES wrote:
>>>>>>>>>>> Hi Frans,
>>>>>>>>>>>
>>>>>>>>>>> For a new project I would use a 18f27j53. I have seen that
>>>>>>>>>>> you have implemented and done some tests with 18f24j10 (with
>>>>>>>>>>> same programming specs) apparently unsuccessful as you mark
>>>>>>>>>>> it as "not working".
>>>>>>>>>>>
>>>>>>>>>>> Do you think it needs a little more time to spend to make it
>>>>>>>>>>> work or it seems to bee very hard to find what's wrong with
>>>>>>>>>>> these controllers ???
>>>>>>>>>>>  
>>>>>>>>>>> Thanks for your response.
>>>>>>>>>>>  
>>>>>>>>>>> Cheers,
>>>>>>>>>>>  
>>>>>>>>>>> Patrick
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>>

[Usbpicprog-technical] [usbpicprog-technical] Re: New Pic controller...

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

Hi Patrick,

I also send this to the mailing list, because it might be interesting
for others to read as well.
Have you already tried the other code (28 in stead of 50)? This code is
really a bitshift of the other one, so I think you must have looked
wrong while measuring.
It could also be that the MCLR entry is alright, but that the code for
reading is different from other PIC18F devices.
It is always difficult to introduce a new PIC family. Microchip likes it
to put some slight differences in every programming specification,
probably just to make our life miserable!
I will have a look at the code more thoroughly.

Frans


On 09/22/2010 01:00 AM, Patrick NIES wrote:
>
> Hi Frans,
>
> First, the piece of code I send last time was not good. For the delays
> to work I forget the ''lasttick=tick;'' before the
> ''while((tick-lasttick)<6)continue;'' line.
>
> I've replaced these lines by some ''DelayMs(6)'' but no response of
> the PIC. After five days of work, searching and testing everything I
> can or I think of, still no response.
>
> Tired of that, *I finally buy a PicKit3 !!!*
>
> Of course very nice thing, works without problems with MPLab and it
> permits to confirm that my 27j53 was not (yet) killed by my numerous
> tests, and of course no way to drive it on Linux, back to the very
> irritating Vi$ta 8-(.
>
> I've done some ''reverse engineering'' to try to understand what we do
> wrong on UPP.
>
> I'll try to describe what I find with my very old Tektronix 2236 scope:
>
> The detection of the PicType is OK if I select the good device in the
> configuration menu in MPLab. Otherwise MPLab says the DevID do not match.
>
> The Pic is always supplied by the programmer (when choose in
> settings). I had doubts about that, thought that maybe the entry in
> programming mode was possible just after some VDD Off/ VDD On cycles.
>
> The delays: The MCLR ''high'' pulse have a duration of, approximately,
> 0.5Msec. Follow a MCLR ''low'' of 4Msec and the 32bits key. Not very
> new and conforms to the specs.
>
> More surprising: The 32 bits key is not the same as in the datasheet.
> Instead of 4D 43 48 50 I find 4D 43 24 28 !!! I must confirm that
> because I have just 5 seconds to read my scope screen during PicKit3
> read the code memory of the Pic, and I'm not very certain...
>
> Still searching for the truth !!! ;-)
>
> Have a nice Week End,
>
> Patrick
>
>
>
> Frans Schreuder a écrit :
>> Hi Patrick,
>>
>> I have added your additions to the subversion repository.
>> Thanks!
>>
>> Frans
>>
>> On 09/17/2010 01:29 AM, Patrick NIES wrote:
>>>
>>> Hi Frans,
>>>
>>> Two things:
>>>
>>> The capacitor on the VDDCore Pin must be between 5.4 and 18MF. I put
>>> 10MF here.
>>>
>>> The P19 time is largely greater than the one you have write =>
>>> 4Msec. I have added a 6Msec time to be safe, and another 6Msec
>>> between Vdd rise and first MCLR rise.
>>>
>>> In prog_lolvl.c:/
>>> /
>>>
>>> /
>>> if(picfamily==PIC18J)/
>>>
>>> / {/
>>>
>>> / TRISPGD_LOW = 0;/
>>>
>>> / PGD_LOW = 0; //PGD and PGC to 3.3V mode (output)/
>>>
>>> / TRISPGC_LOW = 0;/
>>>
>>> / PGC_LOW = 0;/
>>>
>>> / VDD=0; //VDD high,/
>>>
>>> */while((tick-lasttick)<6)continue;/*
>>>
>>> / clock_delay(); //P13 = 100ns min/
>>>
>>> / VPP_RUN=1; //VPP to 4.5V/
>>>
>>> / VPP_RUN=0; //and immediately back to 0.../
>>>
>>> */while((tick-lasttick)<6)continue;/*
>>>
>>> / clock_delay(); //P19 = 40ns min/
>>>
>>> / //write 0x4D43, high to low, other than the rest of the commands
>>> which are low to high.../
>>>
>>> / //0x3D43 => 0100 1101 0100 0011/
>>>
>>> / //from low to high => 1100 0010 1011 0010/
>>>
>>> / //0xC2B2 /
>>>
>>> / pic_send_word(0xC2B2);/
>>>
>>> / //write 0x4850 => 0100 1000 0101 0000 => 0000 1010 0001 0010 =>
>>> 0x0A12/
>>>
>>> / pic_send_word(0x0A12);/
>>>
>>> / VPP_RUN=1; /
>>>
>>> / return;/
>>>
>>> / }/
>>>
>>> Not yet tested.
>>>
>>> Cheers,
>>>
>>> Patrick
>>>
>>>
>>> Frans Schreuder a écrit :
>>>> Dear Patrick,
>>>>
>>>> This 32 bit key is implemented, however I have not gotten it to
>>>> work yet.
>>>> I will try to implement the X7J53 devices if you want to try them out.
>>>>
>>>> Frans.
>>>>
>>>> On 09/16/2010 10:13 AM, Patrick NIES wrote:
>>>>>
>>>>> Yes,
>>>>>
>>>>> /Entry into ICSP modes for PIC18F2XJXX/4XJXX family
>>>>> devices is somewhat different than previous PIC18
>>>>> devices. As shown in Figure 2-6, entering ICSP
>>>>> Program/Verify mode requires three steps:
>>>>> 1.   Voltage is briefly applied to the MCLR pin.
>>>>> 2.   A 32-bit key sequence is presented on PGD.
>>>>> 3.   Voltage is reapplied to MCLR and held.
>>>>> *The programming voltage applied to MCLR is VIH, or
>>>>> essentially, VDD*. There is no minimum time requirement
>>>>> for holding at VIH. After VIH is removed, an interval of at
>>>>> least P19 must elapse before presenting the key
>>>>> sequence on PGD.
>>>>>
>>>>> /Although the MCLR pin is 5.5V tolerant, in the programing specs
>>>>> VIH must not exceed VDD.
>>>>>
>>>>> I'll try with a zener diode...
>>>>>
>>>>> Patrick
>>>>> /
>>>>>
>>>>> /
>>>>>
>>>>> Frans Schreuder a écrit :
>>>>>> Dear Patrick,
>>>>>>
>>>>>> It is not that easy, also the 24J10 is not yet recognized. Please
>>>>>> do not connect them yet as I am not even sure if they might be
>>>>>> destroyed by usbpicprog.
>>>>>> I am still considering if it might be necessary to implement
>>>>>> another 3.3V zener diode on VPP while programming the 18FXXJXX
>>>>>> devices.
>>>>>>
>>>>>> Kind regards,
>>>>>>
>>>>>>
>>>>>> Frans Schreuder
>>>>>>
>>>>>> On 09/16/2010 01:25 AM, Patrick NIES wrote:
>>>>>>>
>>>>>>> Hi Frans,
>>>>>>>
>>>>>>> Could you please implement the 18f27j53 and the 18f47j53 ?
>>>>>>>
>>>>>>> I begin today some tests with this devices and it would be nice
>>>>>>> if they be recognised by UPP.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Patrick
>>>>>>>
>>>>>>> Frans Schreuder a écrit :
>>>>>>>> Hi Patrick,
>>>>>>>>
>>>>>>>> I will need some more time on the 24J10, but as soon as it is
>>>>>>>> working the 27j53 will be peanuts as well.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>>
>>>>>>>> Frans
>>>>>>>>
>>>>>>>> On 08/26/2010 01:14 AM, Patrick NIES wrote:
>>>>>>>>> Hi Frans,
>>>>>>>>>
>>>>>>>>> For a new project I would use a 18f27j53. I have seen that you
>>>>>>>>> have implemented and done some tests with 18f24j10 (with same
>>>>>>>>> programming specs) apparently unsuccessful as you mark it as
>>>>>>>>> "not working".
>>>>>>>>>
>>>>>>>>> Do you think it needs a little more time to spend to make it
>>>>>>>>> work or it seems to bee very hard to find what's wrong with
>>>>>>>>> these controllers ???
>>>>>>>>>  
>>>>>>>>> Thanks for your response.
>>>>>>>>>  
>>>>>>>>> Cheers,
>>>>>>>>>  
>>>>>>>>> Patrick
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>>

Re: [Usbpicprog-technical] Help making one. Getting strange results...

[RedoX <ad...@re...>]

 On 05/09/2010 12:48, Frans Schreuder wrote:
>  Hello,
>
> In case you don't get an e-mail from the mailing list, I also send it
> to your e-mail address.
> The voltage on R1 should be about 13.something volt, 12V is too low. I
> still suspect your capacitors.
> I am also curious what you connected as a target board, is there
> anything else besides the target microcontroller? Or did you maybe
> make other connections to the MCLR line?
>
> Good luck!
>
> Frans
Thanks,

I re-registered to the mailing-list so it should be ok now. Thanks !

According to your last advice, I tried to change the capacitors, first
by new 1uF => Still getting 12v at R1. Then I tried with 10uF and got
12.8v.

As target board, all I get is the target PIC (wired on a protoboard).
Nothing else.

I'll wait for the others PIC to arrive, then I'll try and keep you
updated. I don't have too much hope, but maybe the one I get were
damaged before I got them... Anyway, during my next holidays (in 6
weeks) I'll make an other board.

Thanks for you help :)

Re: [Usbpicprog-technical] Help making one. Getting strange results...

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

  Hello,

In case you don't get an e-mail from the mailing list, I also send it to 
your e-mail address.
The voltage on R1 should be about 13.something volt, 12V is too low. I 
still suspect your capacitors.
I am also curious what you connected as a target board, is there 
anything else besides the target microcontroller? Or did you maybe make 
other connections to the MCLR line?

Good luck!

Frans

Op 4-9-2010 23:06, RedoX schreef:
>   Hello,
>
> R13 is disconnected. That's what i though first, but because it was on
> the schematics I tried with... Now It's OK, left removed.
>
> In fact, the values I gave you were taken with a voltmeter (pretty
> accurate) and not only with the IO test program (there a difference of
> 0.20-0.30 V between the voltmeter and the software.)
>
> I tried removing the 12V Zener, without success.
>
> In fact, the voltage pump seems to work well: When I measure before Q4 I
> get a little more than 12V, but after Q4, the voltage doesn't reach more
> than 10.7-11V. This 2v loss seems common, normal with this kind of
> transistors... According to the datasheet: the Gate Threshold Voltage
> seems to be typically 2.1v. I tried to bypass Q4 but that's no good
> idea... VPP is good but no more controlled, so devices won't go in
> programming mode...
>
> I'm using 1uF 50V capacitors, it should be fine (and my getting 12v at
> R1 !), and I tried changing the transistor with a one picked from an
> other store (different serie, still BS170) without better result.
>
> When I tried to recognize the 18f, Vpp is around 10.7v, when I try with
> the 16F, VPP goes to 9.7v... According to the datasheets, theses VPP
> voltages are correct to enter programming mode, but shoudln't be
> differents and the 16f should be detected, even if it doesn't want to
> program (as the 18f is doing (but the device may be in cause, I'm not
> sure it's ok...))
>
> I'm waiting for some others 18F from Microchip, I'll try with these
> ones... And at last, I'll try an other board... Maybe I have some kind
> of bad luck with this one ^^
>
> I don't know how to reply directly to your reply, so I'm sending you
> this email. I hope I'm not wrong, I'm not quite familiar this Mailing lists.
> Moreover, I subscribed to the mailing list-archive , but got no
> notification of your answer... I'll check this.
>
> Thanks for your help.
>
> ------------------------------------------------------------------------------
> This SF.net Dev2Dev email is sponsored by:
>
> Show off your parallel programming skills.
> Enter the Intel(R) Threading Challenge 2010.
> http://p.sf.net/sfu/intel-thread-sfd
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical

Re: [Usbpicprog-technical] Help making one. Getting strange results...

[RedoX <ad...@re...>]

 Hello,

R13 is disconnected. That's what i though first, but because it was on
the schematics I tried with... Now It's OK, left removed.

In fact, the values I gave you were taken with a voltmeter (pretty
accurate) and not only with the IO test program (there a difference of
0.20-0.30 V between the voltmeter and the software.)

I tried removing the 12V Zener, without success.

In fact, the voltage pump seems to work well: When I measure before Q4 I
get a little more than 12V, but after Q4, the voltage doesn't reach more
than 10.7-11V. This 2v loss seems common, normal with this kind of
transistors... According to the datasheet: the Gate Threshold Voltage
seems to be typically 2.1v. I tried to bypass Q4 but that's no good
idea... VPP is good but no more controlled, so devices won't go in
programming mode...

I'm using 1uF 50V capacitors, it should be fine (and my getting 12v at
R1 !), and I tried changing the transistor with a one picked from an
other store (different serie, still BS170) without better result.

When I tried to recognize the 18f, Vpp is around 10.7v, when I try with
the 16F, VPP goes to 9.7v... According to the datasheets, theses VPP
voltages are correct to enter programming mode, but shoudln't be
differents and the 16f should be detected, even if it doesn't want to
program (as the 18f is doing (but the device may be in cause, I'm not
sure it's ok...))

I'm waiting for some others 18F from Microchip, I'll try with these
ones... And at last, I'll try an other board... Maybe I have some kind
of bad luck with this one ^^

I don't know how to reply directly to your reply, so I'm sending you
this email. I hope I'm not wrong, I'm not quite familiar this Mailing lists.
Moreover, I subscribed to the mailing list-archive , but got no
notification of your answer... I'll check this.

Thanks for your help.

Re: [Usbpicprog-technical] Help making one. Getting strange results...

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

Hello,

First of all, R13 should be left unmounted, that's why it has no value.
I don't think the ground plane is a problem here, but your VPP seems to
be too low, it should be somewhere around 12V (not 10.7). Could you also
measure it using a multimeter?
You can also try to remove the 12V Zener diode because it might be
causing problems (just leave it open).
Also have a look at the 1uf capacitors, maybe they have quite a high
resistance or their value is not good enough. You can also try 10uF
elcos for that.

I hope this will help you a bit further, anyway - don't hesitate to ask
again if it still doesn't work.

Frans

On 09/01/2010 12:02 AM, RedoX wrote:
>  Hello,
>
> First, I'm a French student, I know my English isn't perfect, but I'll
> try to make it look good. I apologize in advance for my mistakes. So:
>
> I've been trying (fighting ? ^^ ) to make a board of the through-hole
> version of UsbPicProg for almost a week now, but I'm still having a lot
> of problems with it... I got a single side board so, I'm not using the
> ground plane on top of the board, but put some jumpers to join grounds
> on the bottom plane. Maybe that's the cause of all my problems... Your
> opinion on that point ? I don't think that's a problem but am maybe
> wrong too :/
>
> I didn't put R13 on the board because, I didn't know what value
> choosing, and when I tried wit ha 10k Ohms resistor, the results were
> even worse, so I removed it. Am I wrong ?
>
> I'm currently using Archlinux 32bits  with the latest versions
> availables at download (r924 for the firmware).
> IO Test are showing promising results (10.7v on VPP, the others are OK.)
>
> I've checked and checked again my board, but I've got some weird results:
> I have 3 models of PICs: three 12F683, three 16f688 and two 18f2550 (one
> is on the board, the other one wasn't working well when I got It :/).
>
> With the 12f683, my board is working well. (Detect, Read, Erase, Check
> Blank, Program, .. Everything !)
> With the 18f2550, the chip is recognized, can be read, but write on it
> is not possible at all (erasing or programming, same result, no
> changes.) Voltages are OK in all ways: VPP, VDD, ... And the chip isn't
> dead, I'm able to program it with a JDM-like programmer (3-4 resistors,
> and a BS170 to get voltage on Vdd, it's not working without it (while
> the 12f683 is OK without the mosfet...)) with picprog software.
> With the 16f688, even worse... The chip isn't even recognized by the
> software. (I've tried different ones, no results)
>
> Oh, when I'm running the IO tests, board connected to a chip, I get this
> result: When I set Vpp to float and Vdd to 5v, Vpp goes to 4.7v (as Vdd
> really does).
>
> I tried many times, checked every traces, checked almost every single
> solder plot, checked all the transistors, ... Tried version 4.0 stable
> of the software and firmware. No results in any way.
> I've planned to make an other board, cleaner than this one (traces are
> not perfect everywhere) but I wish to make this one working if possible
> as I don't have to much time at the moment...
>
> Do you have any idea ? Met the same problems maybe ?
>
> First, thank for your project, very interesting.
> And Thanks in advance for every little piece of help you may give to me.
>
> ------------------------------------------------------------------------------
> This SF.net Dev2Dev email is sponsored by:
>
> Show off your parallel programming skills.
> Enter the Intel(R) Threading Challenge 2010.
> http://p.sf.net/sfu/intel-thread-sfd
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>   

[Usbpicprog-technical] Help making one. Getting strange results...

[RedoX <ad...@re...>]

 Hello,

First, I'm a French student, I know my English isn't perfect, but I'll
try to make it look good. I apologize in advance for my mistakes. So:

I've been trying (fighting ? ^^ ) to make a board of the through-hole
version of UsbPicProg for almost a week now, but I'm still having a lot
of problems with it... I got a single side board so, I'm not using the
ground plane on top of the board, but put some jumpers to join grounds
on the bottom plane. Maybe that's the cause of all my problems... Your
opinion on that point ? I don't think that's a problem but am maybe
wrong too :/

I didn't put R13 on the board because, I didn't know what value
choosing, and when I tried wit ha 10k Ohms resistor, the results were
even worse, so I removed it. Am I wrong ?

I'm currently using Archlinux 32bits  with the latest versions
availables at download (r924 for the firmware).
IO Test are showing promising results (10.7v on VPP, the others are OK.)

I've checked and checked again my board, but I've got some weird results:
I have 3 models of PICs: three 12F683, three 16f688 and two 18f2550 (one
is on the board, the other one wasn't working well when I got It :/).

With the 12f683, my board is working well. (Detect, Read, Erase, Check
Blank, Program, .. Everything !)
With the 18f2550, the chip is recognized, can be read, but write on it
is not possible at all (erasing or programming, same result, no
changes.) Voltages are OK in all ways: VPP, VDD, ... And the chip isn't
dead, I'm able to program it with a JDM-like programmer (3-4 resistors,
and a BS170 to get voltage on Vdd, it's not working without it (while
the 12f683 is OK without the mosfet...)) with picprog software.
With the 16f688, even worse... The chip isn't even recognized by the
software. (I've tried different ones, no results)

Oh, when I'm running the IO tests, board connected to a chip, I get this
result: When I set Vpp to float and Vdd to 5v, Vpp goes to 4.7v (as Vdd
really does).

I tried many times, checked every traces, checked almost every single
solder plot, checked all the transistors, ... Tried version 4.0 stable
of the software and firmware. No results in any way.
I've planned to make an other board, cleaner than this one (traces are
not perfect everywhere) but I wish to make this one working if possible
as I don't have to much time at the moment...

Do you have any idea ? Met the same problems maybe ?

First, thank for your project, very interesting.
And Thanks in advance for every little piece of help you may give to me.

Re: [Usbpicprog-technical] 16f884 won't program

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

Great news, so I can add it to the supported devices section? Does
everything work? (Data / Code / Config / Erase)

On 08/23/2010 08:21 PM, James Goode wrote:
> On Mon, 2010-08-23 at 08:42 +0200, Frans Schreuder wrote:
>   
>> Dear James,
>>
>> Could you try r924 of the firmware? (you can still use the installed
>> version of the PC software)
>>
>> You can find it here:
>> http://usbpicprog.org/downloads/firmware-924-20100823.tar.gz
>>
>> Kind regards,
>>
>> Frans Schreuder
>>
>> On 08/21/2010 08:31 PM, Frans Schreuder wrote:
>>     
>>> Using the development version probably won't help, I will have a look at
>>> the 16F884 code soon.
>>>
>>> Kind regards,
>>>
>>> Frans Schreuder
>>>
>>> On 08/21/2010 03:25 PM, James Goode wrote:
>>>   
>>>       
>>>> On Sat, 2010-08-21 at 14:47 +0200, Frans Schreuder wrote:
>>>>   
>>>>     
>>>>         
>>>>> Dear James,
>>>>>
>>>>> It seems something is wrong in the firmware of usbpicprog for this
>>>>> device. I will have a look at it somewhere this week.
>>>>> Can you tell me which version of the software / firmware you are using?
>>>>> I guess 0.4.0 for both?
>>>>>
>>>>> Kind regards,
>>>>>
>>>>> Frans Schreuder
>>>>>
>>>>> On 08/21/2010 12:47 PM, James Goode wrote:
>>>>>     
>>>>>       
>>>>>           
>>>>>> Hi,
>>>>>>
>>>>>> I have a small program (about 60 bytes) that I'd like to write to a
>>>>>> 16f884.  It seems to program fine, but when I read the program, bytes
>>>>>> 00-07, 10-17, 20-27, 30-37, 40-47, 50-57 (hex) are FF 3F FF 3F FF 3F FF
>>>>>> 3F.  The program does not run when I connect the PIC to it's circuit.
>>>>>>
>>>>>> Any idea what is wrong?
>>>>>>
>>>>>> --James.
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> This SF.net email is sponsored by 
>>>>>>
>>>>>> Make an app they can't live without
>>>>>> Enter the BlackBerry Developer Challenge
>>>>>> http://p.sf.net/sfu/RIM-dev2dev 
>>>>>> _______________________________________________
>>>>>> Usbpicprog-technical mailing list
>>>>>> Usb...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>>>>>>   
>>>>>>       
>>>>>>         
>>>>>>             
>>>>> ------------------------------------------------------------------------------
>>>>> This SF.net email is sponsored by 
>>>>>
>>>>> Make an app they can't live without
>>>>> Enter the BlackBerry Developer Challenge
>>>>> http://p.sf.net/sfu/RIM-dev2dev 
>>>>> _______________________________________________ Usbpicprog-technical mailing list Usb...@li... https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>>>>>     
>>>>>       
>>>>>           
>>>> Hi,
>>>>
>>>> I am using software 0.4.0-1 and hardware 0.4.0.  Should I try using the
>>>> development version of the software?
>>>>
>>>> --James.
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> This SF.net email is sponsored by 
>>>>
>>>> Make an app they can't live without
>>>> Enter the BlackBerry Developer Challenge
>>>> http://p.sf.net/sfu/RIM-dev2dev 
>>>> _______________________________________________
>>>> Usbpicprog-technical mailing list
>>>> Usb...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>>>>   
>>>>     
>>>>         
>>>   
>>>       
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by 
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev 
>> _______________________________________________ Usbpicprog-technical mailing list Usb...@li... https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>>     
>
> Hi,
>
> It works fine with r924.
>
> Many thanks,
>
> --James.
>
>
>
> ------------------------------------------------------------------------------
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users 
> worldwide. Take advantage of special opportunities to increase revenue and 
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>   

Re: [Usbpicprog-technical] 16f884 won't program

[James G. <ja...@jg...>]

On Mon, 2010-08-23 at 08:42 +0200, Frans Schreuder wrote:
> Dear James,
> 
> Could you try r924 of the firmware? (you can still use the installed
> version of the PC software)
> 
> You can find it here:
> http://usbpicprog.org/downloads/firmware-924-20100823.tar.gz
> 
> Kind regards,
> 
> Frans Schreuder
> 
> On 08/21/2010 08:31 PM, Frans Schreuder wrote:
> > Using the development version probably won't help, I will have a look at
> > the 16F884 code soon.
> >
> > Kind regards,
> >
> > Frans Schreuder
> >
> > On 08/21/2010 03:25 PM, James Goode wrote:
> >   
> >> On Sat, 2010-08-21 at 14:47 +0200, Frans Schreuder wrote:
> >>   
> >>     
> >>> Dear James,
> >>>
> >>> It seems something is wrong in the firmware of usbpicprog for this
> >>> device. I will have a look at it somewhere this week.
> >>> Can you tell me which version of the software / firmware you are using?
> >>> I guess 0.4.0 for both?
> >>>
> >>> Kind regards,
> >>>
> >>> Frans Schreuder
> >>>
> >>> On 08/21/2010 12:47 PM, James Goode wrote:
> >>>     
> >>>       
> >>>> Hi,
> >>>>
> >>>> I have a small program (about 60 bytes) that I'd like to write to a
> >>>> 16f884.  It seems to program fine, but when I read the program, bytes
> >>>> 00-07, 10-17, 20-27, 30-37, 40-47, 50-57 (hex) are FF 3F FF 3F FF 3F FF
> >>>> 3F.  The program does not run when I connect the PIC to it's circuit.
> >>>>
> >>>> Any idea what is wrong?
> >>>>
> >>>> --James.
> >>>>
> >>>>
> >>>>
> >>>> ------------------------------------------------------------------------------
> >>>> This SF.net email is sponsored by 
> >>>>
> >>>> Make an app they can't live without
> >>>> Enter the BlackBerry Developer Challenge
> >>>> http://p.sf.net/sfu/RIM-dev2dev 
> >>>> _______________________________________________
> >>>> Usbpicprog-technical mailing list
> >>>> Usb...@li...
> >>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
> >>>>   
> >>>>       
> >>>>         
> >>> ------------------------------------------------------------------------------
> >>> This SF.net email is sponsored by 
> >>>
> >>> Make an app they can't live without
> >>> Enter the BlackBerry Developer Challenge
> >>> http://p.sf.net/sfu/RIM-dev2dev 
> >>> _______________________________________________ Usbpicprog-technical mailing list Usb...@li... https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
> >>>     
> >>>       
> >> Hi,
> >>
> >> I am using software 0.4.0-1 and hardware 0.4.0.  Should I try using the
> >> development version of the software?
> >>
> >> --James.
> >>
> >>
> >> ------------------------------------------------------------------------------
> >> This SF.net email is sponsored by 
> >>
> >> Make an app they can't live without
> >> Enter the BlackBerry Developer Challenge
> >> http://p.sf.net/sfu/RIM-dev2dev 
> >> _______________________________________________
> >> Usbpicprog-technical mailing list
> >> Usb...@li...
> >> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
> >>   
> >>     
> >   
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by 
> 
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> _______________________________________________ Usbpicprog-technical mailing list Usb...@li... https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical


Hi,

It works fine with r924.

Many thanks,

--James.

Re: [Usbpicprog-technical] 16f884 won't program

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

Dear James,

Could you try r924 of the firmware? (you can still use the installed
version of the PC software)

You can find it here:
http://usbpicprog.org/downloads/firmware-924-20100823.tar.gz

Kind regards,

Frans Schreuder

On 08/21/2010 08:31 PM, Frans Schreuder wrote:
> Using the development version probably won't help, I will have a look at
> the 16F884 code soon.
>
> Kind regards,
>
> Frans Schreuder
>
> On 08/21/2010 03:25 PM, James Goode wrote:
>   
>> On Sat, 2010-08-21 at 14:47 +0200, Frans Schreuder wrote:
>>   
>>     
>>> Dear James,
>>>
>>> It seems something is wrong in the firmware of usbpicprog for this
>>> device. I will have a look at it somewhere this week.
>>> Can you tell me which version of the software / firmware you are using?
>>> I guess 0.4.0 for both?
>>>
>>> Kind regards,
>>>
>>> Frans Schreuder
>>>
>>> On 08/21/2010 12:47 PM, James Goode wrote:
>>>     
>>>       
>>>> Hi,
>>>>
>>>> I have a small program (about 60 bytes) that I'd like to write to a
>>>> 16f884.  It seems to program fine, but when I read the program, bytes
>>>> 00-07, 10-17, 20-27, 30-37, 40-47, 50-57 (hex) are FF 3F FF 3F FF 3F FF
>>>> 3F.  The program does not run when I connect the PIC to it's circuit.
>>>>
>>>> Any idea what is wrong?
>>>>
>>>> --James.
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> This SF.net email is sponsored by 
>>>>
>>>> Make an app they can't live without
>>>> Enter the BlackBerry Developer Challenge
>>>> http://p.sf.net/sfu/RIM-dev2dev 
>>>> _______________________________________________
>>>> Usbpicprog-technical mailing list
>>>> Usb...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>>>>   
>>>>       
>>>>         
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by 
>>>
>>> Make an app they can't live without
>>> Enter the BlackBerry Developer Challenge
>>> http://p.sf.net/sfu/RIM-dev2dev 
>>> _______________________________________________ Usbpicprog-technical mailing list Usb...@li... https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>>>     
>>>       
>> Hi,
>>
>> I am using software 0.4.0-1 and hardware 0.4.0.  Should I try using the
>> development version of the software?
>>
>> --James.
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by 
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev 
>> _______________________________________________
>> Usbpicprog-technical mailing list
>> Usb...@li...
>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>>   
>>     
>   

Re: [Usbpicprog-technical] 16f884 won't program

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

Using the development version probably won't help, I will have a look at
the 16F884 code soon.

Kind regards,

Frans Schreuder

On 08/21/2010 03:25 PM, James Goode wrote:
> On Sat, 2010-08-21 at 14:47 +0200, Frans Schreuder wrote:
>   
>> Dear James,
>>
>> It seems something is wrong in the firmware of usbpicprog for this
>> device. I will have a look at it somewhere this week.
>> Can you tell me which version of the software / firmware you are using?
>> I guess 0.4.0 for both?
>>
>> Kind regards,
>>
>> Frans Schreuder
>>
>> On 08/21/2010 12:47 PM, James Goode wrote:
>>     
>>> Hi,
>>>
>>> I have a small program (about 60 bytes) that I'd like to write to a
>>> 16f884.  It seems to program fine, but when I read the program, bytes
>>> 00-07, 10-17, 20-27, 30-37, 40-47, 50-57 (hex) are FF 3F FF 3F FF 3F FF
>>> 3F.  The program does not run when I connect the PIC to it's circuit.
>>>
>>> Any idea what is wrong?
>>>
>>> --James.
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by 
>>>
>>> Make an app they can't live without
>>> Enter the BlackBerry Developer Challenge
>>> http://p.sf.net/sfu/RIM-dev2dev 
>>> _______________________________________________
>>> Usbpicprog-technical mailing list
>>> Usb...@li...
>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>>>   
>>>       
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by 
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev 
>> _______________________________________________ Usbpicprog-technical mailing list Usb...@li... https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>>     
>
> Hi,
>
> I am using software 0.4.0-1 and hardware 0.4.0.  Should I try using the
> development version of the software?
>
> --James.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by 
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>   

Re: [Usbpicprog-technical] 16f884 won't program

[James G. <ja...@jg...>]

On Sat, 2010-08-21 at 14:47 +0200, Frans Schreuder wrote:
> Dear James,
> 
> It seems something is wrong in the firmware of usbpicprog for this
> device. I will have a look at it somewhere this week.
> Can you tell me which version of the software / firmware you are using?
> I guess 0.4.0 for both?
> 
> Kind regards,
> 
> Frans Schreuder
> 
> On 08/21/2010 12:47 PM, James Goode wrote:
> > Hi,
> >
> > I have a small program (about 60 bytes) that I'd like to write to a
> > 16f884.  It seems to program fine, but when I read the program, bytes
> > 00-07, 10-17, 20-27, 30-37, 40-47, 50-57 (hex) are FF 3F FF 3F FF 3F FF
> > 3F.  The program does not run when I connect the PIC to it's circuit.
> >
> > Any idea what is wrong?
> >
> > --James.
> >
> >
> >
> > ------------------------------------------------------------------------------
> > This SF.net email is sponsored by 
> >
> > Make an app they can't live without
> > Enter the BlackBerry Developer Challenge
> > http://p.sf.net/sfu/RIM-dev2dev 
> > _______________________________________________
> > Usbpicprog-technical mailing list
> > Usb...@li...
> > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
> >   
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by 
> 
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> _______________________________________________ Usbpicprog-technical mailing list Usb...@li... https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical


Hi,

I am using software 0.4.0-1 and hardware 0.4.0.  Should I try using the
development version of the software?

--James.

Re: [Usbpicprog-technical] 16f884 won't program

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

Dear James,

It seems something is wrong in the firmware of usbpicprog for this
device. I will have a look at it somewhere this week.
Can you tell me which version of the software / firmware you are using?
I guess 0.4.0 for both?

Kind regards,

Frans Schreuder

On 08/21/2010 12:47 PM, James Goode wrote:
> Hi,
>
> I have a small program (about 60 bytes) that I'd like to write to a
> 16f884.  It seems to program fine, but when I read the program, bytes
> 00-07, 10-17, 20-27, 30-37, 40-47, 50-57 (hex) are FF 3F FF 3F FF 3F FF
> 3F.  The program does not run when I connect the PIC to it's circuit.
>
> Any idea what is wrong?
>
> --James.
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by 
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>   

[Usbpicprog-technical] 16f884 won't program

[James G. <ja...@jg...>]

Hi,

I have a small program (about 60 bytes) that I'd like to write to a
16f884.  It seems to program fine, but when I read the program, bytes
00-07, 10-17, 20-27, 30-37, 40-47, 50-57 (hex) are FF 3F FF 3F FF 3F FF
3F.  The program does not run when I connect the PIC to it's circuit.

Any idea what is wrong?

--James.

Re: [Usbpicprog-technical] programmer not detected

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

Dear aa zz,

First of all, please try to be more specific in your questions; all your
questions are very short, cryptical and I always need to guess what
exactly do you mean!
With settings, I guess you mean the configuration word of the PIC18F2550
controller in usbpicprog? They are given in the .hex file.
Or do you mean the settings of WinPic800? That depends on the programmer
you are using, but mostly, if it detects the PIC18F2550, it is alright.
(you just need to verify, and make sure it programs at least program
memory and configuration words).

Frans

On 07/26/2010 10:29 AM, aa zz wrote:
> Hi
>
> What are the settings need to done when downloading the bootloader for
> the firstime using WinPic800 ?
>
> Thx
>
> ------------------------------------------------------------------------
> *From:* Frans Schreuder <fra...@gm...>
> *To:* usb...@li...
> *Sent:* Sunday, 25 July 2010 18:46:09
> *Subject:* Re: [Usbpicprog-technical] programmer not detected
>
> Hi,
>
> The steps you followed are right, although I can't see if you followed
> all the steps carefully.
> When you plug in the usbpicprog programmer, you also have to install the
> driver (found in the program files\usbpicprog\driver directory)
> If Windows is giving you this message ("Usb device not recognized"),
> then you have probably not soldered something correctly.
> It could be the capacitor on the Vusb pin of the PIC18F2550.
> Have you also verified that the bootloader was programmed correctly?
> Have you placed the jumper between MCLR and VDD on the "self programming
> header"?
> You could also try a different operating system (e.g. Ubuntu) and see if
> it works there, in Ubuntu you don't have to install any drivers.
> If it's still not working, please let me know which leds on the
> programmer are on.
>
> Kind regards,
>
> Frans Schreuder
>
> aa zz schreef:
> > Hi
> >
> > Here are the details ..
> >
> > 1. create UsbPicProg circuit based on schematic shown in the website,
> > ( usbpicprog-hardware-0.3.1.pdf )
> > 2. download the bootloader ( boot1.0.hex, from firmware-0.4.0 folder )
> > on the chip using another programmer; using WinPic800
> > 3. install the chip on UsbPicProg programmer, created in step 1
> > 4. plug the programmer to laptop ( running Win XP ), and i get "USB
> > Device Not Recognized"
> >
> > Plz help
> >
> > ------------------------------------------------------------------------
> > *From:* Frans Schreuder <fra...@gm...
> <mailto:fra...@gm...>>
> > *To:* usb...@li...
> <mailto:usb...@li...>
> > *Sent:* Friday, 23 July 2010 14:29:54
> > *Subject:* Re: [Usbpicprog-technical] programmer not detected
> >
> > Hi,
> >
> > Have you tried the jumpers?
> > Did you solder everything correctly?
> >
> > You need to give more information...
> >
> > Frans
> >
> > On 07/22/2010 05:53 PM, aa zz wrote:
> >> Hi
> >>
> >> I have program the bootloader, but no bootloder or programmer found ?
> >> Any idea
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> This SF.net email is sponsored by Sprint
> >> What will you do first with EVO, the first 4G phone?
> >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> >>
> >>
> >> _______________________________________________
> >> Usbpicprog-technical mailing list
> >> Usb...@li...
> <mailto:Usb...@li...>
> >> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
> >> 
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Sprint
> > What will you do first with EVO, the first 4G phone?
> > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Usbpicprog-technical mailing list
> > Usb...@li...
> <mailto:Usb...@li...>
> > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
> > 
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> <mailto:Usb...@li...>
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>
>
> ------------------------------------------------------------------------------
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share 
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://ad.doubleclick.net/clk;226879339;13503038;l?
> http://clk.atdmt.com/CRS/go/247765532/direct/01/
>
>
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>   

Re: [Usbpicprog-technical] programmer not detected

[aa zz <ber...@ya...>]

Hi

What are the settings need to done when downloading the bootloader for the 
firstime using WinPic800 ?

Thx




________________________________
From: Frans Schreuder <fra...@gm...>
To: usb...@li...
Sent: Sunday, 25 July 2010 18:46:09
Subject: Re: [Usbpicprog-technical] programmer not detected

Hi,

The steps you followed are right, although I can't see if you followed 
all the steps carefully.
When you plug in the usbpicprog programmer, you also have to install the 
driver (found in the program files\usbpicprog\driver directory)
If Windows is giving you this message ("Usb device not recognized"), 
then you have probably not soldered something correctly.
It could be the capacitor on the Vusb pin of the PIC18F2550.
Have you also verified that the bootloader was programmed correctly?
Have you placed the jumper between MCLR and VDD on the "self programming 
header"?
You could also try a different operating system (e.g. Ubuntu) and see if 
it works there, in Ubuntu you don't have to install any drivers.
If it's still not working, please let me know which leds on the 
programmer are on.

Kind regards,

Frans Schreuder

aa zz schreef:
> Hi
>
> Here are the details ..
>
> 1. create UsbPicProg circuit based on schematic shown in the website, 
> ( usbpicprog-hardware-0.3.1.pdf )
> 2. download the bootloader ( boot1.0.hex, from firmware-0.4.0 folder ) 
> on the chip using another programmer; using WinPic800
> 3. install the chip on UsbPicProg programmer, created in step 1
> 4. plug the programmer to laptop ( running Win XP ), and i get "USB 
> Device Not Recognized"
>
> Plz help
>
> ------------------------------------------------------------------------
> *From:* Frans Schreuder <fra...@gm...>
> *To:* usb...@li...
> *Sent:* Friday, 23 July 2010 14:29:54
> *Subject:* Re: [Usbpicprog-technical] programmer not detected
>
> Hi,
>
> Have you tried the jumpers?
> Did you solder everything correctly?
>
> You need to give more information...
>
> Frans
>
> On 07/22/2010 05:53 PM, aa zz wrote:
>> Hi
>>
>> I have program the bootloader, but no bootloder or programmer found ? 
>> Any idea
>>
>>
>> 
------------------------------------------------------------------------------
>> This SF.net email is sponsored by Sprint
>> What will you do first with EVO, the first 4G phone?
>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>>
>>
>> _______________________________________________
>> Usbpicprog-technical mailing list
>> Usb...@li...
>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>>  
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> ------------------------------------------------------------------------
>
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>  


------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Usbpicprog-technical mailing list
Usb...@li...
https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical

Re: [Usbpicprog-technical] programmer not detected

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

Hi,

The steps you followed are right, although I can't see if you followed 
all the steps carefully.
When you plug in the usbpicprog programmer, you also have to install the 
driver (found in the program files\usbpicprog\driver directory)
If Windows is giving you this message ("Usb device not recognized"), 
then you have probably not soldered something correctly.
It could be the capacitor on the Vusb pin of the PIC18F2550.
Have you also verified that the bootloader was programmed correctly?
Have you placed the jumper between MCLR and VDD on the "self programming 
header"?
You could also try a different operating system (e.g. Ubuntu) and see if 
it works there, in Ubuntu you don't have to install any drivers.
If it's still not working, please let me know which leds on the 
programmer are on.

Kind regards,

Frans Schreuder

aa zz schreef:
> Hi
>
> Here are the details ..
>
> 1. create UsbPicProg circuit based on schematic shown in the website, 
> ( usbpicprog-hardware-0.3.1.pdf )
> 2. download the bootloader ( boot1.0.hex, from firmware-0.4.0 folder ) 
> on the chip using another programmer; using WinPic800
> 3. install the chip on UsbPicProg programmer, created in step 1
> 4. plug the programmer to laptop ( running Win XP ), and i get "USB 
> Device Not Recognized"
>
> Plz help
>
> ------------------------------------------------------------------------
> *From:* Frans Schreuder <fra...@gm...>
> *To:* usb...@li...
> *Sent:* Friday, 23 July 2010 14:29:54
> *Subject:* Re: [Usbpicprog-technical] programmer not detected
>
> Hi,
>
> Have you tried the jumpers?
> Did you solder everything correctly?
>
> You need to give more information...
>
> Frans
>
> On 07/22/2010 05:53 PM, aa zz wrote:
>> Hi
>>
>> I have program the bootloader, but no bootloder or programmer found ? 
>> Any idea
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Sprint
>> What will you do first with EVO, the first 4G phone?
>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>>
>>
>> _______________________________________________
>> Usbpicprog-technical mailing list
>> Usb...@li...
>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>>   
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> ------------------------------------------------------------------------
>
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>   

Re: [Usbpicprog-technical] programmer not detected

[aa zz <ber...@ya...>]

Hi

Here are the details ..

1. create UsbPicProg circuit based on schematic shown in the website, ( 
usbpicprog-hardware-0.3.1.pdf )
2. download the bootloader ( boot1.0.hex, from firmware-0.4.0 folder ) on the 
chip using another programmer; using WinPic800
3. install the chip on UsbPicProg programmer, created in step 1
4. plug the programmer to laptop ( running Win XP ), and i get "USB Device Not 
Recognized"


Plz help



________________________________
From: Frans Schreuder <fra...@gm...>
To: usb...@li...
Sent: Friday, 23 July 2010 14:29:54
Subject: Re: [Usbpicprog-technical] programmer not detected

 Hi,

Have you tried the jumpers?
Did you solder everything correctly?

You need to give more information...

Frans

On 07/22/2010 05:53 PM, aa zz wrote: 
Hi
>
>I have program the bootloader, but no bootloder or programmer found ? Any idea
>
>
> ------------------------------------------------------------------------------ 
>This SF.net email is sponsored by Sprint What will you do first with EVO, the 
>first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________ Usbpicprog-technical mailing 
>list Usb...@li... 
>https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical 
>

Re: [Usbpicprog-technical] programmer not detected

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

Hi,

Have you tried the jumpers?
Did you solder everything correctly?

You need to give more information...

Frans

On 07/22/2010 05:53 PM, aa zz wrote:
> Hi
>
> I have program the bootloader, but no bootloder or programmer found ?
> Any idea
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>
>
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>