-
Notifications
You must be signed in to change notification settings - Fork 22
Add STM32F103xD, STM32F103xG series and fix STM32F103xE startup file #151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
targets/TARGET_STM/TARGET_STM32F1/TARGET_STM32F103xD/TOOLCHAIN_IAR/stm32f103xd.icf
Show resolved
Hide resolved
Hi! Thank you for the contribution. Any way you could provide some more detail on the motivation for this change? What boards are these chips used in? Or are they for custom boards only? |
I believe it is in context of this question #124 These MCUs were added to ARM MbedOS in January, exactly 2 days after last Upstream merge, but many more changes were done and Mbed OS6.17 was also released. |
I need it for custom boards. My first intention is to port one existing application (STM32F103xD) using Mbed Studio to Mbed-CE+CLion, and I plan to start a new application using STM32F103VG. |
It would be great to update to 6.17 , this of course will solve my issue, but I could imagine it is a huge work, I will be more than happy if this PR is accepted to start working seriously with Mbed-CE asap. |
Oh so this code is copied straight from Mbed? |
Yes, it is. |
In that case, this can be greenlighted! I just thought that you wrote all this yourself so I wanted some more background info. |
Sorry, next time I´ll be more specific. Thank you very much. |
Summary of changes
Impact of changes
Migration actions required
Documentation
Pull request type
Test results
Reviewers