Flashing an F18

You are reading a single comment by @thejoker187 and its replies. Click here to read the full conversation.

•

thejoker187

Hello Guys, I've also tried with openocd v11 on windows but it is not working, this is the error I'm having:

Open On-Chip Debugger 0.11.0 (2021-03-07-12:52)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
WARNING: interface/stlink-v2.cfg is deprecated, please switch to interface/stlink.cfg
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD

nRF52 device has a CTRL-AP dedicated to recover the device from AP lock.
A high level adapter (like a ST-Link) you are currently using cannot access
the CTRL-AP so 'nrf52_recover' command will not work.
Do not enable UICR APPROTECT.

Info : clock speed 1000 kHz
Info : STLINK V2J34S7 (API v2) VID:PID 0483:3748
Info : Target voltage: 3.151546
Warn : target nrf52.cpu examination failed
Error: jtag status contains invalid mode value - communication failure
Polling target nrf52.cpu failed, trying to reexamine
Examination failed, GDB will be halted. Polling again in 100ms
Info : Previous state query failed, trying to reconnect
Error: jtag status contains invalid mode value - communication failure
Polling target nrf52.cpu failed, trying to reexamine
Examination failed, GDB will be halted. Polling again in 300ms
Info : starting gdb server for nrf52.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : Previous state query failed, trying to reconnect
Error: jtag status contains invalid mode value - communication failure
Polling target nrf52.cpu failed, trying to reexamine
Examination failed, GDB will be halted. Polling again in 700ms
Info : Previous state query failed, trying to reconnect
Error: jtag status contains invalid mode value - communication failure

I'm using a stlink v2 clone by the way

P.S. I tried even with stlink.cfg as interface, the result is the same, consider that the VDD pad on pcb is connected to the 3.3v on the adapter

•

fanoush in reply to @thejoker187

consider that the VDD pad on pcb is connected to the 3.3v on the adapter

If you still have battery in or even have charger attached I would not do that, just 3 wires GND,SWCLK,SWDIO. Also some stlink dongles have bad label on case - some go like SWDIO,GND,SWCLK. some are SWCLK,SWDIO,GND and few may have case not matching the pcb - so you may try if GND pin is really GND (is zero ohm to second GND and to USB GND).

Flashing an F18

About

Espruino