With west merged in does that mean we can no longer use the cmake/ninja debug type of flow (I'm seeing a problem). If not, will the west setup instructions work on an existing working directory or do

Hi Sven, There is an open issue: https://github.com/zephyrproject-rtos/zephyr/issues/11917 Please feel free to review and provide feedback. Best, Marti > > > >

Hi! I have written a bitbanged 1-wire driver for the nRF52 to interface with DS18B20 sensors. Since it seems to be impossible to read back from a pulled up open-drain driver without clearing the DIR

Hello Dave, "Dave Marples" <dave@...> wrote: Thanks for this post. The best suggestion I however would have is to look it up in the mailing list archive and link from the Github

Hello Kumar, "Kumar Gala" <kumar.gala@...> wrote: So, did the freeze officially happen on last Friday? What next steps can we expect? [] -- Best Regards, Paul Linaro.org | Open source

Folks, I'm new around here so please bear with me and nudge me in the right direction if I get things wrong. I have just submitted Pull Request 13031 which implements DMA mode on the STM32F4 series

Hi Johan, Indeed when using the Big Endian I'm getting the same result. I was mislead as I thought I had to use the little endian as my BLE central applic that needs to decode runs on a BBB, that is

Hi Johan, Thanks, yup, I succeeded just before reading your answer. Indeed I wrongly set my array size, and that after 25 years of 'professional' programming, shame on me... :(. Anyhow, I'm getting

Hi Frank, ... The “_le” in bt_encrypt_le stands for “little endian”. Most Bluetooth protocols are little endian, which is why this convenience API exists. Generic crypto APIs OTOH are usually

Hi Frank, That’s a zero-length array, i.e. it’s not allocating any memory for the variable. Consequently, trying to read or write bd1[0] will cause unexpected behaviour. Other than that I

Hi, If I want to use "bt_encrypt_le", what should be the specification to find the right AES decryptor? I thought I could use the AES_ECB_decrypt from the tiny-AES-C library see :

Hi Joakim, Thanks for your feedback on the topic. Indeed currently I'm using "passkey authorization" during the pairing process. Although I don't have a keyboard or display on my BLE devices I have

Hi, I don't know what I'm doing wrong when trying to advertise raw data via the scan_response function parameter in bt_le_adv_start, probably overlooking something stupid, but I don't get this to

I have run across a build problem that appears to impact Arm platforms. The problem involves improper discarding of ‘const’ defined variables that are only referenced within a single file getting

Hi everyone, I recently saw this while running test cases for west in Shippable: DEPRECATION: Python 3.4 support has been deprecated. pip 19.1 will be the last one supporting it. Please upgrade your

Hi, The service is back in read-only mode. If you have any issues assigned to you, please take the chance to look at the details of the issue and fix as soon as possible. List of the open

Hi Zephyr group, We have found on our Zephyr system that the first device (Android or iOS) pairs/bonds with not problems, but a second (or third etc) device fails to pair/bond most of the

Hi, The native_posix board does not use the Bluetooth simulator. Its random generator is deterministic, but can be seeded ( --seed=<random_seed>) to enable reproducible tests(*1). The nrf52_bsim

Hello Alberto, "Alberto Escolar Piedras (ALPI)" <ALPI@...> wrote: D'oh, I stand corrected. Now I remember it, Bluetooth simulation support, right? [] -- Best Regards, Paul Linaro.org |

All, Just wanted to remind everyone that the code freeze for 1.14 will be this Friday. Please tag any PR as with 1.14 milestone that you feel should try and get merged as part of 1.14. Thanks - k