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.

CC1312R: dev.ti.com and missing startup file questions

Part Number: CC1312R

Team, 

My customer is looking for guidance on:

1) Getting dev.ti.com to recognize the connected CC1312R1 Launchpad from any OS

2) Getting a project complied due to a missing startup_ccs.c file (missing ResetISR symbol).

They downloaded simplelink_cc13x2_sdk_2_20_00_71, but I cannot get it imported into dev.ti.com

Thanks

Viktorija

  • Viktorija,

    1) Please see the wiki on which version of browsers work and which ones do not work.

    2) There should not be any need to download any SDK to the online tools, all SDK's are preloaded.

    and then into CCS cloud.

    after some time compiling and doing other stuff it downloaded and ran on my board.

    I am using Chrome on a new installation of Windows 10.

    Regards,

    /TA

  • I'm using Windows 7 and Chrome 69.0.3497.100. I've installed the latest TICloudAgent.

    I was indeed missing the Cloud button in Tirex, so that did make getting things into the CCS Cloud work to build a first project. Now, I'm stuck trying to get it to run...

    I haven't found any firmware updates or methods for installing them.

    In the mean time, I've been trying to do the web-based installer that has been running continuously for over 3 days.

  • Jason,

    Please try to install SmartRF Studio, on a Windows machine it is the quickest way to make sure you boards are working and have the most up to date firmware installed (SmartRF studio does not download on the fly, so you need to make sure you install the latest version).

    On the CCS side, I have seen the webinstaller fail before. I recommend downloading the offline installer and rebooting your PC before starting to install, then also disable the virus detection during the installation process. The entire process is slow, but should not take more than 10-20 min.

    Regards,
    /TA
  • Using the offline installer for CCS got it installed, eventually. It took a LOT more than 20 minutes.

    SmartRF Studio installed much faster.

    Neither application are detecting the board.
  • What do you mean “Neither application are detecting the board.”?
  • YiKai Chen said:
    What do you mean “Neither application are detecting the board.”?

    For CCS:

    Cortex_M4_0: GEL Output: Memory Map Initialization Complete.
    Cortex_M4_0: Failed Board Reset: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. The firmware and serial number may be updated using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of your installation. View the ReadMe.txt file there for instructions. (Emulation package 8.0.803.0)
    IcePick_C: Error connecting to the target: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. The firmware and serial number may be updated using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of your installation. View the ReadMe.txt file there for instructions. (Emulation package 8.0.803.0)

    For SmartRF:

    No Connected Devices

    :'-(

  • Which CCS version do you use?
  • The issue is related to the USB host port on my PC. The failing port is a USB 3 (Superspeed, blue connector inside) and the working port is USB 2 (High-speed, black connector inside). I'd tried several different cables and the cables didn't mater.

    What made this difficult to discover was that Device Manager repeatedly showed the XDS110 device enumerate and disappear, yet even 'xdsdfu -e' could never see any XDS110 device. At least looking at that utility convinced me to look more and more at the hardware level until I decided to try a different port.