microchip studio thoughts

[snarkysparky]

anybody used it yet.

what does it seem like they are up to?   Is it just a rename on studio 7 or are they paving a path to more revenue.

Not much info available on the page.

[up8051]

Renamed Atmel Studio 7, XC8 compiler support added.

[ataradov]

It is just a rename of AS7 to divorce it from 32-bit MCUs. 32-bit MCUs will only be supported by MPLAB X.

[westfw]

It is supposed to have some fixes, so it's not JUST a rename.  But it's still the same old VS 2015 based stuff.  (probably the fixes are from an update of some random microsoft module.)

[ajb]

It is just a rename of AS7 to divorce it from 32-bit MCUs. 32-bit MCUs will only be supported by MPLAB X.

wait, so Atmel/Microchip Studio will no longer support any of the SAM series?

[ataradov]

wait, so Atmel/Microchip Studio will no longer support any of the SAM series?

Hard to tell on what exactly will happen. The focus for 32-bit MCUs is definitely on MPLAB X. The ASF and other Atmel frameworks will not have new device support pretty much for sure. But the AS itself as a basic IDE may still support them.

[Lindley]

It is just a rename of AS7 to divorce it from 32-bit MCUs. 32-bit MCUs will only be supported by MPLAB X.

wait, so Atmel/Microchip Studio will no longer support any of the SAM series?

You want to look at Microchips Studio pages, they clearly state for AVR And SAM chips.

Going by Microchips problems with  the new MPLABX think we will be sticking with AS7 for now !

[rvalente]

I've just faced this, I'm starting a dev and chose the SAM C series, my natural go to was the MPLAB X but many features are still missing (like live watch) them I've switched to Microchip Studio for now.

The choice of netbeans in past for MPLABX IMHO was a huge mistake but, microchip likes to thing different

I'd say I still prefer STM32CubeIDE (Atollic) but probably because I was more used to it.

[ataradov]

You want to look at Microchips Studio pages, they clearly state for AVR And SAM chips.

Existing devices will not be removed, of course. But the new devices don't have to be named "SAM" and don't have to be supported by the MS.

[Mark19960]

I absolutely cannot stand MPLAB X.
Have a high resolution display? Ugh..... it's cancer.

AS7 that is now "Microchip Studio" always had quirky things like slow loading of large projects which they did greatly improve.
That was a welcome fix.

It works, but I have to wonder if it's on borrowed time.

[ajb]

I'd say I still prefer STM32CubeIDE (Atollic) but probably because I was more used to it.

Before Atollic was bought by ST it also had support for other manufacturers' parts, including Atmel IIRC, so if you can find one of those older versions and your part has been around long enough that might work for you.  I don't remember what the limitations on the free version were, though.  Or since STM32CubeIDE/Atollic are based on Eclipse it should be possible to put together your own solution using Eclipse CDT and GDB, although it will be more work to get everything into place.  I think there are some additional plugins designed to support embedded development in Eclipse that might help.  It's been a while since I was motivated enough to look into that.

[westfw]

They're an interesting dilemma, IDEs.  On the one hand, as an "uncommitted" developer or hobbyist, it would be nice to learn a single IDE and be able to program any microcontroller (or desktop, or whatever) you happen to chose (and any language), and get REALLY GOOD at using that particular IDE.

But as a potentially job-seeking professional, any particular position is likely to prefer that you have experience on the IDE that THEY happen to use, or at least "the chip vendor IDE" as a sort of benchmark standard for having SOME relevant experience.

I guess it's one of the advantages of using Makefiles (or similar) and cli-based build tools; at least that way everyone get pick their favorite editor.  (Although Makefile complexity tends to increase all by itself, until you need One Guy who has "maintain and explain the makefile" as a major part of their job.

Too bad we can't agree on one particular standard IDE that has all the features.



(Though I guess, on the bright side, IDEs aren't REALLY that different from one another.  They each have "annoying quirks", and an occasional "particularly nice feature", but ... one is pretty much like another.)

[asmi]

They're an interesting dilemma, IDEs.  On the one hand, as an "uncommitted" developer or hobbyist, it would be nice to learn a single IDE and be able to program any microcontroller (or desktop, or whatever) you happen to chose (and any language), and get REALLY GOOD at using that particular IDE.

There is a commercial plugin VisualGDB to Visual Studio which enables using it for firmware development and live debugging for a whole bunch of MCUs architectures. You might want to look at that. I prefer using vendor toolchains so I didn't try it myself, but if it's as good as they claim it to be, it should be all you need if you prefer sticking to a single IDE.