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.

LAUNCHXL-CC1352P: rfEasyLinkNp init on CC1352P1_LAUNCHXL with any of the 2.4GHz modes fails

Part Number: LAUNCHXL-CC1352P
Other Parts Discussed in Thread: CC1352P

Greetings,

I'm using the EasyLink from simplelink_cc13x2_26x2_sdk_3_20_00_68 with the CC1352P1_LAUNCHXL board and finding that any of the 2.4GHz modes are failing init. The AT command reference shows 'Error 0005' which doesn't quite make sense (EasyLink_Status_Tx_Error = 5). The other modes appear to work fine.

What I'm looking for is a way to test our CC1352P board in our production environment thus I want to ensure they can TX and RX both at 2.4GHz, and at Sub1GHz.

Thanks,

Tim 

  • Hi Tim,

    Not sure what the issue is, but SmartRF Studio can be used to test and evaluate the radio in your production environment if the JTAG interface is available.

    BR,

    Seong

  • Seong,

    Regarding using SmartRF Studio for production testing of boards - that's an interesting idea. We don't use the XDS110 JTAG adapter however and use an FTDI based one. Can SmartRF studio and CCS for that matter be used with FTDI based JTAG adapters?

    Tim

  • Hi Tim,

    The 2.4 GHz proprietary settings available in the SDK are unfortunately not correct. These will be temporarily removed in the upcoming Q3 SDK and updated in the Q4 release. 

    In SmartRF Studio, correct settings are available for 2.4 GHz prop, but only if you select CC26x2R (for now).

    SmartRF Studio and its associate production test library requires JTAG for communication. 

    One alternative method you can use, is the BLE Stack and HCI commands. Using the HostTest SW example, you can call the HCI commands through UART. The API includes various test commands for continuous Tx, Rx, sending and receiving packets, etc.

    Regards,
    Fredrik