Summary of Pitfalls in FreeRTOS Project Configuration

If you haven’t tried other methods online, you can go directly to step four.1) After generating the project files from MX, open them in Keil5, compile, and you will encounter the following error:Summary of Pitfalls in FreeRTOS Project Configuration

01_FREETOS_my\01_FREETOS_my.sct(7): error: L6236E: No section matches selector - no section to be FIRST/LAST.

There is a missing startup file, but when MX generates the project files, there is actually a startup file located at\MDK-ARM\RTE\Device\STM32F103C8as shown in the image below, with a .s suffix fileSummary of Pitfalls in FreeRTOS Project Configuration2) There is a claim online that by checking the startup item in project management, the startup file will naturally appear in the file tree on the left.Summary of Pitfalls in FreeRTOS Project ConfigurationSummary of Pitfalls in FreeRTOS Project ConfigurationAfter checking, I recompiled and found that it resulted in an errorSummary of Pitfalls in FreeRTOS Project Configuration

01_FreeRTOS_my\01_FreeRTOS_my.axf: Error: L6200E: Symbol SystemCoreClock multiply defined (by system_stm32f10x.o and system_stm32f1xx.o).

3) After researching, it may be necessary to comment out these three segments of code in the startup file.Summary of Pitfalls in FreeRTOS Project Configuration4) Still useless, I tried the second solution, adding the startup file here and unchecking the option from the previous step, then recompiling, and it worked √Summary of Pitfalls in FreeRTOS Project Configuration5) In addition, it seems thatSTM32Cube v1.8.5 needs to be associated with CMSIS V2.0 to utilize the features and capabilities of CMSIS V2.0 during the development process, better adapting to the specific project requirements.Summary of Pitfalls in FreeRTOS Project Configuration

Leave a Comment