• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 341 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.

LAUNCHXL-CC26X2R1: Last byte in GapScan_setParam not documented

Mario Mateas
Prodigy 30 points

Part Number: LAUNCHXL-CC26X2R1

I'm using simplelink_cc13x2_26x2_sdk_5_20_00_52.A.

I've connected a TI Launchpad to my computer and, through BTool, I'm sending a GapScan_setParam command to it. As I look in the log, I can see that the first lines actually represent a warning, telling me that the last byte was not decoded. I didn't edit anything in the list of command parameters.

This is how the BTool log looks like, after the execution fo the command:

The last byte (the 0x08 marked with red) doesn't seem to be labeled in the log.

The same goes for GapScan_getParam's response in the log (see below). There is a 0x08 which is not documented.

What does this byte represent? How should we call it?

  • 0
    TI__Guru** 101570 points

    Hi,

    Please allow me some time to look into this question.

    For information, I am able to reproduce your observations and I'll reach out to the R&D team to get some feedback.

    Please bear with me.

    Best regards,

  • +1 in reply to Clément
    TI__Guru** 101570 points

    Hi again,

    I have run some tests and the content of AdvRepportFields should actually be on 2 bytes. In other words, in your case, its content should be 0x08A7. It means, in your case the field SCAN_ADVRPT_FLD_DATALEN is also enabled.

    For additional details, you can refer to the file gap_scanner.h and the enum GapScan_AdvRptField_t (copied below for convenience).

    /// Fields of Adv Report
enum GapScan_AdvRptField_t {
  SCAN_ADVRPT_FLD_EVENTTYPE      = BV( 0), //!< eventType field
  SCAN_ADVRPT_FLD_ADDRTYPE       = BV( 1), //!< addrType field
  SCAN_ADVRPT_FLD_ADDRESS        = BV( 2), //!< address field
  SCAN_ADVRPT_FLD_PRIMPHY        = BV( 3), //!< primPhy field
  SCAN_ADVRPT_FLD_SECPHY         = BV( 4), //!< secPhy field
  SCAN_ADVRPT_FLD_ADVSID         = BV( 5), //!< advSid field
  SCAN_ADVRPT_FLD_TXPOWER        = BV( 6), //!< txPower field
  SCAN_ADVRPT_FLD_RSSI           = BV( 7), //!< RSSI field
  SCAN_ADVRPT_FLD_DIRADDRTYPE    = BV( 8), //!< dirAddrType field
  SCAN_ADVRPT_FLD_DIRADDRESS     = BV( 9), //!< dirAddress field
  SCAN_ADVRPT_FLD_PRDADVINTERVAL = BV(10), //!< prdAdvInterval field
  SCAN_ADVRPT_FLD_DATALEN        = BV(11), //!< dataLen field
};

    I have reported the issue and it will be addressed in a future SDK release.

    Thank you for your help,

    Best regards,