• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 53 subscribers
  • Views 1341 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.

CC2640R2F-Q1: HCI_LE_EnhancedTransmitterTest over ble5stack simple_peripheral -PTM

Albert Bang
Intellectual 1050 points
Part Number: CC2640R2F-Q1
Other Parts Discussed in Thread: BLE-STACK

Hi,

A customer tried to test "HCI_LE_EnhancedTransmitterTest" over a "ble5stack simple_peripheral -PTM" project. They are using the simplelink_cc2640r2_sdk_2_20_00_49.

The "HCI_LE_EnhancedTransmitterTest" command were sent from BTool(v1.42.10BLE5)

As you see below log,  there were no response from the peripheral when the "HCI_LE_EnhancedTransmitterTest" were sent to the peripheral.

please let me know how to clear this issue !

-------------------------------------------------------------------
[3] : <Tx> - 02:05:45.216
-Type           : 0x01 (Command)
-OpCode         : 0x2034 (HCI_LE_EnhancedTransmitterTest)
-Data Length    : 0x04 (4) byte(s)
 TxChannel      : 0x01 (1)
 TestData       : 0x0A (10)
 DtmPktPattern  : 0x00 (0) (Dtm_PRBS9)
 TxPhyType      : 0x01 (1) (Phy 1 Mbps)
Dump(Tx):
0000:01 34 20 04 01 0A 00 01                         .4 .....
--------------------------------------------------------------------
[4] : <Tx> - 02:05:52.269
-Type           : 0x01 (Command)
-OpCode         : 0x2034 (HCI_LE_EnhancedTransmitterTest)
-Data Length    : 0x04 (4) byte(s)
 TxChannel      : 0x00 (0)
 TestData       : 0x00 (0)
 DtmPktPattern  : 0x00 (0) (Dtm_PRBS9)
 TxPhyType      : 0x01 (1) (Phy 1 Mbps)
Dump(Tx):
0000:01 34 20 04 00 00 00 01                         .4 .....
--------------------------------------------------------------------
[5] : <Tx> - 02:06:26.679
-Type           : 0x01 (Command)
-OpCode         : 0x201E (HCI_LE_TransmitterTest)
-Data Length    : 0x03 (3) byte(s)
 TX Channel     : 0x00 (0)
 TestData Length: 0x00 (0)
 TestData       : 00
Dump(Tx):
0000:01 1E 20 03 00 00 00                            .. ....
--------------------------------------------------------------------
[6] : <Rx> - 02:06:26.713
-Type           : 0x04 (Event)
-EventCode      : 0x000E (HCI_CommandCompleteEvent)
-Data Length    : 0x04 (4) bytes(s)
 Packets        : 0x01 (1)
 OpCode         : 0x201E (HCI_LE_TransmitterTest)
 Status         : 0x00 (0) (SUCCESS)
Dump(Rx):
0000:04 0E 04 01 1E 20 00                            ..... .
--------------------------------------------------------------------

  • 0
    TI__Mastermind 37380 points
    Albert,

    I'm looking into this for you. I need to look into the source code of the stack to see if something is going wrong or missing.
  • 0 in reply to Evan Wakefield
    TI__Mastermind 37380 points
    Can you provide the steps that they took to get to this point? As in what BTool commands did they use before this? It would be good if you could send a full log of what they tried to do.
  • 0 in reply to Evan Wakefield
    TI__Mastermind 37380 points

    Also, to be clear, did they follow the full steps provided here in enabling PTM in an application?

    Sorry did not mean to click TI think's resolved. Accidentally clicked it when trying to edit this post. 

  • 0 in reply to Evan Wakefield
    TI__Intellectual 1050 points

    Hi

    Test  procedure is simple.

    1. compile default ble5_simple_peripheral (flashRom_stacklibrary_PTM) and fusing it.

    2. open the BTool

    3. see the rest of step below.

    As far as i know, the full steps mentioned in the ble-stack user guide is already implemented in the ble5_simple_peripheral (flashRom_stacklibrary_PTM). right ?

    [1] : <Info> - 10:03:11.320
    Port opened at 9/21/2018 10:03:11 AM
    --------------------------------------------------------------------
    [2] : <Tx> - 10:03:11.425
    -Type           : 0x01 (Command)
    -OpCode         : 0xFC1D (HCIExt_ResetSystemCmd)
    -Data Length    : 0x01 (1) byte(s)
     Type           : 0x00 (0) (Chip Reset)
    Dump(Tx):
    0000:01 1D FC 01 00                                  .....
    --------------------------------------------------------------------
    [3] : <Rx> - 10:03:11.524
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (HCI_LE_ExtEvent)
    -Data Length    : 0x05 (5) bytes(s)
     Event          : 0x041D (1053) (HCIExt_ResetSystemCmdDone)
     Status         : 0x00 (0) (SUCCESS)
     CmdOpCode      : 0xFC1D (HCIExt_ResetSystemCmd)
    Dump(Rx):
    0000:04 FF 05 1D 04 00 1D FC                         ........
    --------------------------------------------------------------------
    [4] : <Tx> - 10:03:12.026
    -Type           : 0x01 (Command)
    -OpCode         : 0xFE00 (GAP_DeviceInit)
    -Data Length    : 0x08 (8) byte(s)
     ProfileRole    : 0x08 (8) (
                      Central)
     AddrMode       : 0x00 (0) (ADDRMODE_PUBLIC)
     RandomAddr     : 00:00:00:00:00:00
    Dump(Tx):
    0000:01 00 FE 08 08 00 00 00 00 00 00 00             ............
    --------------------------------------------------------------------
    [5] : <Warning> - 10:03:22.050
    GAP Device Initialization Timeout
    Device May Not Function Properly
    --------------------------------------------------------------------
    [6] : <Tx> - 10:03:36.239
    -Type           : 0x01 (Command)
    -OpCode         : 0x0C03 (HCI_Reset)
    -Data Length    : 0x00 (0) byte(s)
    Dump(Tx):
    0000:01 03 0C 00                                     ....
    --------------------------------------------------------------------
    [7] : <Rx> - 10:03:36.257
    -Type           : 0x04 (Event)
    -EventCode      : 0x000E (HCI_CommandCompleteEvent)
    -Data Length    : 0x04 (4) bytes(s)
     Packets        : 0x01 (1)
     OpCode         : 0x0C03 (HCI_Reset)
     Status         : 0x00 (0) (SUCCESS)
    Dump(Rx):
    0000:04 0E 04 01 03 0C 00                            .......
    --------------------------------------------------------------------
    [8] : <Tx> - 10:03:40.829
    -Type           : 0x01 (Command)
    -OpCode         : 0x2034 (HCI_LE_EnhancedTransmitterTest)
    -Data Length    : 0x04 (4) byte(s)
     TxChannel      : 0x00 (0)
     TestData       : 0x00 (0)
     DtmPktPattern  : 0x00 (0) (Dtm_PRBS9)
     TxPhyType      : 0x01 (1) (Phy 1 Mbps)
    Dump(Tx):
    0000:01 34 20 04 00 00 00 01                         .4 .....
    --------------------------------------------------------------------
    [9] : <Tx> - 10:03:58.015
    -Type           : 0x01 (Command)
    -OpCode         : 0x201F (HCI_LE_TestEnd)
    -Data Length    : 0x00 (0) byte(s)
    Dump(Tx):
    0000:01 1F 20 00                                     .. .
    --------------------------------------------------------------------
    [10] : <Rx> - 10:03:58.033
    -Type           : 0x04 (Event)
    -EventCode      : 0x000E (HCI_CommandCompleteEvent)
    -Data Length    : 0x06 (6) bytes(s)
     Packets        : 0x01 (1)
     OpCode         : 0x201F (HCI_LE_TestEnd)
     Status         : 0x0C (12) (CMD_DISALLOWED)
     NumOfPackets   : 0x0000 (0)
    Dump(Rx):
    0000:04 0E 06 01 1F 20 0C 00 00                      ..... ...
    --------------------------------------------------------------------
    [11] : <Tx> - 10:04:04.260
    -Type           : 0x01 (Command)
    -OpCode         : 0x201E (HCI_LE_TransmitterTest)
    -Data Length    : 0x03 (3) byte(s)
     TX Channel     : 0x00 (0)
     TestData Length: 0x00 (0)
     TestData       : 00
    Dump(Tx):
    0000:01 1E 20 03 00 00 00                            .. ....
    --------------------------------------------------------------------
    [12] : <Rx> - 10:04:04.282
    -Type           : 0x04 (Event)
    -EventCode      : 0x000E (HCI_CommandCompleteEvent)
    -Data Length    : 0x04 (4) bytes(s)
     Packets        : 0x01 (1)
     OpCode         : 0x201E (HCI_LE_TransmitterTest)
     Status         : 0x00 (0) (SUCCESS)
    Dump(Rx):
    0000:04 0E 04 01 1E 20 00                            ..... .
    --------------------------------------------------------------------

  • 0 in reply to Albert Bang
    TI__Mastermind 37380 points
    Hi Albert,
    I will update this by Friday.
  • 0 in reply to Albert Bang
    TI__Guru 55305 points
    Hi,

    So the HCI_LE_EnhancedTransmitterTest is not supported unfortunately, we are trying to figure out why it's not supported.

    Meanwhile, if you are interested, you can get an overview regarding which function are supported inside :: icall_hci_tl.c
    Search "HCI_TL_PTM", then you will see hciTranslationTable[ ] which includes all the supported HCI commands under this mode.