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.

LAUNCHXL-CC1352R1: "Antenna switch" signal in DMM Example code

Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: CC1352R

Hy,

for a new project I was looking for a good start project for a subGhz / BLE device. As I do not know if I ever need subGhz and BLE simultaneously I took the dmm_wsnnode_ble5_sp_cc1352r1lp project .

I tried to port to my hardware, seems well, but then I come across the function

void rfDriverCallback(RF_Handle client, RF_GlobalEvent events, void *arg)
{
    (void)client;
    RF_RadioSetup* setupCommand = (RF_RadioSetup*)arg;

    if ((events & RF_GlobalEventRadioSetup) &&
            (setupCommand->common.commandNo == CMD_PROP_RADIO_DIV_SETUP)) {
        /* Sub-1 GHz, requires antenna switch high */
        PINCC26XX_setOutputValue(Board_RF_SUB1GHZ, 1);
    }
    else if (events & RF_GlobalEventRadioPowerDown) {
        /* Disable antenna switch to save current */
        PINCC26XX_setOutputValue(Board_RF_SUB1GHZ, 0);
    }
}

I assume, this switches on and off antenna (?) by DIO_30. But when I look into schematic nothing is connected to DIO_30.

Can I just comment out the PINCC26XX_setOutputValue calls, or even get rid of the whole rfDriverCallback?

And, evenmore general: There are two different folders "board":

  •  C:\ti\simplelink_cc13x2_sdk_2_30_00_45\source\ti\boards\CC1352R1_LAUNCHXL
  •  C:\ti\simplelink_cc13x2_sdk_2_30_00_45\source\ti\ble5stack\boards\CC1352R1_LAUNCHXL

Content is slightly different. The DMM example includes the C:\ti\simplelink_cc13x2_sdk_2_30_00_45\source\ti\ble5stack\ folder. Is that correct?

Regards

Harald

  • Hi Harald,

    The CC1352R LaunchPad used to have an RF switch to toggle between the sub-1 GHz RF port and the 2.4 GHz RF port. This switch is now replaced with a diplexer and the the RF switch code is no longer needed. You can safely remove it, it will also be removed in the next SDK.

    The BLE stack uses slightly different board files (for now). When using the BLE stack you should also use the board files inside the BLE stack folder.

    Regards,
    Fredrik