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.

CC2530 CC2591 rx and tx settings

Other Parts Discussed in Thread: CC2591, CC2530

Hi,

I have realize a custom PCB with CC2530 + CC2591.

In the schematics, I have connected the signals as below:

HGM_EN = P2.1 instead of P0.7

PA_EN = P2.0 instead of P1.1

LNA_EN = P2.2 instead of P0.6

I use TI-MAC 1.4.3 and I need to set the CC2591 for TX and RX mode.

I try to set CC591 in power up TX at the end of RX, so in mac_rx.c

line 1196

static void rxDone(void)

{

#if defined BOOST

ENABLE_TX_PA();  

ENABLE_TX_LNA(); // 

#endif

....

........

}

and in mac_tx.c line 202 where I see this comment:

/*--------------------- * Prepare for transmit. */

I put the CC2591 in TX mode, so:

#if defined BOOST  

ENABLE_TX_PA();

ENABLE_TX_LNA();

#endif

Now, I can see the beacon sent from the device with good RSSI but I've some problem in the associate procedure.

I think that the RX/TX and reverse change doesn't work well.

Does anybody tell me where I should set the CC2591 for a correct RX/TX behavior?

thank you

Best Regards,

Emanuele

  • Hi Emanuele,

    I think the pins you have selected to connect to PA/LNA is not ideal, and you should consider changing them.

    First of all, PA_EN and LNA_EN signal can be driven automatically from the radio HW module if you choose one of the pins P1.0 - P1.5.

    The CC2530 chip can automatically output the PA_EN and LNA_EN signal if pins are configured correctly through the OBSSEL registers. OBSSEL registers can be muxed to P1.0 - P1.5 pins only (please see macRadioTurnOnPower() in mac_radio_defs.c, under HAL_PA_LNA compilation flag to see how OBSSEL registers are configured)

    Second of all, P2.1 and P2.2 pins are used to drive the debug module of the chip, which is for flashing and debugging. So definitely not a good idea to use those.

    Thanks,

    TheDarkSide

  • Dear TheDarkSide,

    thank you for the fast answer.

    I have choose these pins because in my board is the only free pin that I can use..

    I hope I can set the RX/TX mode in the TI-MAC with setting the pin of the port I selected. 

    Can you tell me the section of TI-MAC where I should to set it or where I can try to set the CC2591 behavior?

    thank you

    Regards,

    Emanuele

  • Hi Emanuele,

    the pins you decided to use have a conflict with the debug interface pins. I know it may sound harsh but I really think you need to change the design. 

    Otherwise, there's a risk that you enter the chip in debug mode while operating the PA/LNA part.

    We recommend  you move the control of PA/LNA to pins P1.0 - P1.5 is makes it also easier from a SW control standpoint, as the HW will automatically drive the PA/LNA signals when and only there is radio activity (Tx/Rx), without the need of SW controlling the line as a GPIO just before the TX and RX activity.

    So that solution is cleaner from an architecture standpoint and will achieve higher performance in terms of both link budget as well and power consumption, as the front end will be turned on and driven accordingly in sync with the HW radio Tx/Rx activity, without SW delays.

    Thanks,

    TheDarkSide 

  • Hi,

    mmm.. You are right to tell me to change the design, but I really don't know how I can do because I use all the P1 pin to other things.. Enable LDO, I2C, Enable EEPROM and RTC and so on..

    So, I would to try to set the CC2591 with SW routine.. 

    Do you know in which part of code TI-MAC I can try to set the RX/TX of CC2591?

    thank you and Best regards,

    Emanuele

  • Hi TheDarkSide,


    I change the pin like you told me and now all works fine.

    I've only one problem, a big problem, sometimes the rssi of the sent packet is about -90dbm instead of -30dbm that I usually read.

    I check all the register and settings but is ok and is the same for all packet trasmitted.

    Do you know if there are a bug or something like this?

    thank you

    Regards,

    Emanuele