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-CC2640R2: CC2640R2 connecting to TIDA-01580

Part Number: LAUNCHXL-CC2640R2
Other Parts Discussed in Thread: TIDA-01580, , CC2640R2F

I have been trying to connect the following setup

Image preview

1. Plug in the LAUNCHXL-CC2640R2 board on the USB port of the PC. Then connect TIDA-01580 to LAUNCHXL-CC2640R2

2. Insert one CR3032 battery into the BT1 connector on the TIDA-01580 board, and power it on by using the S2 switch (ensure J8 is shorted on the TIDA-01580 board).

3. Open CCS as administrator (Right click on the CCS icon and run as administrator).

4. Click on the Project option in the main toolbar and then click Import CCS projects.

5. Browse to select the installed firmware (Default: C:\Program Files (x86)\Texas Instruments\TIDA-01580\TIDA-01580_firmware) and import all projects. Click the OK button.

6. Click View, Project Explorer and select TIDA-01580_firmware_tx.

7. Click on the Run and Debug buttons. This action programs the board with the selected project file.

8. Disconnect the TIDA-01580 board from the LAUNCHXL-CC2640R2 device.

Step 7 is taking hours!

Do I need this probe to debug?

Software:


CCS 7.3.0.00019

SimpleLink_CC2640R2_SDK 1.40.00.45

Please advise.

Ben

  • Ben,

    I don't know why step 7 is taking too long - this can take anywhere from 20, 30 seconds to a few minutes depending if the project is up-to-date or not. 

    However, step 7 comprises many steps that may be influencing the delay. To break down Step 7 so you can isolate the problem, I would do the following:

    - Rebuild the project by selecting the project, then right-clicking and selecting Rebuild Project. Take not of how long it takes.
       - The option Rebuild Project removes all generated files and builds the project as if it was just imported to the workspace. This takes longer as all source files are re-built, thus it is not necessary during development as t takes longer to complete (a simple Build Project will only re-build the files that were modified).

    - After the project build is complete, proceed to manually launch a debug session. Section 7.3.2 of the CCS User's Guide contains tips on how to do it.

    https://software-dl.ti.com/ccs/esd/documents/users_guide/index.html

    At that point you can have a good idea where is the bottleneck of your system and proceed to the troubleshooting of the problem.

    For Build issues, the most common problems are excessive activity in the system (another process accessing the hard drives or taking excessive CPU time, for example) or network delays (in case the code is version controlled and the repository is remote).

    Otherwise, I would check the troubleshooting section of the Debugging JTAG page below:

    https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html

    Hope this helps,

    Rafael

  • Do I need the XDS110 JTAG Debug Probe? It's nowhere in the TIDA-01580 User Guide. 

    www.digikey.com/.../85395

  • Ben Campion said:
    1. Plug in the LAUNCHXL-CC2640R2 board on the USB port of the PC. Then connect TIDA-01580 to LAUNCHXL-CC2640R2

    You want to use the CC2640R2F Launchpad as debugger to TIDA-01580? The relevant connections are JTAG_TMS, JTAG_TCK, nRESET, GND. You also need to make sure the CC2640R2F Launchpad is setup as debugger.

    Ben Campion said:
    CCS 7.3.0.00019

    Use the latest CCS version, 

    Ben Campion said:
    SimpleLink_CC2640R2_SDK 1.40.00.45

    This is very old SDK version. Do you use this because the firmware for TIDA-01580 uses SDKv1.40?

    -kel

  • Ben,

    Did the suggestions helped you program the device on the board?

    Ben Campion said:

    Do I need the XDS110 JTAG Debug Probe? It's nowhere in the TIDA-01580 User Guide. 

    Well, you certainly need some sort of Debug Probe to program the device.

    As Markel suggested, a regular Launchpad development kit can act as a debug probe, provided you remove the row of jumpers to isolate the bottom part that contains the device and connect wires from the top row of jumper pins to the target board. Be careful to use short connections to reduce noise and attenuation at the data transfer.

    Hope this helps,

    Rafael

  • I was able to debug and program ble5_project_zero_cc2640r2lp_app, ble5_simple_central_cc2640r2lp_app, and ble5_simple_peripheral_cc2640r2lp_app without the XDS110 JTAG Debug Probe. I have the XDS110 JTAG Debug Probe software package however. So can you explain why these projects could be programmed onto the launchpad successfully but I can't program TIDA-01580_firmware_tx?

  • Ben,

    Are you trying to program the TIDA-01580_firmware_tx on the launchpad or to your own board?

    If the board, surely there is something going wrong with the communications between the XDS110 and the CC2640R2F device on your board. I would closely follow the tips on the Troubleshooting section of the page I sent in my previous post, especially the hardware checklist.

    Also, you can try to reduce the TCLK speed when using CCS. The process of experimenting with the TCLK speed is also linked from the page above and reproduced below:

    https://youtu.be/mKxaztkCsYw

    If you are using 2-pin cJTAG, you can switch between OSCAN1 and OSCAN2. If you are using 4-pin JTAG, you can set the Frequency directly.

    cJTAG:

    JTAG:

    Hope this helps,

    Rafael

  • Hi Ben,

    Not sure what is going on with step 7, but have you build the CCS project properly also have generated hex file. If you have generated hex file, can you try programming the TIDA-01580 using SmartRF Flash Programmer 2. If your TIDA-01580 board is not detected by SmartRF Flash Programmer 2 then you have some problem with JTAG connection.

    -kel