[sdiy] Microchip.. for futur projects, choice to do.. PICs or Arduino

cheater cheater cheater00social at gmail.com
Thu Feb 25 12:19:20 CET 2021

Skip all the 8-bit and 16-bit bs and go straight for a high powered
arm cpu with C, Micropython, or arduino-copilot running on it, or
something to that effect. Arduously optimizing stuff and working out
timings in inner loops is not worth anyone's time nowadays, not until
you're building things in the millions of units. don't waste your time
and just develop for something powerful.

And before you think of it, if you have to have a UI with a screen,
don't even bother writing for an LCD driver on your arm micro.
instead, have an LCD driven by a raspberry pi, over hdmi, so people
can hook up something larger, and have that raspberry pi talk to the
arm micro via i2c or serial, in a format that is easy to understand
(and hopefully human readable to some extent). i.e. if someone tries
to reverse engineer it in the future, it's easy. suddenly the
serviceability of your synth shoots up by 1000%, and the ease of
development will pay dividends through massively reduced time to
market. honestly nowadays developing non-repairable digital user
interfaces using proprietary software which can't be debugged after it
hits the market is not just a stupid waste of effort, it's unethical.
Just look at what John Deere are doing to squeeze money out of
farmers, and you'll agree.

The highest cost in a synth still remains and will likely forever be
the metal enclosure and the potentiometers.

On Wed, Feb 24, 2021 at 10:16 PM Jean-Pierre Desrochers
<jpdesroc at oricom.ca> wrote:
> Hi list,
> This is off synth DIY topics (but not as much..)
> But I'm at a crosspoint here.
> I've been a Microchip PIC user for many years so far.
> I've designed many projects around 8 bits PIC16Fxxxx devices.
> In these last years I used Microchip's development IDE
> MPLAB IDE then updated to MPLAB X IDE for the last years.
> These environments are well constructed to work in assembly
> Or (in my case C code).
> To me the weak part of Microchip environments has always been
> Their debuggers (ICD2-3, PicKIT3, etc..).
> I'm telling that because in the last 4 days I struggled to make
> my ICD3 debug a PIC16F1783 as it should without success.
> I posted my issues on Microchip's forum and had 'some' replies
> Like did you correctly connect your ICD ?
> or what length of ICD to board cable are you using ?
> but then... complete silence there..
> It seems that the interests are mostly aimed to 16 & 32bits PICs.
> And... I remembered seeing many posts and videos about how easy
> it is to use Arduino as a 'bridge' to get a small project done.
> Free user interface/programming environment available.
> Final projects on Atmel micros ??
> I'm stuck with Microchip unreliable debugging hardware so far.
> Maybe there are MPLAB IDE compatible hardware debuggers
> but I doubt it.
> So I'd like to hear you about what should I use for my future needs..
> Again I'm a 8 bits micro user programming in  C.
> If a good choice of Arduino board would help me to faster
> develop small projects that would interest me..
> Your opinions welcomed.
> _______________________________________________
> Synth-diy mailing list
> Synth-diy at synth-diy.org
> http://synth-diy.org/mailman/listinfo/synth-diy
> Selling or trading? Use marketplace at synth-diy.org

More information about the Synth-diy mailing list