Also:
Regards...WikiPedia wrote:In 2015, Microchip released the PIC32MZ EF family, using the updated MIPS M5150 Warrior M-class processor
Regards...WikiPedia wrote:In 2015, Microchip released the PIC32MZ EF family, using the updated MIPS M5150 Warrior M-class processor
May I kindly remind you that you exactly did that, nearly 3 years you did not update the dsPIC and PIC32 compilers ,while the one after the other ARM releases were produced.Adding not only new devices but hole new vendors ,We the dsPIC and PIC32 users had to wait and mE did not care if we complained at all,My Question why is this such and issue to make the ARM users wait a bit while you catch up on PIC32 you did it with a smile to the Microchip users .Again this just shows the mE bias towards the ARM products .darko.ilijevski wrote:PIC, we would be overwhelmed with the requests to support ARM,
Hello Darko,darko.ilijevski wrote:Hi,
Fixing bugs goes without saying, of course that we want them all fixed. That is why we value our users feedback. Also I doubt that anyone from our team would say something like that - we are here to provide the users with as effortless and as joyful experience as we can.
So - as I have said, we do try to fix all the bugs, but sometimes, the problem lies within the underlying IDE we use to code, so some errors need to wait on the IDE to get fixed. That is especially true for the DPI and other graphical glitches that appear on some systems. Also, for these systems, the problem sometimes lies within the OS itself. We do try to cover all of the commonly used versions of windows, but even Microsoft has abandoned support for them so it is reasonable to expect minor problems of this kind.
Bugs get fixed whenever we release a new version, so be sure that you always use the latest build available on our site. We collect the data about the bugs in the meanwhile and when enough of it was collected, the new version gets built and released, along with some new features, and so on. It's how every software production works.
Lastly, not every report is valid - there are many supposed bugs being reported, which are actually erroneous coding. I have witnessed those more than once. Then, we try to point that out to our users and explain why it happens.
As for the new MCUs, sometimes it's not that easy to implement all the code to work with our libraries, or something doesn't go that well, or for whatever other reason, the MCU has to wait for some other release... There are so many different architectures and MCUs, almost always there is a suitable replacement which actually works. Sometimes not all the circumstances can be foreseen during the library production process...
I hope it is now more clear what is going on with this subject.
Best regards
2.5 years later, still no PIC32MM support. Neither is there support for PIC32MK, PIC32MZ-DA, etc.Aleksandar.Mitrovic wrote:Soon you should notice that those are not empty promises and "automated replies" which we give for every suggestion.
Thank you for staying with us!