Tuesday, May 22nd 2018, 11:43pm UTC+2

You are not logged in.

  • Login
  • Register

artur

Beginner

Date of registration: Sep 17th 2015

Posts: 9

1

Wednesday, May 9th 2018, 8:06pm

Ozone + JLinkRemoteServer "Unknown EMU command #28 received"

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:

Source code

1
2
3
4
5
6
7
*** 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

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
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

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 1,048

2

Monday, May 14th 2018, 9:27am

Hello,

Thank you for your inquiry.
The issue regarding unknown emu command #28 is already known and fixed internally. A fixed release is planned in the next two weeks.
However it usually appears as a follow up error to a previous more generic problem when interfacing the hardware. Looking through your logs this seems to be the case here.
Could you try a generic connect using the J-Link Commander directly without J-Link Remote Server? https://wiki.segger.com/J-Link_cannot_co…-Link_Commander

Is your device locked? Could you try command unlock kinetis? Make sure the dialogue is not disalbed: https://wiki.segger.com/Kinetis_Series_D…device_detected

Best regards,
Nino
Please read the forum rules before posting: Forum Rules

Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/


artur

Beginner

Date of registration: Sep 17th 2015

Posts: 9

3

Wednesday, May 16th 2018, 5:24pm

Okay - I'll wait for the fix.

Just for your info: the very same setup worked fine on Windows locally with Ozone or J-Flash Lite + remote desktop, but was not as convenient if I had Ozone running on my development machine. Remote server on Windows gave identical #28 error.