Hello,
I executed J-Link Commander at Cortex-A53 (BCM2837, Raspberry PI 3b/3b+),
but an infinite loop occurs as follows.
Display All
When I execute OpenOCD(github.com/daniel-k/openocd.git)
under the same condition, it works normally as follows.
Display All
I would like advice for solving an infinite loop.
Best regards,
tmukai
I executed J-Link Commander at Cortex-A53 (BCM2837, Raspberry PI 3b/3b+),
but an infinite loop occurs as follows.
Source Code
- SEGGER J-Link Commander V6.44d (Compiled Mar 27 2019 17:09:10)
- DLL version V6.44d, compiled Mar 27 2019 17:08:23
- Connecting to J-Link via USB...O.K.
- Firmware: J-Link V10 compiled Mar 21 2019 15:43:57
- Hardware version: V10.10
- S/N: XXXXXXXXX
- License(s): FlashBP, GDB
- OEM: SEGGER-EDU
- VTref=3.315V
- Type "connect" to establish a target connection, '?' for help
- J-Link>connect
- Please specify target interface:
- J) JTAG (Default)
- S) SWD
- T) cJTAG
- TIF>
- Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
- JTAGConf>
- Specify target interface speed [kHz]. <Default>: 4000 kHz
- Speed>1000
- Device "CORTEX-A53" selected.
- Connecting to target via JTAG
- TotalIRLen = 4, IRPrint = 0x01
- JTAG chain detection found 1 devices:
- #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
- Scanning AP map
- AP scan stopped (required AP found)
- AP[0]: APB-AP
- Scanning ROMTbl @ 0x80000000
- [0]Comp[0] @ 0x80010000: Cortex-A53
- [0]Comp[1] @ 0x80011000: PMU-A53
- [0]Comp[2] @ 0x80012000: Cortex-A53
- [0]Comp[3] @ 0x80013000: PMU-A53
- [0]Comp[4] @ 0x80014000: Cortex-A53
- [0]Comp[5] @ 0x80015000: PMU-A53
- [0]Comp[6] @ 0x80016000: Cortex-A53
- [0]Comp[7] @ 0x80017000: PMU-A53
- End of ROM table
- [0]Comp[0] @ 0x80010000: Cortex-A53
- [0]Comp[1] @ 0x80011000: PMU-A53
- [0]Comp[2] @ 0x80012000: Cortex-A53
- [0]Comp[3] @ 0x80013000: PMU-A53
- [0]Comp[4] @ 0x80014000: Cortex-A53
- [0]Comp[5] @ 0x80015000: PMU-A53
- [0]Comp[6] @ 0x80016000: Cortex-A53
- [0]Comp[7] @ 0x80017000: PMU-A53
- End of ROM table
- [0]Comp[0] @ 0x80010000: Cortex-A53
- [0]Comp[1] @ 0x80011000: PMU-A53
- [0]Comp[2] @ 0x80012000: Cortex-A53
- [0]Comp[3] @ 0x80013000: PMU-A53
- [0]Comp[4] @ 0x80014000: Cortex-A53
- [0]Comp[5] @ 0x80015000: PMU-A53
- [0]Comp[6] @ 0x80016000: Cortex-A53
- [0]Comp[7] @ 0x80017000: PMU-A53
- End of ROM table
- (... Infinity Loop ...)
When I execute OpenOCD(github.com/daniel-k/openocd.git)
under the same condition, it works normally as follows.
Brainfuck Source Code
- Open On-Chip Debugger 0.9.0-dev-gb796a58c (2019-03-26-15:39)
- Licensed under GNU GPL v2
- For bug reports, read
- http://openocd.sourceforge.net/doc/doxygen/bugs.html
- trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
- adapter speed: 1000 kHz
- jtag_ntrst_delay: 500
- Info : J-Link V10 compiled Mar 21 2019 15:43:57
- Info : J-Link caps 0xb9ff7bbf
- Info : J-Link hw version 101000
- Info : J-Link hw type J-Link
- Info : J-Link max mem block 11496
- Info : J-Link configuration
- Info : USB-Address: 0x0
- Info : Kickstart power on JTAG-pin 19: 0xffffffff
- Info : Vref = 3.322 TCK = 1 TDI = 0 TDO = 0 TMS = 0 SRST = 1 TRST = 1
- Info : J-Link JTAG Interface ready
- Info : clock speed 1000 kHz
- Info : JTAG tap: rpi3.dap tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4)
- Info : rpi3.cpu: hardware has 6 breakpoints, 4 watchpoints
- Info : rpi3.cpu1: hardware has 6 breakpoints, 4 watchpoints
- Info : rpi3.cpu2: hardware has 6 breakpoints, 4 watchpoints
- Info : rpi3.cpu3: hardware has 6 breakpoints, 4 watchpoints
- Info : accepting 'telnet' connection on tcp/4444
- TargetName Type Endian TapName State
- -- ------------------ ---------- ------ ------------------ ------------
- 0 rpi3.cpu aarch64 little rpi3.dap running
- 1 rpi3.cpu1 aarch64 little rpi3.dap running
- 2 rpi3.cpu2 aarch64 little rpi3.dap running
- 3* rpi3.cpu3 aarch64 little rpi3.dap running
- Info : number of cache level 2
- Info : rpi3.cpu3 cluster 0 core 3 multi core
- target state: halted
- target halted in ARM64 state due to debug-request, current mode: EL3H
- cpsr: 0x200003cd pc: 0x1c
- MMU: disabled, D-Cache: disabled, I-Cache: disabled
- Info : number of cache level 2
- Info : rpi3.cpu2 cluster 0 core 2 multi core
- target state: halted
- target halted in ARM64 state due to debug-request, current mode: EL3H
- cpsr: 0x200003cd pc: 0x1c
- MMU: disabled, D-Cache: disabled, I-Cache: disabled
- Info : number of cache level 2
- Info : rpi3.cpu1 cluster 0 core 1 multi core
- target state: halted
- target halted in ARM64 state due to debug-request, current mode: EL3H
- cpsr: 0x200003cd pc: 0x1c
- MMU: disabled, D-Cache: disabled, I-Cache: disabled
- Info : number of cache level 2
- Info : rpi3.cpu cluster 0 core 0 multi core
- target state: halted
- target halted in ARM64 state due to debug-request, current mode: EL3H
- cpsr: 0x600003cd pc: 0x1c8
- MMU: disabled, D-Cache: disabled, I-Cache: disabled
- TargetName Type Endian TapName State
- -- ------------------ ---------- ------ ------------------ ------------
- 0* rpi3.cpu aarch64 little rpi3.dap halted
- 1 rpi3.cpu1 aarch64 little rpi3.dap halted
- 2 rpi3.cpu2 aarch64 little rpi3.dap halted
- 3 rpi3.cpu3 aarch64 little rpi3.dap halted
- Info : dropped 'telnet' connection
I would like advice for solving an infinite loop.
Best regards,
tmukai