• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 266 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.

CC2340R5: switch ble and thread RCP?

Frank(EP) Liu
Expert 5330 points

Part Number: CC2340R5
Other Parts Discussed in Thread: CC2340R2

Tool/software:

Hi Expert,

My customer's application is AP router.

BLE is only for configuration. So, after first time configuration, the cc2340R5 would change to Thread RCP.

Can CC2340R5 do that?

Any example project they can refer to? Assume that cc2340 would need to power off and start new application code from BLE to thread RCP.

for CC2340R5 thread RCP, can customer use below? or other suggestion?

https://github.com/TexasInstruments/ot-ti/tree/thread-v1.3-ti

BR,

frank

  • 0
    TI__Genius 10350 points

    Hi !

    For Thread RCP, the customer can use the Github project you linked, as it's a repo from the official TI Github account and is up to date (it has been updated 3 months ago).

    For switching from BLE to Thread RCP, this does not sound like something that is supported. However, since you only want to use BLE during the first time configuration, you could still do it by using two firmwares and a bootloader, and try to emulate a OAD update without an upload. The first firmware would have BLE capabilities from our SDK and be the primary image, while the second firmware would have Threads RCP capabilities and be the secondary image.

    The bootloader (for example MCUboot) would boot into the primary image, which would have regular BLE capabilities from our SDK, and once the configuration is done, it would lower its image version to make it lower than the secondary image, and force a reset. Upon waking up from reset, the bootloader would see that the secondary image has a higher version than the secondary image, and boot into this secondary image. In case that the user needs to go back to the configuration image, the versions could be changed by the secondary firmware and force reset just like how the primary firmware does it.

    This behavior would emulate how an OAD update changes from one firmware to another, but instead of uploading the other image, it would already be at a fixed address in flash.

    You can read more about MCUboot here and about how we do OAD here.

    Kind regards,
    Maxence

  • 0 in reply to Lea
    TI__Expert 5330 points

    Maxence,

    from the link, only CC2340R5 supports RCP. CC2340R2 cannot support Thread RCP, right?

    BR,

    frank

  • 0 in reply to Frank(EP) Liu
    TI__Genius 10350 points

    Hi !

    If it is not listed, then I would assume that the device is not supported. The reason for this is likely to be the smaller flash and SRAM size. When looking at devices supported by OpenThread, they usually have around 512kB of flash, while the CC2340R2 has only 256kB. The memory requirements given by other manufacturers mention at least 350kB of flash, which the CC2340R52 does not have.

    Kind regards,
    Maxence