Hi, Did you try micropython for zephyr? http://docs.micropython.org/en/latest/zephyr/general.html#zephyr-general Thanks, Jamie

#firmwareupdate #builds

Hi, After going back and forth between nRF connect SDK 1.7.1 and current top of zephyr, it seems that something in the test system when running on actual hardware has been majorly broken in the curren

Hi, We are trying to get twister working to run zephyr tests with code coverage using real hardware (Nordic-based) but seem to be having issues with this: The nrfjprog reset does not seem to work - th

Hi, We have some board file changes to make for when the next release of TF-M is pulled into zephyr, there is an upcoming TF-M release for version 1.5.0 on Monday - will 1.5.0 be used for the upcoming

Hi, Have you tried using the regulators API which was added in 2.5? https://docs.zephyrproject.org/latest/reference/peripherals/regulators.html Thanks, Jamie

#gpio

Hi Markus, Do you have the include at the top of the driver you're developing which incluces the spi-device.yaml file, e.g. from one of the other LIS2XX devices: include: ["spi-device.yaml", "st,lis2d

Hi Sacha, How have you configured it? Have you enabled and set the sample up to have the correct configuration options for your usecase? hcitool, hciconfig etc. are all deprecated tools, bluetoothctl

Sounds like you haven’t setup the udev rules.

Hi Rakshali, See https://docs.zephyrproject.org/latest/getting_started/installation_linux.html Thanks, Jamie

Hi Omar, Have you updated to the latest version of the nRF command line tools from https://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF-Command-Line-Tools and can you try manually using

Hi, Did you configure the Bluetooth stack in zephyr to enable the additional options/features? Hciconfig was deprecated 3 years ago now, use the latest version of blueZ and the latest utilities, not u

#nrf52

Hi Akshay, 00:00:00:00:00:00 is not a valid Bluetooth address, set a valid Bluetooth address and try again Thanks, Jamie

#nrf52

Hi, I have a query on drivers in the zephyr code base in regards to interrupt handling that I am seeking advice on: should a driver in zephyr upon getting an unknown interrupt self-destruct itself, i.

Hi, In all of our modules, UART 0 is the primary UART. We have 8 boards in Zephyr, so we should plan to enable flow control on all those 8 boards and then add 8 overlays to most sample projects to dis

Hi Marti, Let's say there is a board (all our boards are Nordic-based so this applies to all of them) which has a UART brought out to a header, the UART might be used for a multitude of things, it cou

Hi, I only noticed today that the Kconfig option for enabling hardware flow control on UARTs, which used to be an optional Kconfig option, was removed and replaced with a DTS boards file configuration

Hi, We have the following pull requests, two of which are reviewed and need merging and one that needs the testing to finish, can you review/merge these please? https://github.com/zephyrproject-rtos/z

Hi David, You can package them up using nrfutil so that they can update over the old Nordic SDK bootloader, you would just need to adjust the kernel load offset to after the softdevice and you wouldn’

Hi David, Zephyr does not use the Nordic SDK softdevice, it comes with its own Bluetooth stack which gets compiled into your application hex file. You would get rid of the code on your module and flas

Hi, I’m looking through the documentation to find a way (and playing with code) to try and work out how to have the device name advertised in the advert packets (on BLE) rather than scan response pack