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.

LAUNCHXL-F280025C: LAUNCHXL-F280025C XDS connection issue

Part Number: LAUNCHXL-F280025C
Other Parts Discussed in Thread: C2000WARE

TI Friends & Family,

One of our customer is having a connection issue with their LAUNCHXL-F280025C.

On their HP ZBook running Windows 10 Enterprise, they get the 'standard' xds connection error:

Their system works for a TI F28379D Launchpad but not the F280025C LP.  They even tried 2 F280025C LPs.

They have updated the latest _emupack driver package and the 2 ports show properly under Windows Device Manager. 

Interesting to say the least...

They are going to try it on another machine, perhaps at a home PC to test as well.

We too have not seen this issue - I am even running an HP Zbook Win 10 (Pro) OS.

Any thoughts/ known issues / etc with the LAUNCHXL-F280025C specifically?

I assume not, but just wanted to send out an APB to ask.

TY,
CY

  • Hi Chris,

    Can you check if customer is using XDS110 emulator in 2-pin advance mode in target configuration? 

    Refer to Launchxl-F280025C user's guide:

    F28002x Series LaunchPadTm Development Kit

  • Hi Santosh, 

    I assume so (following User Guide) but perhaps not.  I will double-check.  Thank you.

    -Chris

  • Chris,

    The error message is picture, it says about XDS100, so I am assuming he is using xds100v2 in his target configuration like F28379D.

  • Santosh,

    Yes, I believe that is correct.  And per the LP User Guide, XDS110 is shown.  So they should first make sure their target configuration is also setup for XDS110, correct?  (Windows Ports Debug and Data showed XDS100 I believe).

    Does that make sense?

    TY,
    Chris

  • Santosh,

    Once customer is able to try this, I think you are correct.

    When the F28379D worked, it was with xds100.  (xds100v2)

    When the F280025 did not work, it was with xds100.  (xds100v2 assumed)

    If they check target configuration to confirm xds110 and 2-pin advanced mode that might solve this after all.

    Let me know if you agree?

    TY,
    Chris

  • Chris,

    If customer is running example from C2000Ware DriverLib, it should have correct target configuration in the project. He just needs to make sure LP ccxml is Active.

    If he is working on his own custom project, then he needs to make sure in his target configuration he is using XDS110 2-pin Advance mode as per User's Guide.

  • Thanks Santosh,

    I believe the root of the problem is that they are not running an example from C2000Ware DriverLib, rather their own project.  So, sorry for the somewhat trivial question on this forum but this should be helpful for others that might overlook the xds target configuration setting, which I believe is the main issue in this case.  I'll confirm with the customer and if it is something else, will reply to this thread.

    Thanks again,

    Chris

  • Okay, Chris!!

    Let us know if it resolves customer issue.

  • Not quite, but I think it may be something on their end (trying a different machine later).  Latest status from customer:

    Checked and re-configured to “XDS110 emulator in 2-pin advance mode in the Target configuration”, for the original “fsi_ex6_spi_master_tx” project, but didn’t work either...

    Then, started/switched to the alternative “launcxl_ex1_f280025c_demo” project as instructed , progressing … ; but still got following Error: same as before

    Per Error-260 message and the “XDS110SupportReadMe” doc, do I need to use “xdsdfu” to perform firmware fix/update for the on-board XDS110 ??

    My thoughts:  Curious to hear how a different machine works out, if same behavior.  Also suggesting the xdsdfu update not required at this time.  Lastly, asking if they could follow steps starting at Section 2.2 of 280025C LP User Guide exactly as directed and advise.

    -Chris

  • Chris,

    Can you ask customer to go to Target Configuration, open the target configuration and run 'Test Connection' and send the log file?

  • Santosh,

    Absolutely, I will ask.  Good idea.  Thanks again.

    -Chris

  • LP-F280025C CCS Error & Log Message.docx

    Santosh, log attached (for home PC) that generated the same Error (surprisingly).

    Work PC is an HP Zbook running Win 10 Enterprise.

    Home PC is a Dell Inspiron running Win 10 Home.

    I'm not extracting much more than the original error which suggests an xds comms issue.

    Let me know your thoughts, please, as this is strange - both work and home machines generating essentially same error.

    Thanks,
    Chris

  • Chris,

    Can you check if it is enumerating correctly in Windows Device Manager?

    Can we ask customer to update xds110 firmware? The readme file and the firmware is located at:

    C:/ti/ccs1040/ccs/ccs_base/common/uscif/xds110

  • Absolutely, stay tuned.  They are west coast time zone so bear with me.  ;-)

    -Chris

  • Santosh,

    OK here goes:

    Yes, it’s enumerated (correctly, we believe), like this (shown below):

     

     

    Performed “firmware update”, with commands:

     

    • xdsdfu.exe -m
    • xdsdfu.exe -f firmware_3.0.0.16.bin -r

     

    log file attached.

    charlie xdsdfu log.txt
    C:\ti\ccs1040\ccs\ccs_base\common\uscif\xds110>dir
     Volume in drive C is OSDisk
     Volume Serial Number is 4C55-7B2E
    
     Directory of C:\ti\ccs1040\ccs\ccs_base\common\uscif\xds110
    
    09/10/2021  02:40 PM    <DIR>          .
    09/10/2021  02:40 PM    <DIR>          ..
    06/25/2021  09:55 AM            73,152 boot_loader.axf
    06/25/2021  09:55 AM             6,182 boot_loader.bin
    06/25/2021  09:55 AM             3,227 eZ_FetDcdcController.txt
    06/25/2021  09:55 AM           254,968 firmware_3.0.0.16.bin
    06/25/2021  09:55 AM           141,824 xds110reset.exe
    06/25/2021  09:55 AM           176,023 XDS110SupportReadMe.pdf
    06/25/2021  09:55 AM           177,152 xdsdfu.exe
                   7 File(s)        832,528 bytes
                   2 Dir(s)  47,017,746,432 bytes free
    
    C:\ti\ccs1040\ccs\ccs_base\common\uscif\xds110>xdsdfu.exe -m
    
    USB Device Firmware Upgrade Utility
    Copyright (c) 2008-2019 Texas Instruments Incorporated.  All rights reserved.
    
    Scanning USB buses for supported XDS110 devices...
    
    
    <<<< Device 0 >>>>
    
    VID: 0x0451    PID: 0xbef3
    Device Name:   XDS110 Embed with CMSIS-DAP
    Version:       3.0.0.13
    Manufacturer:  Texas Instruments
    Serial Num:    CL251053
    Mode:          Runtime
    Configuration: Standard
    
    Switching device into DFU mode.
    
    C:\ti\ccs1040\ccs\ccs_base\common\uscif\xds110>xdsdfu.exe -f firmware_3.0.0.16.bin -r
    
    USB Device Firmware Upgrade Utility
    Copyright (c) 2008-2019 Texas Instruments Incorporated.  All rights reserved.
    
    Scanning USB buses for supported XDS110 devices...
    
    Downloading firmware_3.0.0.16.bin to device...
    
    C:\ti\ccs1040\ccs\ccs_base\common\uscif\xds110>
    

     

    Unplug/re-plug LP-F280025C, got same “Device Manager” report:

     

     

    Re-launch CCS v10.4.0; imported a new “led_ex1_blinky” project – ‘Build’ fine but not ‘Flash’; got same Error message:

     

     

    Tough sledding, but the thing I notice Santosh is that even though it enumerates properly (we believe) with 2 Ports as xds110 and the screenshots both show xds110, THE ERROR MESSAGE SHOWS XDS100.  They've updated the xdsdfu but any comments welcomed?

    TY,
    Chris

  • Tough sledding, but the thing I notice Santosh is that even though it enumerates properly (we believe) with 2 Ports as xds110 and the screenshots both show xds110, THE ERROR MESSAGE SHOWS XDS100.

    After importing the example, in the CCS project properties under General -> Connection try changing from "Texas instruments XDS100v2 USB Debug Probe" to "Texas Instruments XDS110 USB Debug Probe":

  • Yes, exactly, that might do the trick Chester.  Stay tuned.  Should know momentarily.

    -Chris

  • It worked.  Sweet.  Only comment from customer is they wish this was more clearly shown in the LP manual, or that TI could consider a change to make it as a default setting that comes with all imported LP-F280025C sample projects.  But, that's for then,  For now, we're cooking with gas!

    Thanks guys!

    -Chris