Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

ModusToolbox™ General Forum Discussions

MaMo_1781621
Level 2
Level 2
First like received First like given

Anyone have suggestions on what this error means?

I am using kitprog3 cmsis-dap.My Config Options for debug:

-s "${cy_tools_path:openocd}/scripts"

-s "${workspace_loc}/OnethinxCore_00_config/GeneratedSource"

-c "source [find interface/cmsis-dap.cfg]"

-c "transport select swd"

-c "set ENABLE_CM0 0"

-c "set ENABLE_AQUIRE  0"

-c "source [find target/psoc6.cfg]"

-c "puts stderr {Started by GNU MCU Eclipse}"

-c "init; reset init"

Started by GNU MCU Eclipse

Open On-Chip Debugger 0.10.0+dev-2.1.0.99 (2019-02-01-13:19)

Licensed under GNU GPL v2

For bug reports, read

http://openocd.org/doc/doxygen/bugs.html

swd

0

0

adapter speed: 1000 kHz

** Test Mode acquire not supported by selected adapter

cortex_m reset_config sysresetreq

adapter_nsrst_delay: 200

Info : CMSIS-DAP: SWD  Supported

Info : CMSIS-DAP: FW Version = 1.2.0

Info : CMSIS-DAP: Interface Initialised (SWD)

Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1

Info : CMSIS-DAP: Interface ready

Info : clock speed 1000 kHz

Info : SWD DPIDR 0x6ba02477

Info : psoc6.cpu.cm4: hardware has 6 breakpoints, 4 watchpoints

Info : Listening on port 3333 for gdb connections

** SFlash SiliconID:   0xE2072300

Info : SWD DPIDR 0x6ba02477

Error: Failed to read memory at 0x16002008

Error: mem2array: Read @ 0x16002004, w=4, cnt=1, failed

Info : SWD DPIDR 0x6ba02477

Error: Failed to read memory at 0x16002008

Error: mem2array: Read @ 0x16002004, w=4, cnt=1, failed

target halted due to debug-request, current mode: Thread

xPSR: 0x01000000 pc: 0x00000f00 msp: 0x08047800

Started by GNU MCU Eclipse

Info : Listening on port 6666 for tcl connections

Info : Listening on port 4444 for telnet connections

shutdown command invoked

0 Likes
1 Solution

Hi DheerajK_81​,

Thanks for feedback.

I fixed the error. It is  working only when I use the debug option but this is not a problem.

Kitprog3 led led status is ok.

View solution in original post

0 Likes
2 Replies
DheerajK_81
Moderator
Moderator
Moderator
First comment on KBA First comment on blog 5 questions asked

Off the bat I see a spelling mistake in the config options. Can you change "-c "set ENABLE_AQUIRE  0"" to "-c "set ENABLE_ACQUIRE  0"" and check if it works.

Also, check the Kitprog3 status LEDs to ensure they are in either BULK or HID mode. Refer "Kitprog3 Status LEDs" section in Kitprog3 User Guide for more information.

Regards,

Dheeraj

0 Likes

Hi DheerajK_81​,

Thanks for feedback.

I fixed the error. It is  working only when I use the debug option but this is not a problem.

Kitprog3 led led status is ok.

0 Likes