You are reading a single comment by @thejoker187 and its replies. Click here to read the full conversation.
  • Hi, a bit of progress has been made, after the soldering of bigger battery the device turned back on, as @fanoush suggested I started the hr measure and connected the pcb to my sagger jlink edu mini with openocd now I can connect to the device:

    Open On-Chip Debugger 0.11.0 (2021-07-29) [https://github.com/sysprogs/openocd]
    Licensed under GNU GPL v2
    libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3­
    For bug reports, read
            http://openocd.org/doc/doxygen/bugs.html­
    swd
    Info : Listening on port 6666 for tcl connections
    Info : Listening on port 4444 for telnet connections
    Info : J-Link EDU Mini V1 compiled Sep 24 2021 16:44:11
    Info : Hardware version: 1.00
    Info : VTarget = 1.584 V
    Info : clock speed 1000 kHz
    Info : SWD DPIDR 0x2ba01477
    Error: Could not find MEM-AP to control the core
    ****** WARNING ******
    nRF52 device has AP lock engaged (see UICR APPROTECT register).
    Debug access is denied.
    Use 'nrf52_recover' to erase and unlock the device.
    
    Warn : target nrf52.cpu examination failed
    Info : starting gdb server for nrf52.cpu on 3333
    Info : Listening on port 3333 for gdb connections
    

    now, should I use the nrf52_recover command as openocd suggested ? Or I should try directly to flash the device with Espruino firmware ?

    P.S. The sagger j-link is much more capable that the st-link clone by the way even if the problem I had yesterday was a very low battery on the watch I will try again the stlink tomorrow

About

Avatar for thejoker187 @thejoker187 started