cancel
Showing results for 
Search instead for 
Did you mean: 

STM32F429i Discovery FW v1.0.0 minor correction

gfuehrer
Associate II
Posted on November 02, 2013 at 00:11

These methods were not completely renamed in the file startup_stm32f429_439xx.s:

SVC_Handler -> vPortSVCHandler

PendSV_Handler -> xPortPendSVHandler

SysTick_Handler -> xPortSysTickHandler

Search this file for those old names and you'll see what I mean.

IMHO, the old names are preferable. Is there a reason for changing them? Please consider reverting back to the old names.

- Gary

#stm32f429i-discovery-correction
1 REPLY 1
Posted on November 02, 2013 at 00:52

Well I'm not 100% sure what you mean, can you cite the specific directory your talking about.

I can see the Keil and IAR varients

STM32F429I-Discovery_FW_V1.0.0\Projects\Demonstration\EWARM\startup_stm32f429_439xx.s

STM32F429I-Discovery_FW_V1.0.0\Projects\Demonstration\MDK-ARM\startup_stm32f429_439xx.s

Modify the SVC and PendSV for FreeRTOS, SysTick is left, and the routine is then overloaded to perform it's regular task, AND call xPortSysTickHandler.

The Atollic one is inconsistent in this matter. What exactly is the complaint here, the use of FreeRTOS names for these 3 vectors?

The other template files aren't unreasonable, through there is a somewhat inconsistent mix of STM32F429I-DISCO and STM324x9I-EVAL porting and comments.
Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..