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

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.



Date of registration: May 9th 2018

Posts: 1


Wednesday, May 16th 2018, 12:52pm

J-Link Remote Server Unknown EMU command #28


I'm using J-Link tools version 6.32c and trying to test the remote server function with a USB J-Link. I run remote server on one Windows 10 machine. I then launch J-Link Commander on the second Windows 10 machine within the same LAN.

After executing a connect command I eventually receive a message box on Remote Server stating "Unknown EMU command #28 received. Discontinuing parsing of communication".

Thank you for your help,

Below is a capture of the Commander console and error.

Type "connect" to establish a target connection, '?' for help
Please specify device / core. : STM32F412RG
Type '?' for selection dialog
Please specify target interface:
J) JTAG (Default)
Specify target interface speed [kHz]. : 4000 kHz
Device "STM32F412RG" selected.

Connecting to target via SWD
Found SW-DP with ID 0x2BA01477
Device will be unsecured now.
Found SW-DP with ID 0x2BA01477
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 15 code (BP) slots and 15 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000

****** Error: Communication timed out: Requested 4 bytes, received 0 bytes !
Cannot connect to target.


Super Moderator

Date of registration: Jan 2nd 2017

Posts: 1,048


Wednesday, May 16th 2018, 1:20pm


Thank you for your inquiry.
The issue is already known and has been internally fixed.
A fixed release is planned to be available in the next 1-2 weeks.

To stay up to date with our J-Link software releases we suggest subscribing to our notification list:

Best regards,
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/