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

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" <johan.hedberg@intel.com> wrote:

Hi Jun,

> On 4 Dec 2018, at 0.08, Li, Jun R <jun.r.li@intel.com> 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

Hi Frank,

On 4 Dec 2018, at 17.52, frv <F.Vieren@televic.com> 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

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

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

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

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 

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

I'm using settings to save application data.
But after one setting was writen more than once and application is restarted I get after call settings_load() first value and not last one.
For writing I use settings_save_one().

This is part of flash where settings are stored.

Hi Jun,

On 4 Dec 2018, at 0.08, Li, Jun R <jun.r.li@intel.com> 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

Thanks you for the reponse.
I took the time to extract the modified opus library code from the Smart Ready project (from the .exe to linux) and compared it to the origin opus lib.
Now i will try to use it in a zephry project

Regards,

Nicolas

Nicolas LANTZ
M : +33 (0)6 19 07 43 43
T : +33 (0)9 52 96 81 86
www.ubicore.net

Hi Johan,
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.

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

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.

Thank you!

Regards,
Jun

On 12/3/18, 13:16, "Hedberg, Johan" <johan.hedberg@intel.com> wrote:

Hi,


> On 3 Dec 2018, at 22.03, Li, Jun R <jun.r.li@intel.com> wrote:
> [00:00:00.000,000] <inf> bt_hci_core.hci_vs_init: HW Platform: Nordic Semiconductor (0x0002)
> [00:00:00.000,000] <inf> bt_hci_core.hci_vs_init: HW Variant: nRF51x (0x0001)
> [00:00:00.000,000] <inf> bt_hci_core.hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 1.13 Build 99
> [00:00:00.000,000] <wrn> bt_hci_core.bt_init: No ID address. Expecting one to come from storage.

This is normal when CONFIG_BT_SETTINGS=y is enabled. In such a case the identity address isn’t initialised until the app calls settings_load(), since the identity may be stored in flash.

> [00:00:00.000,000] <inf> bt_hci_core.bt_dev_show_info: Identity: <log_strdup alloc failed>

This shows that the identity has been successfully initialised as a consequence of calling settings_load(), however apparently there are too few log buffers available to log the string-format address.

> • There are about 9 seconds delay between the first message “Bluetooth initialized” and the second one “Advertising successfully started” every time when the board restarts. Not sure what is blocking the booting process.

You’re not the first one to report something like this - it needs to be investigated.

> • I got a “No ID address” warning which is highlighted in red above. The problem never happened before. Is it a new feature? And Does any board need to be provisioned with an ID address before being used from now on?

As I mentioned earlier this is a non-issue. The identity does get loaded properly but there’s an issue allocating a log buffer for its string representation. In general I have a slight suspicion that all these issues could somehow be related to the new logging subsystem.

Johan

Hi,

On 3 Dec 2018, at 22.03, Li, Jun R <jun.r.li@intel.com> wrote:
[00:00:00.000,000] <inf> bt_hci_core.hci_vs_init: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.000,000] <inf> bt_hci_core.hci_vs_init: HW Variant: nRF51x (0x0001)
[00:00:00.000,000] <inf> bt_hci_core.hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 1.13 Build 99
[00:00:00.000,000] <wrn> bt_hci_core.bt_init: No ID address. Expecting one to come from storage.

This is normal when CONFIG_BT_SETTINGS=y is enabled. In such a case the identity address isn’t initialised until the app calls settings_load(), since the identity may be stored in flash.

[00:00:00.000,000] <inf> bt_hci_core.bt_dev_show_info: Identity: <log_strdup alloc failed>

This shows that the identity has been successfully initialised as a consequence of calling settings_load(), however apparently there are too few log buffers available to log the string-format address.

• There are about 9 seconds delay between the first message “Bluetooth initialized” and the second one “Advertising successfully started” every time when the board restarts. Not sure what is blocking the booting process.

You’re not the first one to report something like this - it needs to be investigated.

• I got a “No ID address” warning which is highlighted in red above. The problem never happened before. Is it a new feature? And Does any board need to be provisioned with an ID address before being used from now on?

As I mentioned earlier this is a non-issue. The identity does get loaded properly but there’s an issue allocating a log buffer for its string representation. In general I have a slight suspicion that all these issues could somehow be related to the new logging subsystem.

Johan

Hi All,
Currently i am working on IPV6 over BLE mesh, For that i have chosen reference of RPL Border and RPL Node of zephyr  RTOS.I have seen examples of rpl node and border router, but those were integrated with IEEE 802.15.4 network.
How to integrate RPL node and border router with Bluetooth(nrf52832) to transfer IPV6 packets?
Could you please suggest me some examples that integration of Bluetooth with rpl node or border router?
 
please provide some useful links or information about forming mesh over IPV6.

I would like to form the mesh on IPV6 over BLE, not on Bluetooth mesh profile(on/off example etc...)

Advance in thanks.

BR
Akash.

Hi,

On 1 Dec 2018, at 16.44, cheney chen <wjchen7@hotmail.com> wrote:

Recently I am investigating on adopting a possible BLE Mesh solution in my project. Just found there is BLE mesh support in zephyr now. I am wondering how many nodes can zephyr mesh support? And how about the throughout in point-to-point transfer (e.g. can it support up to 10KB/s throughput in BLE mesh OTA)?

Thanks in advance for any answer to this question. It'd be better if any document or link.

I’ve tried to answer your questions in the GitHub issue (#11789) that you opened before sending this email. In the future, please use either to GitHub *or* the mailing list, but not both, since otherwise we’ll end up having duplicated and unconnected discussions on the same topic.

Johan

Hi,

Recently I am investigating on adopting a possible BLE Mesh solution in my project. Just found there is BLE mesh support in zephyr now. I am wondering how many nodes can zephyr mesh support? And how about the throughout in point-to-point transfer (e.g. can it support up to 10KB/s throughput in BLE mesh OTA)?

Thanks in advance for any answer to this question. It'd be better if any document or link.

Thanks,
Vincent.