• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 56 subscribers
  • Views 981 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

CC2652P: truth table of the switch

CC2652P: RF switch configuration.

fredrikgk
Expert 2160 points
Part Number: CC2652P
Other Parts Discussed in Thread: SYSCONFIG, CC1352P

I am trying to figure out how to configure the RF switch when porting ZNP to CC2652P. I have been looking at the advice given by Clément in the linked thread, and also played a bit around with SysConfig in the CC1352P-2 ZNP project.

Is the advice given really the correct approach? It seems in the RF section innSysConfig I should change "Use Hardware" to "None", select the pins I want to use for switch control and then implement rfDriverCallbackCustom() myself. Is that correct?

This configuration could definitely be more clear in SysConfig, and I am not able to find it documented anywhere. Btw. "RF Antenna Pin" which is used in the RF Driver PinMux section is a really bad name. 

Somewhat related, It seem the ZNP project is by default configured for 20 dBm output power, however, both the initAntennaSwitch() and rfDriverCallback() functions are not used because Board_RF_SUB1GHZ is not defined. So where is the switch between Tx and Rx handled? After all, when using CC2652P that is all I need to do. 

Thanks,
Fredrik

  • 0
    TI__Guru**** 317180 points

    Fredrik, did you forget to include a link to the thread by Clément you are referring to? 

  • 0 in reply to TER
    Expert 2160 points

    The link is above my post. «Original question:»

  • 0 in reply to fredrikgk
    TI__Guru**** 317180 points

    For SDK 3.40 this is the best option since the syscfg version in that release has limitations. 

    This will be slightly better in the Q1 release. 

    When you look at a syscfg file for a given example this syscfg setup is written for the given hardware used. Hence if you want to use CC2652P and syscfg you have to select "Custom board" to be able to setup a different antenna switch. Have you made hardware to test CC2652P on? 

    I looked some at syscfg in an eng release of version 4.1 of the SDK and if you select "custom board" in this version you will be able to select the number of pins you want to use to control the antenna switch and an empty callback will be made which the user has to fill in according to the needed  logic. 

    The comment on the name is sent to the syscfg team. I agree that the naming is not good and could be misunderstood. 

  • 0
    Expert 2160 points

    Sounds good, I will take a look at the Q1 release. 

    How about this:

    fredrikgk said:
    Somewhat related, It seem the ZNP project is by default configured for 20 dBm output power, however, both the initAntennaSwitch() and rfDriverCallback() functions are not used because Board_RF_SUB1GHZ is not defined. So where is the switch between Tx and Rx handled? After all, when using CC2652P that is all I need to do. 

  • 0 in reply to fredrikgk
    TI__Mastermind 32430 points

    Hi,

    In ti_drivers_config.c (generated by SysConfig), RFCC26XX_hwAttrs has pointer to function rfDriverCallback, which is also defined in ti_drivers_config.c.

    This callback, when triggered, will also call function initRfFrontend to initialize the relevant control signals.

    Hope this helps.

    Regards,
    Toby

  • 0 in reply to Toby
    Expert 2160 points

    Thanks! I was confused by the rfDriverCallback also being present in CC1352P_2_LAUNCHXL_fxns.c.