Looks like UART flow control is not implemented on stm32f746g_disco. I am going to get that working. Hopefully that makes this setup work.

#uart #bluetoothmesh #hci

Hi, This is a valid and quite common set up. The most important thing you'll need to enable is the host-side UART HCI driver using CONFIG_BT_H4=y. Johan

#uart #bluetoothmesh #hci

Hello, I am trying to configure Zephyr as a HCI UART host. My setup: nrf52840_pca10056 nordic dev kit running zephyr/samples/bluetooth/hci_uart. This seems pretty straight forward. stm32f746g_disco de

#uart #bluetoothmesh #hci

Hello! A couple of months ago, I requested some help to enable the LPN and friend features in this post: https://lists.zephyrproject.org/g/devel/topic/18050411#2060 Which turned out successfully with

#bluetoothmesh

Hi Rodrigo, Can you access Models after following these steps ? Provisioning & Configuration of Models -> un-provisioning (using reset node option in #nRFMesh) -> re-provisioning & re-configuration of

#bluetoothmesh #nrf52840

Hi Rajat, This could be helpful https://devzone.nordicsemi.com/b/blog/posts/nrf-blinky-compatible-firmware-using-zephyr-blueto You've to make changes as per your Board design. regards, vikrant

#bluetoothmesh #nrf52832 #ble

Hi Vikrant, Advertising on Coded PHY needs the implementation of Extended Advertising feature of BT V5.0. This feature has not been implementation, only a initial effort was attempted. That said, any

#bluetoothmesh #ble

Hi, http://blog.bluetooth.com/exploring-bluetooth-5-going-the-distance Is concept of, LE Codded PHY present in current Zephyr implementation to increase range between two #BluetoothMesh Nodes ? What i

#bluetoothmesh #ble

Hi, MyNewt's is a good start point. But looks need more work to make zephyr bluetooth mesh be used in light. I am looking forward it. In the mean time, I can start sensor model coding on zephyr when t

#bluetoothmesh

Hi Johan, Mynewt's lighting model app is very simple & basic, if compare it with diagram on page 296 of model specs. And it is not what I'm expecting. Hello Bluetooth_SIG members, Is Bluetooth_SIG goi

#bluetoothmesh

Hi Vikrant, MyNewt's Bluetooth Mesh is essentially the same as Zephyr's mesh, since it was ported from Zephyr. Most likely you can take any model implementation from there and use it directly (or with

#bluetoothmesh

Hi to all, is there any one who tried to implement Lighting Models (page 296 of Mesh_Model_Specification v1.0.pdf) using Zephyt #BluetoothMesh API ? I want to control three things -> Light On Off, Lig

#bluetoothmesh

Hi to all, I solved my own issue. Please refer this ... https://github.com/vikrant8051/zephyr/blob/mesh_demo/samples/boards/nrf52/mesh/onoff_level_app/src/mesh/doer.c Thank You !!

#bluetoothmesh

Hi, I forgot to mentioned about struct server_state *state_ptr = model->user_data; ---------------------------------------------------------------------------------------- struct server_state { int cu

#bluetoothmesh

Hi, Hi to all, I am trying to implement Generic_Delta_Server_Unack (Level Server) as follow ... void gen_delta_set(struct bt_mesh_model *model, struct bt_mesh_msg_ctx *ctx, struct net_buf_simple *buf)

#bluetoothmesh

Hi Vikrant, At the moment the default settings for NVS and FCB are indeed overlapping; you cannot use them at the same time. To use NVS and FCB together my advice would be to look at the board dts fil

#nvs #fcb #bluetoothmesh

Hi As you notice right now it is impossible to use both NVS and FCB out of the box. So you need a hack. I think finally this problem should be resolved by introduction of dedicate flash slot which are

#nvs #fcb #bluetoothmesh

Hi all, I wanna use #NVS to save #BluetoothMesh Models states. As per current implementation, #BluetoothMesh stack is using #FCB for persistent storage. If I use #NVS (with default setting) along with

#nvs #fcb #bluetoothmesh

Hi Andy, commit 43553da9b2bb9e537185695899fb5184c3b17ebe Author: Andy Ross <andrew.j.ross@...> Date: Thu May 31 11:13:49 2018 -0700 kernel/sched: Fix preemption logic The should_preempt() code w

#bluetoothmesh

Vikrant8051 <vikrant8051@...> wrote: I was pointed to this on IRC. The symptom you've got there sounds a lot like a scheduler mistake that got fixed yesterday, where ostensibly-pended threads co

#bluetoothmesh