Preaload Image

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #468

    mazidulalam
    Participant

    Hi Alex,

    Finally I got my path adapter from segger. But after connecting I am getting the following errors. Any idea on how to fix this?

    Open On-Chip Debugger 0.10.0+dev-00433-g9b83e617 (2018-07-26-14:42)
    Licensed under GNU GPL v2
    For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
    adapter speed: 1000 kHz
    srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
    Info : mohor tap selected
    Info : adv debug unit selected
    Info : Option 1 is passed to adv debug unit
    Info : core 0 selected
    Info : add flash_bank rv32m1 rv32m1.flash0
    Info : add flash_bank rv32m1 rv32m1.flash1
    Info : J-Link V10 compiled Oct 26 2018 12:04:17
    Info : Hardware version: 10.10
    Info : VTarget = 2.903 V
    Info : clock speed 1000 kHz
    Error: JTAG scan chain interrogation failed: all zeroes
    Error: Check JTAG interface, timings, target power, etc.
    Error: Trying to use configured scan chain anyway…
    Error: rv32m1.cpu: IR capture error; saw 0x00 not 0x01
    Warn : Bypassing JTAG setup events due to errors
    Info : adv debug unit is configured with option ADBG_USE_HISPEED
    Warn : Burst read timed out
    Warn : Burst read timed out
    Error: Burst read failed
    Error: Couldn’t read the CPU state
    Warn : Burst read timed out
    Warn : Burst read timed out
    Error: Burst read failed
    Warn : Debug IF CPU control reg read failure.
    Warn : Resetting JTAG TAP state and reconnectiong to debug IF.
    Info : adv debug unit is configured with option ADBG_USE_HISPEED
    Warn : …attempt 1 of 5
    Warn : Burst read timed out
    Warn : Burst read timed out
    Error: Burst read failed
    Warn : Debug IF CPU control reg read failure.
    Warn : Resetting JTAG TAP state and reconnectiong to debug IF.
    Info : adv debug unit is configured with option ADBG_USE_HISPEED
    Warn : …attempt 2 of 5
    Warn : Burst read timed out
    Warn : Burst read timed out
    Error: Burst read failed
    Warn : Debug IF CPU control reg read failure.
    Warn : Resetting JTAG TAP state and reconnectiong to debug IF.
    Info : adv debug unit is configured with option ADBG_USE_HISPEED
    Warn : …attempt 3 of 5
    Warn : Burst read timed out
    Warn : Burst read timed out
    Error: Burst read failed
    Warn : Debug IF CPU control reg read failure.
    Warn : Resetting JTAG TAP state and reconnectiong to debug IF.
    Info : adv debug unit is configured with option ADBG_USE_HISPEED
    Warn : …attempt 4 of 5
    Warn : Burst read timed out
    Warn : Burst read timed out
    Error: Burst read failed
    Warn : Debug IF CPU control reg read failure.
    Warn : Resetting JTAG TAP state and reconnectiong to debug IF.
    Info : adv debug unit is configured with option ADBG_USE_HISPEED
    Warn : …attempt 5 of 5
    Error: Could not re-establish communication with target
    Error: Error while calling rv32m1_is_cpu_running
    Polling target rv32m1.cpu failed, trying to reexamine
    Warn : Burst read timed out
    Warn : Burst read timed out
    Error: Burst read failed
    Error: Couldn’t read the CPU state
    Examination failed, GDB will be halted. Polling again in 100ms
    Warn : Burst read timed out
    Warn : Burst read timed out
    Error: Burst read failed
    Warn : Debug IF CPU control reg read failure.
    Warn : Resetting JTAG TAP state and reconnectiong to debug IF.
    Info : adv debug unit is configured with option ADBG_USE_HISPEED
    Warn : …attempt 1 of 5
    Warn : Burst read timed out
    Warn : Burst read timed out
    Error: Burst read failed
    Warn : Debug IF CPU control reg read failure.
    Warn : Resetting JTAG TAP state and reconnectiong to debug IF.
    Info : adv debug unit is configured with option ADBG_USE_HISPEED

    #346

    mazidulalam
    Participant

    Sorry target config mentioned above gives this error:
    openocd: src/jtag/core.c:343: jtag_checks: Assertion `jtag_trst == 0′ failed.

    But this works:
    target create $_TARGETNAME cortex_m -dap $_CHIPNAME.dap -ap-num 0

    #345

    mazidulalam
    Participant

    Yes I have. This is my target in openocd config file:

    set _TARGETNAME $_CHIPNAME.cpu
    target create $_TARGETNAME rv32m1 -endian little -chain-position $_TARGETNAME

    #334

    mazidulalam
    Participant

    I have managed to establish connection with the board via cmsis-dap interface but cant flash program any code as halt command fails every time. As mentioned above cmsis-dap works with arm cores, I should be able to program on M0 and M4 cores of the board, right?

Viewing 4 posts - 1 through 4 (of 4 total)