I'm not able to understand it. Why Zephyr did these type of changes when there is no demo examples for modules like NFFS ? Please help to solve this issue. In tests/subsys/fs/nffs_fs_api/ there are

Hi Vikranth, Zephyr VFS patches got merged yesterday. These changes are not part of v1.11 but got merged yesterday. Please refer to the changes needed to comply with VFS under

Hello, I upgrade to Zephyr v.1.11 & getting this error while opening file using NFFS [general] [ERR] fs_open: fs_open:mount point not found!! error -2 while opening test.txt It was working perfectly

Hello, How to upgrade firmware on #nRF52840_PDK over Bluetooth Link using newly added FOTA feature in v1.11.0 ? Please provide in detail step wise solution if possible. Where I will find demo example

Hi Vikrant, I tried +8dBm settings and I simply see the increased RSSI value on my iPhone scanning for advertisements. Regards, Vinayak

Hello Vinayak, I modified it at stack level so that TX power get set to +8 dBM. For that, I edited /home/vikrant/projects/zephyr/zephyr/subsys/bluetooth/controller/ll_sw/ll_test.c:189:

Hi Vikrant, As I said before: «Feel free to supply the correct h/w Tx Power enumeration to callers of

Hello Vinayak, NRF_RADIO->TXPOWER = 0x8; //+8dBm err = bt_enable(bt_ready); if (err) { printk("Bluetooth init failed (err %d)\n", err); return; }

Hi Vikrant, The Zephyr BLE controller does not implement the Tx power set interface in the upstream code, hence Zephyr controller operates with +0dBm transmit power. Feel free to supply the

Hello, Recently while doing demo test in my office, I found that range of silicon labs SoC with max. +10dbm power = 2 * range of nRF52 with max. +8 dbm power Silicon labs demo kit was executing own

Awesome, thanks! >>If he/she clicks on "yes" then only process go ahead. >>[ Here APP will only connect to Devices which are in vicinity by >>checking their signal strength (RSSI) ] >>So I think,

Hi Vikrant, Zephyr's Bluetooth stack exposes ECC as standard HCI commands & events through subsys/bluetooth/host/hci_ecc.c. And you're right that it's the FIPS P-256 curve that both LE Secure

Hi Johan, https://github.com/kmackay/micro-ecc has support for 5 standard curves: secp160r1, secp192r1, secp224r1, secp256r1, and secp256k1. Out of secp256r1 and secp256k1, which one is used by Zephyr

Hi Johan, Thanks for reply !! Ok, but I don't know how to integrate & use it in my current project since there is no any documentation available about it. So I chose alternate way but will figure out

Hi Vikrant, micro-ecc is what the Zephyr TinyCrypt uses, and it is also what the Zephyr Bluetooth Security Manager (LE pairing) and mesh implementations use, so no need to start installing micro-ecc

Hello World !! I found solution as micro-ecc library -> https://github.com/kmackay/micro-ecc to generate #AdminKey or Master key on both sides without transferring it on insecure Bluetooth Link. Thank

Hello, How to use ECDH mechanism to establish common #AdminKey or Master Key, using functions defined in $zephyr_base/subsys/bluetooth/host/ecc.h for normal BLE devices ? We uses this concept, in

Hello, If I enabled encryption or authentication to access BLE device characteristic, we have to do OOB pairing. But in some cases, it is not possible like budget LED lights. In this case, how to make

Johan, thanks a bunch for your comprehensive reply. You're correct that I started with the mesh_demo configuration and probably "borrowed" code from elsewhere as well, so that explains how I arrived

Hi Martin, Negative 'int' type errors in Zephyr generally map to POSIX error numbers. E.g. 35 is the same as ENOTSUP. Looking through the possible code paths that bt_mesh_init() triggers, it seems