Date   

CONFIG_BT_PRIVACY cannot be enabled with Hci_uart sample #nrf52832 #hci

icephyr
 

Hi guys, I met a problem here and hop anybody can help.

I want to enable the config CONFIG_BT_PRIVACY, and according to the official document, the config depends on BT_SMP BT_CONN BT_HCI_HOST BT_HCI and BT。 So I have to set all these configs above to  "y"  first, but BT_HCI_HOST conflicts with config BT_HCI_RAW and I have to disable BT_HCI_RAW config if I want to enable BT_HCI_HOST.  But the hci_uart sample will compiled with errors if BT_HCI_RAW is disabled.

So I wonder how to enable CONFIG_BT_PRIVACY in hci_uart sample ?

thanks
config BT_HCI_HOST
  # Virtual/hidden option to make the conditions more intuitive
  bool
  default y
  depends on !BT_HCI_RAW
  select POLL
 
config BT_PRIVACY
    bool
    prompt "Privacy Feature" if BT_SMP && BT_CONN && BT_HCI_HOST && BT_HCI && BT depends on BT_SMP && BT_CONN && BT_HCI_HOST && BT_HCI && BT help Enable local Privacy Feature support. This makes it possible to use Resolvable Private Addresses (RPAs).


Re: Invitation: Zephyr Bug Triage @ Thu 6 Dec 2018 10am - 11am (CST) (Kumar Gala)

Nashif, Anas
 

From: devel@... [mailto:devel@...] On Behalf Of Lincoln Simmons
Sent: Wednesday, December 5, 2018 9:58 PM
To: Kumar Gala <kumar.gala@...>
Cc: devel@...; tsc-private@...
Subject: Re: [Zephyr-devel] Invitation: Zephyr Bug Triage @ Thu 6 Dec 2018 10am - 11am (CST) (Kumar Gala)

 

Is it possible to join the Slack channel even if we don't have an email from one of the approved domains?

 

Thanks,

Lincoln Simmons

 

On Wed, Dec 5, 2018, 10:00 AM Kumar Gala <kumar.gala@...> wrote:

All,

 

We are going to have our first Bug Triage meeting in hope of working on reducing the bug count for the 1.14/LTS release.  Will use both a Zoom call and slack channel #triage.

 

Thanks

 

- kumar



Begin forwarded message:

 

From: Brett Preston <bpreston@...>

Subject: Invitation: Zephyr Bug Triage @ Thu 6 Dec 2018 10am - 11am (CST) (Kumar Gala)

Date: December 5, 2018 at 10:48:38 AM CST

Reply-To: Brett Preston <bpreston@...>

 

Zephyr Bug Triage

Zephyr Working Group is inviting you to a scheduled Zoom meeting.

Join Zoom Meeting
https://zoom.us/j/993312203

One tap mobile
+16699006833,,993312203# US (San Jose)
+16465588656,,993312203# US (New York)

Dial by your location
+1 669 900 6833 US (San Jose)
+1 646 558 8656 US (New York)
+1 877 369 0926 US Toll-free
+1 855 880 1246 US Toll-free
Meeting ID: 993 312 203
Find your local number: https://zoom.us/u/ankEMRagf

 

 

When

Thu 6 Dec 2018 10am – 11am Central Time - Chicago

Where

https://zoom.us/j/993312203 (map)

Calendar

Kumar Gala

Who

(Guest list has been hidden at organiser's request)

Going (kumar.gala@...)?   Yes - Maybe - No    more options »

Invitation from Google Calendar

You are receiving this email at the account kumar.gala@... because you are subscribed for invitations on calendar Kumar Gala.

To stop receiving these emails, please log in to https://www.google.com/calendar/ and change your notification settings for this calendar.

Forwarding this invitation could allow any recipient to modify your RSVP response. Learn More.

 


Re: Invitation: Zephyr Bug Triage @ Thu 6 Dec 2018 10am - 11am (CST) (Kumar Gala)

Lincoln Simmons
 

Is it possible to join the Slack channel even if we don't have an email from one of the approved domains?

Thanks,
Lincoln Simmons


On Wed, Dec 5, 2018, 10:00 AM Kumar Gala <kumar.gala@...> wrote:
All,

We are going to have our first Bug Triage meeting in hope of working on reducing the bug count for the 1.14/LTS release.  Will use both a Zoom call and slack channel #triage.

Thanks

- kumar

Begin forwarded message:

From: Brett Preston <bpreston@...>
Subject: Invitation: Zephyr Bug Triage @ Thu 6 Dec 2018 10am - 11am (CST) (Kumar Gala)
Date: December 5, 2018 at 10:48:38 AM CST
Reply-To: Brett Preston <bpreston@...>

Zephyr Bug Triage

Zephyr Working Group is inviting you to a scheduled Zoom meeting.

Join Zoom Meeting
https://zoom.us/j/993312203

One tap mobile
+16699006833,,993312203# US (San Jose)
+16465588656,,993312203# US (New York)

Dial by your location
+1 669 900 6833 US (San Jose)
+1 646 558 8656 US (New York)
+1 877 369 0926 US Toll-free
+1 855 880 1246 US Toll-free
Meeting ID: 993 312 203
Find your local number: https://zoom.us/u/ankEMRagf



When
Thu 6 Dec 2018 10am – 11am Central Time - Chicago
Where
https://zoom.us/j/993312203 (map)
Calendar
Kumar Gala
Who
(Guest list has been hidden at organiser's request)
Going (kumar.gala@...)?   Yes - Maybe - No    more options »

Invitation from Google Calendar

You are receiving this email at the account kumar.gala@... because you are subscribed for invitations on calendar Kumar Gala.

To stop receiving these emails, please log in to https://www.google.com/calendar/ and change your notification settings for this calendar.

Forwarding this invitation could allow any recipient to modify your RSVP response. Learn More.



Re: How to configure BLE Mesh FN and LPN?

Johan Hedberg
 

Hi Frank,

You need to have CONFIG_BT_MESH_FRIEND=y and/or CONFIG_BT_MESH_LOW_POWER=y enabled to get access to Friendship functionality. You might also want to look at the various BT_MESH_LPN_* and BT_MESH_FRIEND_* options found in subsys/bluetooth/host/mesh/Kconfig, however their default values should be enough to get you started.

As Friend there’s nothing special you need to do in your application, except enable the Kconfig option for it and make sure the corresponding Configuration Model State is enabled (either statically as the default value or by a configuration client).

As LPN you need to call bt_mesh_lpn_set(true) to go into Low Power mode. The reason why this is at runtime is to allow for devices that have variable power sources, e.g. an internal battery but may also be plugged to a stable external power source from time to time. The selection of Friend node happens automatically, but you can control the process by setting CONFIG_BT_MESH_LPN_RECV_WIN_FACTOR, CONFIG_BT_MESH_LPN_RSSI_FACTOR and CONFIG_BT_MESH_LPN_MIN_QUEUE_SIZE to desired values. To get a good understanding of these and how they influence the Friend Offer Delay calculation please refer to the Mesh specification (sections 3.6.6.3.1 and 3.6.6.4.1 in particular).

As for meshctl from BlueZ, I’m not sure if it has any Friendship features. It can definitely not act as a Friend or LPN since it is GATT-only (Friendship is an advertising-only concept in the current spec), but it might have Configuration Client support to toggle the Friend state at runtime (note: LPN has no matching Configuration Model state so you need to use the Zephyr API I mentioned earlier).

Johan

On 5 Dec 2018, at 19.02, frv <@frv> wrote:

Hallo Zephyr Community, Johan,

So far I'm very impressed with the possibilities Zephyr and its BT Mesh framework already offers.
I recently played around successfully with the Generic On/Off sample application deployed on multiple nRF boards creating a BLE Mesh network.
I modified a little bit the code to have the use case I wanted to implement.

As far as I can see in the current Mesh code base v1.13 there is already support for implementing a Lower Power and a Friend node.

I'm just wondering how configuration is actually done, I would think a lower power node must say which is his friend node or vice versa? Maybe I missed it but I can't see anything implemented in the meshctl tool for doing this. And beside setting some defines in the code, is there additional coding needed.

Any help is very welcome,
Thanks in advance,
Best regards,
Frank




Re: Zephyr documentation

Carles Cufi
 

Hi Mayank,

 

A good start would be here: https://docs.zephyrproject.org/latest/devices/index.html

 

Then depending on what kind of driver you want to write my advice would be to look at an existing one and inspect the code in order to understand how it is implemented.

 

Carles

 

From: devel@... <devel@...> On Behalf Of Mayank Upadhyay
Sent: 05 December 2018 19:49
To: devel@...
Subject: [Zephyr-devel] Zephyr documentation

 

Hi, I am new to this Zephyr platform but I have worked on some other RTOs platform for quite some time and I want to get started with this platform by writing my own driver but I didn't get the appropriate documentation so can you guys help me out with this?


Zephyr documentation

Mayank Upadhyay
 

Hi, I am new to this Zephyr platform but I have worked on some other RTOs platform for quite some time and I want to get started with this platform by writing my own driver but I didn't get the appropriate documentation so can you guys help me out with this?


How to configure BLE Mesh FN and LPN?

frv
 

Hallo Zephyr Community, Johan,

So far I'm very impressed with the possibilities Zephyr and its BT Mesh framework already offers.
I recently played around successfully with the Generic On/Off sample application deployed on multiple nRF boards creating a BLE Mesh network.
I modified a little bit the code to have the use case I wanted to implement.

As far as I can see in the current Mesh code base v1.13 there is already support for implementing a Lower Power and a Friend node.

I'm just wondering how configuration is actually done, I would think a lower power node must say which is his friend node or vice versa? Maybe I missed it but I can't see anything implemented in the meshctl tool for doing this. And beside setting some defines in the code, is there additional coding needed.

Any help is very welcome,
Thanks in advance,
Best regards,
Frank


Invitation: Zephyr Bug Triage @ Thu 6 Dec 2018 10am - 11am (CST) (Kumar Gala)

Kumar Gala
 

All,

We are going to have our first Bug Triage meeting in hope of working on reducing the bug count for the 1.14/LTS release.  Will use both a Zoom call and slack channel #triage.

Thanks

- kumar

Begin forwarded message:

From: Brett Preston <bpreston@...>
Subject: Invitation: Zephyr Bug Triage @ Thu 6 Dec 2018 10am - 11am (CST) (Kumar Gala)
Date: December 5, 2018 at 10:48:38 AM CST
Reply-To: Brett Preston <bpreston@...>

Zephyr Bug Triage

Zephyr Working Group is inviting you to a scheduled Zoom meeting.

Join Zoom Meeting
https://zoom.us/j/993312203

One tap mobile
+16699006833,,993312203# US (San Jose)
+16465588656,,993312203# US (New York)

Dial by your location
+1 669 900 6833 US (San Jose)
+1 646 558 8656 US (New York)
+1 877 369 0926 US Toll-free
+1 855 880 1246 US Toll-free
Meeting ID: 993 312 203
Find your local number: https://zoom.us/u/ankEMRagf



When
Thu 6 Dec 2018 10am – 11am Central Time - Chicago
Where
https://zoom.us/j/993312203 (map)
Calendar
Kumar Gala
Who
(Guest list has been hidden at organiser's request)
Going (kumar.gala@...)?   Yes - Maybe - No    more options »

Invitation from Google Calendar

You are receiving this email at the account kumar.gala@... because you are subscribed for invitations on calendar Kumar Gala.

To stop receiving these emails, please log in to https://www.google.com/calendar/ and change your notification settings for this calendar.

Forwarding this invitation could allow any recipient to modify your RSVP response. Learn More.



Re: Duplicate messages when using bt_mesh_model_publish() and groups

Martin <ma@...>
 

Hi,
thanks guys for your help. I have been using the nRF Mesh app for
provisioning. Setting Interval Steps = 0 indeed solves the issue. As I
do not need message transmissions, this solution is perfectly fine. I
guess I should have cross-checked with meshctl :-(

Martin


Am Di., 4. Dez. 2018 um 17:35 Uhr schrieb Vikrant More <@vikrant8051>:


Hi,
Client could re-transmit message to make sure that it will get receive
by Server. All re-transmitted message has same TID. Using it at App level
we could ignore previously received duplicate message.

This concept is explored in samples/boards/nrf52/mesh/onoff_level_lighting_vnd_app.
For details refer device_composition.c in it.

If you are using #nRFMesh Android App, then in Publication Setting (in your case
it would be Generic OnOff client -> SET PUBLICATION ) set Intervals Steps to 0.

Actually there is bug in App's nomenclature....but as of now
set Interval Steps = 0.

After this client will only send one message to Server & there will be no re-transmission
of same message from client side.

Regards,
vikrant

On Tue, Dec 4, 2018 at 9:20 PM Martin <ma@...> wrote:

Hi,
I am running samples\boards\nrf52\mesh\onoff-app on two NRF52 DKs.
What I notice is that mesh messages are duplicated, i.e. when pressing
a button on the server node (that is publishing to group 0xC00A), one
message is sent ("publish to ..."). But on the client node, (which is
subscribing to 0XC00A), the callback for incoming mesh messages
gen_onoff_set is called twice (2x "gen_onoff_set" output).
I would really like to reduce the messages sent to a minimum so am
wondering why this is happening and how to solve this.. It seems to me
as if messages sent via bt_mesh_model_send only appear once. Could
someone help me?

Thanks,
Martin



Re: Is bluetooth sample "peripheral" still working well?

Johan Hedberg
 

Hi Jun,

On 4 Dec 2018, at 18.13, Li, Jun R <jun.r.li@...> wrote:
Actually, the function "settings_load" is called in the sample "peripheral" which you can take a look at.
I know.

I assume an random address will be written to the settings after the first booting, right? However, I still see the message "NO ID address" showing up every time when the board reboots. Should I do extra work to generate a random mac and write it to the settings?
No. The warning comes before settings_load() to indicate to the app developer that settings_load() will need to be called, i.e. the warning is not supposed to go away. I think everything is working fine with regard to this - you’re just getting distracted with this benign warning message :)

I'll try increasing the stack size to see if it is helpful to resolve "HARD FAULT". Specifically, in which thread you want to increase its stack size, settings or Bluetooth?
Usually it’s the thread that calls settings_load() that ends up having an increase in stack usage. In the case of the peripheral app it’s the system workqueue (which calls bt_ready which calls settings_load). However, you should analyse the stack usage of all stacks to to decide whether they’re the right size for your application.

Are you seeing this fault with an unmodified upstream peripheral app? If so we need to fix this upstream. That said, I didn’t see such an issue when running this app on both nRF52 and nRF51 boards today.

Johan


Re: Duplicate messages when using bt_mesh_model_publish() and groups

vikrant8051 <vikrant8051@...>
 

Hi,
Client could re-transmit message to make sure that it will get receive
by Server. All re-transmitted message has same TID. Using it at App level
we could ignore previously received duplicate message.

This concept is explored in samples/boards/nrf52/mesh/onoff_level_lighting_vnd_app.
For details refer device_composition.c in it.

If you are using #nRFMesh Android App, then in Publication Setting (in your case
it would be Generic OnOff client -> SET PUBLICATION ) set Intervals Steps to 0.

Actually there is bug in App's nomenclature....but as of now
set Interval Steps = 0.

After this client will only send one message to Server & there will be no re-transmission
of same message from client side.

Regards,
vikrant


On Tue, Dec 4, 2018 at 9:20 PM Martin <ma@...> wrote:
Hi,
I am running samples\boards\nrf52\mesh\onoff-app on two NRF52 DKs.
What I notice is that mesh messages are duplicated, i.e. when pressing
a button on the server node (that is publishing to group 0xC00A), one
message is sent ("publish to ..."). But on the client node, (which is
subscribing to 0XC00A), the callback for incoming mesh messages
gen_onoff_set is called twice (2x "gen_onoff_set" output).
I would really like to reduce the messages sent to a minimum so am
wondering why this is happening and how to solve this.. It seems to me
as if messages sent via bt_mesh_model_send only appear once. Could
someone help me?

Thanks,
Martin




Re: Is bluetooth sample "peripheral" still working well?

frv
 

Hi Johan,

Thanks for this useful feedback, clarifying a few things more, much appreciated! 

Best regards,
Frank


Re: Duplicate messages when using bt_mesh_model_publish() and groups

frv
 
Edited

Hi Martin,

How is the provisioning done? Probably via the meshctl tool. 
On the client node, only one element bound to a Generic OnOff Server model is subscribed to the group address?

Because I'm also running this Mesh onoff applic on 4 nRF52 DKs: 1 board for publishing, 2 boards for subscribing and 1 acting as relay node (for extending BLE coverage).

Further I modified the applic code a little bit so that it no longer waits for 1 second to publish when a button is pressed (no need in my use case to reuse the same button for switching on and off).

Honestly I didn't noticed a double receive in the logging. As I noticed an intial delay of 1 second I first focussed on getting rid off the logging, but the 1 second delay was caused by how the button press was implemented for supporting switching on/off by a single button.

If finding some time I will have a look at my logging when enabled again.

Best regards,
Frank


Re: Is bluetooth sample "peripheral" still working well?

Li, Jun R
 

Hi Johan,
Actually, the function "settings_load" is called in the sample "peripheral" which you can take a look at. I assume an random address will be written to the settings after the first booting, right? However, I still see the message "NO ID address" showing up every time when the board reboots. Should I do extra work to generate a random mac and write it to the settings?

I'll try increasing the stack size to see if it is helpful to resolve "HARD FAULT". Specifically, in which thread you want to increase its stack size, settings or Bluetooth?

Thank you!
Jun



On 12/4/18, 01:51, "Hedberg, Johan" <@jhe> wrote:

Hi Jun,

> On 4 Dec 2018, at 0.08, Li, Jun R <jun.r.li@...> wrote:
> Thanks for the quick reply! Is there an issue addressing the 9 second delay problem during the booting process? It seems the issue #11780 (https://github.com/zephyrproject-rtos/zephyr/issues/11780) is similar though it is using mesh network stack.

Based on bisecting it seems commit 4d94257162b22f37104e9f85238ed7c3486c5a1c is introducing the issue. Reverting it made the delay and log_strdup failure go away for me. It also fixed the timestamps (they shouldn’t be all zero).

> And how can I get rid of the warning "No ID address"? It always happens on every booting up process.

Why do you want to get rid of it? It’s there to remind app writers that they need to do something extra (i.e. call settings_load) after calling bt_enable().

> Actually, I found another "HARD FAULT" issue if I don't erase all of the flash memory after flashing the firmware built from the latest master. I'll try to identify if the is caused by my app or just a generic one. But basically, this never happened before I rebased the app.

This is something I haven’t seen. What do you mean by not erasing all flash memory? Which parts don’t you erase? What was there from before? You might have uncovered some issue with the settings subsystem if there’s some garbage data there. It’s also worth excluding the possibility of stack overflow, since the settings code increases stack usage. So try increasing your stack sizes before anything else.

Johan


Re: Is bluetooth sample "peripheral" still working well?

Johan Hedberg
 

Hi Frank,

On 4 Dec 2018, at 17.52, frv <@frv> wrote:
Is it correct to say that no public address is set by Nordic for BT HW? Thus probably it is normal this warning "No ID address" is shown.
Not quite. An Identity Address can be either a public address or a static random address. In most cases nRF boards only have a static random address but no public address. In this case the warning just means that at that point the stack has neither one of those addresses, and is waiting for settings_load() to read one from flash (if nothing is found in flash then the stack will go ahead and try to use our HCI vendor extensions to read the static random address from the controller).

Sometime ago this topic was published:
https://lists.zephyrproject.org/g/devel/topic/28283753#5452

I'm wondering if my proposal is valid regarding how to set a public address in case of NRF HW. I didn't investigate myself further but probably Zephyr's "load_settings" function gets its stored info from UICR in case of Nordic HW.
I assume you mean settings_load()? That reads the storage partition in flash, i.e. it’s not related to the FICR or UICR registers.

Johan


Re: Is bluetooth sample "peripheral" still working well?

frv
 

Hi Johan,

Is it correct to say that no public address is set by Nordic for BT HW? Thus probably it is normal this warning "No ID address" is shown. 

Sometime ago this topic was published:
https://lists.zephyrproject.org/g/devel/topic/28283753#5452

I'm wondering if my proposal is valid regarding how to set a public address in case of NRF HW. I didn't investigate myself further but probably Zephyr's "load_settings" function gets its stored info from UICR in case of Nordic HW.


thanks,
Best regards,
Frank


Duplicate messages when using bt_mesh_model_publish() and groups

Martin <ma@...>
 

Hi,
I am running samples\boards\nrf52\mesh\onoff-app on two NRF52 DKs.
What I notice is that mesh messages are duplicated, i.e. when pressing
a button on the server node (that is publishing to group 0xC00A), one
message is sent ("publish to ..."). But on the client node, (which is
subscribing to 0XC00A), the callback for incoming mesh messages
gen_onoff_set is called twice (2x "gen_onoff_set" output).
I would really like to reduce the messages sent to a minimum so am
wondering why this is happening and how to solve this.. It seems to me
as if messages sent via bt_mesh_model_send only appear once. Could
someone help me?

Thanks,
Martin


Re: Running rpl border and rpl node on bluetooth

frv
 
Edited

Hi Akash,

I think you better have a look at these links (as well):
https://www.zephyrproject.org/zephyr-project-announces-openthread-first-thread-protocol-implementation-integrate-zephyr-rtos/
https://openthread.io/platforms/zephyr

Probably you want a hybride setup BLE mesh towards Thread (OpenThread) network..., I think some puzzling between network technologies is required at this moment. 
Maybe a little bit too soon to come up with the examples you would love to see I'm afraid. 

Best regards,
Frank


Re: Minimum one second delay in activating board LED in Zephyr Bluetooth Mesh based on OnOff applic

frv
 
Edited

Hi all, Vikrant,

Thanks for your feedback.

However the issue if you can call it an issue, is that the BL Mesh OnOff sample applic sets by default a minimum 1 second delay before publishing the state of the button press, this makes it possible to distinguish between a single and a double button press either to switch on or either to switch off (linked to one button only).


Best regards,
Frank 


Re: Settings subsystem

robert.konc@...
 

Hi

Thanks for answer, Andrzej.

Find that I lock value after first key find in flash. I did not know that FBC scan all keys in flash. The problem is that some keys are writen more times and after long period could this be problem. I will try to implement settings with NFFS.

Regards,
Robert