PIC32MZ...

[AndrF]

*****************************************************************************************************
* 1 Question
*****************************************************************************************************

I installed the XC32 compiller and XC32 toolsuite.

Trying to compile a simple project with 32MX150F128B - get the error:

1.jpg (80.08 KiB) Viewed 22471 times

With Firewing 32 toolsuite - All OK:

2.jpg (93.19 KiB) Viewed 22471 times

My tsMicrochip32.ini file:

3.jpg (25.24 KiB) Viewed 22471 times

The files in the path are present.

Why not work with XC32 toolsuite?

*****************************************************************************************************
* 2 Question
*****************************************************************************************************
I want to use PIC32MZ2048ECM144. How to create a bas-file?

[Jerry Messina]

For the first error you need to install the Legacy Peripheral Libraries for XC32 which are no longer included in the XC32 download. Go to the Microchip XC download page http://www.microchip.com/pagehandler/en ... s/mplabxc/ and at the very bottom you'll find the PIC32 legacy libraries download.

For #2, I've never tried creating device files for the 32MZ so I don't know what's involved. The system file generator program for the PIC32 still requires files from MPLAB, and MPLAB doesn't have support for the 32MZ. You would likely run into other problems since they're not supporting the peripheral libraries for the 32MZ either.

[AndrF]

For the first error you need to install the Legacy Peripheral Libraries for XC32 which are no longer included in the XC32 download. Go to the Microchip XC download page http://www.microchip.com/pagehandler/en ... s/mplabxc/ and at the very bottom you'll find the PIC32 legacy libraries download.

Please specify the exact link.

For #2, I've never tried creating device files for the 32MZ so I don't know what's involved. The system file generator program for the PIC32 still requires files from MPLAB, and MPLAB doesn't have support for the 32MZ. You would likely run into other problems since they're not supporting the peripheral libraries for the 32MZ either.

OK. I will use 32MX.

[Jerry Messina]

Sorry... it's at the bottom of the XC Downloads page.

For windows, try http://www.microchip.com/mymicrochip/fi ... e=en574270

[octal]

Why would you use a PIC32MZ when you know almost ALL its peripherals are still buggy. Did yoy looked at the errata datasheet?
http://ww1.microchip.com/downloads/en/D ... 00663A.pdf

Check for example the I2C related page. It's first time I see a silicon manufacturer (at this level of silicon) asking me to use software I2C.

pic32mzbug.png (170.29 KiB) Viewed 22434 times

[Jerry Messina]

Now that Microchip bought Atmel maybe they'll fire the PIC32 and MPLABX teams and switch to ARM.

The $3.6 billion they paid is probably a drop in the bucket compared to fixing the recent debacles they've created.

[octal]

From my point of view, the main problem with PIC32 is not the core (MIPS is really very nice and their M14K consumes less than ARM), the problem is that their PIC32 costs arround $8 while other mips vendors provides processors able even to run Linux for arround $2. Add to that the fact that their peripherals are buggy.
Atmel SAM7 series (ARM) are very nice (I heared very nice echo from people using them). I hope Microchip will encourage them instead of killing them.