Hi John! On Mon, Nov 11, 2019 at 10:57 AM John J. McDonough wr= ote: > I've been using PIC32 for a while and it doesn't feel a lot different > from PIC16. Using the "normal" stuff, MPLAB-X, XC32, ICD 3 and PICkit 3 > (still haven't bit the bullet and sprung for an ICD 4). That's my hope - familiarity! > Neil mentioned not being so hung up on performance, and the PIC32 family > offers pretty significant performance and crazy large memory, so there > aren't a lot of places where stressing over performance is a winning > strategy. I can focus more on readability than performance. My main hope is that peripherals are a bit more speedy, primarily PWM. As cameras get faster, my LED projects need faster refresh rates to keep ahead. > I haven't messed much with Harmony, mostly based on my sketchy > experience with other Microchip libraries. Over the years I have built > up a fair collection of my own libraries for the PIC24 and dsPIC, and > they largely port to the PIC32 without incident. At the moment I have a collection of bits I use as well. While some of the Harmony libraries seem intriguing, at the moment I don't really have much of a use for them. > I did get my toe in the water playing with the ChipKIT boards, and they > work, but like the Arduino, a little limiting. In a world where you can > get proto boards from China for next to nothing, I would rather have it > my way! Yep, that's my plan too. Even if I do spring for a dev board, I do plan on spinning a board for the PIC32 and the RF module I plan to use. Might as well mess about with the devices I hope to actually use! Josh --=20 A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. -Douglas Adams --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .