|
Re: bluetooth: mesh_shell: mallformed beacon
Hi Steve,
The following PR should fix this:
https://github.com/zephyrproject-rtos/zephyr/pull/5161
Johan
Hi Steve,
The following PR should fix this:
https://github.com/zephyrproject-rtos/zephyr/pull/5161
Johan
|
By
Johan Hedberg
·
#1325
·
|
|
Provisioning a Bluetooth mesh node using Android app by SiLabs
Hello everyone !
I'm trying to provision and configure a mesh node using Android app by SiLabs.
After disabling the OOB feature from controller side, node gets successfully provisioned.But
Hello everyone !
I'm trying to provision and configure a mesh node using Android app by SiLabs.
After disabling the OOB feature from controller side, node gets successfully provisioned.But
|
By
ashish.shukla@corvi.com <ashish.shukla@...>
·
#1324
·
|
|
does zephyr support LoRaWAN or have such plan?
Does zephyr support LoRaWAN or have such plan?
Does zephyr support LoRaWAN or have such plan?
|
By
Yongfa Zhou <yongfaz@...>
·
#1323
·
|
|
bluetooth: mesh_shell: mallformed beacon
I'm configuring mesh_shell with bluez' meshctl.
The beacons for cfg_srv are disabled.
During the initialization of configuration, a beacon gets sent to
meshctl with a cmac of all zeros. Meshctl
I'm configuring mesh_shell with bluez' meshctl.
The beacons for cfg_srv are disabled.
During the initialization of configuration, a beacon gets sent to
meshctl with a cmac of all zeros. Meshctl
|
By
Steve Brown
·
#1322
·
|
|
Re: How to use "mesh" and "mesh_demo" under ./zephyr/sample/bluetooth?
Hi Kai,
The mesh_demo app doesn't do external provisioning, rather it has
hard-coded addresses and keys (the address is set using a NODE_ADDR
build-time define).
The mesh app, on the other hand,
Hi Kai,
The mesh_demo app doesn't do external provisioning, rather it has
hard-coded addresses and keys (the address is set using a NODE_ADDR
build-time define).
The mesh app, on the other hand,
|
By
Johan Hedberg
·
#1321
·
|
|
How to use "mesh" and "mesh_demo" under ./zephyr/sample/bluetooth?
Hi there,
I’m using Zephyr v1.10.0-rc1 and I can build “mesh” and “mesh_demo” on my Windows laptop for BBC micro:bit and nRF52 PCA10040.
I want to use it for testing like provisioning,
Hi there,
I’m using Zephyr v1.10.0-rc1 and I can build “mesh” and “mesh_demo” on my Windows laptop for BBC micro:bit and nRF52 PCA10040.
I want to use it for testing like provisioning,
|
By
Kai Ren
·
#1320
·
|
|
Re: Running bluetooth examples using qemu
Hi Johan, another issue:
Every time my application stay connected for a period it receives a disconnection with the following code:
[bt] [DBG] bt_smp_recv: (0x20002048) Received SMP code 0x06 len
Hi Johan, another issue:
Every time my application stay connected for a period it receives a disconnection with the following code:
[bt] [DBG] bt_smp_recv: (0x20002048) Received SMP code 0x06 len
|
By
Primini
·
#1319
·
|
|
Re: Driver for AT86RF
Hi,
There is a plan, at leat I'd like to get that device supported for
15.4. For instance to support the openlabs daughter board (it's the
ATRF 233 variant on it).
Would you be willing to make a
Hi,
There is a plan, at leat I'd like to get that device supported for
15.4. For instance to support the openlabs daughter board (it's the
ATRF 233 variant on it).
Would you be willing to make a
|
By
Tomasz Bursztyka
·
#1318
·
|
|
Re: Running bluetooth examples using qemu
Hi Johan,
Disabling host flow control using the option that you mentioned the sample works fine.
I will take care some side effects because of this configuration, thanks for the advice.
Have a nice
Hi Johan,
Disabling host flow control using the option that you mentioned the sample works fine.
I will take care some side effects because of this configuration, thanks for the advice.
Have a nice
|
By
Primini
·
#1316
·
|
|
workq test pattern failure, must the CONFIG_POLL be opened?
Hi all:
i run the workqueue test case on test/kernel/workq dirctory, but seems alwasy failure because of "first_pending_thread" valid on below function , so the put workq operation return without
Hi all:
i run the workqueue test case on test/kernel/workq dirctory, but seems alwasy failure because of "first_pending_thread" valid on below function , so the put workq operation return without
|
By
曹子龙
·
#1315
·
|
|
Re: Running bluetooth examples using qemu
Hi Tiago,
This looks like the reason for the failure. I.e. your PC's Broadcom
controller doesn't like the Host Buffer Size HCI command that Zephyr
sends, causing the Zephyr Bluetooth initialization
Hi Tiago,
This looks like the reason for the failure. I.e. your PC's Broadcom
controller doesn't like the Host Buffer Size HCI command that Zephyr
sends, causing the Zephyr Bluetooth initialization
|
By
Johan Hedberg
·
#1314
·
|
|
Re: Running bluetooth examples using qemu
Hi Johan,
from the host side I got btmon's log:
$ sudo btmon
Bluetooth monitor ver 5.47
= Note: Linux version 4.10.0-38-generic (x86_64)
Hi Johan,
from the host side I got btmon's log:
$ sudo btmon
Bluetooth monitor ver 5.47
= Note: Linux version 4.10.0-38-generic (x86_64)
|
By
Primini
·
#1313
·
|
|
Silicon Labs Bluetooth Mesh App compatible Zephyr mesh example for nRF52840-PDK
I wanna control Leds on nRF52840-PDK board using Silicon Labs Bluetooth Mesh App.
Is there any one who has modify $zephyr/samples/bluetooth/mesh example so that it will get compatible for Silicon
I wanna control Leds on nRF52840-PDK board using Silicon Labs Bluetooth Mesh App.
Is there any one who has modify $zephyr/samples/bluetooth/mesh example so that it will get compatible for Silicon
|
By
Vikrant More <vikrant8051@...>
·
#1312
·
|
|
Driver for AT86RF
Hello developer team,
are there any plans to include drivers for the Atmel AT86RF radio modules in the Zephyr project?
Best,
Mathias
Hello developer team,
are there any plans to include drivers for the Atmel AT86RF radio modules in the Zephyr project?
Best,
Mathias
|
By
Mitterdorfer Mathias, HELLA-Automation <mathias.mitterdorfer@...>
·
#1317
·
|
|
Performance compare between the zephyr IP stack and LWIP
HI all:
is there anybody has done the performance test on zephyr compare to LWIP? which one is better on the fileld.
thanks for support.!
HI all:
is there anybody has done the performance test on zephyr compare to LWIP? which one is better on the fileld.
thanks for support.!
|
By
曹子龙
·
#1311
·
|
|
Bluetooth get datetime
Hi everyone,
Usually, to get real datetime on a device you would normally do it through wifi, but since the board I'm using has only Bluetooth, is there a way where I can get the real datetime using
Hi everyone,
Usually, to get real datetime on a device you would normally do it through wifi, but since the board I'm using has only Bluetooth, is there a way where I can get the real datetime using
|
By
Jie Zhou <zhoujie@...>
·
#1310
·
|
|
Re: Running bluetooth examples using qemu
Hi Tiago,
I can't really say for sure what's going wrong, but it would help if you
got some more logs for the situation. On the Linux side, you could run
btmon to see what HCI commands (if any)
Hi Tiago,
I can't really say for sure what's going wrong, but it would help if you
got some more logs for the situation. On the Linux side, you could run
btmon to see what HCI commands (if any)
|
By
Johan Hedberg
·
#1309
·
|
|
Running bluetooth examples using qemu
Hi everyone!
I am trying to run examples from samples using qemu_x86 board but I am facing with bluetooth init error -5 when executing examples that handle connection/disconnection callbacks.
I follow
Hi everyone!
I am trying to run examples from samples using qemu_x86 board but I am facing with bluetooth init error -5 when executing examples that handle connection/disconnection callbacks.
I follow
|
By
Primini
·
#1308
·
|
|
how to configure node for subscribe & public address
After connecting with Device we get following options while configuring the device.
[config: Target = 0100]# h
Client Configuration Menu
Available commands:
target <unicast>
After connecting with Device we get following options while configuring the device.
[config: Target = 0100]# h
Client Configuration Menu
Available commands:
target <unicast>
|
By
Vikrant More <vikrant8051@...>
·
#1307
·
|
|
Zephyr 1.10.0-rc1 tagged
Hi,
We have just tagged Zephyr 1.10.0-rc1 which means that merge window for new features and major changes is closed.
We will be working on stabilizing the release during the next couple of weeks
Hi,
We have just tagged Zephyr 1.10.0-rc1 which means that merge window for new features and major changes is closed.
We will be working on stabilizing the release during the next couple of weeks
|
By
Nashif, Anas
·
#1306
·
|