Hi Michał - You want the devicetree organization to match the hardware description. So in the case of the Ambiq GPIO controller, I think your best bet is to create only GPIOA and GPIOB controllers. Th

#bluetooth #ambiq

Hey Keith, Thanks for the lead. This certainly helps. I still have some questions, hope that's ok. Lets say I'm describing the bytes that relate to gpio controller A: ``` gpioa: gpio@40010000 { compat

#bluetooth #ambiq

The GPIO driver for the ITE IT8xxx2 family also interleaves the register space. You could follow the model used for that driver - create multiple reg phandles for the individual registers. https://git

#bluetooth #ambiq

Hello, I'm trying to add support for the Ambiq Apollo series chips. I'm new to the Zephyr and not very experienced with Device Tree format. Currently I'm working on the zephyr/dts/arm/ambiq/apollo.dts

#bluetooth #ambiq

Hi, I have two questions about HCI RPMsg: 1. If I have nRF5340DK, what's the <board name> I can use to build the firmware? nrf5340dk_nrf5340? nrf5340dk_nrf5340_cpuapp? nrf5340dk_nrf5340_cpunet? 2. I f

#bluetooth #hci

Hi, you can check the content of the build.ninja in the build directory. Look for the files that you suspect are built incorrectly and check the build flags. That should at least confirm that the prob

#builds #debug #bluetooth #nrf52 #nrf52832

Hello, NOTE: I also posted this on github:https://github.com/zephyrproject-rtos/zephyr/issues/27706 I don't know which channel is the correct one for these types of issues. I have a question about deb

#builds #debug #bluetooth #nrf52 #nrf52832

Hello, I'm use the sample code at \zephyr\tests\bluetooth\shell\ and the HW platform is nrf52840dk, what I'm trying to do is to make HW send ADV_EXT_IND and AUX_ADV_IND. After flashing the firmware in

#bluetooth #nrf52840 #shell

Hello Community, We are using nordic's nrf52840_pca10056 chip on our custom board and on top of that zephyr's 'hci_uart' application is running. (Zephyr version v2.1.0).On our custom board, the host s

#hci #nrf52480 #uart #ble #bluetooth

Hi Andreas, No, I don’t think that combination would make sense. One option I forgot to mention is the bt_mesh_suspend() & bt_mesh_resume() APIs. You could try suspending mesh operations (advertising

#bluetoothmesh #bluetooth

Hi Johan, thank you very much for your help in that matter. I am aware of the reduced scanning time for the mesh. It’s just that in my scenario the mesh is running all day long, and occasionally some

#bluetoothmesh #bluetooth

Hi Andreas, There’s nothing in the standard that prohibits it, but it will reduce the efficiency of the mesh network. The mesh advertising bearer is designed in such a way that assumes the nodes to be

#bluetoothmesh #bluetooth

Hello, on my nRF52 board I am planning to have a Bluetooth mesh node running and then eventually (e.g. on button press) create a connection to a smartphone (nRF52 in Central, smartphone in Peripheral

#bluetoothmesh #bluetooth