• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 467 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.

CC1314R10: CC1314R10 Custom Board Collector Example Not Running in Standalone Mode

Arun Kumar4
Prodigy 60 points
Part Number: CC1314R10
Other Parts Discussed in Thread: LP-XDS110ET

Tool/software:

Hi,

We are working with a custom PCB based on the CC1314R10 IC and have followed the same circuit as provided in the TI evaluation kit.

We are facing an issue when flashing programs onto the custom board:

  • We flashed the Collector example from the simplelink_cc13xx_cc26xx_sdk_7_41_00_17 SDK.

  • The program works correctly when the board is connected to the LP-XDS110ET debugger.

  • However, in standalone mode (without debugger connection), the program does not run.

To verify further:

  • We also flashed the basic UART example, which runs correctly in standalone mode.

  • We have tested this on two identical boards, and both exhibit the same behavior.

  • Additionally, we have a similar custom board from a different project, where both the Collector and UART examples work fine in standalone mode.

We would appreciate your assistance in understanding and resolving this issue.

Our specific queries:

  1. Why does the Collector example fail to run in standalone mode, while the UART example works fine?

  2. What additional configuration or hardware dependencies might the Collector example have that could prevent it from running independently?

Looking forward to your guidance.

Regards,
Arun

  • 0
    TI__Guru* 82601 points

    Hi Arun,

    The Collector example expects to get commands over the UART line to start the network, open the network etc.

    If you want it to do this without UART commands, you can add the following to the compiler predefines: AUTO_START

    Cheers,

    Marie H

  • 0 in reply to Marie H
    Prodigy 60 points

    Thank you for your response to our query. 

    However, our situation is slightly different. When we run the "collector" example on our custom CC1314R10 board, the CUI is visible only when the debugger is connected. It does not appear in standalone mode. 

    Additionally, we integrated a second UART interface into the collector example to output debug messages and verify that the program is running. Similar to the CUI, these debug prints are only visible when the debugger is connected. In standalone mode (i.e., without the debugger), neither the CUI nor the debug messages are not displayed.

     To isolate the issue, we imported a separate UART example using FreeRTOS and added debug prints within a task that runs every one second. This example functions correctly in both debugger mode and standalone mode. 

    Our specific question is: 

    1. Why does the collector example fail to run in standalone mode, while the UART example runs correctly without the debugger? 

    We appreciate your support and look forward to your guidance.

  • 0 in reply to Arun Kumar4
    TI__Guru* 82601 points

    Hi Arun,

    I am not able to reproduce what you are seeing on a LaunchPad.

    (One note that I don't think is related, but wanted to mention: We have a HW issue on the ITM on CC1314, which means the ITM will only start if a debugger is connected during startup. However this does not affect the UART.)

    Since you have a custom board, can you let me know how you are connecting the uart to the laptop? Are you using an XDS110 with JTAG line?

    Can you verify whether the rest of the application is running correctly when you don't have a debugger attached? E.g. blink an LED after completing initialization?

    Cheers,

    Marie H

  • 0 in reply to Marie H
    Prodigy 60 points

    Hi Marie,

    Thank you for your response to our query.

    To clarify our issue, We have add some points below.

    We are encountering a problem when flashing programs onto our custom board (CUS_BOARD_1). We have flashed the Collector example code from the simplelink_cc13xx_cc26xx_sdk_7_41_00_17 SDK. The program runs as expected when the board is connected to the LP-XDS110ET debugger. However, in standalone mode (without the debugger connected), the program does not execute.

    To investigate further, we flashed the same Collector example onto another custom board (CUS_BOARD_2). In this case, the program works correctly both with and without the debugger connected.

    (Note: As an additional test, we flashed the UART example code onto both custom boards (CUS_BOARD_1 and CUS_BOARD_2). With the UART example, both boards function correctly in both debugger-connected and standalone modes.)

    The key difference between the two boards lies in the hardware configuration: the SPI pins on CUS_BOARD_1 are connected directly to another MCU's SPI pins, whereas CUS_BOARD_2 is not connected to any external MCU.

    In response to your earlier questions:

    We have configured the UART pins and connected them to a TTL converter, which is interfaced with a laptop. No debugger is connected to the custom CC1314R10 board during this test.

    Our custom board does not have an onboard LED. However, we configured a GPIO pin as an output and programmed it to toggle every one second. We did not observe any voltage change on that pin using a multimeter.

    We appreciate your continued support and would be grateful for your guidance in resolving this issue.

    Regards,
    Arun

  • 0 in reply to Arun Kumar4
    TI__Mastermind 33810 points

    Hi,

    Please provide your schematic of your custom boards (CUS_BOARD_1 and CUS_BOARD_2) so we can check this as a first step.

  • 0 in reply to RGW
    Prodigy 60 points

    Hi, 

    Please find the attached schematics of both boards.

    TI_CC1314_SCH_CUS2_Working.pdfTI_CC1314_SCH_CUS1.pdf

  • 0 in reply to Arun Kumar4
    Prodigy 60 points

    Hi RGW, 

    This is a kind reminder to request clarification regarding the discussion mentioned above. Please update us with the current progress.

    Regards,
    Arun

  • 0 in reply to Arun Kumar4
    TI__Mastermind 33810 points

    Hi,

    Apologies for a late reply.

    Can you change R43 to 100k ?

    10 k to VDDS should not be used on the nRESET line.

  • 0 in reply to RGW
    Prodigy 60 points

    Hi,

    Changed but result is same.

    We observe issue only whenever we implement the RF programming (collector example code) with out debugger (standalone mode)

    We can able to run RF program with debugger.

    Regards,

    Arun