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.

TIDA-01624: Confirmation

Genius 9880 points
Part Number: TIDA-01624
Other Parts Discussed in Thread: CC2640R2F, , CC2640

Hi Team,

Customer want to confirm if the test setup using this reference design is correct. Below is the inquiry.

"Can you please let me know if my flash programmer detects the CC2640R2F chip of my custom board by looking into the pictures I have attached? How can I understand if the flash programmer 2 detects the chip?

Also, by looking into the picture of my connection, can you please let me know if it seems okay to you. I have connected the 10 pin adapter of the XDS110 to the 10 pin CC debugger connector. Can you please let me know if this is correct or not? Should I take out the CC debugger connector from the set-up?

"

Regards,

Maynard

  • Hi Maynard,

    Can you show which pins on your debugger are connecting to which pins on the patch? It is difficult to tell from the image alone.

    Also, do you have a CC2640R2 launchpad on hand? I find that it is simpler to use the onboard debugger from the launchpad, and it will allow for shorter connections.

    Best Regards,
    Brandon Fisher

  • Hi Brandon,

    Below is the response of the customer.

    "

    My pin connections of the debugger and jtag of the TIDA-01624 .

    ARM 10-Pin Connector
    VCC (1)    (2) SWDIO
    GND (3)   (4) SWCLC
    GND (5)   (6) SWO
    N/U   (7)   (8) N/U
    GND (9)   (10) Reset

    10-pin JTAG/SW interface
    VCC (1)    (2) SWDIO/ TMS
    GND (3)   (4) SWCLK/ TCLK
    GND (5)   (6) SWO/ TDO
    KEY  (7)   (8) NC/ TDI
    GND (9)   (10) nReset
    detect



    I don't have any CC2640R2 launchpad, as I found on the texas instrument website that standalone debugger XDS110 will work for the CC2640R2F chip.

    Also, I forgot to mention in my previous message that during debugging should I advertise the BLE chip of TIDA-01624 first?

    "

    Regards,

    Maynard

  • Hi Maynard,

    Yes, they should be able to use the standalone debugger, the launchpad for the CC2640R2F just has an XDS110 debugger onboard. I simply find the launchpad jumpers just make the connections more straightforward and accessible. 

    As a note, according to this thread, the CC2640R2F does not support ARM SWD interface. They will have to use cJTAG or JTAG for programming purposes. Based on the current connections only 2-pin cJTAG would be an option (TDI is left N/C). I believe their current connections will work, as long as they configure for 2-pin cJTAG accordingly. 

    Also, I forgot to mention in my previous message that during debugging should I advertise the BLE chip of TIDA-01624 first?

    With the software included with the TIDA-01624 design, the device will not advertise at all until the switch (S1) is pressed after the board is powered on. If you do not hit the switch the patch will just wait in sleep mode. 

    Best Regards,
    Brandon Fisher

  • Hi Brandon, 

    Below is the response of the customer.

    I have checked the link you provided and have some related questions. Can you please take a look into my following questions:

    1) Can you please let me know which two pins of cjtag on TIDA-01624 board should be connected to which two pins of XDS-100 debugger? If we connect only 2 pins, will the other pins remain open? Also, do we have to use any additional hardware (2 pin cjtag) in our current connection, or just connecting 2 pins of the TIDA-01624 jtag with 2 pins of XDS-100 debugger should be fine? If we have to use an additional hardware (please provide a link for purchase), how and where should we add in our current connection?

    2) Is 3 V external power supply okay for the TIDA-01624 board?

    3) Also, during interfacing will flash programmer 2 will detect the chip as TIDA-01624, or it will detect the board as CC2640r2f ? How can I make sure that flash programmer 2 detects the chips of TIDA-01624?

    Regards,

    Maynard

  • Hi Maynard,

    1) Can you please let me know which two pins of cjtag on TIDA-01624 board should be connected to which two pins of XDS-100 debugger? If we connect only 2 pins, will the other pins remain open? Also, do we have to use any additional hardware (2 pin cjtag) in our current connection, or just connecting 2 pins of the TIDA-01624 jtag with 2 pins of XDS-100 debugger should be fine? If we have to use an additional hardware (please provide a link for purchase), how and where should we add in our current connection?

    They should not need to change anything about their hardware with those connections. It should be fine as is. The XDS110 debugger uses the same pins for SWCLK/TCK and for SWDIO/TMS. These are the two pins used in cJTAG, and as they are already connected you should not encounter any issues. 

    2) Is 3 V external power supply okay for the TIDA-01624 board?

    Yes during operation and testing the board was used with a 3.0V Power supply. You may choose to use 3.3V during flashing though, as I believe that is the nominal voltage of the standalone XDS110 debugger. 

    3) Also, during interfacing will flash programmer 2 will detect the chip as TIDA-01624, or it will detect the board as CC2640r2f ? How can I make sure that flash programmer 2 detects the chips of TIDA-01624?

    It will detect the CC2640R2F as the connected device, that is the target device onboard TIDA-01624 that is being flashed. TIDA-01624 is just a reference design number that we use to refer to the whole board design.

    Best Regards,
    Brandon Fisher

  • Hi Brandon,

    Thank you for your support, below is the response of the customer.

    "Hi It's good to know that our connection is okay. However, with our current connection we are getting errors in flash programmer 2 as I previously described (pictures attached). Flash programmer 2 does not automatically detect CC2640 R2F chip. I selected the target as CC2640R2F chips for the XDS-1110 debugger, and when I select the connect option I got those errors. It would be a great help if you could kindly forward the errors to TIDA teams, so that I can know how and what should be changed in the device setting. Also, I wanted to know if I have to change anything in the software settings in flash programmer 2?



    Also, which software do you recommend for programming (CCS/IAR)?"

    Regards,

    Maynard

  • Hi Maynard,

    I'm going to redirect this thread to our team which supports the CC2640R2F, as they will have more familiarity with this kind of programming issue on the device. 

    At a minimum, if they are going to use 2-pin cJTAG they would need to change the settings of Flash programmer 2 (use the wrench icon in the top right corner, location shown below).

    Best Regards,
    Brandon Fisher

  • Hi Brandon,

    Good day. Any update on this regarding the programming issue?

    Who should we need to reach out on this?

    Thank you.

    Regards,

    Maynard

  • Maynard,

    Please apologize for the delay;

    From the screenshots, the error message indicates the selected entry on the tree on the left is not the XDS110 entry but instead the UART.

    The error message gives away this issue, which mentions the serial connection and bootloader:

    "Connecting over serial bootloader failed: No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate."

    To fix this, please select the top entry as indicated in the screenshot below:

    If this does not work, I can see the serial number of your XDS110 is set to 00000000 (where it reads L50000NP on my screenshot) and this may cause some trouble depending on the scenario. If you need some help in setting a serial number, please check the section Finding and updating the serial number of the XDS110 page at:

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

    Regards,

    Rafael

  • Hi Rafael, 

    Apologies for the late response. I just received response from customer that they still having trouble after downloading the link you have provided. Below is the details.

    TIDA_01624_debugging.pdf

    Thank you in advance.

    Regards,

    Maynard

  • Maynard,

    The last step the customer tried may have bricked his XDS110 Debug Probe. I never asked him/her to update the bootloader but only set the serial number, which is not shown in the screenshot.

    At this point the pod is either bricked or the OS is not acknowledging it properly. There is a procedure to check its status and restore a bricked Debug Probe in the section TroubleshootingFlashing the bootloader of the XDS110 Page I sent before. Check the steps there.

    Regarding the prior errors shown in the document, the error in CCS can be found at the Debugging JTAG page below (search for the error number):

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

    Based on the photograph of the system itself, the wiring itself looks very long and very busy between the Debug Probe and the target board, which can cause signal integrity issues. The customer can experiment changing the JTAG TCLK speed to see if the integrity helps. The short clip below can help with this:

    https://youtu.be/mKxaztkCsYw

    In the last pictures, the customer still showed trying to connect using the UART entry.

    Hope this helps,

    Rafael

  • Hi Rafael,

    According to customer, the connection is ok now however, after hitting the debugging option in CCS I am getting a window like in the image below. They want to know what  would be the next step to load the program successfully to TIDA-01624.

    Thank you in advance.

    Regards,

    Maynard

  • Maynard,

    The screenshot shows a normal Debug session; code and debug symbols are loaded, the debugger is stopped at main().

    There shouldn't be any issues from that point and on.

    Regards,

    Rafael