At the microchip masters in August we used harmony 3.0b in some of the classes. You could actually make a project with a main.c
I was told we might see that in October.
The pic32mk is still relatively new, I think the tools generally lag behind the hardware.
phew, one major release about one year later? what for?
My wild guess would be initial support for ATSAM (hope not, finish supporting your chips first.) but if you are allowed to share...
Don't get me wrong, that's exciting news. I used harmony 1 and it was bloody awful, ditched immediately. This month i decided to put time in learning harmony 2 (for USB of course) and it was a much more pleasant experience. Easier to understand, easier to get into (still won't touch the framework for anything different than USB or debug trace)
3.0 must be even better :)
October, which year :D?
32MK is relatively new but my point is, a family with specific features is released with very poor support for such features?
I would speculate that's lack of adoption that put support for this part behind and lack of support that keep adoption behind.
dsPIC33CH/CK on the other hand were officialy released a couple of months ago, with an update for MPLABX that added support for dual-core projects. Things were working from day zero, lots of excitement from the forum, all of us early adopters proceeded to learn how to use the new parts without fighting with the tools which meant that in one day test projects on how to use the new peripherals and the MSI were available, done by users. start a thread for a problem in the dsPIC33CH/CK and in no time somebody will be able to help with an example for the specific part.
With the MK i feel abandoned, support after three weeks hasn't responded. I figured a new version was imminent and maybe (i said maybe) they wanted to delay until it was released, a "please wait as we are going to release an update soon" could have been nice
post edited by JPortici - 2018/10/10 02:41:06