Have just started using PICkit2PLUS, and get a warning when loading certain .hex files (attached), however the programs seem to run fine after written to the PIC. What should I be checking for?
I find the cli difficult to understand.
I found I can use pickit2 or 3 with no setting change and pickit 2/3 plus when first try failed.
Not a clue about voltage and other settings.
eg. 18f25k22 running at 3.3V. I don't know which option to use but somehow I can get it to flash hex and it works.
This is not gcb problem but using pickit in general.
This is why I prefer to use avr. It's easier to use and a 328 is more functional than a 18f25k22.
I looked up the actual pickit to chip wiring and there's options with a cap,diode and resistor I used on a project but for bread board it's pin1 RE3/VPP/MCLR,
pin 28 RB7 RX2/DT2
pin 27 RB6/TX2.CK2
and ground.
This is icsp I think but still not a clue. It works for my robots and a glcd setup...if it feels like it.
I got a northern programmer if anyone wants it...I never got it to work.
I find a nano 328 a nice little board and switching the programmer options easy as drag to top of list and just change com port if needed.
Just my thoughts of using same gcb code on pic and avr.
Not everone uses command line code or knows scripting.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I got a northern programmer if anyone wants it...I never got it to work.
If Anobium hadn't got his claim in first, I'd have staked a claim to this!
I love my NSDSP programmer. It is superbly quick, superbly reliable and macOS compatible. I use mine multiple times daily both at home and (mainly) at work. The other day I sat and programmed 150 tiny 12F1840 chips that were soldered on the board using a little 'clip' adapter and my NSDSP programmer. I'm thinking of making a six or eight way gang programmer with them.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Have a look in the installation. The command line Help is extensive and we have include CLI guide using with compilers like the Proton IDE.
I found I can use pickit2 or 3 with no setting change and pickit 2/3 plus when first try failed.
Not a clue about voltage and other settings.
The programming datasheet is a great resource for this data.
eg. 18f25k22 running at 3.3V. I don't know which option to use but somehow I can get it to flash hex and it works.
Good to hear,
This is not gcb problem but using pickit in general.
When you refer to GCB you do mean Great Cow BASIC where we have already integrated the CLI into the programming experience.
As more users share the IDE experience the guides will improve.
Re the PICKit in general. In the installation folder there are two very good guides to the PICkit2 and PICkit2 and the software.
This is why I prefer to use avr. It's easier to use and a 328 is more functional than a 18f25k22.
I looked up the actual pickit to chip wiring and there's options with a cap,diode and resistor I used on a project but for bread board it's pin1 RE3/VPP/MCLR,
pin 28 RB7 RX2/DT2
pin 27 RB6/TX2.CK2
and ground.
We have investigate and rejected programming AVR. There are some great tools out there.
Re AVR v PIC I do not have a view - PICKitPlus is for PIC.
This is icsp I think but still not a clue. It works for my robots and a glcd setup...if it feels like it.
In the installation folder there are two very good guides to the PICkit2 and PICkit2 and the software.
I got a northern programmer if anyone wants it...I never got it to work.
Send to me, You do know my adderss.
But, this is typically a simple process to resolve. To use the NSProgrammer. First erase the chip with PICKitPlus and the NSProgrammer should work.
I find a nano 328 a nice little board and switching the programmer options easy as drag to top of list and just change com port if needed.
Good to here.
Just my thoughts of using same gcb code on pic and avr.
Great Cow BASIC is a great portable language, so, this good to hear.
Not everone uses command line code or knows scripting.
Very true. Using PICKitAutoWatch does resolve learning CLI or scripting.
The more guides we write the easier is should get - for everyone.
Cheers
Last edit: Anobium 2020-01-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks. The onus is on me to learn.
PICKitAutoWatch is new to me.
I will use the pic and ili9341 as working project..cos it works
but what advantage over clicking flash hex button and it does?
pic on gcb seems to have a mind of it's own ie it shows pic or doesn't.
complains no supply or just works.
As is I have pickit2 connected to pic and can power the board but the program won't run until usb connected to pickit 2.
If I disconnect pickit2 from the board and power it starts the program.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can use the cli and flash hex or trying the picautowatch.
cli just does it.
Why don't it show the programmer or the chip in use?
not intuative. press button and see. not.
sorry, I don't get the point of this app or I'd use it.
Is it for new pics only that pk+ handles?
Why can't it find the file from the gcb file that is open in the ide and then the device and programmer?
I had to say the hex file and then find the pic from a list.
I then found if you restart it, it's forgotten previous settings.
What does ticking the boxes do?
what does #config MCLRE=on ... do, or doesn't?
I don't like using pics...unless they're on a usb microchip dev board.
I think there's some 40 pin pics with loads of ram and features to explore and that's where pk+ comes in. There seems problems using them though from the forum.
I'll wait before going through pps again. uchip data and the pin meanings etc. complicated stuff.
not fun.
Have just started using PICkit2PLUS, and get a warning when loading certain .hex files (attached), however the programs seem to run fine after written to the PIC. What should I be checking for?
Your program is for a 12f683 and you have a 16f88 select in the software.
Correct one of them, source code or the chip seletion, as they need to be the same.
I find the cli difficult to understand.
I found I can use pickit2 or 3 with no setting change and pickit 2/3 plus when first try failed.
Not a clue about voltage and other settings.
eg. 18f25k22 running at 3.3V. I don't know which option to use but somehow I can get it to flash hex and it works.
This is not gcb problem but using pickit in general.
This is why I prefer to use avr. It's easier to use and a 328 is more functional than a 18f25k22.
I looked up the actual pickit to chip wiring and there's options with a cap,diode and resistor I used on a project but for bread board it's pin1 RE3/VPP/MCLR,
pin 28 RB7 RX2/DT2
pin 27 RB6/TX2.CK2
and ground.
This is icsp I think but still not a clue. It works for my robots and a glcd setup...if it feels like it.
I got a northern programmer if anyone wants it...I never got it to work.
I find a nano 328 a nice little board and switching the programmer options easy as drag to top of list and just change com port if needed.
Just my thoughts of using same gcb code on pic and avr.
Not everone uses command line code or knows scripting.
If Anobium hadn't got his claim in first, I'd have staked a claim to this!
I love my NSDSP programmer. It is superbly quick, superbly reliable and macOS compatible. I use mine multiple times daily both at home and (mainly) at work. The other day I sat and programmed 150 tiny 12F1840 chips that were soldered on the board using a little 'clip' adapter and my NSDSP programmer. I'm thinking of making a six or eight way gang programmer with them.
Let me decompose this.
Have a look in the installation. The command line Help is extensive and we have include CLI guide using with compilers like the Proton IDE.
The programming datasheet is a great resource for this data.
Good to hear,
Re the PICKit in general. In the installation folder there are two very good guides to the PICkit2 and PICkit2 and the software.
We have investigate and rejected programming AVR. There are some great tools out there.
Re AVR v PIC I do not have a view - PICKitPlus is for PIC.
Send to me, You do know my adderss.
But, this is typically a simple process to resolve. To use the NSProgrammer. First erase the chip with PICKitPlus and the NSProgrammer should work.
Great Cow BASIC is a great portable language, so, this good to hear.
Very true. Using PICKitAutoWatch does resolve learning CLI or scripting.
The more guides we write the easier is should get - for everyone.
Cheers
Last edit: Anobium 2020-01-27
Thanks. The onus is on me to learn.
PICKitAutoWatch is new to me.
I will use the pic and ili9341 as working project..cos it works
but what advantage over clicking flash hex button and it does?
pic on gcb seems to have a mind of it's own ie it shows pic or doesn't.
complains no supply or just works.
As is I have pickit2 connected to pic and can power the board but the program won't run until usb connected to pickit 2.
If I disconnect pickit2 from the board and power it starts the program.
I can use the cli and flash hex or trying the picautowatch.
cli just does it.
Why don't it show the programmer or the chip in use?
not intuative. press button and see. not.
sorry, I don't get the point of this app or I'd use it.
Is it for new pics only that pk+ handles?
Last edit: stan cartwright 2020-01-27
Why can't it find the file from the gcb file that is open in the ide and then the device and programmer?
I had to say the hex file and then find the pic from a list.
I then found if you restart it, it's forgotten previous settings.
What does ticking the boxes do?
what does #config MCLRE=on ... do, or doesn't?
I don't like using pics...unless they're on a usb microchip dev board.
I think there's some 40 pin pics with loads of ram and features to explore and that's where pk+ comes in. There seems problems using them though from the forum.
I'll wait before going through pps again. uchip data and the pin meanings etc. complicated stuff.
not fun.
Last edit: stan cartwright 2020-01-27