M-Labs
/
zynq-rs
11
0
Fork 15
Code Issues 6 Pull Requests 1 Releases Wiki Activity

openocd failure Error: JTAG-DP STICKY ERROR #7

New Issue
Closed
opened 2019-12-26 19:19:43 +08:00 by sb10q · 3 comments
sb10q commented 2019-12-26 19:19:43 +08:00
Owner
Copy Link
$ openocd -f zc706.cfg
Open On-Chip Debugger 0.10.0-snapshot (2019-12-24-01:53)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
adapter speed: 1000 kHz
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
Zynq CPU1.
srst_only separate srst_gates_jtag srst_push_pull connect_deassert_srst
Info : clock speed 1000 kHz
Info : JTAG tap: zynq.tap tap/device found: 0x23731093 (mfg: 0x049 (Xilinx), part: 0x3731, ver: 0x2)
Info : JTAG tap: zynq.dap tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)
Error: JTAG-DP STICKY ERROR
Error: Could not initialize the APB-AP
Info : JTAG tap: zynq.tap tap/device found: 0x23731093 (mfg: 0x049 (Xilinx), part: 0x3731, ver: 0x2)
Info : JTAG tap: zynq.dap tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)
Error: JTAG-DP STICKY ERROR
Error: Could not initialize the APB-AP
Error: JTAG-DP STICKY ERROR
Error: Could not initialize the APB-AP
Warn : zynq.cpu.0: ran after reset and before halt ...
Warn : zynq.cpu.1: ran after reset and before halt ...
TARGET: zynq.cpu.0 - Not halted
in procedure 'xilinx_ps7_init' called at file "zc706.cfg", line 34
in procedure 'reset' called at file "./xilinx-tcl.cfg", line 52
in procedure 'ocd_bouncer'

Using openocd from nixpkgs 20.03pre206438.a06925d8c60 and zc706 9199bb7a16.

``` text $ openocd -f zc706.cfg Open On-Chip Debugger 0.10.0-snapshot (2019-12-24-01:53) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html adapter speed: 1000 kHz Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'. Zynq CPU1. srst_only separate srst_gates_jtag srst_push_pull connect_deassert_srst Info : clock speed 1000 kHz Info : JTAG tap: zynq.tap tap/device found: 0x23731093 (mfg: 0x049 (Xilinx), part: 0x3731, ver: 0x2) Info : JTAG tap: zynq.dap tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Error: JTAG-DP STICKY ERROR Error: Could not initialize the APB-AP Info : JTAG tap: zynq.tap tap/device found: 0x23731093 (mfg: 0x049 (Xilinx), part: 0x3731, ver: 0x2) Info : JTAG tap: zynq.dap tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Error: JTAG-DP STICKY ERROR Error: Could not initialize the APB-AP Error: JTAG-DP STICKY ERROR Error: Could not initialize the APB-AP Warn : zynq.cpu.0: ran after reset and before halt ... Warn : zynq.cpu.1: ran after reset and before halt ... TARGET: zynq.cpu.0 - Not halted in procedure 'xilinx_ps7_init' called at file "zc706.cfg", line 34 in procedure 'reset' called at file "./xilinx-tcl.cfg", line 52 in procedure 'ocd_bouncer' ``` Using openocd from nixpkgs 20.03pre206438.a06925d8c60 and zc706 9199bb7a1656ad6b7ca4a293918d00fc109ddb52.
sb10q commented 2019-12-27 17:53:17 +08:00
Author
Owner
Copy Link

This seems to persist until the board is power-cycled, and this is triggered (inexplicably) by the firmware booting to "Eth On".

This seems to persist until the board is power-cycled, and this is triggered (inexplicably) by the firmware booting to "Eth On".
sjm commented 2020-01-06 04:22:08 +08:00
Contributor
Copy Link

I could shut this error up by setting this to false: https://git.m-labs.hk/M-Labs/zc706/src/branch/master/libboard_zc706/src/boot.rs#L115

I could shut this error up by setting this to false: https://git.m-labs.hk/M-Labs/zc706/src/branch/master/libboard_zc706/src/boot.rs#L115
astro commented 2020-01-10 05:14:35 +08:00
Contributor
Copy Link

Ah! openocd is missing core1. Thanks for debugging that.

If core1 gets just reset but not stopped it is going to idle in WFE. Sounds okay to me.

Ah! openocd is missing core1. Thanks for debugging that. If core1 gets just reset but not stopped it is going to idle in `WFE`. Sounds okay to me.
astro closed this issue 2020-01-10 05:16:02 +08:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: M-Labs/zynq-rs#7
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?