CC2652R: Usage of CC2592 front end with CC2652R

Hi Ryan, I know I've marked this post as resolved but i want to know how to check if CC2592 is properly configured.

CC2652R pins configuration:

    /* Map RFC_GPO0 to DIO13 */
    IOCPortConfigureSet(IOID_13, IOC_PORT_RFC_GPO0, IOC_IOMODE_NORMAL);

    /* Map RFC_GPO1 to DIO7 */
    IOCPortConfigureSet(IOID_7, IOC_PORT_RFC_GPO1, IOC_IOMODE_NORMAL);

    /* Normal I/O */
    IOCPortConfigureSet(IOID_14, IOC_IOCFG31_PORT_ID_GPIO, IOC_IOMODE_NORMAL);

When checking lqi from a HUE Device 2m away from the coordinator(cc2652 + cc2592), it has a really low value. Since i'm using a board of our own design i want to know if the problem is in the cc2592's configuration or in the design.

Regards,

Matias

Do i have to do anything else than configuring pins like shown above?

The lqi I get is 0, which is weird since the cc2652(ZC) is one meter away from the ZED I'm using for test.

Regards,

Matias

Not as I know. Do you use scope to check if PA/LNA pins work when the device does TX/RX?

Hi,

I used scope to check if PA/LNA work and it seems to be working fine but Rx is in low gain mode. What  is the configuration in CC2652 for rx high gain mode? I know both LNA_EN and HGM need to be high to be in rx high gain mode. The problem is I can send zb packages to a zed 20m away but not receive its reports.

Regards

Matias

Hi Matias,

Have you attempted to test in SmartRF Studio 7 with a customized target configuration?  This would help determine whether this is a custom PCB hardware or stack software issue.

Regards,
Ryan

I don't really know how to use SmartRF Studio 7 but when I try to send packets an error message appears indicating "Sending of packet failed.". I'm using Device Control Panel in propietary mode. When i use the same feature with a cc2652r dev kit it works.

How am I supposed to use SmartRF Studio?

Regards,

Matias

There is no proprietary mode for the CC2652R as this is reserved for Sub-1GHz communication.  You should be using IEEE 802.15.4 mode.

http://www.ti.com/lit/swru194 
http://www.ti.com/lit/swru195 

I also assume you are using Rev E silicon with your custom PCB: https://e2e.ti.com/support/wireless-connectivity/zigbee-and-thread/f/158/t/767777

Regards,
Ryan

It's not working. The same message appears: "Sending of packet failed."

Output:

>CMD_RADIO_SETUP executed

> Status: 0x0 IDLE

>CMD_FS executed

> Status: 0x0 IDLE

I have a CC2652 E revision connected to 3v3, gnd, tms and tck from dev kit.

You will need a Custom Target Configuration (I/O Configuration and Output Power) for your CC2592 connection.

Regards,
Ryan

I have configured a custom target as shown in the images below but it still doesn't work. I don't know how to configure Tx power settings.

I have used a scope to check LNA and PA pins and they don't change at all.

Any idea on what's wrong with the configuration/board? 

How do I force HGM pin to 1 always to set RX High-Gain Mode?.

Regards,

Matias

With the disclaimer that I am not an expert at SMARTRFTM-STUDIO or external PA hardware, I recommend trying the Input/Output configurations instead of Radio for all three configurable pins.  Output TX Power settings are dependent on your custom PCB hardware but you can use the CC1352P-2 settings as a guide.  http://www.ti.com/lit/an/swra640b/swra640b.pdf 

Regards,
Ryan

Hi Matias,

Can you post a screenshot of the main device panel in SmartRF Studio were it shows the RF configuration. Also showing the error message you see. 

Can you try running continuous Tx and measure the output from your board with a spectrum analyzer?

Can you try to run the PacketTx RF Driver SW example on your board (simply add the control signals for CC2592) and see if you can receive the packets with a CC26x2R LaunchPad controlled by SmartRF Studio?

If none of these experiments work, check whether the 48 MHz crystal is actually starting up. Check voltages around the board. Monitor the supply voltage when enabling Tx to see if there are any drops triggering BOD.

Enabling HGM in CC2592 is simply a matter of asserting the GPIO connected to the HGM pin. 

Regards,
Fredrik