This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Production RF test

I want to test RF during production but I do not have any GPIO or UART points on my DUT so I don't want to run the DTM. Can anyone tell me what problems there are with this method? Thanks.

The tester is a modified DUT board with UART that uses the NUS to transfer data between the DUT.

  1. Bond and connect the NUS service
  2. DUT will receive packets sent from tester and send the same packet back to tester. Use notification packets to send data between tester and DUT.
  3. Total send 1000 packets, payload 20 bytes (fill with 0, 255, 0, 255…….). Send next packet when receiving previous packet or timer is up. Timeout: 100msec
  4. Check how many packets sent back from DUT, packet loss > 3% means failure
  • Hi Jeff,

    There is an issue with your test that as BLE communication is a reliable communication meaning a packet drop will be re-transmitted until it's ACKED before the next packet can be transmitted. If it couldn't makes it to be ACKED before the timeout, the connection will be terminated.

    And the re-transmission is transparent to the application, so you have no way of telling how many retry has been done for each data packet.

    If you want to test the radio, I would suggest to use the DTM or the radio test example. Note that if you don't have UART interface you can also use the SWD interface (the programming interface) and use SeggerRTT to send command or receive data.

    If you simply want to simply do radio communication and count the number of packet drop, I would suggest base on and modify the Enhanced Shockburst example. With that you can find number of packet drop and number of re-transmission on each packet received.

Related