It's necessary to write to OTP memory (very rare used)
Please be patient until Tarek fixes the patch. The reference manual lists OTP
at 0x0FF9 and 0x0BF9 so the definition should be:
`flash bank $_CHIPNAME.otp stm32l4x 0x0FF9 0 0 0 $_TARGETNAME`
---
**[tickets:#398] Status of STM
There seems to be a mismatch in OTP bank address.
Could you try comment out OTP definition in tcl/target/stm32wbax.cfg
`# flash bank $_CHIPNAME.otp stm32l4x 0x1fff7000 0 0 0 $_TARGETNAME`
It should allow gdb attach.
---
**[tickets:#398] Status of STM fork and adding support for new STM32 s
Tarek wrote 2 moths ago:
> please test using this patch
https://review.openocd.org/c/openocd/+/7694
But I see in all logs:
Open On-Chip Debugger 0.12.0
instead of
Open On-Chip Debugger 0.12.0+dev-00xxx-gd3949b4af339
Jan,
testing a patched config file with an unpatched release OpenOCD binary has
> I am also referring to an open change set here:
> https://review.openocd.org/c/openocd/+/7694
Maybe if you post review feedback on that change set it might help?
As far as I can see nobody has reviewed it so that may be one reason why it's
lying dormant.
---
**[tickets:#398] Status of STM
Would it be possible to get the changes merged? Being able to upload is better
then nothing, even if debugging is still broken.
---
**[tickets:#398] Status of STM fork and adding support for new STM32 silicon**
**Status:** new
**Milestone:** 0.11.0
**Created:** Wed May 31, 2023 11:05 AM UTC by
Attached is the debug log. Thank you for looking into it.
Attachments:
-
[debug.log](https://sourceforge.net/p/openocd/tickets/_discuss/thread/8be01fa6b5/f56a/attachment/debug.log)
(31.1 kB; text/x-log)
---
**[tickets:#398] Status of STM fork and adding support for new STM32 silicon**
**St
To verbalize the last post: With the change I was able to flash my MCU, but I
cannot attach a debugger. Can you look into why the debugging does not work?
---
**[tickets:#398] Status of STM fork and adding support for new STM32 silicon**
**Status:** new
**Milestone:** 0.11.0
**Created:** Wed M
I see that you are using "interface/stlink.cfg"
we recommend using "interface/stlink-dap.cfg" to work with cortex-M33 on Access
Port != 0
---
**[tickets:#398] Status of STM fork and adding support for new STM32 silicon**
**Status:** new
**Milestone:** 0.11.0
**Created:** Wed May 31, 2023 11:05
please test using this patch
https://review.openocd.org/c/openocd/+/7694
---
**[tickets:#398] Status of STM fork and adding support for new STM32 silicon**
**Status:** new
**Milestone:** 0.11.0
**Created:** Wed May 31, 2023 11:05 AM UTC by Jan Henke
**Last Updated:** Wed May 31, 2023 02:04 PM U
I will push a gerrit change in a few minutes with the needed cfg file
---
**[tickets:#398] Status of STM fork and adding support for new STM32 silicon**
**Status:** new
**Milestone:** 0.11.0
**Created:** Wed May 31, 2023 11:05 AM UTC by Jan Henke
**Last Updated:** Wed May 31, 2023 01:59 PM UTC
> 1. What is the status of that fork?
You probably need to ask STM that question?
> 2. I am struggling with creating a working target config file for the
> STM32WBA chip.
What's wrong with the target script that's in the mainline OpenOCD?
https://github.com/openocd-org/openocd/blob/master/tcl/
---
**[tickets:#398] Status of STM fork and adding support for new STM32 silicon**
**Status:** new
**Milestone:** 0.11.0
**Created:** Wed May 31, 2023 11:05 AM UTC by Jan Henke
**Last Updated:** Wed May 31, 2023 11:05 AM UTC
**Owner:** nobody
Hi,
I have purchased a STM32WBA52CG nucelo board
12 matches
Mail list logo
