API parameters definition is miss.

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
RuCh_2181101
Level 3
Level 3
5 likes given First like received First like given

Dear Sir,

     We follow the puart_control and trace the source code.

     Some definition is unknown.

     One is blecon_Conn (UINT8 conn_mode, BD_ADDR peer_addr, UINT8 peer_addr_type)

     We can trace others to find out the value of conn_mode and know the meaning.

     But no information about peer_addr_type. It should be RANDOM and PUBLIC. But how about the definition of their value ?

     Another is HCIULP_ADV_PACKET_REPORT_WDATA, you can see it in puart_control_send_adv_report.

void puart_control_send_adv_report(HCIULP_ADV_PACKET_REPORT_WDATA *evt)

{

        int i;

        test_puart_write(PUART_CONTROL_EVENT_ADVERTISEMENT_REPORT);

        test_puart_write(9 + evt->dataLen);     // length

        test_puart_write(evt->eventType);

        test_puart_write(evt->addressType);

     Again, how about the definition of evertType ?

Best Regards,

Rush Chen

0 Likes
1 Solution

For eventtype (6), it has been renamed from ADV_DISCOVER_IND to ADV_SCAN_IND.

View solution in original post

0 Likes
5 Replies
Anonymous
Not applicable

Although there are no definition, the value should be the same with what the spec describes ^_^

0 Likes

Do you know where can find the detail value ?

0 Likes

peer_addr_type is BLE Spec specific.

eventType = advertisement indication or a scan response, also BLE Spec related.

0 Likes

Hi Sir,

  After checking the BLE Spec.

  Add_type

  0   -> public address

  1   -> random address

eventType

  0   -> ADV_IND

  1   -> ADV_DIRECT_IND

  2   -> ADV_NONCONN_IND

  3   -> SCAN_REQ

  4   -> SCAN_RSP

  5   -> CONNECT_REQ

  6   -> ADV_DISCOVER_IND

   Am I right ?

Best Regards,

Rush Chen

0 Likes

For eventtype (6), it has been renamed from ADV_DISCOVER_IND to ADV_SCAN_IND.

0 Likes