|
Bluetooth BLE device not get discount
Vikrant More <vikrant8051@...>
Hello, Currently I am working on Zephyr Bluetooth APIs to build normal Services-Characteristics based BLE device. I've observed following things: 1) sometimes when app (for eg. nRF Connect) closes even after that device doesn't get disconnected 2) sometimes even smartphone Bluetooth switched off then also device doesn't go from connect state to disconnect state. Success ratio is approx. 60-70% Since device doesn't go in disconnected mode, it stop advertising & I have to restart it for reconnection. Is it because of App or smartphone OS not actually disconnecting at background level ? Thank You !!
|
|
|
|
Re: [Zephyr-devel] error while opening file (NFFS)
Pallala, Ramakrishna <ramakrishna.pallala@...>
Hi Vikranth,
The main change is the introduction of mount point which will allow us to have multiple file systems at once. Now the file system mounting responsibility to given to application and it should tie the backend storage which is intended to use.
We have three examples as of today which demonstrate the usage of file systems API’s:
tests/subsys/fs/fat_fs_api/ => Demonstrate FATFS usage, I would suggest you look into it as it is simple and not many files are there. tests/subsys/fs/nffs_fs_api/ => Demonstrate NFFS usage tests/subsys/fs/multi-fs/ => Demonstrate both FATFS and NFFS usage together.
Look into the test_*_mount.c files in these tests which will show how to mount a file system from Application.
This feature is destined for v1.12 release and I will add the documentation accordingly.
Thanks, Ram
From: Vikrant More [mailto:vikrant8051@...]
Sent: Monday, March 12, 2018 4:46 PM To: Pallala, Ramakrishna <ramakrishna.pallala@...> Cc: zephyr-devel@...; zephyr-users@... Subject: Re: [Zephyr-devel] error while opening file (NFFS)
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 multiple files ....which one to refer ?? What is proper sequence for initialization ? Please give me sample code to open, read, write & close for file using NFFS as per latest patches.
On Mon, Mar 12, 2018 at 4:06 PM, Pallala, Ramakrishna <ramakrishna.pallala@...> wrote:
|
|
|
|
Re: [STM32L4] looks there is no way to flash and debug?
Erwan Gouriou
Ok, so openoncd support is indeed not provided for this board. And it happens it is not present neither in openocd. Though, it will work by re-using configuration provided for nucleo_l476rg. Duplicate following files and move them into nucleo_l432kc folder: -support/openocd.org -board.cmake
On 13 March 2018 at 09:47, Carles Perello <carles.perello@...> wrote: After the build sequence
|
|
|
|
Re: [STM32L4] looks there is no way to flash and debug?
Carles Perello
After the build sequence
toggle quoted messageShow quoted text
cmake -GNinja -DBOARD=nucleo_l432kc .. ninja [1/95] Generating always_rebuild Building for board nucleo_l432kc [90/95] Linking C executable zephyr/zephyr_prebuilt.elf Memory region Used Size Region Size %age Used FLASH: 11376 B 256 KB 4.34% SRAM: 4576 B 64 KB 6.98% IDT_LIST: 132 B 2 KB 6.45% [95/95] Linking C executable zephyr/zephyr.elf ninja flash [0/1] Flashing nucleo_l432kc flash is not supported with this board. Please check the documentation for alternate instructions. I am using zephyr release 1.11.0 under windows (using msys2) regards
On Tue, Mar 13, 2018 at 9:41 AM, Erwan Gouriou <erwan.gouriou@linaro.org> wrote:
Hi Carles,
|
|
|
|
Re: [STM32L4] looks there is no way to flash and debug?
Erwan Gouriou
Hi Carles, There is no particular limitation on STM32L4 that should prevent you to flash and debug. Can you provide us more details on your set up to understand what is going on (board, SW, environment, error you encounter..)? Cheers Erwan
On 13 March 2018 at 09:35, Carles Perello <carles.perello@...> wrote: Hello
|
|
|
|
[STM32L4] looks there is no way to flash and debug?
Carles Perello
Hello
I am starting to do a development on STM32L4 nucleo based boards....but seems that something is misconfigured as I cant do flash or debug (either make or ninja). Any pointer to what I can change to make is work is more than welcome :-) regards Carles
|
|
|
|
Re: [Zephyr-devel] error while opening file (NFFS)
Vikrant More <vikrant8051@...>
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 multiple files ....which one to refer ??
On Mon, Mar 12, 2018 at 4:06 PM, Pallala, Ramakrishna <ramakrishna.pallala@...> wrote:
|
|
|
|
Re: [Zephyr-devel] error while opening file (NFFS)
Pallala, Ramakrishna <ramakrishna.pallala@...>
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 tests/subsys/fs/nffs_fs_api/ on the latest code.
Thanks, Ram
From: zephyr-devel-bounces@... [mailto:zephyr-devel-bounces@...]
On Behalf Of Vikrant More
Sent: Monday, March 12, 2018 3:52 PM To: zephyr-devel@...; zephyr-users@... Subject: [Zephyr-devel] error while opening file (NFFS)
Hello, I upgrade to Zephyr v.1.11 & getting this error while opening file using NFFS It was working perfectly fine with previous version. Could anybody help me to solve this issue ?
|
|
|
|
error while opening file (NFFS)
Vikrant More <vikrant8051@...>
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
|
|
|
|
about to use FOTA & Lightweight flash storage layer for constrained devices from v1.11.0
Vikrant More <vikrant8051@...>
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.Is it "$zephyr_base/samples/drivers/soc_flash_nrf5" ? If we try to update value of variable stored on flash, then we have to erase complete page or driver should write down new value on new address location. Is newly added flash storage layer take care of that since in general SoC supports only 10K erase cycle ? Thank You !!
|
|
|
|
Re: increasing nRF52 Bluetooth range
Chettimada, Vinayak Kariappa
Hi Vikrant,
I tried +8dBm settings and I simply see the increased RSSI value on my iPhone scanning for advertisements.
Regards, Vinayak
From: Vikrant More [mailto:vikrant8051@...]
Sent: Thursday, March 08, 2018 11:46 AM To: Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...> Cc: zephyr-devel@...; zephyr-users@...; Cufi, Carles <Carles.Cufi@...> Subject: Re: [Zephyr-users] increasing nRF52 Bluetooth range
Hello Vinayak, I modified it at stack level so that TX power get set to +8 dBM. For that, I edited these 2 files. But unfortunately didn't found any difference in range. Thank You !!
On Thu, Mar 8, 2018 at 3:47 PM, Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...> wrote:
|
|
|
|
Re: increasing nRF52 Bluetooth range
Vikrant More <vikrant8051@...>
Hello Vinayak, I modified it at stack level so that TX power get set to +8 dBM./home/vikrant/projects/zephyr/zephyr/subsys/bluetooth/controller/ll_sw/ll_test.c:189: radio_tx_power_set(8); /home/vikrant/projects/zephyr/zephyr/subsys/bluetooth/controller/ll_sw/ctrl.c:5902: radio_tx_power_set(8); Thank You !!
On Thu, Mar 8, 2018 at 3:47 PM, Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...> wrote:
|
|
|
|
Re: increasing nRF52 Bluetooth range
Chettimada, Vinayak Kariappa
Hi Vikrant,
As I said before: «Feel free to supply the correct h/w Tx Power enumeration to callers of https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/bluetooth/controller/hal/nrf5/radio/radio.c#L112”
Please review the callers of “radio_tx_power_set”
One for sure is https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/bluetooth/controller/ll_sw/ctrl.c#L5902
Supply 0x08 instead of 0 as the current param.
Regards, Vinayak
From: Vikrant More [mailto:vikrant8051@...]
Sent: Thursday, March 08, 2018 9:56 AM To: Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...> Cc: zephyr-devel@...; zephyr-users@...; Cufi, Carles <Carles.Cufi@...> Subject: Re: [Zephyr-users] increasing nRF52 Bluetooth range
Hello Vinayak, NRF_RADIO->TXPOWER = 0x8; //+8dBm
I modified power to +8 dBM as per your suggestion but didn't find any improvement in the range. Am I missing something besides this ? Thank You !!
On Thu, Mar 8, 2018 at 1:57 PM, Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...> wrote:
|
|
|
|
Re: increasing nRF52 Bluetooth range
Vikrant More <vikrant8051@...>
Hello Vinayak, NRF_RADIO->TXPOWER = 0x8; //+8dBmerr = bt_enable(bt_ready); if (err) { printk("Bluetooth init failed (err %d)\n", err); return; } bt_conn_cb_register(&conn_callbacks); bt_conn_auth_cb_register(&auth_cb_display);
On Thu, Mar 8, 2018 at 1:57 PM, Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...> wrote:
|
|
|
|
Re: increasing nRF52 Bluetooth range
Chettimada, Vinayak Kariappa
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 correct h/w Tx Power enumeration to callers of https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/bluetooth/controller/hal/nrf5/radio/radio.c#L112
nRF52840 supports +8dBm and Zephyr controller supports external power amplifiers too using the PA/LNA GPIO lines, in case you want your h/w design to have external chips to get further tx power.
Regards, Vinayak
From: zephyr-users-bounces@... [mailto:zephyr-users-bounces@...]
On Behalf Of Vikrant More
Sent: Thursday, March 08, 2018 7:53 AM To: zephyr-devel@...; zephyr-users@...; Cufi, Carles <Carles.Cufi@...> Subject: [Zephyr-users] increasing nRF52 Bluetooth range
Hello, Recently while doing demo test in my office, I found that
Silicon labs demo kit was executing own stack.
Is this because of only +2dbm difference ? How to increase nRF52 range by configuring Zephyr ? Thank You !!
|
|
|
|
increasing nRF52 Bluetooth range
Vikrant More <vikrant8051@...>
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 stack. Is this because of only +2dbm difference ? How to increase nRF52 range by configuring Zephyr ? Thank You !!
|
|
|
|
Re: Securing BLE device communication without OOB pairing (multiple devices)
Vikrant More <vikrant8051@...>
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, this method may solve the issue of Authentication. Am >>I right ? But I'm waiting for solution for above mentioned query. If am using Human to authenticate, his own device just before ECDH key agreement process, is that enough in case of no OOB channel? As per my understanding, problem arises only when user click on "YES" even when he has not seen Blinking LED. That means user App is connected to attacker Device & it will share #CommonKey of his devices to attacker. Are there any flaws in this mechanism besides this ? ------------------------------------------------------------------------------------ Have you seen, this video about #BluetoothMesh ? I think Bluetooth SIG has twitted about them sometimes before. As per my understanding, they have not used input OOB, output OOB or static OOB for authentication. On my inquiry, they reply as: "The authentification is automatic, comming from the signal power measured by the smartphone. You have to go 15/20cm from the device you want to pair." In this case, what is your opinion ? ------------------------------------------------------------------------ Alternate Way (which is final solution if there is no OOB channel for authentication): Device after flashing firmware on it whenever get power will generate random no. & stored it on flash memory & will not create it again in future. Then after every reboot it will send that random no. on device UART terminal. Based on that unique Random no. manufacturer has to create QR code & label it on that device. This is most secured way but some people will not understand its importance since as company it will be burden for them. -----------------------------------------------------------------------------
On Mar 4, 2018 11:48 AM, "Johan Hedberg" <johan.hedberg@...> wrote: Hi Vikrant,
|
|
|
|
Re: Securing BLE device communication without OOB pairing (multiple devices)
Hi Vikrant,
toggle quoted messageShow quoted text
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 Connections (LE Security Manager enhancement that debuted with Bluetooth 4.1) and Mesh Provisioning use. The micro-ecc library that TinyCrypt has a copy of can be found here: ext/lib/crypto/tinycrypt/source/ecc*.c The main header file is here: ext/lib/crypto/tinycrypt/include/tinycrypt/ecc.h Johan
On Sun, Mar 04, 2018, Vikrant More wrote:
Hi Johan,
|
|
|
|
Re: Securing BLE device communication without OOB pairing (multiple devices)
Vikrant More <vikrant8051@...>
Hi Johan, Out of secp256r1 and secp256k1, which one is used by Zephyr #BluetoothMesh ?https://github.com/kmackay/micro-ecc has support for 5 standard curves: secp160r1, secp192r1, secp224r1, secp256r1, and secp256k1. As per #BluetoothMesh specs, it should be FIPS-P256 curve. Is Zephyr built in micro-ecc library different than what I am currently using ?
On Sun, Mar 4, 2018 at 1:16 AM, Vikrant More <vikrant8051@...> wrote:
|
|
|
|
Re: Securing BLE device communication without OOB pairing (multiple devices)
Vikrant More <vikrant8051@...>
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 how to use Zephyr's library in coming days. >>Once user confirm it, then only #CommonKey get transfer as command to 3rd characteristic & BLE device save it as #CommonKey. >>>>You can acheive confidentiality with the ECDH method, but without some >>>>OOB mechanism you won't be able to securely authenticate the peer you're >>>>talking to. So I don't see this as any different than doing pairing >>>>using NoInputNoOutput as the IO capability.  Here, before initiating ECDH to generate share secret , Smartphone App will send commands to LED lights that will blink it for while & App will ask Admin User -> "Have you seen any Blinking LED ?" 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, this method may solve the issue of Authentication. Am I right ? May be it is not enough....but I don't have any other option since LED Lights generally does not have OOB channels. I can't use NFC since not every phone have that feature. So ... ?? Thank You !!
On Sat, Mar 3, 2018 at 9:18 PM, Johan Hedberg <johan.hedberg@...> wrote: Hi Vikrant,
|
|
|