CC2640: Configuring CC2640 for Proprietary mode

Hi,

It is recommended to use CC2640R2 device for any new development instead of CC2640.
Since you have already received the settings needed for these modes of operation, can you please elaborate on the performance issues you have been seeing.

RF register overrides are used to configure modules on the device for optimal configuration for a specific PHY implementation. Since this device can be programmed over wide range of datarates and modulations, some customization is needed for operation in different modes.

The RF core can operate using code in ROM or using patches. MCE, RFE and CPE are different modules responsible for different functions such as packet handling, front end configuration etc. Depending on functions that need modifications, the module responsible for this function might execute using patch instead of ROM. This is configured using "MCE_RFE_OVERRIDE" function.

Please use the overrides and patches provided by TI for proper operation of radio.

For TX output power, please use the settings from latest release of smartrf studio. These settings are derived based on testing hardwar selected on studio such as the launchpad.

HS APIs are typically needed when the datarate is higher than 1mbps and below this datarate, proprietary APIs can be used.

Regards,

Hi SVS,

Thank you for the prompt reply. This does a lot to give me a pretty good overview of whats going on, but not all the detail I need to operate this chip in proprietary mode. I'll look into switching our hardware design to the CC2640R2 device as you are recommending that for new designs.

As for configuring the device in proprietary mode, SmartRF Studio only has settings for 100kbps and 250kbps for the CC2640R2F, therefore I can not produce the settings for the higher data rate modes I described above. The CC2640 datasheet calls out settings for 5Mbps proprietary operation which is what lead me to include this chip in our design.

For our product's application we must have 2Mbps proprietary operation. Can you provide the settings for these modes of operation given that SmartRF Sudio cannot produce them? I have seen posts elsewhere in the forum that people have been able to operate in these modes, but they didn't post details of the code and configuration.

Best,
~Matt

HI SVS,

In our current design we have a CC2640 which only supports BLE4.2 and doesn't have the commands for BLE5 (at least in the SDK, I have no idea if the radio ROM supports them). The CC2640 Datasheet (SWRS176B) explicitly calls out the 5Mbps Proprietary mode as well as 2Mbps GFSK for BLE so I'm hoping it's possible to get it into these mode. Without support in SmartRF Studio, I'm still very unclear on how to hand craft a radio setup command to use for 2Mbps proprietary mode on the CC2640.

I think what you are suggesting is for me to use SmartRF Studio to generate a config file for the CC2640 in BLE mode. The output of that is shown at the end of my post here (BLE tx/rx command omitted). I think there are the changes I need, but I still have some questions outlined:

• In yellow, change the rfMode to propreitary_2_4
• In purple, it seems to me that the mode of the setup command would need to change out of BLE mode?
• In Orange, are the BLE modem control and RF patches still correct for prop mode?
• In Green, there is no documentation on the internal registers that the register overrides set. Same as above, are these still correct for prop mode
• Beyond setting the .mode in setup, it's unclear if I need to set the data rate anywhere else (2Mbps vs 5Mbps) and if any other support settings that need to change
• If all that setup is done correctly, as you stated above I'd use the HS API commands for packet TX and RX

Best,

~Matt

 

Code begins below:

//*********************************************************************************

// Generated by SmartRF Studio version 2.11.0 (build#126)

// The applied template is compatible with tirtos_simplelink_2_21_00

// Device: CC2640 Rev. 2.2

//

//*********************************************************************************

//*********************************************************************************

// Parameter summary

// Adv. Address: 010203040506

// Adv. Data: 255

// BLE Channel: 17

// Frequency: 2440 MHz

// PDU Payload length:: 30

// TX Power: 5 dBm

// Whitening: true

#include <driverlib/rf_mailbox.h>

#include <driverlib/rf_common_cmd.h>

#include <driverlib/rf_ble_cmd.h>

#include <ti/drivers/rf/RF.h>

#include <rf_patches/rf_patch_cpe_ble.h>

#include <rf_patches/rf_patch_rfe_ble.h>

#include "smartrf_settings.h"

// TI-RTOS RF Mode Object

RF_Mode RF_ble =

{

   .rfMode = RF_MODE_BLERF_MODE_PROPRIETARY_2_4,

   .cpePatchFxn = &rf_patch_cpe_ble,

   .mcePatchFxn = 0,

   .rfePatchFxn = &rf_patch_rfe_ble,

};

// Overrides for CMD_RADIO_SETUP

uint32_t pOverrides[] =

{

   // override_use_patch_ble_1mbps.xml

   // PHY: Use MCE ROM, RFE RAM patch

   MCE_RFE_OVERRIDE(0,0,0,1,0,0),

   // override_synth_ble_1mbps.xml

   // Synth: Set recommended RTRIM to 5

   HW_REG_OVERRIDE(0x4038,0x0035),

   // Synth: Set Fref to 3.43 MHz

   (uint32_t)0x000784A3,

   // Synth: Set loop bandwidth after lock to 80 kHz

   (uint32_t)0xA47E0583,

   // Synth: Set loop bandwidth after lock to 80 kHz

   (uint32_t)0xEAE00603,

   // Synth: Set loop bandwidth after lock to 80 kHz

   (uint32_t)0x00010623,

   // Synth: Configure PLL bias

   HW32_ARRAY_OVERRIDE(0x405C,1),

   // Synth: Configure PLL bias

   (uint32_t)0x1801F800,

   // Synth: Configure PLL latency

   HW32_ARRAY_OVERRIDE(0x402C,1),

   // Synth: Configure PLL latency

   (uint32_t)0x00608402,

   // Synth: Use 24 MHz XOSC as synth clock, enable extra PLL filtering

   (uint32_t)0x02010403,

   // Synth: Configure extra PLL filtering

   HW32_ARRAY_OVERRIDE(0x4034,1),

   // Synth: Configure extra PLL filtering

   (uint32_t)0x177F0408,

   // Synth: Configure extra PLL filtering

   (uint32_t)0x38000463,

   // override_phy_ble_1mbps.xml

   // Tx: Configure symbol shape for BLE frequency deviation requirements

   (uint32_t)0x013800C3,

   // Rx: Configure AGC reference level

   HW_REG_OVERRIDE(0x6088, 0x0045),

   // Tx: Configure pilot tone length to ensure stable frequency before start of packet

   HW_REG_OVERRIDE(0x52AC, 0x0360),

   // Tx: Compensate timing offset to match new pilot tone setting

   (uint32_t)0x01AD02A3,

   // Tx: Compensate timing offset to match new pilot tone setting

   (uint32_t)0x01680263,

   // override_frontend_id.xml

   (uint32_t)0xFFFFFFFF

};

// CMD_RADIO_SETUP

// Radio Setup Command for Pre-Defined Schemes

rfc_CMD_RADIO_SETUP_t RF_cmdRadioSetup =

{

   .commandNo = 0x0802,

   .status = 0x0000,

   .pNextOp = 0, // INSERT APPLICABLE POINTER: (uint8_t*)&xxx

   .startTime = 0x00000000,

   .startTrigger.triggerType = 0x0,

   .startTrigger.bEnaCmd = 0x0,

   .startTrigger.triggerNo = 0x0,

   .startTrigger.pastTrig = 0x0,

   .condition.rule = 0x1,

   .condition.nSkip = 0x0,

   .mode = 0x00, // Does this need to be either 0x02 or 0x05 for 2Mbps or 5Mbps?

   .__dummy0 = 0x00,

   .config.frontEndMode = 0x0,

   .config.biasMode = 0x0,

   .config.analogCfgMode = 0x0,

   .config.bNoFsPowerUp = 0x0,

   .txPower = 0x9330,

   .pRegOverride = pOverrides

};

// CMD_FS

// Frequency Synthesizer Programming Command

rfc_CMD_FS_t RF_cmdFs =

{

   .commandNo = 0x0803,

   .status = 0x0000,

   .pNextOp = 0, // INSERT APPLICABLE POINTER: (uint8_t*)&xxx

   .startTime = 0x00000000,

   .startTrigger.triggerType = 0x0,

   .startTrigger.bEnaCmd = 0x0,

   .startTrigger.triggerNo = 0x0,

   .startTrigger.pastTrig = 0x0,

   .condition.rule = 0x1,

   .condition.nSkip = 0x0,

   .frequency = 0x0988,

   .fractFreq = 0x0000,

   .synthConf.bTxMode = 0x0,

   .synthConf.refFreq = 0x0,

   .__dummy0 = 0x00,

   .__dummy1 = 0x00,

   .__dummy2 = 0x00,

   .__dummy3 = 0x0000

};