[SOLVED] Ozone + JLinkRemoteServer "Unknown EMU command #28 received"

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] 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. *** J-Link Remote Server V6.32b Warning ***Unknown EMU command #28 received. Discontinuing parsing of communication.
    2. *** J-Link Remote Server V6.32b Warning ***
    3. Client disconnected.
    4. Waiting for client connection... Client connected.
    5. *** J-Link Remote Server V6.32b Warning ***
    6. Unknown EMU command #28 received. Discontinuing parsing of communication.
    7. *** J-Link Remote Server V6.32b Warning ***


    In Ozone log I see:

    Source Code

    1. J-Link: Connecting to J-Link via TCP/IP (xxxxxxxxxx:19020)
    2. p, li { white-space: pre-wrap; }
    3. J-Link: Connected with SEGGER J-Link Remote Server V6.32b compiled 18:30:30 on May 8 2018
    4. J-Link: Device "MK12DN512XXX5" selected.
    5. J-Link: InitTarget()
    6. J-Link: Found SW-DP with ID 0x2BA01477
    7. J-Link: Scanning AP map to find all available APs
    8. J-Link: AP[2]: Stopped AP scan as end of AP map has been reached
    9. J-Link: AP[0]: AHB-AP (IDR: 0x24770011)
    10. J-Link: AP[1]: JTAG-AP (IDR: 0x001C0000)
    11. J-Link: Iterating through AP map to find AHB-AP to use
    12. J-Link: AP[0]: Core found
    13. J-Link: AP[0]: AHB-AP ROM base: 0xE00FF000
    14. J-Link: CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
    15. J-Link: Found Cortex-M4 r0p1, Little endian.
    16. J-Link: FPUnit: 10 code (BP) slots and 15 literal slots
    17. J-Link: CoreSight components:
    18. J-Link: ROMTbl[0] @ E00FF000
    19. J-Link: ROMTbl[0][0]: EE0FF000, CID: ED200001, PID: ED200001 ???
    20. J-Link: connected to target device
    21. Debug.Start();
    22. Connection failed
    23. Debug.SetConnectMode (CM_DOWNLOAD_RESET);
    24. Debug.Start();
    25. J-Link: Connecting to J-Link via TCP/IP (xxxxxxxxxxx:19020)
    26. J-Link: Connected with SEGGER J-Link Remote Server V6.32b compiled 18:30:30 on May 8 2018
    27. J-Link: Device "MK12DN512XXX5" selected.
    28. J-Link: InitTarget()
    29. J-Link: Found SW-DP with ID 0x2BA01477
    30. J-Link: Scanning AP map to find all available APs
    31. J-Link: AP[2]: Stopped AP scan as end of AP map has been reached
    32. J-Link: AP[0]: AHB-AP (IDR: 0x24770011)
    33. J-Link: AP[1]: JTAG-AP (IDR: 0x001C0000)
    34. J-Link: Iterating through AP map to find AHB-AP to use
    35. J-Link: AP[0]: Core found
    36. J-Link: AP[0]: AHB-AP ROM base: 0xE00FF000
    37. J-Link: CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
    38. J-Link: Found Cortex-M4 r0p1, Little endian.
    39. J-Link: FPUnit: 10 code (BP) slots and 15 literal slots
    40. J-Link: CoreSight components:
    41. J-Link: ROMTbl[0] @ E00FF000
    42. J-Link: ROMTbl[0][0]: EE0FF000, CID: ED200001, PID: ED200001 ???
    43. J-Link: connected to target device
    44. J-Link: connection to target device lost.
    45. J-Link: CPU could not be halted
    46. J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
    47. J-Link: Reset: Reset device via AIRCR.SYSRESETREQ.
    48. J-Link: Reset: SYSRESETREQ has confused core.
    49. J-Link: Reset: Using fallback: VECTRESET.
    50. J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
    51. J-Link: Reset: Reset device via AIRCR.VECTRESET.
    52. J-Link: Reset: CPU may have not been reset (DHCSR.S_RESET_ST never gets set).
    53. J-Link: Reset: Using fallback: Reset pin.
    54. J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
    55. J-Link: Reset: Reset device via reset pin
    56. J-Link: Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
    57. J-Link: Reset: Reconnecting and manually halting CPU.
    58. J-Link: CPU could not be halted
    59. J-Link: Reset: Core did not halt after reset, trying to disable WDT.
    60. J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
    61. J-Link: Reset: Reset device via reset pin
    62. J-Link: Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
    63. J-Link: Reset: Reconnecting and manually halting CPU.
    64. J-Link: CPU could not be halted
    65. J-Link: Reset: Failed. Toggling reset pin and trying reset strategy again.
    66. J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
    67. J-Link: Reset: Reset device via AIRCR.SYSRESETREQ.
    68. J-Link: Reset: SYSRESETREQ has confused core.
    69. J-Link: Reset: Using fallback: VECTRESET.
    70. J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
    71. J-Link: Reset: Reset device via AIRCR.VECTRESET.
    72. J-Link: Reset: CPU may have not been reset (DHCSR.S_RESET_ST never gets set).
    73. J-Link: Reset: Using fallback: Reset pin.
    74. J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
    75. J-Link: Reset: Reset device via reset pin
    76. J-Link: Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
    77. J-Link: Reset: Reconnecting and manually halting CPU.
    78. J-Link: CPU could not be halted
    79. J-Link: Reset: Core did not halt after reset, trying to disable WDT.
    80. J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
    81. J-Link: Reset: Reset device via reset pin
    82. J-Link: Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
    83. J-Link: Reset: Reconnecting and manually halting CPU.
    84. J-Link: CPU could not be halted
    85. J-Link: InitTarget()
    86. J-Link: Connect Under Reset
    87. J-Link: Communication error while accessing MDM-AP.
    88. J-Link: Connect Under Reset
    89. J-Link: AfterResetTarget()
    90. J-Link: Could not read hardware status!
    91. DAP error while reading DP-Ctrl-Stat register.
    92. InitTarget(): PCode returned with error code -1
    93. Elf.GetBaseAddr();
    94. Target.SetReg ("SP", 0x0);
    95. Target.SetReg ("SP", 0x0): not connected
    96. Target.SetReg ("PC", 0x0);
    97. Target.SetReg ("PC", 0x0): not connected
    98. J-Link: disconnected from target device
    Display All
  • 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? wiki.segger.com/J-Link_cannot_…ty_using_J-Link_Commander

    Is your device locked? Could you try command unlock kinetis? Make sure the dialogue is not disalbed: wiki.segger.com/Kinetis_Series…s#Secured_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.
    Alternatively our support ticketing system can be used as well: segger.com/ticket/
  • 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.