PIC32MX170F256B

[Coccoliso]

Hi at all,

I want to increase RAM adn FW32 and apart of loader and I saw that the PIC32MX170F256B can might take the place of PIC32MX150F128B
- as in forum I added the descriptor by copying it from the smaller brother changing RAM/ROM sizes
- compile using XC 1.30 instead of Firewing

but .. in XC 1.30 I detected the problem of a missing library that is this "libmchp_peripheral_32MX170F256B.a"
Some willing can tell me in which XC-1.XX I can find this damned file ?
I'd like to keep things as they are because the development system (Mplab IDE/XC32/Firewing/PicKit 2) works like a Swiss watch on multiple PCs (W10 also) and putting a stick in the wheels could be a disaster

[David John Barker]

it would normally be under

C:\Program Files (x86)\Microchip\MPLAB C32 Suite\pic32mx\lib

[Coccoliso]

Hi David,
the XC32-V1.30 version does not have the Peripheral Library for the 32mx170f256 and exists since the XC32-V1.32 version .
Hence the question arises spontaneously.. "why do I have the version XC32-V1.30?"
I did not remember why on a single PC I was left to the version XC32-V1.30 but today I took the whim to understand why.

The machine in question is a W10 x64 with a Pentium I7 and if I install XC32 versions higher than 1.30 (from 1.32 more precisely) the xctoolsuite crashes or better continues to compile without ever getting to the end.
Today I understand why.. Xctoolsuite launches two XC.EXE sessions, both with a very low percentage of CPU (0,1%) and they're pretty much stationary, I see them in the Task Manager.
I have no idea why on this machine ONLY I can not compile with the XC32-V1.32 (and following) is the only one on 4 machine with W10 x64 with this problem.
This morning I had read a post that concerned the 32mx170f256 and there someone had raised the XC32 infinite compilation problem.