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.

CC1350: Using 2.4Ghz proprietary mode

Part Number: CC1350
Other Parts Discussed in Thread: CC2650

Hello,

this is probably going to be a bit of a ramble because there's lots of information coming from lots of places! Essentially, we need to use the 2.4Ghz radio on the CC1350 in proprietary mode for a particular application. We have used the CC2650 in 2.4Ghz proprietary mode but support for that seems to have been withdrawn from SmartRF Studio, although the examples are still available.

There have been a few other forum posts about this but none of the answers have been satisfactory - there are significant differences between the radios that are not addressed in the answers or documented in the Technical Reference Manual. Looking at the differences between the files generated by SmartRF Studio for Bluetooth mode for the 2 chips it's not obvious what needs to be done.

Ideally there would be a working smartrf_settings file for the CC1350 that you could let us have, even if the 2.4 Ghz mode is not publicly documented (although appears several times in rf_cmd_prop.h) If this isn't possible, will 2.4Ghz proprietary be officially supported by the CC1352? This would also enable us to develop the concept further.


many thanks,

James

  • Hello James,

    We are not supporting any PHY other than BLE in 2.4GHz band on CC1350.

    For 2.4GHz operation, it is recommended to use CC2640R2 device which is currently supported in SDK and smartrf studio.

    2.4GHz operation will also be supported on CC1352 but the exact details are being worked out.

    Can you please provide more details on the exact configuration that you are looking for in 2.4GHz band (data rate, configurability, link budget etc) and we can suggest the best option going forward.

    Regards,

  • We are also looking for a single solution which can support SubGhz, IEEE802.15.4 in 2.4Ghz and proprietary 2.4GHz mode.

    Unlike the CC2652, it is not clearly mentioned in the data sheet whether CC1352 is supporting proprietary 2.4GHz mode or not. We want

    2Mbps 4-GFSK in 2.4GHz with CC1352. Is it possible?

  • Thanks for the fast reply! We've managed to get the 2.4Ghz radio to work on the CC1350 and communicate with a CC2650. However, just looking for a few pointers on how to get good performance. We don't need to high data rates - 50kbps is enough, as we'll only be sending a few bytes at a time, and power consumption is more critical. We'll probably use the lowest possible transmit power after a bit of testing.

    Should we use set any of the overrides differently from the Sub-1 Ghz settings? The patches seem to be fine, I suspect if the patch files were incompatible nothing would work. But there are settings like the loop bandwidth after lock that probably should change to get the best performance?

    And presumably we should use the txPower settings from SmartRF settings for Bluetooth on the CC1350 as well? Is it safe to use up to 12dB at 2.4Ghz, or should we stick to the 5dB the CC2650 goes up to (as apparently the front-end on the CC1350 is not as well optimised for 2.4Ghz.)

    thanks again,

    James
  • Hello James,

    We do not have settings available for proprietary mode of operation in 2.4GHz band on CC1350. The best place to start will be to compare the overrides for BLE mode on CC1350 in 2.4GHz band and the settings for CC1350 in sub-GHz band for parameters such as RSSI offset and loop bandwidth. Output power settings for BLE mode can also be used for proprietary mode and the maximum output power setting is 9dBm in 2.4GHz on CC1350.

    Regards,
  • thanks very much - this just about answers my questions. Just a final thought, which is that if we're using the latest patches, are the calculated values better than picking and choosing overrides? My understanding is that the overrides force the setting of values which can otherwise be calculated from the setup command. Just doing a diff of the different overrides for different settings is quite intimidating especially when there are no comments!

    thanks again,

    James