Hello,
I am trying to use Ozone 2.56e with JLinkRemoteServer 6.32b ARM (raspberry pi). Unfortunately communication seems to break down.
Thank you for help.
On the server end I get:
In Ozone log I see:
Display All
I am trying to use Ozone 2.56e with JLinkRemoteServer 6.32b ARM (raspberry pi). Unfortunately communication seems to break down.
Thank you for help.
On the server end I get:
Source Code
- *** J-Link Remote Server V6.32b Warning ***Unknown EMU command #28 received. Discontinuing parsing of communication.
- *** J-Link Remote Server V6.32b Warning ***
- Client disconnected.
- Waiting for client connection... Client connected.
- *** J-Link Remote Server V6.32b Warning ***
- Unknown EMU command #28 received. Discontinuing parsing of communication.
- *** J-Link Remote Server V6.32b Warning ***
In Ozone log I see:
Source Code
- J-Link: Connecting to J-Link via TCP/IP (xxxxxxxxxx:19020)
- p, li { white-space: pre-wrap; }
- J-Link: Connected with SEGGER J-Link Remote Server V6.32b compiled 18:30:30 on May 8 2018
- J-Link: Device "MK12DN512XXX5" selected.
- J-Link: InitTarget()
- J-Link: Found SW-DP with ID 0x2BA01477
- J-Link: Scanning AP map to find all available APs
- J-Link: AP[2]: Stopped AP scan as end of AP map has been reached
- J-Link: AP[0]: AHB-AP (IDR: 0x24770011)
- J-Link: AP[1]: JTAG-AP (IDR: 0x001C0000)
- J-Link: Iterating through AP map to find AHB-AP to use
- J-Link: AP[0]: Core found
- J-Link: AP[0]: AHB-AP ROM base: 0xE00FF000
- J-Link: CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
- J-Link: Found Cortex-M4 r0p1, Little endian.
- J-Link: FPUnit: 10 code (BP) slots and 15 literal slots
- J-Link: CoreSight components:
- J-Link: ROMTbl[0] @ E00FF000
- J-Link: ROMTbl[0][0]: EE0FF000, CID: ED200001, PID: ED200001 ???
- J-Link: connected to target device
- Debug.Start();
- Connection failed
- Debug.SetConnectMode (CM_DOWNLOAD_RESET);
- Debug.Start();
- J-Link: Connecting to J-Link via TCP/IP (xxxxxxxxxxx:19020)
- J-Link: Connected with SEGGER J-Link Remote Server V6.32b compiled 18:30:30 on May 8 2018
- J-Link: Device "MK12DN512XXX5" selected.
- J-Link: InitTarget()
- J-Link: Found SW-DP with ID 0x2BA01477
- J-Link: Scanning AP map to find all available APs
- J-Link: AP[2]: Stopped AP scan as end of AP map has been reached
- J-Link: AP[0]: AHB-AP (IDR: 0x24770011)
- J-Link: AP[1]: JTAG-AP (IDR: 0x001C0000)
- J-Link: Iterating through AP map to find AHB-AP to use
- J-Link: AP[0]: Core found
- J-Link: AP[0]: AHB-AP ROM base: 0xE00FF000
- J-Link: CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
- J-Link: Found Cortex-M4 r0p1, Little endian.
- J-Link: FPUnit: 10 code (BP) slots and 15 literal slots
- J-Link: CoreSight components:
- J-Link: ROMTbl[0] @ E00FF000
- J-Link: ROMTbl[0][0]: EE0FF000, CID: ED200001, PID: ED200001 ???
- J-Link: connected to target device
- J-Link: connection to target device lost.
- J-Link: CPU could not be halted
- J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
- J-Link: Reset: Reset device via AIRCR.SYSRESETREQ.
- J-Link: Reset: SYSRESETREQ has confused core.
- J-Link: Reset: Using fallback: VECTRESET.
- J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
- J-Link: Reset: Reset device via AIRCR.VECTRESET.
- J-Link: Reset: CPU may have not been reset (DHCSR.S_RESET_ST never gets set).
- J-Link: Reset: Using fallback: Reset pin.
- J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
- J-Link: Reset: Reset device via reset pin
- J-Link: Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
- J-Link: Reset: Reconnecting and manually halting CPU.
- J-Link: CPU could not be halted
- J-Link: Reset: Core did not halt after reset, trying to disable WDT.
- J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
- J-Link: Reset: Reset device via reset pin
- J-Link: Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
- J-Link: Reset: Reconnecting and manually halting CPU.
- J-Link: CPU could not be halted
- J-Link: Reset: Failed. Toggling reset pin and trying reset strategy again.
- J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
- J-Link: Reset: Reset device via AIRCR.SYSRESETREQ.
- J-Link: Reset: SYSRESETREQ has confused core.
- J-Link: Reset: Using fallback: VECTRESET.
- J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
- J-Link: Reset: Reset device via AIRCR.VECTRESET.
- J-Link: Reset: CPU may have not been reset (DHCSR.S_RESET_ST never gets set).
- J-Link: Reset: Using fallback: Reset pin.
- J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
- J-Link: Reset: Reset device via reset pin
- J-Link: Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
- J-Link: Reset: Reconnecting and manually halting CPU.
- J-Link: CPU could not be halted
- J-Link: Reset: Core did not halt after reset, trying to disable WDT.
- J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
- J-Link: Reset: Reset device via reset pin
- J-Link: Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
- J-Link: Reset: Reconnecting and manually halting CPU.
- J-Link: CPU could not be halted
- J-Link: InitTarget()
- J-Link: Connect Under Reset
- J-Link: Communication error while accessing MDM-AP.
- J-Link: Connect Under Reset
- J-Link: AfterResetTarget()
- J-Link: Could not read hardware status!
- DAP error while reading DP-Ctrl-Stat register.
- InitTarget(): PCode returned with error code -1
- Elf.GetBaseAddr();
- Target.SetReg ("SP", 0x0);
- Target.SetReg ("SP", 0x0): not connected
- Target.SetReg ("PC", 0x0);
- Target.SetReg ("PC", 0x0): not connected
- J-Link: disconnected from target device