• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 55 subscribers
  • Views 283 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

LP-CC2651P3: XDS110 USB reconnect problem on LP-CC2651P3

YG JANG
Prodigy 10 points
Part Number: LP-CC2651P3
Other Parts Discussed in Thread: LAUNCHXL-CC26X2R1, ENERGYTRACE

I have three types of development kits as belows.
1. LP-CC2651P3
2. LAUNCHXL-CC26X2R1
3. LAUNCHXL-CC1352P-2

I connect the XDS110 of these devices with jumper cables and use them to upgrade the firmware of the target device.
These devices are connected to a pc (Windows 10) via a usb cable.
When connecting the target device to the XDS110 for firmware upgrade, there is a problem that the USB driver is disconnected and reconnected.
This problem only occurs in LP-CC2651P3.
It doesn't happen in LAUNCHXL-CC26X2R1 and LAUNCHXL-CC1352P-2.
All XDS110 firmware versions are 3.0.0.20.

How can I solve this USB reconnection problem of LP-CC2651P3 ?

  • 0
    TI__Guru**** 206657 points

    Hi YG,

    There are no expected differences between the XDS110 hardware or software versions of these LaunchPads.  Please confirm that each hardware, XDS110 connection, and jumper setting is identical, then provide screenshots of the error observed and possible an image of the current physical setup if the problem persists.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 10 points

    Hi Ryan

    The XDS110 hardware of LP-CC2651P3 differs between LAUNCHXL-CC26X2R1 and LAUNCHXL-CC1352P-2 as shown below.

    The jumper connections on all three launchpads are connected identically.

    The Device manager screen of the PC when three types of Launchpads are connected.

    The following is a video of the problem occurring when the LP-CC2651P3 was tested in this condition.
    If the target device is disconnected from the LP-CC2651P3, nothing happens.
    However, when the target device is reconnected to the LP-CC2651P3, the USB connection is reestablished.
    This problem occurs very frequently with only LP-CC2651P3.

    Regards.
    YG

  • 0 in reply to YG JANG
    TI__Guru**** 206657 points

    Thank you for clarifying.  I had meant to say that there are no functional differences (i.e. all are XDS110 with EnergyTrace), however your further explanation has raised a distinction which I was not aware of.  How does this USB connection reestablishment affect your end use application? 

    Please double-check the USB cables and try using a self-powered USB hub for the LP-CC2651P3 as it can deliver more power per port.  It would also be good to at least check the mini USB connector on this board to see if it is still reliable and solid.  Is this a brand new LP-CC2651P3 out-of-box or has it been used significantly in the past?  Do you have a second one to test against?

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 10 points

    Thank you for efforts!!

    My PCB is consisted of 10 target devices.
    So, I made the jig that is possible to download the firmware to 10 target device at one time.
    And the jig was made with 10 pieces of LP-CC2651P3.

    In this conditions, when I replace the new PCB to download the firmware,
    I have to wait for usb device to reconnect again.
    Therefore, this problem results in wasted time in mass production.

    I am using a self-powered USB hub with 5V 4A capacity.
    The LP-CC2651P3 used in the jig were purchased about two months ago.

    This problem often occurs even when one LP-CC2651P is directly connected to a PC.
    And LAUNCHXL-CC26X2R1 and LAUNCHXL-CC1352P-2 do not occur this problem.

    Regards,
    YG

  • +1 in reply to YG JANG
    TI__Guru**** 206657 points

    Ultimately the LaunchPad's XDS110s are not designed towards mass production and gang programming.  You do have several options:

    1. Use the LaunchPads which operate as you expect or the TMDSEMU110-U 
    2. Accept the brief delay from the LaunchPad which is not optimal for your needs.
    3. Use a third-party gang programmer such as those offered by Segger

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 10 points

    I will accept your suggestion !! 
    Regards,
    YG