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@lists.zephyrproject.org; zephyr-users@lists.zephyrproject.org
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:

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@lists.zephyrproject.org [mailto:zephyr-devel-bounces@lists.zephyrproject.org] On Behalf Of Vikrant More
Sent: Monday, March 12, 2018 3:52 PM
To: zephyr-devel@lists.zephyrproject.org; zephyr-users@lists.zephyrproject.org
Subject: [Zephyr-devel] error while opening file (NFFS)

 

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 fine with previous version.

Could anybody help me to solve this issue ?

 

 

After the build sequence

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@...> wrote:
> 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
>>
>> 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
>> _______________________________________________
>> Zephyr-users mailing list
>> Zephyr-users@lists.zephyrproject.org
>> https://lists.zephyrproject.org/mailman/listinfo/zephyr-users
>
>
_______________________________________________
Zephyr-users mailing list
Zephyr-users@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-users

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
_______________________________________________
Zephyr-users mailing list
Zephyr-users@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-users

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@lists.zephyrproject.org [mailto:zephyr-devel-bounces@lists.zephyrproject.org] On Behalf Of Vikrant More
Sent: Monday, March 12, 2018 3:52 PM
To: zephyr-devel@lists.zephyrproject.org; zephyr-users@lists.zephyrproject.org
Subject: [Zephyr-devel] error while opening file (NFFS)

 

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 fine with previous version.

Could anybody help me to solve this issue ?

 

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@nordicsemi.no>
Cc: zephyr-devel@lists.zephyrproject.org; zephyr-users@lists.zephyrproject.org; Cufi, Carles <Carles.Cufi@...>
Subject: Re: [Zephyr-users] increasing nRF52 Bluetooth range

 

Hello Vinayak,

    NRF_RADIO->TXPOWER = 0x8;  //+8dBm

    err = 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);

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@nordicsemi.no> wrote:

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@lists.zephyrproject.org [mailto:zephyr-users-bounces@lists.zephyrproject.org] On Behalf Of Vikrant More
Sent: Thursday, March 08, 2018 7:53 AM
To: zephyr-devel@lists.zephyrproject.org; zephyr-users@lists.zephyrproject.org; Cufi, Carles <Carles.Cufi@...>
Subject: [Zephyr-users] increasing nRF52 Bluetooth range

 

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 !!  

 

 

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@lists.zephyrproject.org [mailto:zephyr-users-bounces@lists.zephyrproject.org] On Behalf Of Vikrant More
Sent: Thursday, March 08, 2018 7:53 AM
To: zephyr-devel@lists.zephyrproject.org; zephyr-users@lists.zephyrproject.org; Cufi, Carles <Carles.Cufi@...>
Subject: [Zephyr-users] increasing nRF52 Bluetooth range

 

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 !!  

 

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 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,
>
> 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
> #BluetoothMesh ?
>
> As per #BluetoothMesh specs, it should be FIPS-P256 curve.
> Is Zephyr built in *micro*-*ecc* library different than what I am currently
> using ?
>
> Thank You!!
>
> On Sun, Mar 4, 2018 at 1:16 AM, Vikrant More <vikrant8051@...> wrote:
>
> > 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.
> >
> > >>Before this, Admin will Blink LED on BLE Device before transferring
> > #CommonKey to it using Smartphone App.
> > >>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,
> >>
> >> 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 separately.
> >>
> >> 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.
> >>
> >> Johan
> >>
> >> On Sat, Mar 03, 2018, Vikrant More wrote:
> >> > 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 You !!
> >> >
> >> > On Sat, Mar 3, 2018 at 12:57 PM, Vikrant More <vikrant8051@...>
> >> wrote:
> >> >
> >> > > 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 Bluetooth Mesh where every time new
> >> > > Public-Private Key pair get generated on both sides,
> >> > > using which a Master key established after public keys get exchange
> >> over
> >> > > insecure channel.
> >> > >
> >> > > I think it will solve my issue. How to check this mechanism without
> >> > > Android/iOS App after implemented it on Device side ?
> >> > >
> >> > > Thank You !!
> >> > >
> >> > > On Fri, Mar 2, 2018 at 11:20 PM, Vikrant More <vikrant8051@...>
> >> > > wrote:
> >> > >
> >> > >> 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 secure communication at Zephyr App level using
> >> security
> >> > >> keys ?
> >> > >>
> >> > >> ------------------------------------------------------------
> >> > >> ----------------------------------------
> >> > >> This is my implementation where there are 3 characteristics:
> >> > >> 1) 1st (read) characteristic always generates 16 bytes of random data
> >> > >> 2) 2nd (write) characteristic used for authentication
> >> > >> 3) 3rd (write) characteristic which accepts commands
> >> > >>
> >> > >> When BLE device is in factory reset mode,
> >> > >> then Smartphone App read random data from 1st Characteristic & save
> >> it as
> >> > >> #AdminKey (AES-128) for that device.
> >> > >>
> >> > >> Then it again requests(read) another random data from 1st
> >> characteristic
> >> > >> , encrypt it using #AdminKey & send to 2nd characteristic.
> >> > >>
> >> > >> On BLE device side, it will decrypt data using #AdminKey & compare it
> >> > >> with recently send random data. If data matched then BLE device saves
> >> > >> #AdminKey on self flash memory.
> >> > >>
> >> > >> So every device will have unique #AdminKey.
> >> > >>
> >> > >> Now here after, Smartphone who send encrypted random data which is
> >> > >> encrypted using #AdminKey to 2nd characteristic will get #admin
> >> access.
> >> > >> (Random Data from 1st Characteristic)
> >> > >>
> >> > >> Now if I wanna give access to my guests or family members, then in
> >> that
> >> > >> case I have to set 16-bytes of #CommonKey (manually entered number)
> >> for all
> >> > >> BLE devices.
> >> > >>
> >> > >> Before this, Admin will Blink LED on BLE Device before transferring
> >> > >> #CommonKey to it using Smartphone App. Once user confirm it, then
> >> only
> >> > >> #CommonKey get transfer as command to 3rd characteristic & BLE
> >> device save
> >> > >> it as #CommonKey.
> >> > >>
> >> > >> As name suggest, #CommonKey is same for all devices. So here onward,
> >> > >> Smartphone who send encrypted random data using #CommonKey will get
> >> #guest
> >> > >> access of that BLE device. Using #guest access, in case of LED
> >> lights user
> >> > >> can only do On/Off & intensity control.
> >> > >>
> >> > >> So 3rd characteristic only accept commands when user authentic
> >> itself as
> >> > >> #admin or #guest.
> >> > >>
> >> > >> Can I go ahead with this method ?
> >> > >>
> >> > >> But I think it is not secure, since data is exchanged over
> >> unencrypted
> >> > >> link. Isn't it ?
> >> > >>
> >> > >> Is somebody has better robust secure solution as per my requirements
> >> ?
> >> > >>
> >> > >> Thank You !!
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >
> >>
> >
> >

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.

>>Before this, Admin will Blink LED on BLE Device before transferring #CommonKey to it using Smartphone App.
>>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,

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 separately.

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.

Johan

On Sat, Mar 03, 2018, Vikrant More wrote:
> 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 You !!
>
> On Sat, Mar 3, 2018 at 12:57 PM, Vikrant More <vikrant8051@...> wrote:
>
> > 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 Bluetooth Mesh where every time new
> > Public-Private Key pair get generated on both sides,
> > using which a Master key established after public keys get exchange over
> > insecure channel.
> >
> > I think it will solve my issue. How to check this mechanism without
> > Android/iOS App after implemented it on Device side ?
> >
> > Thank You !!
> >
> > On Fri, Mar 2, 2018 at 11:20 PM, Vikrant More <vikrant8051@...>
> > wrote:
> >
> >> 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 secure communication at Zephyr App level using security
> >> keys ?
> >>
> >> ------------------------------------------------------------
> >> ----------------------------------------
> >> This is my implementation where there are 3 characteristics:
> >> 1) 1st (read) characteristic always generates 16 bytes of random data
> >> 2) 2nd (write) characteristic used for authentication
> >> 3) 3rd (write) characteristic which accepts commands
> >>
> >> When BLE device is in factory reset mode,
> >> then Smartphone App read random data from 1st Characteristic & save it as
> >> #AdminKey (AES-128) for that device.
> >>
> >> Then it again requests(read) another random data from 1st characteristic
> >> , encrypt it using #AdminKey & send to 2nd characteristic.
> >>
> >> On BLE device side, it will decrypt data using #AdminKey & compare it
> >> with recently send random data. If data matched then BLE device saves
> >> #AdminKey on self flash memory.
> >>
> >> So every device will have unique #AdminKey.
> >>
> >> Now here after, Smartphone who send encrypted random data which is
> >> encrypted using #AdminKey to 2nd characteristic will get #admin access.
> >> (Random Data from 1st Characteristic)
> >>
> >> Now if I wanna give access to my guests or family members, then in that
> >> case I have to set 16-bytes of #CommonKey (manually entered number) for all
> >> BLE devices.
> >>
> >> Before this, Admin will Blink LED on BLE Device before transferring
> >> #CommonKey to it using Smartphone App. Once user confirm it, then only
> >> #CommonKey get transfer as command to 3rd characteristic & BLE device save
> >> it as #CommonKey.
> >>
> >> As name suggest, #CommonKey is same for all devices. So here onward,
> >> Smartphone who send encrypted random data using #CommonKey will get #guest
> >> access of that BLE device. Using #guest access, in case of LED lights user
> >> can only do On/Off & intensity control.
> >>
> >> So 3rd characteristic only accept commands when user authentic itself as
> >> #admin or #guest.
> >>
> >> Can I go ahead with this method ?
> >>
> >> But I think it is not secure, since data is exchanged over unencrypted
> >> link. Isn't it ?
> >>
> >> Is somebody has better robust secure solution as per my requirements ?
> >>
> >> Thank You !!
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >