connection fail via swd with jlink

We're using nrf52833 and our target board is already running our program well.

Then 

we'd like to flash by using Jlink SWD programmer.

So, we connected vref, gnd, swdio swclk pin between our target and jlink's 20 pin connector by wire.

When we use jlink flasher program, we got the following errors.


Connecting to target via SWD
InitTarget() start
InitTarget()end
RESET (pin15) high, but should be low. Please check target hardware.
RESET (pin15) high, but should be low. Please check target hardware.
RESET (pin15) high, but should be low. Please check target hardware.
RESET (pin15) high, but should be low. Please check target hardware.
RESET (pin15) high, but should be low. Please check target hardware.
RESET (pin15) high, but should be low. Please check target hardware.
RESET (pin15) high, but should be low. Please check target hardware.
InitTarget() start
InitTarget() end
RESET (pin15) high, but should be low. Please check target hardware.
RESET (pin15) high, but should be low. Please check target hardware.
Cannot connect to target.

It seems errors in connection nrf52833 and jlink.

Currently, our target don't use RESET pin (p0.18) after looking into our schematic.

please check and advice us.

Parents
  • After seeing the link you suggested, I checked my issue.

    Then No CONFIG_GPIO_AS_PINRESET was defined in my code. we don't use reset (p0.18) pin in our project.

    and then I did it with using "nrfjprog --recover" and "nrfjprog --eraseall"

    but they fails and give us the following errors.

    C:\Program Files\SEGGER\JLink_V794e>nrfjprog --recover
    [error] [ Client] - Encountered error -102: Command connect_to_emu_with_snr executed for 316 milliseconds with result -102
    ERROR: Unable to connect to a debugger.
    [error] [ Worker] - An unknown error.
    ERROR: JLinkARM DLL reported an error. Try again. If error condition
    ERROR: persists, run the same command again with argument --log, contact Nordic
    ERROR: Semiconductor and provide the generated log.log file to them.
    NOTE: For additional output, try running again with logging enabled (--log).
    NOTE: Any generated log error messages will be displayed.

    C:\Program Files\SEGGER\JLink_V794e>nrfjprog --eraseall
    [error] [ Client] - Encountered error -102: Command connect_to_emu_with_snr executed for 399 milliseconds with result -102
    ERROR: Unable to connect to a debugger.
    [error] [ Worker] - An unknown error.
    ERROR: JLinkARM DLL reported an error. Try again. If error condition
    ERROR: persists, run the same command again with argument --log, contact Nordic
    ERROR: Semiconductor and provide the generated log.log file to them.
    NOTE: For additional output, try running again with logging enabled (--log).
    NOTE: Any generated log error messages will be displayed.

    So, any advice for us?

  • Today, I use nrf52833 DK board as a debugger for our target device following this link.
    The link is "">docs.nordicsemi.com/.../hw_debug_out.html" .

    After test as above,

    Our target is working good with debugger as DK board.

    It is so good for us.

    Then the connection problem with j-link device still happen as before.

    Please advice us why to happen and how to solve.

Reply Children
No Data
Related