add 'stm32l052dap52' (STM32L052K8 MCU) board target #1588
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
'dap52' is Olimex's name of their STM32L052-based fork of 'dap42'
hathach
approved these changes
Aug 10, 2022
There was a problem hiding this comment.
thank you for PR, this is indeed an odd target with dap mcu instead of main mcu. Though I am sure other will find this useful as well, we did have stlink v3 as target as well.
Don't worry about stm32l0538disco, it is added before the family thing, and still haven't got migrated yet. I will do it later on.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds the ST STM32L052 since I encountered a target with said MCU and didn't find an existing board type in TinyUSB.
I tried to follow the newer TinyUSB convention of "boards" sub-directory for a given "family" (stm32l0). There is an existing "stm32l0538disco" board using the older convention that I left untouched since I don't know the reasons behind it still being in the main bsp directory.
I set the board name to "stm32l052dap52". The reason for the naming suffix is that the target that I encountered is the Olimex LoRa-STM32WL-DevKIT, which uses a STM32L052K8 as a CMSIS-DAP adapter for the board's main target, which is a STM32WLE5-series (no USB capability). 'dap52' using the VID:PID 15ba:0044 appears to be Olimex's name of their (slightly buggy) fork of dap42
Olimex did not do the user any favors. Although there is talk in their github repository about a bootloader, that appears to just be leftover verbiage from the dap42 project. There is a SB1 in the schematic labelled "Bootloader", but it doesn't invoke anything. The only practical way to reprogram the STM32L052K8 is via the SWD pins on CON1 (1x10 IDC header).