( I'm not sure if this would be posted here or usbpicprog-technical.
Anyway I posted it here )
I'm using usbpicprog (on a stripboard) with linux zorin 9 64 bit (ubuntu based).
After programmed the bootloader ( boot1.0 from firmware-0.9.9-1.0.0-beta.zip )
into usbpicprog with an external programmer, the usbpicprog is recognized
by the software on linux (usbpicprog 0.9.9-1.0.0-beta - 64 bit) and, with jumper
between VDD and VPP_SELF, all leds are on and says bootloaderv1.0 connected.
After open firmware-0.9.9-1.0.0-beta.hex (also from firmware-0.9.9-1.0.0-beta.zip)
and click select actions>program, the firmware is written the the pic and all is
achieved with success at the final.
My question:
Its is said at usbpicprog website to, at this point, disconnect usppicprog and connect it again after put a jumper between GND and PGC_SELF (maintaining the other one between
VDD and VPP_SELF) so it enters the normal operation (to program PICs by ICSP through usbpicprog programmer).
The problem: it is always entering the bootloader mode (even with the two jumpers GND/PGC_SELF and VDD/VPP_SELF on place) because the usbpicprog 0.9.9-1.0.0-beta - 64 bit on linux continues saying bootloaderv1.0 connected.
How to really start usbpicprog in normal mode after succeed firmeware programming like
in my case?
Really lots of thanks in advance,
Miguel Garcia
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
From your description, it seems you are programming the device in the right way. Have you removed the usb connector and restarted usbpicprog after adding the jumpers?
Frans
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"Have you removed the usb connector and restarted usbpicprog after adding the jumpers?"
As it is explained on my question, yes.
Can I ask something more, just to be shure?
1-
From firmware firmware-0.9.9-1.0.0-beta.zip , is it to
be programming the bootloader boot1.0.hex or boot.hex ?
2-
Jumper between VPP_SELF/VDD (MCLR/VDD) is never removed in bootloader or normal operation as MCLR is set to external, so this pin must be 5V for the pic to start and run.
I'm I right?
3-
The only situation where we remove the Jumper between VPP_SELF/VDD (MCLR/VDD) is if we want to ISCP the pic on the board itself, from an external programmer because it needs to have control on MCLR
I'm I right?
4-
PORTB has its pullups enabled by the bootloader, so if we put the jumper between PGC_SELF/GND (RB6/GND), RB6 is driven 0 and if we remove this jumper, RB6 is not floating but 5V driven from internal pullup.
I'm I right?
5-
If point 4- is right and if you say it will enter bootloader with only VPP_SELF/VDD jumper, RB6 is 5V driven from internal pullup (as there is anything connecting it to GND, so bootloader is entered with a logic high level at PGC_SELF .
I'm I right?
6-
When we put both jumpers:
MCLR (VPP_SELF) is driven high (as ever).
RB6 (VPP_SELF) is driven low so bootloader is prevented
and the picusbprog enters normal operation (for programming
other pics in the ICSP way.
I'm I right?
Lots of thanks again,
Miguel Garcia
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1: boot-1.0.hex or boot.hex should be the same
2: Right, you can remove it to reset the PIC, without removing the USB connector
3: Right, see 2.
4: Also right, this should make it jump to normal operation
5: Exaclty
6: Right
Your assumptions are all right, I hope you will get it to work soon, I guess there is something in your soldering or something if it still doesn't work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello
( I'm not sure if this would be posted here or usbpicprog-technical.
Anyway I posted it here )
I'm using usbpicprog (on a stripboard) with linux zorin 9 64 bit (ubuntu based).
After programmed the bootloader ( boot1.0 from firmware-0.9.9-1.0.0-beta.zip )
into usbpicprog with an external programmer, the usbpicprog is recognized
by the software on linux (usbpicprog 0.9.9-1.0.0-beta - 64 bit) and, with jumper
between VDD and VPP_SELF, all leds are on and says bootloaderv1.0 connected.
After open firmware-0.9.9-1.0.0-beta.hex (also from firmware-0.9.9-1.0.0-beta.zip)
and click select actions>program, the firmware is written the the pic and all is
achieved with success at the final.
My question:
Its is said at usbpicprog website to, at this point, disconnect usppicprog and connect it again after put a jumper between GND and PGC_SELF (maintaining the other one between
VDD and VPP_SELF) so it enters the normal operation (to program PICs by ICSP through usbpicprog programmer).
The problem: it is always entering the bootloader mode (even with the two jumpers GND/PGC_SELF and VDD/VPP_SELF on place) because the usbpicprog 0.9.9-1.0.0-beta - 64 bit on linux continues saying bootloaderv1.0 connected.
How to really start usbpicprog in normal mode after succeed firmeware programming like
in my case?
Really lots of thanks in advance,
Miguel Garcia
Dear Miguel Garcia,
From your description, it seems you are programming the device in the right way. Have you removed the usb connector and restarted usbpicprog after adding the jumpers?
Frans
Hello
Before anything, thanks for your rapid answer.
"Have you removed the usb connector and restarted usbpicprog after adding the jumpers?"
As it is explained on my question, yes.
Can I ask something more, just to be shure?
1-
From firmware firmware-0.9.9-1.0.0-beta.zip , is it to
be programming the bootloader boot1.0.hex or boot.hex ?
2-
Jumper between VPP_SELF/VDD (MCLR/VDD) is never removed in bootloader or normal operation as MCLR is set to external, so this pin must be 5V for the pic to start and run.
I'm I right?
3-
The only situation where we remove the Jumper between VPP_SELF/VDD (MCLR/VDD) is if we want to ISCP the pic on the board itself, from an external programmer because it needs to have control on MCLR
I'm I right?
4-
PORTB has its pullups enabled by the bootloader, so if we put the jumper between PGC_SELF/GND (RB6/GND), RB6 is driven 0 and if we remove this jumper, RB6 is not floating but 5V driven from internal pullup.
I'm I right?
5-
If point 4- is right and if you say it will enter bootloader with only VPP_SELF/VDD jumper, RB6 is 5V driven from internal pullup (as there is anything connecting it to GND, so bootloader is entered with a logic high level at PGC_SELF .
I'm I right?
6-
When we put both jumpers:
MCLR (VPP_SELF) is driven high (as ever).
RB6 (VPP_SELF) is driven low so bootloader is prevented
and the picusbprog enters normal operation (for programming
other pics in the ICSP way.
I'm I right?
Lots of thanks again,
Miguel Garcia
1: boot-1.0.hex or boot.hex should be the same
2: Right, you can remove it to reset the PIC, without removing the USB connector
3: Right, see 2.
4: Also right, this should make it jump to normal operation
5: Exaclty
6: Right
Your assumptions are all right, I hope you will get it to work soon, I guess there is something in your soldering or something if it still doesn't work.