• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 780 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

COM-port assignement problems with Stellaris Launchpad (EK-LM4F120XL)

Joerg Quinten
Guru 17650 points

Hi there,

I've started playing around with my new Stellaris Launchpads (ordered 2 pcs. of EK-LM4F120XL from TI e-Store in my latest order).

One has a non-working Stellaris Virtual COM Port! The ICDI functionality is fine but the virtual com port is not working (although it shows up correctly in Win7). I've check the other Launchpad which is working fine.

The one in question has the serial no (sticker on bottom of the PCB) 120900269F.

Kind regards
aBUGSworstnightmare 

  • 0
    TI__Expert 8180 points

    aBUGsworstnightmare,

    Would it be possible to take a screenshot of your device manager?  Are all three drivers present in the device manager (Stellaris Virtual Serial Port, Stellaris ICDI DFU Device, and Stellaris ICDI JTAG/SWD Interface)?  Make sure that all other Stellaris devices are not connected to the PC when checking this.  

    It sounds like the driver might not have installed correctly for the Stellaris Virtual Serial Port or has not been installed yet.  If all three devices are present, try removing and then reinstalling the drivers (as outlined in this document).

    -Rebecca

  • 0 in reply to Rebecca Ringhof
    Guru 47900 points

    Rebecca Ringhof said:
    Are all three drivers present in the device manager

    But Rebecca - strongly implied is that one of our Bug's boards does work!  Would not this confirm his PC side is proper?

  • 0 in reply to Rebecca Ringhof
    Guru 17650 points

    Hi Rebecca,

    I poked around a while with the COM-port numbers assigned to this board. Since I have 4 in total (2 from my latest order) I've checked the COM-port no. assigned to them. They got 18-20, the one that wasn't working out-of-the-box was assigned COM10.

    I then changed the port-no to COM21 and now it's working.

    You were right! Sounds pretty much like a conflict with another resource/driver on my OS.

    Rgds
    aBUGSworstnightmare

    non-working config (COM10)

     

    working config (COM21)