MCUX 11.5 - Bug in pin configuration GUI for K32L

[dmarks_ls]

I'm developing a project for the K32L2A4 (specifically, the K32L2A41VLH1A 64-LQFP).  I'm using the latest MCUX 11.5 and the latest SDK (2.11.0) for the FRDM-K32L4A2S.

I have found that when I am selecting and configuring pins in the Pins configuration menu, when I start setting some GPIO directions to "Output" from "Not Specified", this causes the tool to flag unrelated pin functions as improperly configured.  Example -- here I have just assigned a group of GPIOs as outputs, and several other pins are now flagged in orange.

When I flip to the functional group that contains those orange pins, here's what I see.

The workaround is simply to save the MEX file, exit MCUX, and reload MCUX.  When you return to the Pins screen, all pins appear green and no pin-specific problems are displayed.

David R.

[Pavel_Hernandez]

Hello drodgers

In order to help you could you upload the .mex please. For have the same configuration, I tried but I don’t see the same case.

Regards 

Pavel_Hernandez

[dmarks_ls]

Attached.  This is my complete configuration.

[Pavel_Hernandez]

Hello drodgers

I review your information. These warnings pop up If you change the default parameters from special IO functions (I2C,UART,etc).

With the [.mex] file I opened with the Config tool standalone and all is green.

When I import to the MCUXpress shows all in red.

I have and observation are you selecting the right uC ?, because there are different package.

Regards,
Pavel_Hernandez

[dmarks_ls]

We are using the 64-pin VLH package in our product, not the 100-pil VLL package on the FRDM kit.

[Pavel_Hernandez · Accepted solution]

Hello,

Thank you for letting us know this, I will notify the corresponding team to evaluate fixed in further versions.

Regards,

Pavel_Hernandez