Please let me ask a question here. First some content. I am a hobbyst in France playing since years with Microchip 8bits PIC by using MikroElektronika MikroBasic as programming langage.
I discovered GCBasic 3 weeks ago on Youtube just by looking for some nice videos about PIC and the tutorials from Even pushed me in the world of GCBasic.
I have a project for my CNC machine requiring a microcontroller to execute routing of signals, and I do not know why, I choose a PIC16F17146 for that projet.
Now it is so that MikroBasic in his latest version do not support this PIC. This is a good excuse for me to start this project with GCBasic and learn more with this development tool. It is also so that the programmer mikroProg also not support yet the PIC16F17146. So to solve that, I ordered a PICKit 5 to be able to program these chips.
By following Even's tutorials, the integration of PICKit 5 as programmer with GCBasic was so far fine.
I am able to program a PIC12F1840 (yes that was the only board that I had on my desk, because the project with the PIC16F17146 is only virtual in my head).
Now to my question. These are both command lines that are set in Programmer parameters box:
Should have a PICkit2 to program these chips.. much faster. :-)
But, the PK5. What is happening with the 'standard' parameters ?
Here is a portion of the Help for the IPECMD
OA<Type><Value> ICD4, ICD5 and ICE4 Setting None
Types:
A = PGC resistor value in Kohms
B = PGC resistor value in Kohms
C =PGC Config 0-None, 1-Pull up, 2-Pull down
D =PGD Config 0-None, 1-Pull up, 2-Pull down
S =Programming Speed 0-Minimum, 1-Medium, 2-Maximum
L =LED Brightness 1-10
The says is it applicable to 'other' programmers but you could try addung -OA0 (that is letter 0, letter A then Zero.).
Try this. If this does not work then we can open a ticket with Microchip to get them to support PK4/5 in slow mode.
So, try adding the new parameter -OA0 then report back.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tested both parameters (-OA0 and -OAS0), in the 2 cases the programming of the PIC12F1840 was fine, no errors, no error messages, no issues. In the next days and weeks, I will learn more to program with GCBasic and work on my new project.
Thank for your help
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Actually with or without parameters I have no issues or errors anymore. When I had setup the PK5 config first time in GCStudio, I got the error that the speed was to high (in the GCStudio terminal). I have no experience with MPLAP IPE GUI or CLI, so I was searching in multiple ways, and I found the option in the GUI. I set as low and try another programming. Since it is working. I do not know why exactly, could be also a hardware issue? That was the first point of my post basically, I cannot understand why that happened.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear GCBasic Community,
Please let me ask a question here. First some content. I am a hobbyst in France playing since years with Microchip 8bits PIC by using MikroElektronika MikroBasic as programming langage.
I discovered GCBasic 3 weeks ago on Youtube just by looking for some nice videos about PIC and the tutorials from Even pushed me in the world of GCBasic.
I have a project for my CNC machine requiring a microcontroller to execute routing of signals, and I do not know why, I choose a PIC16F17146 for that projet.
Now it is so that MikroBasic in his latest version do not support this PIC. This is a good excuse for me to start this project with GCBasic and learn more with this development tool. It is also so that the programmer mikroProg also not support yet the PIC16F17146. So to solve that, I ordered a PICKit 5 to be able to program these chips.
By following Even's tutorials, the integration of PICKit 5 as programmer with GCBasic was so far fine.
I am able to program a PIC12F1840 (yes that was the only board that I had on my desk, because the project with the PIC16F17146 is only virtual in my head).
Now to my question. These are both command lines that are set in Programmer parameters box:
C:\Program Files\Microchip\MPLABX\v6.15\mplab_platform\mplab_ipe\ipecmd.exe
-TPPK5 -P%chipmodel% -M -F"%filename%" -OL -W
But I needed to change the program speed to low inside the MPLAB IPE v6.15 to be able to programm successfully the PIC12F1840 over GC Studio.
From your experience, do you thing something must be changed or added ?
Thank a lot
Fabrice
Last edit: Fabrice Engel 2023-09-02
Hell Fabrice.. welcome.
Should have a PICkit2 to program these chips.. much faster. :-)
But, the PK5. What is happening with the 'standard' parameters ?
Here is a portion of the Help for the IPECMD
The says is it applicable to 'other' programmers but you could try addung -OA0 (that is letter 0, letter A then Zero.).
Try this. If this does not work then we can open a ticket with Microchip to get them to support PK4/5 in slow mode.
So, try adding the new parameter -OA0 then report back.
Thank for feedback, I will try and report...
Hello, quick feedback from my side,
I tested both parameters (-OA0 and -OAS0), in the 2 cases the programming of the PIC12F1840 was fine, no errors, no error messages, no issues. In the next days and weeks, I will learn more to program with GCBasic and work on my new project.
Thank for your help
Fabrice - can I confirm please.
You need these parameters to make the PK5 programmer work? What is the error message without the parameters. Please post the actual error message.
I have been assured by the PK5 Microchip Product Manager that the PK5 operates the same as a PK4 and therefore the there should be no issues.
So, your insights into the operation of the PK5 will halp my nexy conversation with Microchip.
Actually with or without parameters I have no issues or errors anymore. When I had setup the PK5 config first time in GCStudio, I got the error that the speed was to high (in the GCStudio terminal). I have no experience with MPLAP IPE GUI or CLI, so I was searching in multiple ways, and I found the option in the GUI. I set as low and try another programming. Since it is working. I do not know why exactly, could be also a hardware issue? That was the first point of my post basically, I cannot understand why that happened.
No problem. Probably as glitch somewhere.
Enjoy - GCBASIC and thank you for posting.
Thank a lot, I assume I will be back soon with new questions :)