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: Does the CC2340R52E0RKPR support the simultaneous use of Zigbee and Bluetooth?

Part Number: CC2340R5

I am using the CC2340R52E0RKPR chip. I want to create a device that can use both Zigbee and Bluetooth. Can I use Zigbee for transmitting small data and switch to Bluetooth for transmitting large data? If it's possible, could you provide some examples? If it's supported, I would appreciate it if you could offer me some references for reference. Thank you.

  • Hello Bin Mu, 

    I believe our DMM solution is still being worked on and we do not have external examples, however it is possible to instead utilize MCUboot (overwrite or XIP) to switch between two application images where one would be BLE and one would be Zigbee, but there would be considerable delay using this technique. 

    Thanks,
    Alex F

  • I attempted to use the content in the example at dev.ti.com/.../node to switch the image. However, I could only switch from the first image to the second image. After reaching the second image, no matter if I pressed the button or restarted, I was still in the second image. Even when I first switched to image two, pressing the button again would lead to a strange phenomenon where the red light would flash rapidly. According to my understanding, this example is supposed to be able to switch images, and it should be able to switch back and forth between the two images, rather than just being able to switch once.

  • Hello Bin Mu,

    After reaching the second image, no matter if I pressed the button or restarted, I was still in the second image

    We may need to update the PMCTL value in the button callback, could you enter debugging and place a breakpoint on the PMCTL register set line and then see what the actual PMCTL register reflects? 

    red light would flash rapidly

    This is the MCUboot fail routine, there are two cases I can think of, first is if we did not comment out MCUBOOT_DIRECT_XIP_REVERT in the loader.c file, and the second case is if we did not remove all of the code in the button callback in the application image (as it invalidates the image header and would case an error like the red light flashing rapidly) 

    Thanks,
    Alex F

  • I've figured out the reason. Thank you for your help.