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.

CCS/LAUNCHXL-CC1352R1: SysCfg does not totally remove the display when the display is removed

Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: CC1352R, SYSCONFIG, BOOSTXL-SHARP128

Tool/software: Code Composer Studio

Hello

First of all, I want to say how much I am enjoying life since I transitioned from my previous preferred embedded hardware vendor to TI. Your support is excellent, as is your training and documentation. And your prices are great too. As I said, life is good!

I recently started learning about proprietary radio protocols using the CC1352R1 Launchpad. And I am also learning about syscfg. I have discovered what might be a bug, or more likely, I need a bit more training on how to use syscfg.

Here are the steps to duplicate my problem.

1. Import the following project into CCS: SimpleLink CC13x2 26x2 SDK - 3.40.00.2 / Examples / Development Tools / CC1352R LaunchPad / TI Drivers / rxPacketErrorRate / TI_RTOS / CCS Compiler / rfPacketErrorRate

2. Open syscfg and note that it uses two displays - a UART display and a Sharp display. Remove them both. (I am going to use another UART based display with a totally different protocol.) Note that on the peripheral list the following items are not longer shown to be in use: display, UART and a few other items. 

3. I now need to add a UART back. I would like to use pins DIO22 and DIO22 (pins 5 and 6 on the header). Click on the + symbol next to UART. Now note that a default UART is created with no hardware, Send and Receive, using pins DIO16/32 and DIO11/18. Now attempt to change the pins to DIO22/5 and DIO24/6. SysCfg shows those pins are still tied to the Sharp display even though the Sharp display is no longer in the project.

I have also observed this does not occur on the uartech project for this processor board. That project never included a display and syscfg happily lets me use those specific pins without warning me they are used by the display.

Is this a bug or is there something I am missing?

Clark

  • Hi Clark,

    Thanks for reporting the issue. I can reproduce the issue also. I am following up with the SysConfig experts to get more details. I'll pass on any updates I get.

    Thanks

    ki

  • Hi Clark,

    Our SysConfig expert has analyzed the issue and determined that this expected behavior. The issue is that the example is pulling in a BoosterPack and the warning is indicating that the pin is wired to the :CD pf the BoosterPack. There is no issue with the uart eacho example because it does not rely on a BoosterPack.

    To workaround the issue, use one of the below options:

    1) Remove the displays, save the changes, and then opening the .syscfg file in a text editor and remove the following line from the top of the script:

    const BOOSTXL_SHARP128 = scripting.addHardware("/ti/boards/boosterpacks/BOOSTXL-SHARP128")

    2) OR simply ignore the warning if the BoosterPack is not being used

    Thank you for raising this issue with us. We are looking to make improvements with the UI so that this does not cause confusion in the future.

    Thansk

    ki