MSPM0-SDK: The Systick interrupt priority set in SysConfig is invalid

Hello Torris,

When you do ay configuration modification in Sysconfig, you can click  and you can find the file Sysconfig generates

You can click the ti_msp_config.c. And when you change the priority, you can find the .c file has the same modification at the same time. It means your modification is valid. And compiler will build the Syconfig when you build the project. And if you really want to check whether this modification is valid in Burnable files (.bin, .hex, .txt), you can output a TI txt file which is more readable and check wherther this file is modified when you only change the priority in Sysconfig.

Best Regards,

Janz Bai

Hi Janz,

Thank you for your reply. I knew this question sounded impossible, so I recorded a video to verify this.

 2025-05-29 21-05-35.zip

I see what you mean -- changing that field in sysconfig doesn't cause an NVIC_SetPriority() call to appear in SYSCFG_DL_SYSTICK_init().

The (CMSIS) SysTick_Config() automatically sets the priority to 3 (really 0xFF, but the extra bits get dropped). But when I changed the field to e.g. 0 or 2 I didn't see anything in dl_config.c that changed it.

You could try inserting your own NVIC_SetPriority(SysTick_IRQn, 3) after the call to SYSCFG_DL_init().

[Edit: I mis-read the CMSIS code the first time.]

Hello Torris,

What the version of SDK and Sysconfig you used? You can check it from properties -> dependencies. 

I try to modify the priority in Sysconfig and generated TI.txt file after project build. I found that the di_config.c can be modified automatically and the txt file of priority 1,2,3 is not same.

You can try to add NVIC_SetPriority(SysTick_IRQn, 3) after the call to SYSCFG_DL_init() in your code, and check whether it is useful.

And you can also modify the optimization level to "0" and try to do tests again. you can check the optimization level from: properties -> Tools -> Arm compiler -> optimization.

Best Regards,

Janz Bai

Hi Janz,

I’m using MSPM0 SDK version 2.4.0.06 and SysConfig version 1.23.0. I also tried updating SysConfig to 1.23.1, but the issue still persists.

Changing the optimization level didn’t resolve the problem either. However, after manually adding NVIC_SetPriority(SysTick_IRQn, 3) after SYSCFG_DL_init(), everything works fine.

Best Regards,
Torris

Ok, Torris, you can do it by "manually adding NVIC_SetPriority(SysTick_IRQn, 3) after SYSCFG_DL_init()," now. And I remember this issue, when I am free, I will double confirm it and if it is an error, I will let our internal team to resolve it on CCS/SDK

Hi Janz,

Not sure if you've had a chance to reproduce the issue. I did a bit more testing and found that the problem only occurs when the “Enable SysTick And Start Counting” option is checked. If that option is not checked, everything works as expected.

Just wanted to share this additional finding—hope it helps with the verification.

Thanks again!
Torris

Hello Torris,

Much thanks for your effort on this. I will mark this and test and discuss with our software colleague.

Best Regards,

Janz Bai