This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSPM33-SDK: MSPM33 PinMux Resource Conflict issue

Part Number: MSPM33-SDK
Other Parts Discussed in Thread: SYSCONFIG

Hello Team,

I have issue with MSPM33  SDK Sysconfig resource conflict.

Instead of showing a Resource conflict when PinMux overlaps, the following error message appears.

 

I used UC13_0 and UC13_2 as UART first, and then they tried to configure SPI.

When selected UC13_0 and UC13_2 as the PinMux for SPI, it did not alert as a resource conflict but showed the warning below.

image.png
Oh Snap! The last change caused an exception...

TypeError: Cannot read properties of undefined (reading 'attributes')

at Object.getAttribute (C:\ti\mspm33_sdk_1_02_00_00\source\ti\driverlib\.meta\Common.js:3295:34) at Object.validatePinmux (C:\ti\mspm33_sdk_1_02_00_00\source\ti\driverlib\.meta\spi\SPIMSPM0.syscfg.js:639:19) at W.finalValidate (localhost:54860/.../ui.js:519:1071989) at localhost:54860/.../ui.js:519:888640 at kt (localhost:54860/.../ui.js:342:4794) at Qr.va (localhost:54860/.../ui.js:342:39864) at g.finalValidate (localhost:54860/.../ui.js:519:888594) at localhost:54860/.../ui.js:519:916363 at kt (localhost:54860/.../ui.js:342:4794) at Qr.va (localhost:54860/.../ui.js:342:39864)

---

 

Please find root cause of this problem.

 

Thank you.

  • Hello,

    Could you give further details or send your sysconfig file?

    if only the IOmux changed is the SPI configured as well? Potentially you can change this in your main code if you're trying to change the Unicomm functionality on the fly.

    Sincerely,

    Erik Vaughn