SYSCONFIG: Trying to adapt rfCarrierWave to CC1352P7 for 2.4 GHz and +20 dBm

Part Number: SYSCONFIG
Other Parts Discussed in Thread: CC1352P7

Hi,

I'm currently working with a proprietary board based on a CC1352P7. The +20 dBm PA is used for 2.4 GHz. I'm trying to use CCS and SysConfig to adapt the existing rfCarrierWave sample application in order to make it transmits on 2.4 GHz at +20 dBm with 802.15.4 modulation. 

To do this, I create a new project for the CC1352P7-4 LaunchPad, based on rfCarrierWave, Clang compiler and TI-RTOS7.

Then, with SysConfig:

In RF STACKS > Custom, I unselect Custom PHY Setting, 433 Mhz and select IEEE 802.15.4-2006, 250 kbps, OQPSK, DSSSS = 1.8, 10 dBm.

When I try to build, I get the following error messages:

[33]../rfCarrierWave.c:84:5: error: use of undeclared identifier 'RF_cmdTxTest'
[34]    RF_cmdTxTest.config.bUseCw = 1;
[35]    ^
[36]../rfCarrierWave.c:93:62: error: use of undeclared identifier 'RF_cmdPropRadioDivSetup'
[37]    rfHandle = RF_open(&rfObject, &RF_prop, (RF_RadioSetup*)&RF_cmdPropRadioDivSetup, &rfParams);
[38]                                                             ^
[39]../rfCarrierWave.c:93:36: error: use of undeclared identifier 'RF_prop'
[40]    rfHandle = RF_open(&rfObject, &RF_prop, (RF_RadioSetup*)&RF_cmdPropRadioDivSetup, &rfParams);
[41]                                   ^
[42]../rfCarrierWave.c:98:38: error: use of undeclared identifier 'RF_cmdFs'
[43]        RF_runCmd(rfHandle, (RF_Op*)&RF_cmdFs, RF_PriorityNormal, NULL, 0);
[44]                                     ^
[45]../rfCarrierWave.c:101:38: error: use of undeclared identifier 'RF_cmdTxTest'
[46]        RF_runCmd(rfHandle, (RF_Op*)&RF_cmdTxTest, RF_PriorityNormal, &rfCmdCallback, ( RF_EventCmdAborted | RF_EventCmdPreempted ));
[47]                                     ^
[48]5 errors generated.

What can I do to correct these errors?

Regards,
Pascal

  • Hi Pascal,

    When you make changes to the Sysconfig RF Stack then this changes the name conventions of the generated ti_radio_config.c file used by rfCarrierWave.c when using RF commands.  So you can either rename rfCarrierWave instances with the new names in ti_radio_config.c or further modify your SysConfig Custom Module radio settings to use the original names.

    You will also notice that RF_cmdTxTest no longer contains the config.bUseCw option.  You will need to reference the rflib documentation for IEEE specific commands and parameters.  And here is the PropRF User's Guide for your consideration.  I recall you are going to need to use RF_runScheduleCmd instead of RF_runCmd

     LAUNCHXL-CC1352P: RF_runCmd 
     LP-CC1352P7: Basic project to transmit and receive an IEEE 802.15.4 frame 
     
    You also have some extra steps to utilize 20 dBm

     LP-CC2652PSIP: How to set 10dbm & 20 dbm Power Amplifier for CC2652PSIP & CC2652P7 MCUs 
     CC2652P7: Sysconfig CC1352P7-1 LP → Custom board CC2652P7 (+20 dBm ) 

    Using Smart RF Studio 7 and the Radio Test Library is preferred for these reasons.

    Regards,
    Ryan

  • Thank you for your reply, Ryan.

    Meanwhile, I was able to find a way to do what I had to do. And this is consistent with the information you provided, which reassures me Slight smile In a few words:

    • I generated the power table and the commands with SmartRF Studio 7
    • I created an instance of the rfCarrierWave example with CCS
    • I built the project, moved the generated files to a subdirectory of the top directory, and excluded the syscfg file from build
    • I added a new source code file, where I overload rfDriverCallbackAntennaSwitching so that antenna switching for PA is done according to the custom board design
    • I set XOSC cap-array delta, in ti_devices_config.c, according to the board design
    • In rfCarrierWave.c, I renamed the RF_cmdPropRadioDivSetup command to RF_cmdRadioSetup
    • I replaced (most of) the contents of ti_radio_config.* by the contents of the smartrf_settings.c files generated by SmartRF Studio

    Regards,
    Pascal