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.

CC1352P: CC1352P Custom RF Switch Truth table

Part Number: CC1352P

Could someone please review the following custom RF switch implementation for the CC1352P. We have a slight adjustment to the default RF switch table which is normally mutually exclusive per path 

DIO28 DIO29
2.4GHZ PA 1 1
2.4GHZ RX 1 0
OFF 0 0

Here is how we would implement this by slightly modifying the rfDriverCallbackAntennaSwitching: 

Here is the mods to the applicable section: 

            /* 2.4 GHz */
            if (paType == RF_TxPowerTable_HighPA)
            {
                /* PA enable --> HIGH PA
                 * LNA enable --> 2.4 GHz
                 */
                /* Note: RFC_GPO3 is a work-around because the RFC_GPO1 (PA enable signal) is sometimes not
                         de-asserted on CC1352 Rev A. */
                PINCC26XX_setMux(antennaPins, DIO_29, PINCC26XX_MUX_RFC_GPO3);
                PINCC26XX_setMux(antennaPins, DIO_28, PINCC26XX_MUX_GPIO);
                PINCC26XX_setOutputValue(DIO_28, 1);
            } else {
                /* RF core active --> 2.4 GHz */
                PINCC26XX_setMux(antennaPins, DIO_28, PINCC26XX_MUX_GPIO);
                PINCC26XX_setMux(antennaPins, DIO_29, PINCC26XX_MUX_GPIO);
                PINCC26XX_setOutputValue(DIO_28, 1);
            }

  • Hi,

    If you are using the SKY13317-373 as in the CC1352P reference designs the truth table must match the one given in the SKY13317-373 datasheet (Table 4 of p3): https://www.skyworksinc.com/-/media/SkyWorks/Documents/Products/301-400/SKY13317-373LF_200914L.pdf 

    From the datasheet: Any state other than described in this table places the switch into an undefined state. An undefined state will not damage the device.

    This is a limitation of the switch itself.

    Regards,

    Zack

  • Hey Zack, 

    We are using a different switch resulting in the updated truth table. Would like a sanity check that the code achieves the desired truth table. 

    With our different switch, DIO28 applies power to the switch. Hence DIO28 needs to be asserted for PA Tx, non PA Tx, and Rx. Then DIO29, when true, enables the PA path and when false, enables the RX / Non PA Tx path. 

  • Understood, thanks for the additional context - I saw that you got feedback from Ryan (which I think answered your question very comprehensively).

    I will mark this thread as resolved as from what I understand your question was answered. If you have any follow-up questions about this you can reopen this thread by replying (or you can make a new thread and link to this one).


    Regards,

    Zack