• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 146 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.

CC2652P7: Porting SiLab BLE to TI CC2652P7

Bank
Prodigy 70 points
Part Number: CC2652P7

Tool/software:

Hi,

Port an existing Silicon Labs BLE device to the TI CC2652P7 platform while maintaining compatibility with the current application.
The new device must support the following operational guidelines:
  • Control operations should function without requiring an active BLE connection.
  • BLE connection should only be established for the following purposes: Firmware updates (OTA), Remote control setup, Interaction with specialized devices designed for advanced functions.

SDK: simplelink_cc13xx_cc26xx_sdk_8_30_01_01

See more detail in the attachment

Porting SiLab - TI CC2652P7.xlsx

Are there any specific aspects that need to be considered or improved?
Additionally, could you recommend any tools or applications suitable for testing?

Best regards,

Bank

  • 0
    TI__Expert 4390 points

    Hello,

    Thank you for reaching out! This is a bit of an open question, when asking about specific aspects to consider, in regards to what? Also, could you clarify what you'd like to be testing? 

    Best Regards,

    Tarek D

  • 0
    Prodigy 70 points

    Hi,

    I apologize for the delayed response.

    Regarding the existing device, the Advertising PDU configuration is set to ADV_NONCONN_IND. However, I noticed that it is not possible to configure ADV_NONCONN_IND directly via SysCfg.

    To work around this, I copied the ti_ble_config.h and ti_ble_config.c files from the default SysConfig-generated folder into the main project directory and excluded the originals from the build process.

    Subsequently, I modified the following parameter in the code:

    GapAdv_params_t advParams1 = {
  .eventProps =   GAP_ADV_PROP_SCANNABLE,
  .primIntMin =   160,
  .primIntMax =   160,
  .primChanMap =  GAP_ADV_CHAN_ALL,
  .peerAddrType = PEER_ADDRTYPE_PUBLIC_OR_PUBLIC_ID,
  .peerAddr =     { 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa },
  .filterPolicy = GAP_ADV_WL_POLICY_ANY_REQ,
  .txPower =      GAP_ADV_TX_POWER_NO_PREFERENCE,
  .primPhy =      GAP_ADV_PRIM_PHY_1_MBPS,
  .secPhy =       GAP_ADV_SEC_PHY_1_MBPS,
  .sid =          0
};

    After flashing the firmware to the device and observing the advertising behavior using a BLE sniffer, I found that the PDU type was reported as AUX_ADV_IND, which is incorrect based on our intended configuration.

    Could you please advise how to correctly configure the device to use the ADV_NONCONN_IND PDU type?

     

    Best regards,

    Bank

  • 0 in reply to Bank
    TI__Expert 4390 points

    Hello Bank,

    Thank you for providing this information! We will take a look at your issue and get back to you ASAP. Expect an answer by Monday (6-23)

    Best Regards,

    Tarek

  • 0
    Prodigy 70 points

    Hi Tarek,

    Have you any update?

    Best regards,

    Bank

  • 0 in reply to Bank
    TI__Expert 4390 points

    Hello Bank,

    thank you for your patience! Taking a step back, if you would like a non-connectable scannable undirected advertisement, please use the scannable undirected event properties option. If you would like a non-connectable non-scannable undirected advertisement, please use Non-connectable and Non-scannable undirected event properties option. I don't believe there's a need for excluding files from the build.

    I hope this helps!

    Best Regards,

    Tarek D