[sdiy] OT: uC Development Environments

[john slee]

My development is all server stuff for work nowadays — overwhelmingly
Golang — but the same principles can easily apply to microcontrollers and
other languages.

I build everything in Docker containers, even if it’s a tool I will only
use on my laptops. This way I can populate a fully working development
environment and easily copy that environment around and be confident that
it will work everywhere.

In the pre-Docker years I used to take a similar approach but simply using
tar archives.

IIRC Emilie Gillet has done something like this for working on her
products, and shared it with the community.

John


On Thu, Mar 5, 2020 at 09:54 MTG <grant at musictechnologiesgroup.com> wrote:

> Like you, I've been using mainly IDE's provided for whatever platform
> I'm on, however, I have also used Visual Studio Code and it's pretty good.
>
> The problem with a lot of the new environments is that they are a moving
> target. PlatformIO updates a lot for instance. It would be very hard I
> think to create a long-term system that you could recreate 5 or 10 years
> down the line.
>
> GB
>
> On 3/4/2020 2:10 PM, Jay Schwichtenberg wrote:
> > Everyone,
> >
> > I'd like to get some ideas, thoughts and opinions on setting up a
> > micro-processor development environment on my PC (Windows).
> >
> > I was a HW/SW embedded/bare metal engineer until I retired. I did
> > contract work and have worked with processors from the 8080, Z80, 6800
> > ... to todays MicroChips, ARMs and Intel Pentiums chips. Being a
> > contractor I would usually work onsite to have access to programmers,
> > test equipment and prototypes. The customer would have the development
> > environment already established (Eclipse, gcc tool chain, MPLAB, IAR,
> > Keil) so I just used what was there.
> >
> > Well now I getting ready to setup my PC to do some development at home
> > which will mainly be targeting SDIY. Doing stuff at home gives me a lot
> > more choices of processors to work with. Going to be doing NXP ARM
> > (chips and Teensys), STMicro ARM (chips, Nucleo, Discovery) , MicroChip
> > things, Raspberry PI and probably some Arduino too.
> >
> > The obvious choice would be to download and use MCUXpresso,
> > STM32CubeIDE, MPLAB and Arduino development environments. That would be
> > a lot but doable. One thing that a number of people seem to be using now
> > days is VisualDBG ($) which integrates into MS Visual Studio which seems
> > to be all inclusive.
> >
> > VisualDBG seems to be OK but it doesn't seem to have the ability to do
> > setup code and provide peripheral drivers like the other environments.
> > Also don't have a clue of how well VisualDBG would support manufacture's
> > libraries, board support code and demo code.
> >
> > So what are other people doing, thoughts, ideas?
> >
> > Thanks much.
> > Jay S.
> >
> > _______________________________________________
> > Synth-diy mailing list
> > Synth-diy at synth-diy.org
> > http://synth-diy.org/mailman/listinfo/synth-diy
> >
> >
> _______________________________________________
> Synth-diy mailing list
> Synth-diy at synth-diy.org
> http://synth-diy.org/mailman/listinfo/synth-diy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://synth-diy.org/pipermail/synth-diy/attachments/20200305/786aa121/attachment.htm>