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.

CC256x testing guide: send defined amount of packet several times

Other Parts Discussed in Thread: CC256XQFNEM

Hello,

I'm using the CC256xQFNEM module and accesing it over HCI UART.

I use it for testing another device. What I want to do is just sending 1000 packets in BLE test mode.

In the wiki guide I found a nice description on how to do so (Transmitter test).

If I run first time cmd: HCI_BLE_Transmitter_Test, I see on the sprectrum analyzer the TX signal.

Issue: If a run same comand a second time, I don't see anything.

If I run it a third time, I see it again.

Every second HCI_BLE_Transmitter_Test it doesn't output a signal.

Does anybody has an idea why this can happen?

Here my procedure:

1. Apply SP

2. Apply BLE addon

3. Enable BLE

4. Set test mode parameter

5. Start TX -> OK

6. Start TX -> No signal

7. Start TX  -> OK

etc..

xx. End BLE test mode

Thanks for any help

Joel

 

  • Joel,

          You have to end the test (HCI_BLE_Test_End 0x201f) before starting it again.

    ~Miguel

  • Hi Miguel,

    I tried to end the test with HCI_BLE_Test_End, but still the same behaviour. I tried various combination like, reset the radio ctrl, trying to apply BLE addon again, reconfigure BLE Test... But nothing worked. Only every second tx_start was execute.

    I checked as well the current profile and I see only every second time the increase (TX). I tried it on 4 different devices. 

    What I do is the transmit procedure for the A device. I hope this is still working with B device as well. If I execute the configuration for B Type, I see for each tx_start a transmittion. But with the B configuration I can not tell how many packets should be send . I just can say: start and stop. But I need to transmit a defined number of packets and therefore the cmd: HCI_VS_Set_LE_Test_Mode_Parameters is exactly what I need.

    Thanks for your help

    Joel

  • Joel,

    Did you observe the same behavior with CC2564A and CC2564B devices? The HCI_VS_Set_LE_Test_Mode_Parameters should also work with the CC2564B device.

    ~Miguel
  • Miguel,

    Unfortunattly I only have B devices (4 pieces). So I can't crosscheck that. I tried a lot of combinations this morning... On one combination, which from my point of view should work, I see the following:
    Procedure:
    1) Load SP
    2) Load addOn for BLE
    3) Reset BT CTRL
    4) Enable BLE (enable, load code)
    5) Set LE test params

    6) Start TX => OK

    7) BLE end
    8) EnableBLE (disable, do not load code (0))
    next trial
    9) Enable BLE (enable, do not load code(0)) => tried as well with loading code
    10) Set LE test params

    11) Start TX => No TX

    12) BLE end
    13) Enable BLE (disable, do not load code (0))

    Last point (13) shows an error: Code 12 = UART_HCI_ERR_BREAK
    Maybe this error helps to find root cause.

    The current profile looks ok. In normal mode ~43mA. During TX 70mA peak for 625us per packet at a BLE TX level of 5. But only for every second Start TX. For the faulty one current profile shows always 43mA with some peaks on Uart communication...

    Faulty behaviour is only seen for BLE.

    Thanks for support
    Joel
  • Joel,

    You should not enable and disable the BLE code. It should just work with cycles of the HCI_BLE_Transmitter_Test 0x201e and HCI_BLE_Test_End 0x201f commands.

    I will double check in the lab on my side and come back with my results.

    ~Miguel
  • Miguel,

    Before I made this enable/disable procedure, I tried just with HCI_BLE_Transmitter_Test 0x201e and HCI_BLE_Test_End 0x201f cmd cycles. The result was that only for every second cycle it was transmitting...

    I'm curious if you see similar bihaviour in your lab.

    Best regards

    Joel 

  • Joel,

    I used the latest service pack (SP) 1.2 and I did not see an issue. The LE transmission starts ok every time. The sequence is below.

    1) Initialization
    1.1) Download core SP.
    1.2) Download BLE add-on SP.
    2) Test Mode
    2.1) HCI_VS_Set_LE_Test_Mode_Parameters 0xFD77
    2.2) HCI_BLE_Transmitter_Test
    2.2.1) Measure Power in BT tester
    2.3) HCI_BLE_Test_End
    3) Test Mode - second iteration
    3.1) HCI_VS_Set_LE_Test_Mode_Parameters 0xFD77
    3.2) HCI_BLE_Transmitter_Test
    3.2.1) Measure Power in BT tester
    3.3) HCI_BLE_Test_End
    ...
    ...
    and so on.

    One note, the HCI_VS_LE_Enable 0xFD5B is already part of the Download BLE add-on SP (See 1.2 above).

    ~Miguel

  • Hi Miguel,

    Thanks a lot for your investigations. I realy appreciate that!

    I guess you mean for HCI_VS_Set_LE_Test_Mode_Parameters the code  0xFD77 instead of 0xFD74

    What are your parameters? Because if I set continuous TX => Packets to transmit = 0xFFFF. Then your procedure works as well on my side.

    But I want to send i.e. 1000 packets. Here my params:

    RX_Mode = 0
    PER_BER = 0
    tiPackets = 1000                  # 0xFFFF continuous mode works, defined amount number not
    tiChannel = 1                       # Set TX Frequency Channel 2402 + 2*k, where k is the channel (max val is 39)
    tiDataLength = 0x25                 # For RX and TX. Set packet payload length up to 37 (0x25) bytes
    tiPacketType = 0                    # 0 - PRBS 9, 1 - FOFO, 2 - ZOZO, 3 - PRBS 15, 4 - All Ones, 5 - All Zeros, 6 - OFOF, 7 - OZOZ,
    tiPower = 5                 
    TX_AC = 0x71764129
    BER_FH_TH = 0x14
    Tracing = 0

    With this config, the modul is transmitting only every second time. Is there somthing wrong with my configs?

    Thanks again,

    Joel 

  • Hi Joel,

    Yes, I meant 0xFD77. I corrected the information in the post above. I had tried with continuous mode. I will check with defined amount of packets and let you know my outcome

    ~Miguel
  • Hi Joel,

    Yes, there is an issue when using the "defined number of packets". For now, please use the following sequence for both, continuous and defined number of packets:

    1) Initialization
    1.1) Download core SP.
    1.2) Download BLE add-on SP.

    2) Test Mode
    2.1) HCI_VS_Set_LE_Test_Mode_Parameters 0xFD77
    2.2) HCI_BLE_Transmitter_Test
    2.2.1) Measure Power in BT tester
    2.3) HCI_BLE_Test_End

    3) Test Mode - second iteration
    3.1) HCI_VS_Set_LE_Test_Mode_Parameters 0xFD77 (Optional)
    3.2) HCI_BLE_Transmitter_Test
    3.3) HCI_BLE_Transmitter_Test
    3.3.1) Measure Power in BT tester
    3.4) HCI_BLE_Test_End

    4) Test Mode - third iteration (repeat the same sequence displayed in the second iteration)

     ~Miguel

  • Hi Miguel,

    Thanks a lot for your effort.

    Your procedure doesn't work on my side. But what is working for me is the following one:

    1) Initialization
    1.1) Download core SP.
    1.2) Download BLE add-on SP.
    2) Test Mode
    2.1) HCI_VS_Set_LE_Test_Mode_Parameters 0xFD77 (set 1000 packets to transmit)
    2.2) HCI_BLE_Transmitter_Test 
    2.3) HCI_BLE_Transmitter_Test
    2.3.1) Measure Power in BT tester
    2.4) HCI_BLE_Test_End
    3) Test Mode - second iteration
    3.1) HCI_BLE_Transmitter_Test
    3.2) HCI_BLE_Transmitter_Test
     3.3.1) Measure Power in BT tester
    3.4) HCI_BLE_Test_End

    I just send twice the BLE_Transmitter_Test cmd and I need to initialize only once the LE test parameters. On the receiver side I read now each iteration 1000 packets.

    Importent for me is the fact, that there is an issue with the BLE TX test which you could confirm. 

    Thanks for your time. And may keep me up to date if the bug will be fixed in a next SP release.

    Best regards

    Joel

     

  • Joel,

    I had made a copy/paste mistake. I corrected my previous post. Basically, it is the same sequence that you have above.

    Yes, I have reported a bug internally.

    ~Miguel