2021-09-16 07:40 PM
When using IDE 1.7.0, viewing the NVIC configuration window in the configuration tool and then generating code without changing anything causes the .ioc file to be modified. I tried the same thing in CubeMX 6.3.0 and the bug doesn't occur there.
I've attached the .ioc file I've been using. The modification is that line 179 (NVIC.TIM2_IRQn...) gets deleted. I suspect that it is related to Timer 2 being used as the timebase source because changing time base sources to different timers doesn't add the corresponding IRQ. Possibly also some interaction with FreeRTOS, but I haven't investigated enough to be sure.
Has anyone seen similar behavior and/or have an idea of a setting or config that might be causing this behavior?
2021-09-21 02:44 AM
Hello @ALars.2 ,
Thanks for your post,
Could you please explain more the issue seen?
Do you mean that, when you create an ioc file then you generate code, the NVIC configuration panel changes without any intervention?
Thanks, Khouloud
2021-09-22 05:01 PM
It only appears to happen with some existing ioc files. It doesn't happen with a new file, but I haven't looked into if I can replicate the behavior from a new file.
The issue happens when I open the NVIC panel and then immediately generate code (it doesn't matter if I click anything after opening the panel). The ioc file then gets modified to delete the timebase timer interrupt, but the NVIC panel itself doesn't change. The generated code then removes the interrupt configuration, which causes the program to get stuck because the timebase timer isn't fully setup (or something like that). I can't reenable the interrupt because the config window doesn't allow (de)selection of the timebase interrupt. Changing the timebase timer also doesn't enable the associated interrupt, so I have to manually re-add the interrupt configuration by directly editing the ioc file in a text editor.
I did notice that selecting an NVIC tab in a specific peripheral's configuration panel (vs. the main NVIC panel under System Core) doesn't cause the issue.
Again, not certain that it is specifically some interaction with the timerbase timer causing the issue, but I haven't had the issue with anything else so far.
2021-10-08 06:31 AM
Hello @ALars.2 ,
Sorry for the delay,
I will try to reproduce your problem and I'll keep you posted for any new update.
Thanks, Khouloud