-
Notifications
You must be signed in to change notification settings - Fork 3k
Adding STM32L071xx target #13509
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
Adding STM32L071xx target #13509
Conversation
This PR cannot be merged due to conflicts. Please rebase to resolve them. |
@alcheagle, thank you for your changes. |
How can I make this PR on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very good starting point!
Thx
...s/TARGET_STM/TARGET_STM32L0/TARGET_STM32L071CXCTX/device/TOOLCHAIN_ARM/startup_stm32l073xx.S
Outdated
Show resolved
Hide resolved
targets/TARGET_STM/TARGET_STM32L0/TARGET_STM32L071CXCTX/device/TOOLCHAIN_ARM/stm32l073xz.sct
Outdated
Show resolved
Hide resolved
...s/TARGET_STM/TARGET_STM32L0/TARGET_STM32L071CXCTX/device/TOOLCHAIN_IAR/startup_stm32l073xx.S
Outdated
Show resolved
Hide resolved
targets/TARGET_STM/TARGET_STM32L0/TARGET_STM32L071CXCTX/device/TOOLCHAIN_IAR/stm32l073xx.icf
Outdated
Show resolved
Hide resolved
Maybe, you could update PR title with something "STM32L071 xxx" ? |
thanks @jeromecoutant, I forgot to update the files for all the toolchains that are not GCC. I am not an expert of stm32 mcu families and I don't know the differences between all the mcus under stm32l071xx, is it safe to assume that this target could be used for all the mcus in this family? |
Adding STM32L071CXCTX as a generic target to be extended. This addition required to fix some issues on stml0 library
I did a rebase to the master branch and fixed everything you listed and renamed the target @jeromecoutant tell me if I am still missing something. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For my information, do you an information webpage for your custom target ?
Thx
@ARMmbed/team-st-mcd |
The custom target I am creating out of this MCU family is not planned to be publicly available right now, since it is intended for internal usage |
targets/TARGET_STM/TARGET_STM32L0/TARGET_MCU_STM32L071xx/objects.h
Outdated
Show resolved
Hide resolved
targets/TARGET_STM/TARGET_STM32L0/TARGET_MCU_STM32L071xx/device/us_ticker_data.h
Outdated
Show resolved
Hide resolved
Pull request has been modified.
CI started |
Jenkins CI Test : ✔️ SUCCESSBuild Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
Adding STM32L071CXCTX as a generic target to be extended.
This addition required to fix some issues on stml0 library
Summary of changes
Added a new generic target for STM32L071CXCTX based boards. If you want to use this you have to create a custom target that inherits from this target.
Impact of changes
Migration actions required
Documentation
The changes performed are on the following files/directories:
targets/TARGET_STM/TARGET_STM32L0/device/stm32l0xx_hal_conf.h
: some HAL features had to be disabled since the MCU is not using themtargets/TARGET_STM/TARGET_STM32L0/device/stm32l0xx_hal_tsc.h
: changed the order of preprocessor directives to forextern "C" { ... }
definition, since if TSC was disabled the curly bracket (}
) was missing causing all sort of problemstargets/targets.json
: added the target definitiontargets/TARGET_STM/TARGET_STM32L0/TARGET_STM32L071CXCTX/
: added the target definition filesI performed the changes on mbed-os-6.2.0, the next step is to adapt the target definition for mbed-os-6.2.1, where STM related target definitions have been improved following the various STM32 mcu families.
Pull request type
Test results
I still have not received yet the board using the proper MCU, I performed the unit test with the following command:
I was not able to test against all the available compilers, since I only have the GCC_ARM, but I followed the STM guidelines.
The test were performed by creating a dummy custom test target. The required files are here attached: tests.zip, test.tar.gz.
The test result log are the following: test_results.log
Reviewers