• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 55 subscribers
  • Views 307 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.

CC2652P7: how to modify the openthread.syscfg configuration file to enable Thread and UART in the SysConfig tool？

zhimin he
Prodigy 20 points
Part Number: CC2652P7
Other Parts Discussed in Thread: SYSCONFIG, CC2652R7, CC1352P7

Tool/software:

I have a CC2652P7 on hand and want to know how to modify the openthread.syscfg configuration file to enable Thread and UART in the SysConfig tool. This is my first time using TI's tools, so the more detailed the steps, the better.

  • 0
    TI__Expert 8745 points

    Part Number: CC2652P7

    Tool/software:

    Hi Team,

    I have a CC2652P7 on hand and want to know how to modify the openthread.syscfg configuration file to enable Thread functionality and UART functionality in the SysConfig tool. This is my first time using TI's tools, so the more detailed the steps, the better.

    sdk is simplelink_cc13xx_cc26xx_sdk_7_41_00_17

    Regards,
    Tom Liu

  • 0
    Prodigy 20 points

    sdk is simplelink_cc13xx_cc26xx_sdk_7_41_00_17

  • 0
    TI__Expert 7455 points

    Part Number: CC2652P7

    Tool/software:

    Hi Team

    I have CC2652P7 on hand and would like to know how to modify the openthread.syscfg configuration file to load thread and UART functions in the sysconfig tool? The SDK is SimpleLink_cc13xx_cc26xx_sdk_7_41_00_17. It's my first time using these tools from TI, so the more detailed the steps, the better

  • 0
    TI__Guru**** 217367 points

    Hi zhimin,

    Thread and UART are already enabled in openthread.syscfg.

    https://github.com/TexasInstruments/ot-ti/blob/thread-v1.x-ti-eng/docs/thread-syscfg/getting-started.md 

    Hi Liu, Ao,

    Please check before posting duplicates on the E2E.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 20 points

    Hi Ryan,

    I can't find the CC2652P7 board file in the SDK directory simplelink_cc13xx_cc26xx_sdk_7_41_00_17, only LP_CC2652R7 is available. Can I use LP_CC2652R7 as the board parameter to generate code for CC2652P7? Will the generated code require any modifications?

  • 0 in reply to zhimin he
    TI__Guru**** 217367 points

    You will use the LP_CC1352P7_4 build parameter as the CC2652P7 is binary compatible with the CC1352P7 for 2.4 GHz projects.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 20 points

    However, when I used the parameters for LP_CC1352P7_4 and compiled the Thread firmware for CC2652P7 via openthread.syscfg, a prompt indicating that the firmware is too large appeared when I tried to flash it into the CC2652P7 chip. The specific steps are as follows:

    ./script/build LP_CC1352P7_4
    objcopy -O ihex build/bin/ot-rcp.out build/bin/ot-rcp.hex

    /tmp # ./bbb_cc13xx-sbl /dev/ttyHS0 ot-rcp-2652.hex cc26x2 -e -p -v
    Using Two wrire SBL Interface
    ./bbb_cc13xx-sbl ccDnld-v1.00.00 -- Jun 19 2024 17:25:33

    Device set to: cc26x2
    Opening serial port /dev/ttyHS0
    now tio c_cflag: [000118b7] 80000000
    Open binary file ot-rcp-2652.hex binMode[0]
    Binary file size = 238271
    Connecting:
    Connected
    Erasing:
    [==================================================] 100%
    Downloading:
    [==================================== ] 71%
    address[affa8] not in flash

    Error during download
    Abnormal termination, port close successful

  • 0 in reply to zhimin he
    TI__Guru**** 217367 points

    The CC1352P7 and CC2652P7 share the same number of flash pages and bytes per page.  It is unlikely that something is wrong with the ot-rcp.hex image that you've built if you've used the correct ot-ti build argument and it is likely that you'd encounter the same issue if programming a CC1352P7 using the current programming tool.

    The problem is likely the bbb_cc13xx-sbl executable you are using from the 15.4-Stack Linux Gateway solution which only supports CC26X0 9128 kB) or CC26X2 (352 kB) flash memory configurations.  We can find in <linux_gatway_installation>/example/cc13xx-sbl/app/linux/cc13xxdnld.h that there are only definitions for 32 or 44 flash pages.  You will need to modify and re-build the programming application.

    You could further test and verify this analysis by attempting to program your existing ot-rcp.hex image with Uniflash, which supports the CC2652P7.

    Regards,
    Ryan