I find MCC (the peripheral configurator) does not support USB configuation
at all now. It also does not support any "legacy" but firmly in production
pics which seem to be ubiquitous (i.e. it's not just me using them).

In the context of Atmel being bought by Mchip (news from 4 days ago), can
one expect a drastic change in supported devices / current production
devices? I.e. are older pics going to be significantly harder to obtain
soon? Will Atmel's product range be restricted? Will there be datasheet /
app note mayhem as seen with other acquisitions?

Next to last, the fact that one cannot sanely upgrade mplabx from running
state, and must uninstall it 1st, is scary. Most other Eclipse based tools =
I
know of (like Netbeans) permit upgrades in-program, as far as I know. If it
takes half as long to install and configure the new mplabx to my specs than
it took the 1st one I would rather not upgrade. Yet, I have to, since
Harmony (current) requires mplabx 3.2 and I have 3.1 . Also, there seems to
be no trace of a legacy Harmony download to go with 3.1, perhaps with good
reason. It just so happens I installed 3.1 recently enough that I believe i=
t
not to predate Harmony and XC compilers.

Are we going to see better times soon? I can't help but notice that Atmel's
Studio did not move into Java bloatware ide territory. That is good in one
way but it prevents running said software on linux, for now... I use linux
as development platform so I have an interest there too.

--=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
.