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.

LP-CC1352P7: Why the receiver test the selectivity makes a program stuck at LE 2M?

Part Number: LP-CC1352P7
Other Parts Discussed in Thread: CC1352P7

   Hi Sir, 

  We are testing the LP-CC1352P7 for its BLE recevier peformance, and we used the C:\ti\simplelink_cc13xx_cc26xx_sdk_6_40_00_13\examples\rtos\LP_CC1352P7_1\ble5stack\host_test\tirtos7\ticlang. But when we test the receiver selectivity at LE 2M, we set the wanted signal at 2440MHz and -67dBm, the interference signal at 2444MHz and -31dBm, the program in LP-CC1352P7 has a stuck, we can't use the receiver test until we use the reset button so that it can return to normal. When we test at LE 1M or LE Coded it can work normally, just at LE 2M it makes the mistake. I want to know about why this mistake would happen at LE 2M? are there any solutions can solve it?

  • Hi,

    Are you saying the host_test program is crashing when being interfered with a given signal?

    How do you generate that interference signal, are you using SmartRFStudio?

    Regards,

    Arthur

  • Hi Arthur,

    Yes, the host_test program is crashing when we give the wanted signal and the interference singal together. When we just give the wanted signal, the host_test program can run normally; when the interference singal is given, the host_test program crashed. And we generate the interference singal by using the Vector signal generator SMBV100A, not used the SmartRFStudio. 

  • We will try to reproduce the issue, but we need more characteristics on the interfering signal.

    Could you provide thoses?'

    Regards,

    Arthur

  • Hi Arthur,

    We set the interfering signal as: the interferer shall be continuously modulated with PRBS15 data (i.e., no packet structures or pauses in the signal), and it shall have settled at least 1 ms prior to the activation of the wanted signal. 

  • Hi,

    How do you generate the wanted signal? Is it using another host_test programmed device, or is it using another vector signal generator?

    We also assume that your tests are being done conducted.

    As of now, we have not been able to reproduce the issue with the vector signal generator, or SmartRFStudio, but we are doing it in a radiated setting.

    Regards,

    Arthur

  • Hi Arthur,

    We use another signal generator LitePoint IQxstream-5G to generate the wanted signal, the wanted signal and the interference signal were mixed together by using a power combiner. And the test were dong in a conducted setting.

  • Hi,

    We have tried the following conducted test:

    • Interferer signal at -31dBm, channel 19, running smart RF studio continuous TX, modulated, unmodulated and HCI_LE_EnhancedTransmitterTest 
      • Parameters for HCI_LE_EnhancedTransmitterTest:
    • Wanted signal at -67 dBm, channel 17 running the HCI_LE_EnhancedTransmitterTest command
      • Parameters:
    • Both signals fed into a coupler, connected to the receiver device running the HCI_LE_EnhancedReceiverTest
      • Parameters:

    And we did not manage to reproduce your issue.

    What baudrate are you using in BTool, is it 115200? And at what power does the interferer signal starts to crash the host_test program on your side?

    Regards,

    Arthur

  • Hi Arthur,

    The baudrate in BTool we set is 115200, and the interferer signal power is -31dBm makes the host_test program crashed. But the interferer signal generator we didn't use the smart RF studio.

  • Hi Arthur,

    Can you tell me about the details about using the smart RF studio to generate the interferer signal? We want to use your methods to verify it. 

  • Hi yuetanhuang,

    We used SmartRF studio with the following modes:

    • Packet TX
    • Continuous TX, unmodulated, modulated

    At +20dBm on channel 19

    We will try to test with a vector signal generator as well.

    Regards,

    Arthur

  • Hi Arthur,

    The interferer signal generated by SmartRF studio is not compliant with Bluetooth standards.  The SmartRF studio could not select the PRBS15 data type when the mode is continuous modulated TX.

    We see the standard in the Radio Frequency Physical Layer (RFPHY) / Test Suite.

  • Hi yueyanhuang,

    It looks like it is not possible to do it using SRFSTUDIO, but the device is able to, as seen in Table 25-102.of the TRM.

    In the meantime, we tested with a setup similar to yours, with two vector signal generators generating BLE packets. And we have not been able to reproduce the issue either.

    Have you tried increasing the baudrate on BTool?

    Could you also provide us with logic capture of the serial interface, especially when it crashes?

    Regards,

    Arthur

  • For reference, here is the signal we are generating, on the left, the wanted signal, on the right peak, the interferer:

    And the frequencies:

  • Also,

    Are you continuously sending wanted signal packets, or is there a delay between those packets?

    If there is not delay, please add a 100ms delay.

    Regards,

    Arthur

  • Hi Arthur,

    We have try to increase the baudrate such as 230400, 460800, 921600 on BTool, and when the interfered signal is 2444MHz and -31dBm, the program running noramlly; But if the power of interfered signal had been increased to -27 dBm, the host_test program crashed. We will try to determine if all boards will experience this issue after increasing the baud rate. Currently, only one board has encountered this issue.

    And we set the wanted signal has the packet Interval, as shown in the following figure:

    Also, We want to know about what model of vector signal generator are you using, we try to use the same machine to generate the signal.

  • Hi yuetanghuang,

    Thank you for the information, we will wait for more results from your side.

    We use the ROHDE&SCHWARZ SMW200A Vector signal generator.

    Regards,

    Arthur

  • Hi Arthur R,

    We have tested for five modules and we found that when we increased the baudrate, setted the interfered signal to 2444MHz and -30dBm, the host_test program can work normally; if we increased the power, the host_test program crashed in one of the modules, others still work normally.