Hello,
I was working with the Pins Config Tool for MCXA153 chip and stumbled upon the following bug:
when I change the value of GPIO initial state, suddenly the Update Code button deletes both pin_mux files (.c and .h), as below:
at the same time, this error appears in the code preview panel:
changing back the value of initial state has no effect and the error persists and the pin_mux files are not generated at all (after they are deleted during Update Code).
Regards
Tereza Kubincova
Solved! Go to Solution.
Hello @tkubincova,
we have found an issue in the Pins tool data for MCXA153 causing this behavior for specific GPIO signals configuration. Sorry for the inconvenience.
We have created patch for MCXA142, MCXA143, MCXA152 and MCXA153 parts.
Patch installation instruction
Note: Applies both for MCUXpresso IDE v11.9.x and MCUXpresso Configuration Tools v15
Best Regards
Jan Kucera
Hello @tkubincova,
we have found an issue in the Pins tool data for MCXA153 causing this behavior for specific GPIO signals configuration. Sorry for the inconvenience.
We have created patch for MCXA142, MCXA143, MCXA152 and MCXA153 parts.
Patch installation instruction
Note: Applies both for MCUXpresso IDE v11.9.x and MCUXpresso Configuration Tools v15
Best Regards
Jan Kucera
Hi @tkubincova,
Could you please share the release versions you are using for the IDE and SDK?
I tried replicating your issue by initializing P0_0 as an Output, updating code, and then going back and changing the GPIO initial state. This resulted in the expected behavior for the pin_mux.c file for me, and the code updated successfully without the files getting deleted. Did you see this issue for a specific GPIO? What was the setup you used?
Any extra information that can allow me to replicate this issue would be great to report this issue to the internal ConfigTools team.
Thanks!
BR,
Edwin.