Cart New Account Login

HomeAbout usProductsSupportForumsBlogCustomer Service

Please accept the use of cookies on our site

At PEmicro we use web browser cookies in order to provide you with an enhanced experience and in order to be able to do things like shopping cart processing and identify you when you login to our website.

Click here to accept

search inside this forum
search inside all forums
“Multilink Universal” is not showing up as a Comport or USB device in my device Manager
Joe T. Aug 10, 2017 at 01:16 PM (13:16 hours)
Staff: Kevin M.

  • I am trying to program a NXP NXP_K1x_K11DN512M5, on the Command line with "pegdbserver_console.exe".  When executing the first two error that need resolving are:
    Error opening selected communication interface
    Error - Port not found.

    “PEMicro Multilink Universal” has the Blue LED lit.
    -I am on a Windows 10.
    -The Jungo Drivers look good, properties = “This device is working properly”.

    In my Device Manager
    -Ports(COM& LPT) show nothing relating to my Multilink
    -"Universal Serial Bus Controllers" show nothing relating to my Multilink

    Please advise.


  • Joe,

    If you look under the Jungo tab do you see Multilink 2.0?

    If not, can you try different USB ports and also see if that multilink shows up on different computers?



  • Yes, I have "Multilink 2.0" under the Jungo Tab.
    I was expecting Multilink under the "Universal Serial Bus Controllers" Tab.

    With that said...the connection the PE "Multilink 2.0" has been established now, unfortunately I do not know what to attribute it to, nothing has changed in my Device Manager settings, the command line arguments were always copied and pasted for consistency...the PC was Power cycled many times with attempts to reset "devices", "drivers", etc, then...just "Voila" automagically my command line execution progressed past the connecting to the PE Multilink. Obviously we in the business know "something" had to change somewhere between my command line an the USB port...I will attribute this one to Windows 10 and its many layers that I have little control over.

    Here is my current execution at the command line:
    (reduced my path with "..." for simplicity)

    C:\Users\...\win32>pegdbserver_console.exe -device=Freescale_K1x_K11DN512M5 -startserver -serverport=7224 -interface=USBMULTILINK -speed=5000 -port=USB1 -USE_CYCLONEPRO_RELAYS=1 -Multilink_PowerDownDelay=250 -Multilink_PowerUpDelay=1000 -FORCE_MASS_ERASE=0 -serverip=

    P&E GDB Server for Arm(R) devices, Version
    Copyright 2014, P&E Microcomputer Systems Inc, All rights reserved

    Loading library C:\Users\...\win32\gdi\unit_ngs_arm_internal.dll ... Done.

    Command line arguments: -device=Freescale_K1x_K11DN512M5 -startserver -serverport=7224 -interface=USBMULTILINK -speed=5000 -port=USB1 -USE_CYCLONEPRO_RELAYS=1 -Multilink_PowerDownDelay=250 -Multilink_PowerUpDelay=1000 -FORCE_MASS_ERASE=0 -serverip=
    Device selected is NXP_K1x_K11DN512M5
    User Specified Hardware Selection : Interface=USBMULTILINK and Port=USB1
    Connecting to target.
    P&E Interface detected - Flash Version 9.81
    (C)opyright 2016, P&E Microcomputer Systems, Inc. (

    Loading srec from C:\Users\a72810\.p2\pool\plugins\com.pemicro.debug.gdbjtag.pne.expansion_3.1.0.201707241417\win32\gdi\P&E\usbmlfsufarmens.0981
    Successfully found C:\Users\...\.p2\pool\plugins\com.pemicro.debug.gdbjtag.pne.expansion_3.1.0.201707241417\win32\gdi\P&E\usbmlfsufarmens.0981
    Erasing internal application checksum ...
    Rebooting ...
    Erasing Application region ...
    Blank checking Application region ...
    Programming Application firmware ...
    Rebooting ...

    All steps completed successfully.
    Can not enter background mode.

    Unable to initialize PEDebug.

    PEmicro GDB Launch Failure : The GDB Server was not able to establish a connection to the target processor. Please check your connections and power.
    Verify that the launch settings in the Debug Configuration are accurate.

    Target Disconnected.

  • Joe,

    I am confident that your drivers are working correctly.

    It looks like the Multilink is having trouble establishing a connection to the target.

    Are you sure it is powered and connected properly?

    Do you see the yellow light on the multilink?

  • Kevin,
    Your thoughts are the same as mine.
    No Yellow light on the Multilink.

  • Joe,

    Are you using the multilink to provide power to the target?

    If so, you need to use a config file that contains the following:


    And then pass the name/path of the config file on the command line: configfile=_config.ini

  • Kevin,
    Just a quick top level of my project.
    1) I have never used the "Multilink" device before.
    2) I have never used the "pegdbserver_console.exe"
    3) I am attempting to program a third parties PCB...which I also am becoming acquainted with.

    So any advice you can give me is greatly appreciated.

    You can see in my earlier post above, one of the command parameters I send is "-USE_CYCLONEPRO_RELAYS=1" which now I am learning should power my target via your Multilink. I like your idea of config file as I become more confident in this process.


  • Joe,

    The gdbserver is intended for debugging, not programming.

    Please take a look at the following product:

Add comment

   Want to comment? Please login or create a new PEMicro account.

© 2018 P&E Microcomputer Systems Inc.
Website Terms of Use and Sales Agreement