ARM Cortex-M3 NVIC配置与Freertos
我正在研究使用IAR EWARM v6.70构建的STM32F205 Cortex-M3上使用Freertos v7.3.0预测的遗产。
我的系统间歇性地降落在硬故障异常处理程序和/或看门狗重置中。
我已经跟踪了NVIC配置的一些问题：
- NVIC_PRIORITYGROUPCONFIG（NVIC_PRIORITYGROUP_1）而不是NVIC_PRIORITYGROUP_4。 NVIC_PRIORITYGROUPCONFIG（）来自STM stdperiph驱动程序lib v1.1.0。
- 并非所有应用程序优先级都低于configmax_syscall_interrupt_priority。一些ISR很大，因此我确保所有应用程序优先级都比当前的优先级（优先级较高），而不是验证没有freertos api
呼叫问题，我应该知道其他NVIC/中断与Freertos/Cortex-M3相关的陷阱吗？
谢谢，
- 罗布
I'm working on a legacy projected using FreeRTOS v7.3.0 on an STM32F205 Cortex-M3, built with IAR EWARM v6.70.
My system intermittently lands in the hard fault exception handler, and/or watchdog resets.
I have tracked down some issues with the NVIC config:
- NVIC_PriorityGroupConfig(NVIC_PriorityGroup_1) was used instead of NVIC_PriorityGroup_4. NVIC_PriorityGroupConfig() is from STM StdPeriph Driver Lib v1.1.0.
- Not all app isr priorities were below configMAX_SYSCALL_INTERRUPT_PRIORITY. Some of the isrs are big, so rather than verifying no FreeRTOS API calls, I made sure all app isr priorities are a lower priority (higher priority number) than the current configMAX_SYSCALL_INTERRUPT_PRIORITY setting of 5.
These fixes are in test, but being an intermittent problem, are there any other NVIC/interrupt related gotchas with FreeRTOS/Cortex-M3 that I should be aware of?
Thanks,
-Rob
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论