• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 124 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.

CC1352P: uniflash does no longer working

luigi Desiderato
Prodigy 110 points
Part Number: CC1352P
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hi all,

I' m trying to download the coprocessor project to a Simplelink board but Uniflash does not work: it stops immediately and outputs the following diagnostic:
spawn ./DSLite ENOENT

What have I to do? I never faced with this issue in the past: the PC is the same, I installed the last release of Simplelink library: simplelink_cc13xx_cc26xx_sdk_8_30_01_01

Can someone help me?

Attached the screenshot of what' s happening

Thanks

Luigi

  • 0
    TI__Expert 7645 points

    Hi Luigi,

    this error indicates that the flash executable which is called by the GUI is not found.

    Which version of Uniflash are you currently using?

    Did you already try to reinstall it or to install another version?

    Kind regards,
    Theo

  • 0 in reply to Theo Lange
    Prodigy 110 points

    Hi Theo,
    the installed version is this:

    I' ll try to uninstall and reinstall again and let you know

    Sincerely

    Luigi

  • 0 in reply to luigi Desiderato
    Prodigy 110 points

    Hi Theo,

    as suggested, I completely removed Uniflash and reinstalled it from scratch, installation completed with no error, but once launched Uniflash, a new issue arised: the Launchpad (let me call it A) is no longer detected. If I change the Launchpad (call this second one as B), it is normally available as usual. What have I to do?
    Please note:
    - to this test, I attached only one Launchpad at a time and hence prior to connect Launchpad B, Launchpad A is removed from the USB (and the typical sound from Windows is heared either when unplugging and plugging the Launchpads)
    - the green led on the Launchpad A is on
    - if I try to use the Launchpad A with the CCS debugger, the emulator does no longer respond and the following diagnostic appears:

    - so, it seems the Launchpad A is no longer functional but probably it is possibile to recover it with a suitable tool: can you tell me how can I do that?

    - instead, if I try to use the Launchpad B, no issue

    Obviously I need both Launchpads working...
    Please help me

    Sincerely Luigi

  • 0 in reply to luigi Desiderato
    TI__Expert 7645 points

    Hi Luigi,

    thank you for the update.

    The issue seems to be that the XDS110 firmware is in a bad state.

    Please try to resolve the issue as indicated by the error message.

    Connect the LaunchPad with the error and start the xdsdfu utility in powershell from your CCS installation directory/ccs_base/common/uscif/xds110/xdsdfu.exe

    A User's Guide for the utility can be found in the same directory as pdf. 

    Please follow the instructions to update the XDS110 firmware and verify that the update was successfull.

    Afterwards, everything should work fine.

    Kind regards,
    Theo

  • 0 in reply to luigi Desiderato
    Prodigy 110 points

    Hi Theo,

    I read the documentation and provide an attempt to "Recover a Bricked XDS110 without JTAG", strictly following what is said. Then I downloaded the firmware available for the XDS110 (maybe it is an old version, but this is not a concern to me since Uniflash should update it automatically). Here following the screenshot of what I did:

    The Launchpad then is recognized by Windows, its green led lits, but Uniflash still does not recognize it: what have I to do now? I don' t think the Launchpad is failed at all.

    Sincerely
    Luigi

  • 0 in reply to luigi Desiderato
    TI__Expert 7645 points

    Hi Luigi, 

    could you verify with xdsdfu -m that the new version of the firmware was installed on the XDS110?

    Did you disconnect and reconnect the LaunchPad from the PC before starting Uniflash again?

    If yes please send me a screenshot of how the XDS110 is listed in the windows device manager -> COM ports.

    Kind regards,
    Theo

  • 0 in reply to Theo Lange
    Prodigy 110 points

    Hi Theo,

    now all is working again as expected after this sequence:
    - disinstalled uniflash
    - completely removed the installation folder where at least two empty files still survived after disinstallation (why? it should not happen...)
    - used xdsdfu to restart the Launchpad from scratch, shorting the TDO pin to gnd as mentioned in the documentation about "Recover a Bricked XDS110 without JTAG"
    - reinstalled uniflash leaving connected the Lauchpad to the USB port (that is powered)
    - used xdsdfu to download the firmware version available in the just installed uniflash with -r option which means the xds is rebooted aftermath
    At this point the Launchpad comes visible to both CCS and uniflash (with Windows sounding behavior)
    Then, running any function on Uniflash, it is required to update the xds firmware and I did it (it proceeds autonomously)
    So, finally, the Launchpad is functional as it once was.
    Problem finally solved, but I really don' t know what was the cause of this issue. Anyway, now I know how to do in the case this might happen again.
    Many thanks,

    Sincerely,
    Luigi

  • 0 in reply to luigi Desiderato
    TI__Expert 7645 points

    Hi Luigi,

    I'm happy to hear that everything works fine again!

    Great that you could follow the additional instructions "Recover a Bricked XDS110 without JTAG".

    I'm not fully sure in which state your XDS was since it was still showing up on Windows. One option how this can happen is when a firmware update is interrupted by disconnecting the XDS110. Maybe uniflash or CCS tried an update the last time that you connected the board and encountered some issue.

    Kind regards,
    Theo