STM32WBA missing target configuration file

Open

#19 opened on May 31, 2023 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 35/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Stale
Tech stack: c
Domain: devtools, embedded-iot

Research direction

Review commit 54c8f87e552db5198ee47e094bdbc6b4a72c634a alongside target/stm32l4x.cfg and target/stm32wbx.cfg, then consult RM0493 section 40.2.8 for the STM32WBA identifiers. Done means adding a working STM32WBA target configuration that can flash an application to the board.

Written by the indexing model from the issue text.

Description

In commit 54c8f87e552db5198ee47e094bdbc6b4a72c634a support for the STM32WBA chip was added to the STM32L4x flash driver, unfortunately without any target configuration file.

Even with the above commit added to my local OpenOCD, I cannot flash my application into the board, as neither the existing target/stm32l4x.cfg nor target/stm32wbx.cfg work with the board. I have no prior experience with writing my own target config, so I am quite lost now. I have found the JTAG ID of the chip in the reference manual (RM0493 section 40.2.8), but cannot find the correct SWD ID. Also I am not sure what other changes need to be done to adapt an existing config file for this chip.

Can someone with more experience look into creating a working STM32WBA target config file? I noticed the same is also true for the STM32C0x chip (flash driver yes, target config no).

Dominant language: C
Stars: 202
Forks: 57
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.