This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

EK-TM4C123GXL: Stellaris Virtual Serial Port requires an interactive window

Part Number: EK-TM4C123GXL

Hello,

I have an EK-TM4C123GXL. My PC is Windows 7 Home Premium SP1.

I have an issue trying to install the driver for the COM port. The other two drivers (DFU and JTAG) are correctly installed.

Whenever I try to install the COM port driver I get this message (in Spanish):

So far, I have tried:

1.- Downloading and installing latest (and older, too) drivers (as per this webpage : www.ti.com/.../STELLARIS_ICDI_DRIVERS

Driver is:

[Version]
Signature="$Windows NT$"
Class=Ports
ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
Provider=%MFGNAME%
LayoutFile=layout.inf
CatalogFile=stellaris_icdi_com.cat
DriverVer=12/31/2015,2.0.7922

2.- Downloading and installing both Full Release and Kit Software (as per this webpage: https://www.ti.com/tool/download/SW-TM4C

I cannot start to work without having this feature corrected.

Thank you in advance for your help.

Josep Vicedo.

  • Hello Josep,

    Your image did not load correctly unfortunately so I can't see the error to help - please try and re-upload the image.

  • Hi,

    Let me upload it again:

    Hello,

    I have an EK-TM4C123GXL. My PC is Windows 7 Home Premium SP1.

    I have an issue trying to install the driver for the COM port. The other two drivers (DFU and JTAG) are correctly installed.

    Whenever I try to install the COM port driver I get this message (in Spanish):

    The approximante translation is:

    "Windows found a problem installing the controller software for the device.

    Windows found a device controller for the device, but there was an error when installing it.

    Stellaris Virtual Serial Port

    This operation requires of an interactive windows station.

    If you know the manufacturer of your device, look for inforation about the device controller software in their Technical Support."

    So far, I have tried:

    1.- Downloading and installing latest (and older, too) drivers (as per this webpage : www.ti.com/.../STELLARIS_ICDI_DRIVERS

    Driver is:

    [Version]
    Signature="$Windows NT$"
    Class=Ports
    ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
    Provider=%MFGNAME%
    LayoutFile=layout.inf
    CatalogFile=stellaris_icdi_com.cat
    DriverVer=12/31/2015,2.0.7922

    2.- Downloading and installing both Full Release and Kit Software (as per this webpage: https://www.ti.com/tool/download/SW-TM4C

    3.- Taking ownership of the driver folder

    4.- Starting my PC in the accept unsigned drivers mode

    All these tests are done with deactivated firewall and full permissions.

    I cannot start to work without having this feature corrected.

    Thank you in advance for your help.

    Josep Vicedo.

  • Hello Josep,

    It looks like the port that is not working is the Virtual Serial Port and not the ICDI, so have you tried the USB drivers located at: [Install Path]\TivaWare_C_Series-2.2.0.295\windows_drivers yet?

    You should be able to do a manual installation and then point Windows to that exact folder. That should install the correct USB drivers.

  • Hello,

    Thank you for your answer.

    This is the procedure I have followed and hasn't worked.

    I have downloaded and installed the pack and done this steps:

    (find controller device software in the PC)

    Select folder

    (Windows could not install your In-Circuit Debug Interface

    Windows cannot find device controller software for your device.

    If you know the SW device manufacturer, ask about info...)

    For the other two drivers:

    (Best SW is already installed

    Windwos determined that the device controller software for this device is already up-to-date

    Stellaris...)

    Is this the correct approach?

    Thank you for your help.

    Josep.

  • Hello Josep,

    Did you previous try and install the ICDI drivers to that port?

    If so maybe Windows is trying to use them but they don't work correctly.

    I haven't seen this exact issue before, but I have a guess as to what is wrong. 

    The unknown device shouldn't be "In-Circuit Debug Interface", that makes me think it is still trying to use the wrong driver. So you would need to get it back to where Windows just sees it as an unknown device and then try and process I outlined again so it doesn't try and use the wrong driver with the new driver.

    I am not a Windows expert so I don't know how to undo that though...