CC1310: cc1310 + cc1190 + EasyLink Driver

Sorry, rfPowerTable is not in EasyLink header, but in smartrf_settings_predefined.c
In smartrf studio can we generate this file too?

CC1310-CC1190 uses a different PA table. You can export this from SmartRF Studio if you select the correct board under Target Configuration in SmartRF Studio.

CC1310-CC1190 also require that you set LNA_PD/ PA_PD. See www.ti.com/.../swra542 for details on this. This require that you add a few line to the init section of your code.

First, double click on CC1310 to open a Device Control Window. Close to the upper left corner in this window you will find a pull down menu under Target Configuration:

 

Select the correct board. 

Then press "code export" to generate the files. 

This will only set the output power you have selected, to find the full table you can either read the app notes (

) or select different powers and see the txPower value mapped to this.

Hi,
I mimicked what packeterrorrate application is doing in my application while initializing and sending a packet. I cross checked the PER radio code with EasyLink API implementation. As far as I checked they seem similar. But my system is not emitting enough power. Current draw peaks at 180mA. Comparatively RSSI on the rx side is not greatly more than a plain CC1310 Launchpad.
My code looks like:

GPIOs:
Board_HGM | PIN_GPIO_OUTPUT_EN | PIN_GPIO_HIGH | PIN_PUSHPULL | PIN_DRVSTR_MAX,
Board_LNA_EN | PIN_GPIO_OUTPUT_EN | PIN_GPIO_LOW | PIN_PUSHPULL | PIN_DRVSTR_MAX,
Board_PA_EN | PIN_GPIO_OUTPUT_EN | PIN_GPIO_LOW | PIN_PUSHPULL | PIN_DRVSTR_MAX,

/* Configure the pins to control the range extender */
PINCC26XX_setMux(pinHandle, Board_LNA_EN, PINCC26XX_MUX_RFC_GPO0);
PINCC26XX_setMux(pinHandle, Board_PA_EN, PINCC26XX_MUX_RFC_GPO1);

RF_pCmdPropRadioDivSetup_lrm->txPower = 0x00CB;

do
{
if ((pOverrides_lrm[i] & 0x0000FFFF) == 0x000088A3)
{
pOverrides_lrm[i] = (uint32_t)0x000188A3;
}
} while ((pOverrides_lrm[i++] != 0xFFFFFFFF));

EasyLink_init(EasyLink_Phy_625bpsLrm);

// Re-define the length of the address
EasyLink_setCtrl(EasyLink_Ctrl_AddSize, 4);

EasyLink_setFrequency(867000000);

EasyLink_transmit(&txPacket);


What could wrong with this code? Could anybody suggest something more to try any changes?

Thanks in advance,
Vamsi

The LP has a narrow band SAW filter. Have you changed this to be optimal for 867 MHz? If not the SAW filter will start filtering the signal.

Also for designs with a FEM/ extra PA you should have access to a spectrum to check that both the conducted and harmonics are as expected to avoid surprises when you do a ETSI or similar test on the board.

I changed the SAW filter to similar component from same company with a center frequency of 866.5 MHz. Part number is

B39871B3717U410

However I have to mention that I didn't alter the notches in your original design.

I was doubting the software initialization because my board is not drawing enough power suggested by your app note while doing TX at highest power setting.  I'm using standard CC1310-LP for RX, so RX filtering is not in picture yet.

Have you been able to do some conducted measurements?

We will need some more time to lay our hands on a spectrum analyzer.
In the meanwhile we measured current and it is 180mA at 0x00CB txPower setting. Ofcourse it is the same at 0x00C6 too.
RSSI at 2mtrs on an CC1310 LP it is reporting -18dBm. Same with CC1310+CC1190 LP too.

Have you ensured/ checked that the RSSI is not saturated?

It's not possible for me to debug on a LP remotely without much more measurement results.

I understand. Thank you.
Just to add one more info, I configured for 868MHz, still the behaviour is same like 867MHz. Though SAW filter is not optimal at 868MHz, but as the rest of the circuit is a copy of the 1310+1190 copy, I will get back to this after doing some measurements.
Thanks.