Hi Simon: Which revision of Zephyr are you using? On Zephyr v2.1.0 I had no problems, but with Zephyr 2.2.0 I am having problems. I have filed a bug for

Hi all, Note: Today we go back to our usual 9AM PDT / 18h CET. Today's topics: - Template to document a driver implementation: discussion as to what it should include - API Terminology

Has anyone tested the hci_usb sample with windows 10 and its native BLE stack? On my end, it won't accept the controller. A reason might be that it lacks classic Bluetooth. can anyone confirm this,

HI Vince, There is no ‘official’ SPI specification, it is a defacto standard, and chip manufacturers can implement it any way they want. Generally most peripherals don’t care what level the

Hi Lawrence, Sorry for unclear description. What I mean is the voltage of MOSI signal inidle state doesn’t remain in high voltage. For example, the following picture shows it begin from high

You need to be inside a zephyr tree (or pointing to it with ZEPHYR_BASE) that has #23054 merged in, so the latest upstream master will do. zephyr-export is implemented in the zephyr tree, not in west

What version of west has 'zephyr-export’?? [galak@spiff zephyr]$ west -V West version: v0.7.2 [galak@spiff zephyr]$ west zephyr-export usage: west [-h] [-z ZEPHYR_BASE] [-v] [-V] <command>

Hi Vince: 2) I am not sure what you mean when you say “the voltage on the MOSI signal is unstable”. The Oscilloscope traces below look fine, however, the probes on your oscilloscope have not

Hi, We have some issues on developing LPC55S69 based on Zephyr OS. 1. EVB can’t run FW successfully if I do operation for double type variable. I found the FW with this problem will

Hi All, A new way of including boilerplate code has been introduced with this PRhttps://github.com/zephyrproject-rtos/zephyr/pull/23054 This means a simple Zephyr application now looks as:#

The beacon sample builds for me at Zephyr v2.1.0 for nrf52_pc10040 with Zephyr SDK 0.11.1. Did you skip a 'west update' or need a --prisitine? "Li, Jun R via

Hey, I’ve tried to build a couple of BLE applications, like “beacon” , “peripheral_hr” with several nRF52 boards such as “nrf52_pca10040”, “nrf52840_pca10056” on the version 2.1.

The ZEBRA RFC (see RFC: https://github.com/zephyrproject-rtos/zephyr/issues/23465) is a feature proposal for a simple way to add secure authentication between two Bluetooth devices. ZEBRA is not part

Reminder: Zephyr Project: Dev Meeting When: Thursday, 26 March 2020, 8:00am to 9:00am, (GMT-07:00) America/Los Angeles Where:https://zoom.us/j/993312203 An RSVP is requested. Click here to

Here’s the agenda topics for this week: * Review PR’s tagged with dev-review * use of PRE_KERNEL_1/PRE_KERNEL_2... * Pinmux/pinctrl (Piotr/Erwan) * Any topics anyone else has - k

Hi all, I was wondering about the state of crypto APIs in Zephyr and whether it makes sense to move them forward or instead we should consider simply using the mbed TLS set of APIs as Zephyr's crypto

Yes previously I posted same issue, but iam not creating any threads in my application

Reminder: Zephyr Project: APIs When: Tuesday, 24 March 2020, 9:00am to 10:00am, (GMT-07:00) America/Los Angeles Where:https://zoom.us/j/177647878 An RSVP is requested. Click here to

Hello, "Jukka Rissanen" <jukka.rissanen@...> wrote: Perhaps it could be rephrased differently: net_buf is more like Zephyr's internal system object. Where it's used currently,