• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 41 subscribers
  • Views 2142 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Linux/WL1837MOD: BLE testing with manual HCI commands

Minjoo Kim
Intellectual 330 points
Part Number: WL1837MOD

Tool/software: Linux

Hello,

I have a board that has wl1837mod on it. To verify its BLE performance, I am following http://processors.wiki.ti.com/index.php/CC256x_Testing_Guide#BLE_Testing chip manually instead of having a Bluetooth test set take care of that. I had no problem for TX measurements, but for RX the step 12 where the SYNC counter is reset does not seem to go through. I have no problem reading though. I tried with different register addresses, and they all got stuck with writing only. I suspect that this is due to different chip families between CC256x and Wl18xx as the testing guide was written for CC256x (I am using this because wl18xx does not have detailed descriptions on how to test BLE without direct DUT control between a test set and the chip). I have copy and pasted the console output. What is the register address of the SYNC counter on wl18xx?

12. Clear Sync Counter

HCI_VS_Write_Hardware_Register 0xFF01, 0x0019324E, 0x0
Outgoing Dump: 01 01 ff 06 4e 32 19 00 00 00
Incoming Event: 04 0e 04 01 01 ff 00 (Command Complete Event)

 # hcitool cmd 0x3f 0x300 0x4e 0x32 0x19 0x00     #HCI_VS_Read_Hardware_Register 0xFF00, 0x0019324E

< HCI Command: ogf 0x3f, ocf 0x0300, plen 4
4E 32 19 00
> HCI Event: 0x0e plen 6
01 00 FF 00 4E 32


# hcitool cmd 0x3f 0x301 0x4e 0x32 0x19 0x00 0x00 0x00     #HCI_VS_Write_Hardware_Register 0xFF01, 0x0019324E, 0x0000
< HCI Command: ogf 0x3f, ocf 0x0301, plen 5
4E 32 19 00 00 00

  • 0
    TI__Mastermind 29301 points

    Minjoo,

    For WL183xMOD device, please follow the WL18xx Bluetooth RF testing guide.

    BR,

    Vihang

  • 0 in reply to Vihang Parmar
    Intellectual 330 points
    Hello Vihang,

    I am well aware of the wl18xx Bluetooth testing guide, but as I stated above, since I do have to test BLE without the DUT control lines between a test set and the chip itself, I do need more information than what is in the testing guide. I can definitely put the device in the BLE test mode with the three commands below, but that is NOT the issue.

    BLE testing
    Transmitter Test

    HCI Tester command format

    Send_HCI_VS_DRPb_Enable_RF_Calibration_Enhanced 0xFDFB, 0x1, 0xFF, 0x80000000, 0x00 //disable RF Calibration
    Send_HCI_BLE_Transmitter_Test 0x201e, 0x00, 0x00, 0
    Send_HCI_BLE_Test_End 0x201f
    Bluetopia HCI tool format:

    SS1Tool cmd 0x3f 0x01fb 0x01 0xff 0x00 0x00 0x00 0x80 0x00 //disable RF Calibration
    SS1Tool cmd 0x08 0x001e 0x00 0x00 0x00
    SS1Tool cmd 0x08 0x001f
    Receiver Test

    HCI Tester command format

    Send_HCI_VS_DRPb_Enable_RF_Calibration_Enhanced 0xFDFB, 0x1, 0xFF, 0x80000000, 0x00 //disable RF Calibration
    Send_HCI_BLE_Receiver_Test 0x201d, 0x00
    Send_HCI_BLE_Test_End 0x201f
    Bluetopia HCI tool format:

    SS1Tool cmd 0x3f 0x01fb 0x01 0xff 0x00 0x00 0x00 0x80 0x00 //disable RF Calibration
    SS1Tool cmd 0x08 0x001d 0x00
    SS1Tool cmd 0x08 0x001f
  • 0 in reply to Minjoo Kim
    TI__Mastermind 29301 points
    Minjoo,

    I understand. Please use the command below for clearing the sync counter in WL18xx.

    HCI_VS_Write_Hardware_Register 0xFF01, 0x200107E2, 0x0000

    BR,
    Vihang
  • 0 in reply to Vihang Parmar
    Intellectual 330 points

    Hello Vihang,

    The register address of 0x200107e2 does not seem to spit out any errors when writing to and reading from it. Though, I never see its value changing even though it has indeed received packets. Can you tell me what it counts? 

    Thanks.