11:26 <Duality> hey all

11:27 <Duality> I am having an issue trying to flash a rp2040 using openocd

11:28 <Duality> I am using a segger jlink and this command is find it start it listens says it found the core: src/openocd -f interface/jlink.cfg -c "transport select swd" -c "adapter speed 1000" -c "bindto 0.0.0.0" -f target/rp2040.cfg -s tcl

11:28 <PaulFertser> Duality: hi

11:29 <PaulFertser> Duality: I suggest you use some pastebin to show full logs

11:29 <Duality> but this command won't work for some reason: src/openocd -f interface/jlink.cfg -c "transport select swd" -c "adapter_khz 6000" -f target/rp2040.cfg -c "program blink.elf reset exit"

11:29 <PaulFertser> The command looks sane, I'd need to say the log to probably tell something useful.

11:38 <Duality> where does openocd store its logs

11:42 <Duality> i also tried -c "log_output /tmp/openocd.log" this is what it says: https://termbin.com/zqw1o

11:44 <PaulFertser> Duality: stdout is ok, you just copy from your terminal emulator.

11:44 <PaulFertser> Duality: you've forgotten -s tcl I guess

11:45 <PaulFertser> Duality: since you're running from source tree and not installing it the regular way.

11:45 <Duality> do you need that even to just flash it

11:45 <PaulFertser> Duality: how is it supposed to find any config files when it's not installed to the destination location?

11:45 <Duality> at the bottom here is the command I copied it's not using -s tcl https://interruptlabs.ca/2022/03/08/Flashing-the-RP2040-with-a-Jlink-and-OpenOCD/

11:46 <PaulFertser> Duality: that's not official OpenOCD documentation.

11:47 <PaulFertser> I can not do anything about it.

11:47 <Duality> well adding -s tcl worked though it says programming finished

11:50 <Duality> I understand now

11:50 <Duality> i read the help for -s

11:50 <Duality> xD makes a lot of sense why it didn't work ...

11:54 <PaulFertser> :)

12:51 <Duality> I am actually not sure if it did flash the device it does say the following several times: https://termbin.com/cxow

12:54 <karlp> add a verify to that program command...

12:55 <karlp> there's no errors there though,

12:55 <karlp> running loader stubs resultsin stopping/starting cores a bit though.

12:57 <Duality> verify failed

12:58 <Duality> https://termbin.com/9bex

12:59 <Duality> says target was in unknonw state and had an error executing cortex_m crc algorithm

13:00 <Duality> it also says it could not read memory at 0x10000234

13:00 <Duality> memory is an external spi flash chip,would this indicate a issue with that, or could it ?

13:17 <Duality> i lowered the speed now I get the following: https://termbin.com/7pg8