Hi Rob, I did not knew that. So there are PICs with 3.3V Vpp.... There are rumours that STM are manufacturing some microcontrolers which are at least few class better than PICs. 32bit arhitecture, very low power, strong compiler. For 8bit, maybe PICs will last a while... Good luck with the programmer!
On Wed, Sep 18, 2024, 20:01 Rob CJ <[email protected]> wrote: > Hi Vasile, > > Initially the charge pump was connected to 5 Volt but due to the fact that > some PICs (like the 18F26J50) only work on at most 3.5 Volt and I needed > some special pattern to apply to the MCLR pin for programming I cannot use > 5 Volt since it will be too high (VPP must be at 3.3 Volt, same as VDD). > > And about the Python stuff. All programming info needs to be extracted > from all XML files of Microchip. Initially I though that a JSON format > would be OK but after some discussion with Rob Hamerling it was easier to > use Python since my plan was already to use a Python to make programming > easier. Rob Hamerling created the script to extract all this info and > created the picpgmdataclassinfo.py. > > So I can - and will - document how to get the programming info in the PIC > Programmer but the programming info itself is in this Python file, see > attachment. I also attached the japp.py library that extracts the > programming info and translates that to data that is send as pic-info (so > there is the initially documentation) and it offers functions to make life > a bit easier.. Last but not least I also attached the Python script that > does the programming and uses the japp.py file (which uses the > picpgmdataclassinfo.py). > > You can of course use some other scripts to get the programmer info in the > PIC programmer as long as you use the commands that transfer the correct > programming data. As said I will update the manual since all is ASCII so > there is no need for any special script language. > > Kind regards, > > Rob > > > > ------------------------------ > *Van:* [email protected] <[email protected]> namens vsurducan > <[email protected]> > *Verzonden:* woensdag 18 september 2024 11:44 > *Aan:* [email protected] <[email protected]> > *Onderwerp:* Re: [jallib] Just Another PIC Programmer (JAPP) update > > One more: why have you used 3.3Vfor the charge pump of the programming > voltage since the main supply is 5V ? > Perhaps it's not very practical to reduce voltage from 5V to 3.3V and then > increase it (3.3V to Vpp) to dissipate on LDO all the switching energy > required for Vpp, even if it works. > > > On Wed, Sep 18, 2024 at 12:24 PM vsurducan <[email protected]> wrote: > > Hi Rob, > Assuming I do not want to hear about Python and I want to use a simple > terminal to send the commands to the programmer, how do I load the pic > programmer info and the hex file? > thx, > > On Sat, Sep 14, 2024 at 5:10 PM [email protected] <[email protected]> > wrote: > > Hi all, > > As a side project I am working on the JAPP. I drafted a manual to share > what you can do with it and give you an idea what I am working on (see > attachment). The challenge is to add all PICs (which are a lot) so I just > started with some PICs. > > With the help of Rob Hamerling I got a nice Python file that contains all > PIC Programming info derived from the MPLABX PIC files. This file will be > provided with the JAPP including some other supporting files. My plan is to > make a PCB for the programmer. > > Note that it is a simple programmer using the same connections as a > PICKit2 or PICkit3. > > The order in which I add PICs is random so if you have certain PICs that > you use frequently let me know. I can add them first. > > Although there are about 100 programming algorithms, some of them (I do > not know how many) are the same (hopefully most of them). Currently I > implemented 5 algorithms but some programming algorithms reuse functions of > other algorithms. > > Since I am currently in the prototyping fase, if you have certain requests > or remarks on the manual, let me know. > > Kind regards, > > Rob > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jallib/045cc916-0f9f-4152-a5d3-9c706b8b963dn%40googlegroups.com > <https://groups.google.com/d/msgid/jallib/045cc916-0f9f-4152-a5d3-9c706b8b963dn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jallib/CAM%2Bj4qs0m7411-BauTMsL4mb4frZFLDGfg5y1N7OyGDA_Zq1ww%40mail.gmail.com > <https://groups.google.com/d/msgid/jallib/CAM%2Bj4qs0m7411-BauTMsL4mb4frZFLDGfg5y1N7OyGDA_Zq1ww%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jallib/GVXP195MB16377CA3C3204ABAB1DF0011E6622%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM > <https://groups.google.com/d/msgid/jallib/GVXP195MB16377CA3C3204ABAB1DF0011E6622%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/CAM%2Bj4qsi2cg4n0J9UR4ORUWKcpEiUhi7w0BGPjvfrFwhxOEyoA%40mail.gmail.com.
