Firewing

Hi,
first of all I want to clarify that, despite the vicissitudes, Firewing 32 has been giving me very good results for years now, so much so that over time I have moved on to using it with my hardware and other MCUs therefore it has certainly been designed and implemented with good programming techniques.
Now I know its strengths and some limitations well but up to now I have always untangled myself but now a problem has arisen passing from the 256 version to the 512 version of the PIC32MX575.
I don't understand why the MCU seems to idle and I can't turn on a single port.
Is there anything missing or incorrect in the definition of the device that I am not aware of ?

Hi,
only an SMD condenser on VCAP that didn't do its job (maybe because cooked)
Now all is OK.
Great FIREWING!

Thanks for the update - useful to know!

Hi John,
over the years I have specialized in using the 32MX575 family which due to the low cost and the small number of PINs in preparation for the SMD board is giving me many and fruitful results.
If someone is interested I have implemented the interrupts and modules for CAN, the various I2C and SPI ..
I remain convinced that even if the market needs go in other directions and the spotlights are all pointed by the parent company towards other chips, know-how and all the good results obtained cannot be thrown away .

Hi Cocoliso,
I would be very thankful if you can share the I2C ans SPI drivers for PIC32MX575 with me.
Regards