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.

CC1310: Debug Issue

Part Number: CC1310
Other Parts Discussed in Thread: CC1350, LAUNCHXL-CC1312R1

Hello,

I have custom board includes CC1310. I wrote a code which takes code from uart, send it via RF and then receive it from RF and receive from RF and sending this data to uart. I am sending datas from terminal emulator such as teraterm, putty etc. Program is working. I have tranceiver code, it waits as a receiver until I send data from terminal.

For example I have 2 same custom boards. I connect them to different terminals. When I send any data from 1st terminal, I can see this data on the other terminal. So it is working. 

1st Board
Message -> Terminal
Terminal -> Uart
Uart -> RF Tranceiver(Transmitter)

2st Board
RF Tranceiver(Receiver) -> Uart
Uart -> Terminal
Terminal shows the message.

Problem is debugging process. I have two Launchpads one is LAUNCHXL-CC1312R1 Rev D and the another is CC1350 Launchpad Rev 1.3 . I am trying to debug one of my custom board. While not debugging custom board can receive data from RF and send it to uart, but if I connect one of eval kit to my custom board, custom board can't receive RF message. How can I provide my custom board to take RF messages while debugger is connected ?

Debug session starts correctly. It is working. I have tasks and I see tasks when I pause debug session. I am using 2-wire debug. Eval kit is connected to my custom board with TMS TCK and GND pins.

  • How do you know that you are not receiving anything when you are debugging? Are you not getting your RF callback indicating that a packet is received, or is just not anything written to the UART?

    It is important to have in mind that when stepping through code, and setting breakpoints when using the radio, you are only halting the CM3 while the RF Code is still running. Because of this it is easy to get in an overflow situation  when debugging, as you are not processing the incoming packets from the radio, and hence it runs our of space for storing incoming packets.

    To be able to help you further it would be useful to see your code, and also get more information regarding what you observe when debugging (status of commands etc.)

    If you take the rfPacketRX and rfPacketTX example and port it to your custom HW, will you not hit a breakpoint in the callback on the RX side (indicating that a packet has been received)?

    Siri

  • I have two leds on my custom board for rx and tx processes. when I send a data from custom board to receiver board( connected to debugger ) I am expecting led to toggle. and also I have breakpoints in software. one is  on the "if (e & RF_EventRxEntryDone)" line. it stops here but does not enter this condition.

  • Have you checked the custom board according to the "board Bringup section in www.ti.com/.../swra640e.pdf

  • Yes I have checked "Board Bringup Section". But there was a problem I can't solve. I could not simulate 2 custom boards at the same time with Smart RF Studio. That's why I tested one by one.

  • Please provide status of the different commands, code example and also the results of testing the rfPacketRX and rfPacketTX on your HW with the debugger connected.

    BR

    Siri

  • You can open 2 boards with SmartRF Studio