LAUNCHXL-CC1352R1: RF Packet tx code getting rf packet failed during transmission with Smart RF studio 7

EBYTE E79-400DM2005S

1. RF Packet tx code getting rf packet failed during transmission with Smart RF studio 7, I have attached my settings for your reference, please let us know what mistake I made or what is wrong…

2. We have tested EBYTE E79-400DM2005S with Rf packet example through CCS but our RF receiver(E70-900M14S1B) doesn’t receive any data from the module but We have uploaded the same program (which is uploaded in E79-400DM2005S) to CC1352-P1 Launch pad that is working fine our E70-900M14S1B rf receiver module received the data from that, please let us know why this problem occurred in the module.

We have search about our issue in google then we have found following links they are faced the same issue.

https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/905982/ccs-cc1352p-ebyte-e79-rf-issue

https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/994933/cc1352p-issue-enabling-the-high-pa-20dbm-on-ebyte-e79-900dm2005s-module

3. Please let me know how to choose 20dbm for Tx power in ccs sys.cfg

If I choose PA option that makes E79-400DM2005S auto reset continuously, we don’t know why this is happening…

4. We have attached our tx and rx module UART log for your reference, our RX module E70-900M14S1B received the data from all other boards but not received from E79-400DM2005S.

Tx log RX log

5. As per your datasheet page number 8, we have control the GPIO 5&6 based on the table but the module doesn’t send the data through RF

We have shared the code snippet for your ref.

GPIO_write(CONFIG_GPIO_GLED, CONFIG_GPIO_LED_ON);

        GPIO_write(CONFIG_GPIO_RLED, CONFIG_GPIO_LED_OFF);

        sleep(1);

        RF_cmdPropTx.pktLen =strlen(FLOW_STATE);

        for (int i=0; i<strlen(FLOW_STATE); i++)

       {

           uint8_t* buffer8 = (uint8_t*) FLOW_STATE;

           packet[i] = buffer8[i];

       }

        /* Send packet */

        RF_EventMask terminationReason =RF_runCmd(rfHandle, (RF_Op*)&RF_cmdPropTx,RF_PriorityNormal, NULL, 0);

Cherry Zhou：

Hi,

Thank you for raising the ticket, it seems that the hyperlink of Tx log RX log are failed and could please help share it again? 

?? ? 说：We have attached our tx and rx module UART log for your reference, our RX module E70-900M14S1B received the data from all other boards but not received from E79-400DM2005S.

 

Tx log RX log

 

Thanks

,

Cherry Zhou：

Hi,

1) 2) and 4) I'm not very familiar with EBYTE E79-400DM2005S and I don't know what the difference is between this module and the CC1352 LaunchPad. You may have to contact Ebyte for support.

3) Depending on device and PHY you have selected, you should be able to open Sysconfig -> RF STACKS -> Select your stack -> Select your PHY -> PHY Properties and check the box for High PA and select your Tx power value.

5) Did you try setting up one of our radio driver example projects (e.g. rfPacketTx) and configure the GPIO with sysconfig?

Thanks