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.

WL1837MOD: How to test / Change Tx Power Levels, Switching between BT and BLE, Different RF test, Continuous TX/RX etc On IMX6+Linux for Compliance?

Part Number: WL1837MOD
Other Parts Discussed in Thread: WL1837


We integrated this WL1837 BT on to IMx6 based board over UART with LInux as OS. Its working fine in Normal Mode.

Now we need to test this BT part of WL1837 in "Test Mode" for operations like below from IMX6 Linux. Linux driver is hci_uart and running Bluez stack on top of this driver.

    1. Switching the BT device between BLE and BT classic?

    2. Changing the Tx power Levels using available commands like hcitool, hciconfig etc or any other tools from TI?

    3. Changing Frequencies / Channel etc?

    4. Continous TX/RX tests


I tried below commands..

1. Putting device into PICAN working fine..

2. TX power Level setting:
   root@imx6: # hciconfig hci0 up

root@imx6: # hciconfig hci0 inqtpl
hci0: Type: Primary Bus: UART
BD Address: 78:04:73:B2:AD:CE ACL MTU: 1021:6 SCO MTU: 180:4
Inquiry transmit power level: 14

root@imx6: # hciconfig hci0 inqtpl 12

root@imx6: # hciconfig hci0 inqtpl
hci0: Type: Primary Bus: UART
BD Address: 78:04:73:B2:AD:CE ACL MTU: 1021:6 SCO MTU: 180:4
Inquiry transmit power level: 14

Dump:-

< HCI Command: Read Inquiry Response Transmit Power Level (0x03|0x0058) plen 0

    HCI Event: Command Complete (0x0e) plen 5
    Read Inquiry Response Transmit Power Level (0x03|0x0058) ncmd 1
    status 0x00 level 14

< HCI Command: Write Inquiry Transmit Power Level (0x03|0x0059) plen 1
level 12


    HCI Event: Command Complete (0x0e) plen 4
    Write Inquiry Transmit Power Level (0x03|0x0059) ncmd 1
    status 0x00
    < HCI Command: Read Inquiry Response Transmit Power Level (0x03|0x0058) plen 0
    HCI Event: Command Complete (0x0e) plen 5
    Read Inquiry Response Transmit Power Level (0x03|0x0058) ncmd 1
    status 0x00 level 14

3. Putting hci0 into PISCAN
   root@imx6: hcitool cmd 0x03 0x01a 0x03
< HCI Command: ogf 0x03, ocf 0x001a, plen 1
  03
> HCI Event: 0x0e plen 4
  01 1A 0C 00

 hcitool cmd 3f 1ca
< HCI Command: ogf 0x3f, ocf 0x01ca, plen 0
> HCI Event: 0x0e plen 4
  01 CA FD 11

Cont_tx o/put

4. Continous TX : But dont know whether these commands worked fine or not?

hcitool cmd 0x03 0x001a 0x00
hcitool cmd 0x3f 0x01fb 0x01 0xff 0x00 0x00 0x00 0x00 0x01
hcitool cmd 0x3f 0x01ca 0x62 0x09 0x01 0x00 0x07 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00

( ./cont_tx.sh
< HCI Command: ogf 0x03, ocf 0x001a, plen 1
  00
> HCI Event: 0x0e plen 4
  01 1A 0C 00
< HCI Command: ogf 0x3f, ocf 0x01fb, plen 7
  01 FF 00 00 00 00 01
> HCI Event: 0x0e plen 4
  01 FB FD 00
< HCI Command: ogf 0x3f, ocf 0x01ca, plen 13
  62 09 01 00 07 00 00 00 00 00 00 00 00
> HCI Event: 0x0e plen 4
  01 CA FD 00 )

5.  Continous RX / TX

hcitool cmd 0x3f 0x01fb 0x01 0xff 0x00 0x00 0x00 0x00 0x01
hcitool cmd 0x3f 0x01cc 0x00 0x03 0x62 0x09 0xff 0xff 0x05 0x00 0x1b 0x00 0x07 0x01 0xff 0x01

6. BT SIG RF Testmode: We see only ISCAN PSCAN got enabled for this commands.Is this what happends?
    hcitool cmd 0x06 0x03
    hcitool cmd 0x03 0x05 0x02 0x00 0x03
    hcitool cmd 0x03 0x1a 0x03

7. BLE testing: Transmitter Test.    Dont know whether this works or not?
    hcitool cmd 0x3f 0x01fb 0x01 0xff 0x00 0x00 0x00 0x80 0x00 //disable RF Calibration
    hcitool cmd 0x08 0x001e 0x00 0x00 0x00
    hcitool cmd 0x08 0x001f

** How to verify or conclude or get any understanding that above parameters are correct for hcitool.?
Is there any easy way or direct linux commands to test my wl1837 BT module for compliance?

  • You need to use hcitool to issue the testing commands, as you mentioned above. Please reset and download the BTS/FW between BT/BLE tests. I am sending you a box link for the testing document.

    Thanks

  • Hi Hari,

    Send us the Box link for the document.. Hope reset command and procedure for BTS / FW downloading will be there in the document..

  • Hi Hari,

    We were unable to open this Box link.. Alternately can you send the document through email? We need to send our boards for compliance testing in next 2 days..

  • Thanks Hari,

    We are trying hcitool commands from these document only... Still for most of the commands, we are seeing like below and we are not seeing status 0x00

    Vendor (0x3f|0x01fb) ncmd 1

    Our BT on wl1837 with IMX6+Linux working in Normal Mode like Transfering files with Mobile using Obex Transfer.
    That means TIInit_12.8.32.bts or TIInit_11.8.32.bts downloading fine. Now from last few days we have are trying to Verify BT in Test mode for Compliance.
    As we dont have Spectrum Analyzer with us but we need to give Linux Command list to Vendor who will test it in their lab. I am following steps for verification of the commands.

    1. hciconfig hci0 up

    2. Continous TX test:-
    hcitool cmd 0x03 0x001a 0x00    //0x001A  Write_Scan_Enable
    hcitool cmd 0x3f 0x01fb 0x01 0xff 0x00 0x00 0x00 0x00 0x01   //Send_HCI_VS_DRPb_Enable_RF_Calibration_Enhanced 0xFDFB
    hcitool cmd 0x3f 0x01ca 0x62 0x09 0x01 0x00 0x07 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00   // Send_HCI_VS_DRPb_Tester_Con_TX 0xFDCA

    Am i using correct params and their values? Can you pls explain us param names and their vaules? how to arrive diff vaules for these params?

    3. Restarted my device before firing next test cases... Am i missing some thing other than hcitool (incorrect??) usage? How do i know whether these hcitool commands worked fine or not?

    4.  Continous RX / TX

    hcitool cmd 0x3f 0x01fb 0x01 0xff 0x00 0x00 0x00 0x00 0x01
    hcitool cmd 0x3f 0x01cc 0x00 0x03 0x62 0x09 0xff 0xff 0x05 0x00 0x1b 0x00 0x07 0x01 0xff 0x01


    5. BT SIG RF Testmode: We see only ISCAN PSCAN got enabled for this commands.Is this what happends?
        hcitool cmd 0x06 0x03
        hcitool cmd 0x03 0x05 0x02 0x00 0x03
        hcitool cmd 0x03 0x1a 0x03

    6. BLE testing: Transmitter Test.    Dont know whether this works or not?
        hcitool cmd 0x3f 0x01fb 0x01 0xff 0x00 0x00 0x00 0x80 0x00 //disable RF Calibration
        hcitool cmd 0x08 0x001e 0x00 0x00 0x00
        hcitool cmd 0x08 0x001f

  • I wonder, if Bluez is somehow enabling the page and inquiry scan. Can, you disable scans using hciconfig? or bluetoothctl? also, can you send the complete console log to see, which commands are failing..

    Thanks

  • Hi, Will send you complete logs tomorrow.. But i executed below command which has out device into noscan mode..

    HCI Command: ogf 0x03, ocf 0x001a, plen 1
      00

    ** This is before firing above command..

    hciconfig -a
    hci0:    Type: Primary  Bus: UART
        BD Address: 78:04:73:B2:AD:CE  ACL MTU: 1021:6  SCO MTU: 180:4
        UP RUNNING
        RX bytes:3391 acl:0 sco:0 events:368 errors:0
        TX bytes:64214 acl:0 sco:0 commands:368 errors:0
        Features: 0xff 0xfe 0x2d 0xfe 0xdb 0xff 0x7b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF
        Link mode: SLAVE ACCEPT
        Name: 'tcs-imx6'
        Class: 0x000000
        Service Classes: Unspecified
        Device Class: Miscellaneous,
        HCI Version: 4.2 (0x8)  Revision: 0x0
        LMP Version: 4.2 (0x8)  Subversion: 0xac0d
        Manufacturer: Texas Instruments Inc. (13)

    ** Executing Continous Tx commands..


    root@tcs-imx6:~# ./cont_tx.sh
    < HCI Command: ogf 0x03, ocf 0x001a, plen 1
      00
    > HCI Event: 0x0e plen 4
      01 1A 0C 00
    < HCI Command: ogf 0x3f, ocf 0x01fb, plen 7
      01 FF 00 00 00 00 01
    > HCI Event: 0x0e plen 4
      01 FB FD 00
    < HCI Command: ogf 0x3f, ocf 0x01ca, plen 13
      62 09 01 00 07 00 00 00 00 00 00 00 00
    > HCI Event: 0x0e plen 4
      01 CA FD 00

    ** Scans are not enabled ..

    root@tcs-imx6:~# hciconfig -a
    hci0:    Type: Primary  Bus: UART
        BD Address: 78:04:73:B2:AD:CE  ACL MTU: 1021:6  SCO MTU: 180:4
        UP RUNNING
        RX bytes:3696 acl:0 sco:0 events:374 errors:0
        TX bytes:64263 acl:0 sco:0 commands:374 errors:0
        Features: 0xff 0xfe 0x2d 0xfe 0xdb 0xff 0x7b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF
        Link mode: SLAVE ACCEPT
        Name: 'tcs-imx6'
        Class: 0x000000
        Service Classes: Unspecified
        Device Class: Miscellaneous,
        HCI Version: 4.2 (0x8)  Revision: 0x0
        LMP Version: 4.2 (0x8)  Subversion: 0xac0d
        Manufacturer: Texas Instruments Inc. (13)

  • Please send complete log and also the test command script. You can disable scans like below:

    #hciconfig noscan

  • BT-Console-logs.zip

    Hi Hari,
    Console logs for few test cases 1. BLE Rx 2. BLE TX, 3. BT Sig Mode,4. BT Continous TX and RX, 5. BT cont RX, 6.BT Continous TX are in attached ZIP file. I have taken these hcitool commands from the document you have sent to us through mbox link. I just made hcitool cmds and its params as small script and executig at once for each test case. I am rebooting the my board for every test case.
    I think the service pack gets downloaded for every reboot.
    Iam just executing these hcitool commands and not checking their validity. But I see some commands are detected by HCI Event and some are saying Vendor specific.

  • Ok.. Yes, some may be vendor specific commands. Please refer to the VS command guide for return values.. It is not clear, what is the issue you are referring here..

    www.ti.com/.../swru442

  • Do you mean console logs are correct for respective hcitool commands.. Mean to say Did the executed commands able to take the BT device in to respective RF test mode??

  • I do not see any thing apparent.. We already pointed you to the VS and Testing guides. If there are any issues during testing let us know..

    Thanks


  • To put it another way, Some of the hcitool commands from the test cases not returning 0x00 ( command exection success ).
    Is it expected? . I have done below steps for every test case exection.
    1. Reboot
    2. hciconfig hci0 up
    3. hciconfig hci0 nocan
    4. hcitool commands with respective opcodes and params.

    1. By observing below logs, One of the TI engineer suspected that when we execute  hciconfig hci0 up , seems to be hciconfig ( because its using Bluez)executing more than required hci commands. So suspecting that the BT device not in test mode but in normal operative mode..


    < HCI Command: Read Local Supported Features (0x04|0x0003) plen 0
    > HCI Event: Command Complete (0x0e) plen 12
        Read Local Supported Features (0x04|0x0003) ncmd 1
        status 0x00
        Features: 0xff 0xfe 0x2d 0xfe 0xdb 0xff 0x7b 0x87
    < HCI Command: Read Local Version Information (0x04|0x0001) plen 0
    > HCI Event: Command Complete (0x0e) plen 12
        Read Local Version Information (0x04|0x0001) ncmd 1
        status 0x00
        HCI Version: 4.2 (0x8) HCI Revision: 0x0
        LMP Version: 4.2 (0x8) LMP Subversion: 0xac0d
        Manufacturer: Texas Instruments Inc. (13)
    < HCI Command: Read BD ADDR (0x04|0x0009) plen 0
    > HCI Event: Command Complete (0x0e) plen 10
        Read BD ADDR (0x04|0x0009) ncmd 1
        status 0x00 bdaddr 78:04:73:B2:B7:B9
    < HCI Command: Read Buffer Size (0x04|0x0005) plen 0
    > HCI Event: Command Complete (0x0e) plen 11
        Read Buffer Size (0x04|0x0005) ncmd 1
        status 0x00
        ACL MTU 1021:6 SCO MTU 180:4
    < HCI Command: Read Class of Device (0x03|0x0023) plen 0
    > HCI Event: Command Complete (0x0e) plen 7
        Read Class of Device (0x03|0x0023) ncmd 1
        status 0x00 class 0x001f00
    < HCI Command: Read Local Name (0x03|0x0014) plen 0
    > HCI Event: Command Complete (0x0e) plen 252
        Read Local Name (0x03|0x0014) ncmd 1
        status 0x00 name ''
    < HCI Command: Read Voice Setting (0x03|0x0025) plen 0
    > HCI Event: Command Complete (0x0e) plen 6
        Read Voice Setting (0x03|0x0025) ncmd 1
        status 0x00 voice setting 0x0060
    < HCI Command: Read Number of Supported IAC (0x03|0x0038) plen 0
    > HCI Event: Command Complete (0x0e) plen 5
        Read Number of Supported IAC (0x03|0x0038) ncmd 1
    < HCI Command: Read Current IAC LAP (0x03|0x0039) plen 0
    > HCI Event: Command Complete (0x0e) plen 8
        Read Current IAC LAP (0x03|0x0039) ncmd 1
        IAC 0x9e8b33 (General Inquiry Access Code)
    < HCI Command: Set Event Filter (0x03|0x0005) plen 1
        type 0 condition 0
        Clear all filters
    > HCI Event: Command Complete (0x0e) plen 4
        Set Event Filter (0x03|0x0005) ncmd 1
        status 0x00
    < HCI Command: Write Connection Accept Timeout (0x03|0x0016) plen 2
        timeout 32000
    > HCI Event: Command Complete (0x0e) plen 4
        Write Connection Accept Timeout (0x03|0x0016) ncmd 1
        status 0x00
    < HCI Command: LE Read Buffer Size (0x08|0x0002) plen 0
    > HCI Event: Command Complete (0x0e) plen 7
        LE Read Buffer Size (0x08|0x0002) ncmd 1
        status 0x00 pktlen 0x001b maxpkt 0x0f
    < HCI Command: LE Read Local Supported Features (0x08|0x0003) plen 0
    > HCI Event: Command Complete (0x0e) plen 12
        LE Read Local Supported Features (0x08|0x0003) ncmd 1
        status 0x00 features 0x0100000000000000 (Link Layer supports LE Encryption)
    < HCI Command: LE Read Supported States (0x08|0x001c) plen 0
    > HCI Event: Command Complete (0x0e) plen 12
        LE Read Supported States (0x08|0x001c) ncmd 1
    < HCI Command: Read Local Supported Commands (0x04|0x0002) plen 0
    > HCI Event: Command Complete (0x0e) plen 68
        Read Local Supported Commands (0x04|0x0002) ncmd 1
        status 0x00
        Commands: ffffff03ceffffff0fffff1ff20fe8fe3ff78fff1c00000061f7ffff7f38
    < HCI Command: Write Simple Pairing Mode (0x03|0x0056) plen 1
        mode 0x01
    > HCI Event: Command Complete (0x0e) plen 4
        Write Simple Pairing Mode (0x03|0x0056) ncmd 1
        status 0x00
    < HCI Command: Write Inquiry Mode (0x03|0x0045) plen 1
        mode 2
    > HCI Event: Command Complete (0x0e) plen 4
        Write Inquiry Mode (0x03|0x0045) ncmd 1
        status 0x00
    < HCI Command: Read Inquiry Response Transmit Power Level (0x03|0x0058) plen 0
    > HCI Event: Command Complete (0x0e) plen 5
        Read Inquiry Response Transmit Power Level (0x03|0x0058) ncmd 1
        status 0x00 level 14
    < HCI Command: Read Local Extended Features (0x04|0x0004) plen 1
        page 1
    > HCI Event: Command Complete (0x0e) plen 14
        Read Local Extended Features (0x04|0x0004) ncmd 1
        status 0x00 page 1 max 1
        Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
    < HCI Command: Set Event Mask (0x03|0x0001) plen 8
        Mask: 0xfffffbff07f8bf3d
    > HCI Event: Command Complete (0x0e) plen 4
        Set Event Mask (0x03|0x0001) ncmd 1
        status 0x00
    < HCI Command: Read Stored Link Key (0x03|0x000d) plen 7
        bdaddr 00:00:00:00:00:00 all 1
    > HCI Event: Command Complete (0x0e) plen 8
        Read Stored Link Key (0x03|0x000d) ncmd 1
        status 0x00 max 10 num 0
    < HCI Command: Write Default Link Policy Settings (0x02|0x000f) plen 2
        policy 0x07
        Link policy: RSWITCH HOLD SNIFF
    > HCI Event: Command Complete (0x0e) plen 4
        Write Default Link Policy Settings (0x02|0x000f) ncmd 1
        status 0x00
    < HCI Command: Read Page Scan Activity (0x03|0x001b) plen 0
    > HCI Event: Command Complete (0x0e) plen 8
        Read Page Scan Activity (0x03|0x001b) ncmd 1
        status 0x00 interval 2048 window 18
    < HCI Command: Read Page Scan Type (0x03|0x0046) plen 0
    > HCI Event: Command Complete (0x0e) plen 5
        Read Page Scan Type (0x03|0x0046) ncmd 1
    < HCI Command: LE Set Event Mask (0x08|0x0001) plen 8
        mask 0x1f00000000000000 (Reserved)
    > HCI Event: Command Complete (0x0e) plen 4
        LE Set Event Mask (0x08|0x0001) ncmd 1
        status 0x00
    < HCI Command: LE Read Advertising Channel Tx Power (0x08|0x0007) plen 0
    > HCI Event: Command Complete (0x0e) plen 5
        LE Read Advertising Channel Tx Power (0x08|0x0007) ncmd 1
        status 0x00 level 0xe (dBm)
    < HCI Command: LE Read White List Size (0x08|0x000f) plen 0
    > HCI Event: Command Complete (0x0e) plen 5
        LE Read White List Size (0x08|0x000f) ncmd 1
    < HCI Command: LE Clear White List (0x08|0x0010) plen 0
    > HCI Event: Command Complete (0x0e) plen 4
        LE Clear White List (0x08|0x0010) ncmd 1
        status 0x00
    < HCI Command: Write LE Host Supported (0x03|0x006d) plen 2
    > HCI Event: Command Complete (0x0e) plen 4
        Write LE Host Supported (0x03|0x006d) ncmd 1
    < HCI Command: Delete Stored Link Key (0x03|0x0012) plen 7
        bdaddr 00:00:00:00:00:00 all 1
    > HCI Event: Command Complete (0x0e) plen 6
        Delete Stored Link Key (0x03|0x0012) ncmd 1
        status 0x00 deleted 0
    < HCI Command: Unknown (0x04|0x000b) plen 0
    > HCI Event: Command Complete (0x0e) plen 12
        Unknown (0x04|0x000b) ncmd 1
    < HCI Command: LE Set Advertising Data (0x08|0x0008) plen 32
    > HCI Event: Command Complete (0x0e) plen 4
        LE Set Advertising Data (0x08|0x0008) ncmd 1
        status 0x00
    < HCI Command: LE Set Scan Response Data (0x08|0x0009) plen 32
    > HCI Event: Command Complete (0x0e) plen 4
        LE Set Scan Response Data (0x08|0x0009) ncmd 1
        status 0x00
    < HCI Command: Write Class of Device (0x03|0x0024) plen 3
        class 0x000000
    > HCI Event: Command Complete (0x0e) plen 4
        Write Class of Device (0x03|0x0024) ncmd 1
        status 0x00
    < HCI Command: Write Local Name (0x03|0x0013) plen 248
        name 'tcs-imx6'
    > HCI Event: Command Complete (0x0e) plen 4
        Write Local Name (0x03|0x0013) ncmd 1
        status 0x00
    < HCI Command: Write Extended Inquiry Response (0x03|0x0052) plen 241
        fec 0x00
        Complete local name: 'tcs-imx6'
        TX power level: 14
        Unknown type 0x10 with 8 bytes data
        Complete service classes: 0x110e 0x110c
    > HCI Event: Command Complete (0x0e) plen 4
        Write Extended Inquiry Response (0x03|0x0052) ncmd 1
        status 0x00

    2. I dont see any device got created in /dev/tty* with hci_uart (We are using Bluez stack on top of the hci_uart). Is it correct to fire
    hciattach /dev/tty* texas 115200 flow and then further hcitool commands? Normally at bootup, driver download TIInit_11.8.32.bts into device.

  • Which are the commands, not returning with success? 

    If the HCI device is already initialized by the Bluez driver during bootup, there is no need to re-issue 'hci_attach'. 

    Before running the RF tests, ensure the page and inquiry scans are disabled. And, additionally you may also issue HCI_Reset, before invoking the RF test commands:

    //HCI Reset

    hcitool cmd 0x03 0x03

    Thanks

  • 1. hciconfig hci0 up
     
    root@tcs-imx6:~# hciconfig hci0 noscan
    root@tcs-imx6:~# hcitool cmd 0x03 0x03
    < HCI Command: ogf 0x03, ocf 0x0003, plen 0
    > HCI Event: 0x0e plen 4
      01 03 0C 00
    root@tcs-imx6:~#
    root@tcs-imx6:~# hciconfig
    hci0:    Type: Primary  Bus: UART
        BD Address: 78:04:73:B2:B7:B9  ACL MTU: 1021:6  SCO MTU: 180:4
        UP RUNNING
        RX bytes:3409 acl:0 sco:0 events:370 errors:0
        TX bytes:64227 acl:0 sco:0 commands:370 errors:0

    ## Continuous TX ###

    ## Write_Scan_Enable
    root@tcs-imx6:~# hcitool cmd 0x03 0x001a 0x00
    < HCI Command: ogf 0x03, ocf 0x001a, plen 1
      00
    > HCI Event: 0x0e plen 4
      01 1A 0C 00

    ###   HCI_VS_DRPb_Enable_RF_Calibration_Enhanced

    root@tcs-imx6:~# hcitool cmd 0x3f 0x01fb 0x01 0xff 0x00 0x00 0x00 0x00 0x01
    < HCI Command: ogf 0x3f, ocf 0x01fb, plen 7
      01 FF 00 00 00 00 01
    > HCI Event: 0x0e plen 4
      01 FB FD 00

    ## HCI_VS_DRPb_Tester_Con_TX

    root@tcs-imx6:~# hcitool cmd 0x3f 0x01ca 0x62 0x09 0x01 0x00 0x07 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
    < HCI Command: ogf 0x3f, ocf 0x01ca, plen 13
      62 09 01 00 07 00 00 00 00 00 00 00 00
    > HCI Event: 0x0e plen 4
      01 CA FD 00

  • Hi Hari,

    Is it possible for you to connect to us over webx and observe my BT device behavior and the procedure followed to perform this hcitool commands for RF tests. We need to go for Compliance Testing in couple of days.

    Timings: Today i.e 12th, before 8PM IST

                 Tomorrow i.e 13th March after 8:30 AM IST

    It will be very helpful for us to debug this RF test commands.

    Thanks..

  • Which RF Compliance testing tool are you using and who is the testing house? I will loop in our HW team, if you have specific questions on failed cases etc.. 

  • Dear Hari,

    We are preparing the units to be sent to one of the test house in Hong kong for FCC,CE testing.In fact we had to ship the units today.

    But the test house need to put the EUT (WiFi/BT) module in Test Mode and test various channels,power , Continious Tx/Rx mode etc.

     We  have tried to follow the procedure shared by you . The commands are being issued from Linux OS . We feel that some of the commands not getting executed as we are not receiving any status .

    In this case need your urgent help to resolve this issue, so that the units can be sent to test house.

    Can we have a webex session with you as per your availability. Pls. suggest.

    Thanks

  • Ok.. I will send invite.

  • Hi Hari,
    1.I used btmgmt,btmon instead of hciconfig, hcidump.
    hcidump was not showing any status for some of the hcitool commands(Especially VS). But btmon showing status "success" for the same hcitool cmds.
    Check the attached log screen shot for the same. Let us know if these commands are working fine.

    2. What are the default settings of hci0 when we make it up throw hciconfig hci0 up?

      These are my device states when we make the hci0 powerd on using btmgmt.
        
       settings: powered bondable ssp br/edr le secure-conn

    [mgmt]# info
    Index list with 1 item
    hci0:   Primary controller
            addr 78:04:73:B2:AD:CE version 8 manufacturer 13 class 0x000000
            supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs le advertising secure-conn debug-keys privacy configuration static-addr
            current settings: bondable ssp br/edr le secure-conn
            name tcs-imx6
            short name
    hci0:   Configuration options
            supported options: public-address
            missing options:

    [mgmt]# power on
    hci0 class of device changed: 0x000000
    hci0 Set Powered complete, settings: powered bondable ssp br/edr le secure-conn
    [mgmt]# le off
    Set Low Energy for hci0 failed with status 0x0d (Invalid Parameters)
    [mgmt]# bondable off
    hci0 Set Bondable complete, settings: powered ssp br/edr le secure-conn
    [mgmt]# ssp off
    hci0 Set Secure Simple Pairing complete, settings: powered br/edr le secure-conn
    [mgmt]# le off
    Set Low Energy for hci0 failed with status 0x0d (Invalid Parameters)
    [mgmt]# secure-conn off
    Invalid command in menu main: secure-conn


    3. Even after Reset commands ( hcitool cmd 0x03 0x03 ) also the setting were
       settings: powered bondable ssp br/edr le secure-conn
       Logs here

    bash-5.0# hcitool cmd 0x03 0x03
    Device open failed: No such device
    bash-5.0# hciconfig hci0 up
    bash-5.0# btmgmt
    [mgmt]# info
    Index list with 1 item
    hci0:   Primary controller
            addr 78:04:73:B2:AD:CE version 8 manufacturer 13 class 0x000000
            supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs le advertising secure-conn debug-keys privacy configuration static-addr
            current settings: powered bondable ssp br/edr le secure-conn
            name tcs-imx6
            short name
    hci0:   Configuration options
            supported options: public-address
            missing options:
    [mgmt]# exit
    bash-5.0# hcitool cmd 0x03 0x03
    < HCI Command: ogf 0x03, ocf 0x0003, plen 0
    > HCI Event: 0x0e plen 4
      01 03 0C 00
    bash-5.0# btmgmt
    [mgmt]# info
    Index list with 1 item
    hci0:   Primary controller
            addr 78:04:73:B2:AD:CE version 8 manufacturer 13 class 0x000000
            supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs le advertising secure-conn debug-keys privacy configuration static-addr
            current settings: powered bondable ssp br/edr le secure-conn
            name tcs-imx6
            short name
    hci0:   Configuration options
            supported options: public-address
            missing options:
    [mgmt]# bondable off
    hci0 Set Bondable complete, settings: powered ssp br/edr le secure-conn
    [mgmt]# ssp off
    hci0 Set Secure Simple Pairing complete, settings: powered br/edr le secure-conn
    [mgmt]# le off
    Set Low Energy for hci0 failed with status 0x0d (Invalid Parameters)
    [mgmt]# bredr off
    Set BR/EDR for hci0 failed with status 0x0b (Rejected)
    [mgmt]# secure-conn off
    Invalid command in menu main: secure-conn

    Use "help" for a list of available commands in a menu.
    Use "menu <submenu>" if you want to enter any submenu.
    Use "back" if you want to return to menu main.
    [mgmt]# power off
    hci0 Set Powered complete, settings: br/edr le secure-conn
    [mgmt]# le off
    hci0 Set Low Energy complete, settings: br/edr secure-conn
    [mgmt]# bredr off
    Set BR/EDR for hci0 failed with status 0x0b (Rejected)
    [mgmt]# secure-conn off
    Invalid command in menu main: secure-conn

    Use "help" for a list of available commands in a menu.
    Use "menu <submenu>" if you want to enter any submenu.
    Use "back" if you want to return to menu main.


    4. hci0 showing following settings after After BT Continous TX

    Current settings: 0x00000a81
              Powered
              BR/EDR
              Low Energy
              Secure Connections

    Thanks

  • As, said earlier, if there are any failures or issues let us know. Please run your RF tests and if there are issues let us know.. 

    Thanks