Re: [Zephyr-devel] Introduction of Youtube video, "Bluetooth Mesh Demo at ELCE Prague 2017"
Kai Ren <kren@...>
Great! I’ve already found the json file on github, one is local_node.json, the other is prov_db.json, but there may be still an issue, Crypto API on Raspberry Pi, detail is this, https://blog.amuehlbeier.de/raspberry-pi-kernel-mit-crypto-erzeugen/ Have you ever fixed this issue? or Do you have any recommend platform to run meshctl?
Meanwhile, I will try your method later. Thanks!!!
Regards, Kai
From: Vikrant More [mailto:vikrant8051@...]
Sent: Thursday, January 4, 2018 12:05 AM To: Kai Ren <kren@...>; zephyr-devel@...; zephyr-users@... Subject: Re: [Zephyr-devel] Introduction of Youtube video, "Bluetooth Mesh Demo at ELCE Prague 2017"
1) Download this --> https://git.kernel.org/pub/scm/bluetooth/bluez.git/snapshot/bluez-5.48.tar.gz
2) tar -xvf bluez-5.48.tar.gz
3) mv bluez-5.48 bluez
4)cd bluez
5)./bootstrap-configure
6)make
7)make install
8)systemctl daemon-reload
9)systemctl restart bluetooth
10)bluetoothd --version
11) cd mesh
Here you will find local_node.json & prov_db.json
On Wed, Jan 3, 2018 at 6:55 PM, Kai Ren <kren@...> wrote:
|
|
Re: [Zephyr-devel] Introduction of Youtube video, "Bluetooth Mesh Demo at ELCE Prague 2017"
Vikrant More <vikrant8051@...>
1) Download this --> https://git.kernel.org/pub/scm/bluetooth/bluez.git/snapshot/bluez-5.48.tar.gz 2) tar -xvf bluez-5.48.tar.gz 3) mv bluez-5.48 bluez 4)cd bluez 5)./bootstrap-configure 6)make 7)make install 8)systemctl daemon-reload 9)systemctl restart bluetooth 10)bluetoothd --version 11) cd mesh Here you will find local_node.json & prov_db.json
On Wed, Jan 3, 2018 at 6:55 PM, Kai Ren <kren@...> wrote:
|
|
Re: Zephyr way of handling large data transfer over BLE
Vinayak Kariappa
Hi Dhananjay,
toggle quoted messageShow quoted text
Take look at this video demonstrating the large data transfer between two nRF52840 PDK boards. The video is old, but not much has changed on the BT API front. Everything from KConfig to API use is demonstrated here.
On 28 Dec 2017, at 14:38, dhananjay gj <dhguja@...> wrote:
|
|
Re: Working with mesh shell
Hi Ashish,
On Fri, Dec 29, 2017, ashish.shukla@... wrote: If I only use /tests/bluetooth/mesh_shell, how am I supposed to bind modelObviously that's not possible. What you could try to do, is to take the mesh_shell code as a starting point and extend it from there with the models that you need. Johan
|
|
Re: Working with mesh shell
ashish.shukla@corvi.com <ashish.shukla@...>
Hi Johan, Here is brief bout what I'm doing : -- Warm regards, Ashish Shukla Jr. Embedded Engineer Research & Development Please consider the environment before printing this e-mail or its attachments. Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi
On Fri, Dec 29, 2017 at 1:00 PM, Johan Hedberg <johan.hedberg@...> wrote: Hi Ashish,
|
|
Re: Working with mesh shell
Hi Ashish,
On Fri, Dec 29, 2017, ashish.shukla@... wrote: can you share a working code that's compatible with mesh shell? OtherwiseWhich application are you using? An unmodified tests/bluetooth/mesh_shell should work directly. If you're using something else you might at least want to take a look at the configuration of the mesh_shell app. Johan
|
|
Re: Working with mesh shell
ashish.shukla@corvi.com <ashish.shukla@...>
hi Johan, shell> Initializing... [bt] [INF] hci_vs_init: HW Platform: Nordic Semiconductor (0x0002) [bt] [INF] hci_vs_init: HW Variant: nRF52x (0x0002) [bt] [INF] hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 1.10 Build 99 [bt] [INF] show_dev_info: Identity: d0:23:3e:36:04:49 (random) [bt] [INF] show_dev_info: HCI: version 5.0 (0x09) revision 0x0000, manufacturer 0xffff [bt] [INF] show_dev_info: LMP: version 5.0 (0x09) subver 0xffff Bluetooth initialized [bt] [DBG] bt_mesh_cfg_cli_init: (0x20002360) primary 1 [bt] [DBG] bt_mesh_health_cli_init: (0x20002360) primary 1 [bt] [INF] bt_mesh_prov_init: Device UUID: 00000000-0000-0000-0000-d0233e360449 Mesh initialized Type "help" for supported commands. Before any Bluetooth commands you must run "init" mesh> init [bt] [DBG] bt_mesh_cfg_cli_init: (0x20000270) primary 1 [bt] [DBG] bt_mesh_health_cli_init: (0x20000270) primary 1 -- Warm regards, Ashish Shukla Jr. Embedded Engineer Research & Development Please consider the environment before printing this e-mail or its attachments. Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi
On Thu, Dec 28, 2017 at 7:12 PM, Johan Hedberg <johan.hedberg@...> wrote: Hi Ashish,
|
|
Re: Zephyr way of handling large data transfer over BLE
dhguja@gmail.com
Hello Carles, Many thanks for the reply. One final question, Is there an example in zephyr samples that handles transmitting large data? or any profile supported in zephyr that i can use to circumvent this application level segmentation. The intention of this question is coming from the fact that L2CAP layer handles segmentation to some extent (limited by memory available) and we are using GATT for custom profiles.
On Thu, Dec 28, 2017 at 3:10 PM, Cufi, Carles <Carles.Cufi@...> wrote:
|
|
Re: Zephyr way of handling large data transfer over BLE
Carles Cufi
Hi there,
Yes, should be applicable to all those since they all call bt_att_create_pdu() which will block if there’s no buffers available.
Regards,
Carles
From: dhananjay gj [mailto:dhguja@...]
Sent: 28 December 2017 15:06 To: Cufi, Carles <Carles.Cufi@...>; zephyr-users@... Subject: Re: [Zephyr-users] Zephyr way of handling large data transfer over BLE
Hello Carles, Many thanks for the information. Is this information is applicable to GATT indicate, write, read too? Regards, Dhananjay GJ
On Thu, Dec 28, 2017 at 2:50 PM, Cufi, Carles <Carles.Cufi@...> wrote:
|
|
Re: Zephyr way of handling large data transfer over BLE
dhguja@gmail.com
Hello Carles, Many thanks for the information. Is this information is applicable to GATT indicate, write, read too?
On Thu, Dec 28, 2017 at 2:50 PM, Cufi, Carles <Carles.Cufi@...> wrote:
|
|
Re: Zephyr way of handling large data transfer over BLE
Carles Cufi
Hi there,
Provided the peer does not initiate a GATT MTU Exchange, which would be handled automatically by the Zephyr BLE stack, you can simply call bt_gatt_notify() in a loop and from a thread while modifying the contents of the attribute in each iteration. When GATT runs out of buffers the the bt_gatt_notify() call will block until more are available, so you do not need to wait for an event like when using the SoftDevice.
Regards,
Carles
From: zephyr-users-bounces@... [mailto:zephyr-users-bounces@...]
On Behalf Of dhananjay gj
Sent: 28 December 2017 13:45 To: zephyr-users@... Subject: [Zephyr-users] Zephyr way of handling large data transfer over BLE
Hello All, I have a question related to the one i asked last week. (https://lists.zephyrproject.org/pipermail/zephyr-users/2017-December/000915.html). But i will rephrase it and be more generic to what i am looking for now because that question was already answered and solution works too. I have an Android client (BLE central) and zephyr OS based BLE device as peripheral (nRF device) transfer data over a custom profile. I am aware that in BLE we can transfer only 20 bytes at a time. And also there are possibilities to extend
the data packet size or increase the ATT_MTU size based on negotiation. But for compatibility purposes, I will avoid using these techniques. I am also not using BLE mesh or nordic softdevice SDK.
I am searching if there is any solution similar to the accepted answer in this thread for nordic SDK: https://devzone.nordicsemi.com/question/1741/dealing-large-data-packets-through-ble/)
Any example or leads to this using zephyr is much appreciated. Thanks in advance.
Regards, Dhananjay GJ
|
|
Re: Working with mesh shell
Hi Ashish,
On Thu, Dec 28, 2017, ashish.shukla@... wrote: I understand basics on configuration model. However, I'm trying to add appThe first thing the shell prints is that it asks you to run "init" before any other command. Since you haven't done that the "provision" command doesn't do anything, and then you get EAGAIN (errno 11) when you try to send a message, which is the error that the mesh stack returns when you're not provisioned and try to send messages. Johan
|
|
Re: [Zephyr-devel] Working with mesh shell
Vikrant More <vikrant8051@...>
Hi to all, #meshctl take care of netKey & appKey in background. is #mesh_shell does same thing Or I have to add those key manually ? Currently getting following log --> mesh> shell> Initializing... [bt] [INF] hci_vs_init: HW Platform: Nordic Semiconductor (0x0002) [bt] [INF] hci_vs_init: HW Variant: nRF52x (0x0002) [bt] [INF] hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 1.10 Build 99 [bt] [INF] show_dev_info: Identity: e2:da:a3:e1:e1:c6 (random) [bt] [INF] show_dev_info: HCI: version 5.0 (0x09) revision 0x0000, manufacturer 0xffff [bt] [INF] show_dev_info: LMP: version 5.0 (0x09) subver 0xffff Bluetooth initialized[bt] [INF] bt_mesh_prov_init: Device UUID: 00000000-0000-0000-0000-e2daa3e1e1c6 Mesh initialized mesh> provision 1 1 [bt] [INF] bt_mesh_provision: Primary Element: 0x0001 [bt] [DBG] bt_mesh_provision: (0x20000260) net_idx 0x0001 flags 0x00 iv_index 0x0000 mesh> dst 1 Destination address set to 0x0001 mesh> mod-app-bind 1 1 1000 Unable to send Model App Bind (err -11) mesh>
On Thu, Dec 28, 2017 at 2:16 PM, ashish.shukla@... <ashish.shukla@...> wrote:
|
|
Zephyr way of handling large data transfer over BLE
dhguja@gmail.com
Hello All, I have a question related to the one i asked last week. (https://lists.zephyrproject.org/pipermail/zephyr-users/2017-December/000915.html). But i will rephrase it and be more generic to what i am looking for now because that question was already answered and solution works too. In that case, what is the zephyr way of handling large data transfer over BLE.? Do we need to handle segmentation and reassembly in the application layer by our selves only ? or any callback events possible in case buffer is full during multi packet transmission so that we can handle this?. I am searching if there is any solution similar to the accepted answer in this thread for nordic SDK: https://devzone.nordicsemi.com/question/1741/dealing-large-data-packets-through-ble/) Any example or leads to this using zephyr is much appreciated. Thanks in advance.
|
|
Re: Working with mesh shell
ashish.shukla@corvi.com <ashish.shukla@...>
Hi Johan, I understand basics on configuration model. However, I'm trying to add app key, it results in following error -- Warm regards, Ashish Shukla Jr. Embedded Engineer Research & Development Please consider the environment before printing this e-mail or its attachments. Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi
On Thu, Dec 28, 2017 at 1:54 PM, Johan Hedberg <johan.hedberg@...> wrote: Hi Ashish,
|
|
Re: Working with mesh shell
Hi Ashish,
On Thu, Dec 28, 2017, ashish.shukla@... wrote: I'm trying to provision a local node only.Are there any specific commands you're wondering about? You can get the full list of them by typing "help". You'd e.g. start with provisioning by typing "provision <network index> <unicast address>". The shell does require basic knowledge of the configuration model, so I hope you can explore the available commands and by experimenting get something working. Each configuration model related shell command maps directly to a configuration model message, so you'll need to look at the respective specification section for each command for the details of its parameters, etc. Johan
|
|
Re: Working with mesh shell
ashish.shukla@corvi.com <ashish.shukla@...>
Hi Johan, I'm trying to provision a local node only.
On 28-Dec-2017 1:37 PM, "Johan Hedberg" <johan.hedberg@...> wrote: Hi Ashish,
|
|
Re: Working with mesh shell
Hi Ashish,
On Thu, Dec 28, 2017, ashish.shukla@... wrote: can you please list out set of commands in order to provision and configureZephyr does not yet have provisioner support. You can only provision the local node throught the mesh shell at the moment (since that does not involve running the full provisioning protocol). Johan
|
|
Working with mesh shell
ashish.shukla@corvi.com <ashish.shukla@...>
Hi, can you please list out set of commands in order to provision and configure a simple onoff server? -- Warm regards, Ashish Shukla Jr. Embedded Engineer Research & Development Please consider the environment before printing this e-mail or its attachments. Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi
|
|
Re: Subscribing to heartbeat messages in a mesh network
Hi Ashish,
On Thu, Dec 28, 2017, ashish.shukla@... wrote: I'm almost there with mesh shell. Only a small issue, after disabling allCONFIG_INIT_STACKS=n Johan
|
|