13:12 <muli> Hi, 1st here for me. I'm trying to flash an STM32L151 with a Raspi5 via linuxgpiod. I got it working with the JLink-Debugger where I'm erasing the flash via GDB. No I'm trying the same via the GPIOs but I got the following error from "startup.tcl":

13:12 <muli> (gdb) monitor reset halt

13:12 <muli> Translation from khz to adapter speed not implemented

13:12 <muli> Error executing event reset-start on target stm32l1.cpu:

13:12 <muli> embedded:startup.tcl:1193: Error:

13:12 <muli> in procedure 'ocd_process_reset'

13:12 <muli> in procedure 'ocd_process_reset_inner' called at file "embedded:startup.tcl", line 1193

13:12 <muli> [stm32l1.cpu] halted due to debug-request, current mode: Thread

13:12 <muli> xPSR: 0x01000000 pc: 0xfffffffe msp: 0xfffffffc

13:12 <muli> As far as I see "startup.tcl" is part of the OpenOCD binary and there are several files called "startup.tcl" but they are shorter than 1000 lines. How do I know where to look for the error. Grep gives me the following (from the source code):

13:12 <muli> pi@cm5-pi:~/Documents/openocd $ grep -rn 'ocd_process_reset_inner' *

13:12 <muli> src/target/startup.tcl:21:set success [expr {[catch {ocd_process_reset_inner $MODE} result] == 0}]

13:12 <muli> src/target/startup.tcl:31:proc ocd_process_reset_inner { MODE } {

13:12 <muli> tcl/target/ti_cc3220sf.cfg:26:proc ocd_process_reset_inner { MODE } {

13:12 <muli> tcl/target/psoc4.cfg:98:proc ocd_process_reset_inner { MODE } {

13:12 <muli> Any help is appreciated.

15:10 <karlp> muli: what version of openocd, and with what target/board config please?

15:11 <karlp> what does openocd say when it connects, before you get gdb involved?

15:11 <karlp> with gdb, you should be able to just use "load" without needing any manual reset halt steps.

15:22 <PaulFertser> Hm, looks like a regression, linuxgpiod can't set frequency and so reset halt fails.

15:23 <PaulFertser> muli: I suggest you comment out all "adapter speed" commands from target/stm32l1.cfg and retry.

15:40 <muli> Version is 0.12.0, The target config is the following: https://pastebin.com/c6B1bee8 it's nearly identical to the stm32l1.cfg but I added the 2nd bank (I know there's stm32l1x_dual_bank.cfg but I made a copy of the configuration to not mess with the original).

15:40 <PaulFertser> muli: I suspect there's some regression with adapters that can't set speed

15:40 <muli> Config for the Raspi is: https://pastebin.com/Uq0eRpp4 (should be identical to the original one)

15:40 <PaulFertser> (or it was never tested

15:44 <muli> Ok, I commented out all "adapter speed" comments. Got to plug things back in and see …

15:53 <muli> The error is gone and it looks like the reset is working now.

15:54 <muli> Thank you.

15:58 <muli> Now I got to figure out how to unlock and erase flash memory. The obvious gdb-commands are failing.

15:58 <muli> Do you think in general it's a good idea to try this with the GPIOs of the Pi5 or is it a deal breaker to not be able to set the adapter speed and I should stick to some kind of programming adapter?

16:49 <karlp> what gdb commands are you using, and how are they failing?

16:50 <karlp> also, this is breakage, we should get it fixed.

17:11 <muli> For unlocking bank 1 I tried:

17:11 <muli> (gdb) monitor stm32lx unlock 1

17:11 <muli> SWD DPIDR 0x2ba01477

17:11 <muli> Failed to read memory at 0x1ff80008

17:11 <muli> STM32Lx unlock failed

17:11 <muli> Protocol error with Rcmd

17:11 <muli> To erase bank 1 I tried to methods:

17:11 <muli> (gdb) monitor stm32lx unlock 1

17:11 <muli> SWD DPIDR 0x2ba01477

17:11 <muli> Failed to read memory at 0x1ff80008

17:11 <muli> STM32Lx unlock failed

17:11 <muli> Protocol error with Rcmd

17:12 <muli> and

17:12 <muli> (gdb) monitor stm32lx mass_erase 1

17:12 <muli> [stm32l1.cpu] target was in unknown state when halt was requested

17:12 <muli> SWD DPIDR 0x2ba01477

17:12 <muli> [stm32l1.cpu] clearing lockup after double fault

17:12 <muli> [stm32l1.cpu] external reset detected

17:12 <muli> [stm32l1.cpu] halted due to debug-request, current mode: Handler HardFault

17:12 <muli> xPSR: 0xa1000003 pc: 0xfffffffe msp: 0x20000f08

17:12 <muli> SWD DPIDR 0x2ba01477

17:12 <muli> Failed to read memory at 0x1ff80008

17:12 <muli> stm32lx mass erase failed

17:12 <muli> Protocol error with Rcmd

17:14 <muli> If I can help to get this fixed tell me how I may help.

17:29 <muli91> Hm, should install a proper IRC client.