#201 dpmv8_dpm_prepare(): Timeout waiting for dpm prepare when calling virt2phys

[Guido Guenther]

When tracing an imx8 board running a linux kernel I'm seeing the following when calling virt2phys:

Debug: 502 26591 command.c:143 script_debug(): command - ocd_command ocd_command type ocd_virt2phys 0x10000
Debug: 503 26591 command.c:143 script_debug(): command - virt2phys ocd_virt2phys 0x10000
Error: 507 27593 armv8_dpm.c:179 dpmv8_dpm_prepare(): Timeout waiting for dpm prepare
Debug: 508 27593 command.c:642 run_command(): Command failed with error code -4
User : 509 27593 command.c:705 command_run_line():

The same happens when trying to attach a remote gdb (I just noticed that it's simpler to reproduce with virt2phys).

Also all CPU cores are up target shows:

> targets
    TargetName         Type       Endian TapName            State       
--  ------------------ ---------- ------ ------------------ ------------
 0* imx8mq.a53.0       aarch64    little imx8mq.cpu         running
 1  imx8mq.a53.1       aarch64    little imx8mq.cpu         examine deferred
 2  imx8mq.a53.2       aarch64    little imx8mq.cpu         examine deferred
 3  imx8mq.a53.3       aarch64    little imx8mq.cpu         examine deferred

The used JTAG debugger is a Olimex ARM-USB-TINY-H. The full log is attached. The board config used is:

transport select jtag
adapter_khz 1000
reset_config trst_and_srst
adapter_nsrst_delay 70
set CHIPNAME imx8mq
set CHIPCORES 4
source [find target/imx8m.cfg]

very similar to NXPs EVK.

[Guido Guenther]

That's the issue I "reported" on IRC yesterday. Since Debian's pastebin expires I put this into the issue tracker.