Hi Vinayak, Ok, so I modified my code as .... static void bt_le_adv_refresh(void) { int err = 0; err = bt_le_adv_start(BT_LE_ADV_CONN, ad, ARRAY_SIZE(ad), sd, ARRAY_SIZE(sd)); if

Hi Vikrant, If you have a connection active, you cannot start another connectable advertising unless you start supporting more than one active connection. Use non-connectable or scannable advertising

Hi all, Maybe you can use crypto device on your product. https://www.microchip.com/wwwproducts/en/ATECC508A You also need to develop an application to configure crypto device chip. Then after

Hi Johan, This is log, Thanks, [bt] [DBG] process_events: (0x20001198) ev->state 0 [bt] [DBG] hci_tx_thread: (0x20001198) Calling k_poll with 2 events [bt] [DBG] bt_hci_cmd_send_sync: (0x20002c54)

Hi Vikrant, You'll need to debug this more then, i.e. get HCI logs and enable debug logs for hci_core.c. Johan

Hi Johan, static void bt_le_adv_refresh(void) { int err,i; for(i=0; i<=14; i++) { name_buffer[i]= '@'; // it is global array } sd[0].data = name_buffer;

Hi Vikrant, You also need to update sd[0].data_len. E.g. sd[0].data_len = strlen(name_buffer); Doing bt_le_adv_stop() and bt_le_adv_start() with a new set of parameters should work. Johan

Hi, I've added functionality where user can change BLE device name which is part of scan response by calling sd[0].data = name_buffer; err = bt_le_adv_start(BT_LE_ADV_CONN, ad,

Hi, I've now updated the PR with a third patch that adds this new Kconfig option for Mesh (called CONFIG_BT_MESH_DEBUG_USE_ID_ADDR). Johan

Hi Vakul, Thanks for reply !! No, APP can't differentiate between Genuine & Fake device. And Yes, user by mistake can connect with his neighbor/attacker Device. solution - 1) APP will check RSSI

Hi Andrew I am using nxp frdm_k64f (has cortex M4 core). In my application, I have a printf() at beginning. This is causing bus fault. Replacing it with an infinite while(1) loop hides the bus fault

Hi Kai, Yes, that's correct. Could you also add a comment to the PR that you've tested it? (this helps getting it merged quicker) I'm also thinking of adding a new Kconfig entry (with a depends

Hi Vikrant I am curious to understand about your security implementation. I work in area of TLS security and I am not bluetooth security expert. In your case, does the app need to

Hi all, I've been waiting for FOTA and FCB support in zephyr and now when it is supported, I cannot see any samples available or proper documentation to use these features in my project. Any help

Hi Johan, Just tested it, it works well, evidence is as below. Adv address is static even if I reset my micro:bit. I guess this address is from Nordic chipset, NRF_FICR->DEVICEADDR, correct?

Hi, In my current project, I haven't implemented OOB pairing ( BLE based smart lights) Using Zephyr built-in ECDH library, shared secret (using secp256r1 curve) get created on Device as well as on APP

I forgot to mention that if this is for Mesh, you'd take the new option into use with something like the following: --- a/subsys/bluetooth/host/mesh/adv.c +++ b/subsys/bluetooth/host/mesh/adv.c @@

Hi Kai, Here's a completely untested pull request which adds the new flag: https://github.com/zephyrproject-rtos/zephyr/pull/6720 Could you try it out and let me know if it works for you? Johan

Hi Johan, The reason I want to use static address is that it will be easy to distinguish on Bluetooth packet sniffer. Currently, if there is a Bluetooth noisy background, it's hard to trace the mesh

It looks like you are getting two exceptions in a row. Were you able to determine the source of the bus fault? That seems like the real issue. What platform is this on? Andrew