MCU-PLUS-SDK-AM243X: am243x sysconfig is SLOW

Part Number: MCU-PLUS-SDK-AM243X
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi 

I found this thread https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1299742/mcu-plus-sdk-am243x-sysconfig-and-compile-time-very-slow/5076406?tisearch=e2e-sitesearch&keymatch=sysconfig%20slow#5076406

Sysconfig becomes slow as when we add more details to it, like I/O and peripherals. 

Is anything done?

Thanks

Rasty

  • Hi Rasty,

    Please tell which MCU+SDK are you using?

    Sysconfig becomes slow as when we add more details to it, like I/O and peripherals. 

    What all peripherals have you added? How much delay are you seeing with peripherals and without peripherals?

    Regards,

    Tushar

  • Hi

    We use motor_control_sdk_am243x_09_01_00_06

    As you can see, If I just change click in list of pad for GPIO, sysconfig freezes for 2 minutes.

    Thanks

    Rasty

  • Hi Rasty,

    Can you please tell is it happening with all GPIO pins or a specific pin is creating the issue?

    Is it happening when configured GPIO instance reaches to a specific number? E.g. configured 5 GPIO instance and the 6th one creating problem.

    Regards,

    Tushar

  • Hi Tushar

    It does not matter. Everything I touch is slow.

    Can share with you our sysconfig. Privately if possible.

    Thanks

    Rasty

  • Hi Rasty, 

    Can share with you our sysconfig. Privately if possible.

    It would be really helpful. You can provide me the file on E2E private chat.

    Regards,

    Tushar

  • Hi

    I sent you sysconfig few days ago.

    Did you get it?

    Thanks

    Rasty

  • Hi Rasty,

    I have checked my messages and it seems that I haven't received any file from you. Can you please double check once?

    Meanwhile, I have just checked the release notes on MCU+SDK where Sysconfig crash issues exist when large number of GPIOs are added. 

    This issue requires fix in the Sysconfig device data itself. The issue has been fixed in the SDK v09.02 and Sysconfig v1.20.

    Please refer below image.

    Please refer RELEASE_NOTES_09_02_00 for details.

    Please try once with the SDK v09.02 and Sysconfig v1.20 and update the results.

    Regards,

    Tushar