• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 51 subscribers
  • Views 172 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC2642R: Utilizing BTool to control a DUT BLE transmitter and a DUT BLE receiver to do PER testing vs distance (Range testing) on multiple channels

William Hiner
Prodigy 20 points
Part Number: CC2642R

What BTool commands or command sequences are needed to setup the transmitter BLE DUT and the receiver BLE DUT to perform range testing at specified channel, power and RFPHY.  The choosing the channel, power and RFPHY seems straightforward but getting data and PER measurements from the receiver hasn't been.

Thank you,

Bill

  • 0
    TI__Genius 12925 points

    Hello Bill,

    To perform PER tests you can use the host_test project (included in the BLE5stack directory of the SDK) flashed into the two devices (acting as TX and RX).
    The following application note (pages 9 - 12) describes the steps and commands that can be followed to get the necessary data for PER calculation.

    https://www.ti.com/lit/swra737
     
    You can even check the commands required for Different PHY Rate if you application requires it (pages 12 - 18).

    Hope this helps.

    Best regards,

    David.

  • 0 in reply to David
    Prodigy 20 points

    I already have this document.  I don't see where the where there is any data back showing the PER data.  Where are the PER results reported?

  • 0 in reply to William Hiner
    TI__Genius 12925 points

    Hello William,

    Btool reports the number of received packets received on the RX side (variable named "NumOfPackets" as seen on Page 12).
    To get the packet error rate (PER), you can divide the number of packets received by the number of packets transmitted.
    The last one you also know as it is configured with the "MISC_GenericCommand" on the TX side under the "data" parameter (which on Page 10 is 60 00, which describes 0x0060 = 96).

    Hope this helps.

    David.