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.

WL1835MOD: Rx BER Meter test

Part Number: WL1835MOD


We are trying to perform rx BER meter test. We are using one DUT conducted sample as the Tx unit and issuing the two commands highlighted at the bottom of the below snapshot.  Then we are using a second DUT conducted sample as the Rx unit and issuing the two commands highlighted at the top of the below snapshot, waiting at least 5 seconds between the two commands.



This is not giving us successful results.  One thing I noticed is that there appears to be a discrepancy between the BD address in the Tx command and that in the Rx command.  I have circled the two addresses in the commands shown above, and as you can see, the order of the bytes appears to be reversed between the two.  We tried to correct this, but still were not successful.


To read the results we are using the following page from the other document


As shown in the highlighted part above, it seems that the first byte of the result should be 0x00.  However, we are always seeing this first byte as 0x01, which tells us the command failed.

Could you help determine where we are going wrong and help us execute the test successfully? 

  • Hi Fatima,

    In order to rule out the confusion with the addresses, could you try using something like 0x222222222222?

    Also, to check additional details about your set up, are any of the other commands reporting back command failed or is it just the Read_BER_Meter_Result command?

    You could test the HCI connection with the following Send_HCI_Inquiry in that same document.

    Are you able to confirm that packets are being transmitted via any of the other tests in the document or via sniffer/spectrum analyzer?

    Lastly, could you inform me of which version of the service pack is being loaded to the Wilink device on boot?