Important changes to forums and questions
All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.
8 years, 8 months ago.
Proting mbed to stm32F103VET6
Althou the guide of med ofiicial : https://developer.mbed.org/handbook/mbed-SDK-porting, it is hard to understand for me.
Any more detail guide?
2 Answers
8 years, 2 months ago.
You can start with using the existing MBED-DEV library for this STM board:
https://developer.mbed.org/platforms/ST-Nucleo-F103RB/
You may need to make some changes to NVIC, STACK, HEAP, RAM and FLASH and maybe some other settings depending on the difference between the two targets, compare the RM's to see the differences.
One problem, but I'm not entirely sure, the ST-LINK firmware may not recognise the target when programing, however I believe all STM32 targets are catered for, you will need to try. Just use the Nucleo ST link (CN4) connections to your custom board and remove JP6 jumper on the Nucleo (can't program two chips at the same time).
8 years, 2 months ago.
Hello, I'm new to mbed sdk, I used stm32F103VET6 on my custom board, now I want to try it in combination with mbed. Has anyone succeded in porting mbed to stm32F103VET6 (or any other uC)? If I follow this guide (https://developer.mbed.org/handbook/mbed-SDK-porting), will I be able to actually use my own custom board with online mbed compiler? If it is to be recognised as a massive storage device it should have some firmware preloaded, in case of STM32 uC and STlink programmer is it the thing of the target uC or STlink firmware? Thank you for the answer
Can you provide details what's hard to understand? It might be easier jsut to clone gihtub repo and look around cmsis/hal folders inside libraries/mbed
posted by Martin Kojtal 02 Sep 2015