263:bug 120:priority: low 95:priority: medium 6:priority: high 31:area: Networking 29:Coverity 15:area: Bluetooth 13:platform: nRF 13:area: Logging 12:area: Kernel 11:area: Drivers 10:area:

Redirecting to devel@... ---------- Forwarded message --------- From: Chee, Chrislynn <chrislynn.chee@...> Date: Fri, Feb 15, 2019 at 6:21 AM Subject: [Zephyr Main] Guide for coremark setup on Zephyr

Hi, After merging https://github.com/zephyrproject-rtos/zephyr/pull/13135#issuecomment-462891136 this PR in local repo, we can do DFU OTA using Android #nRFConnect. But I've observe following

Hi Brianna, A few things to try and check: Make sure you exit the current shell and open a new one if you had sourced zephyr-env.sh in a pre-west zephyr tree with that shell, since that places

Hello, We are creating a project using Zephyr and whenever I try to flash to my board I receive this error about west even though it says that west is initialized. I saw some thread online about this

Hi, Since this is a BlueZ question it’d be better asked on the BlueZ mailing lists. I’ve added it to CC. E.g. Brian or Inga (who know the BlueZ mesh implementation very well) might be able to

Hello Aymeric, If you don’t mind using the bare metal driver in your application as Maureen suggested, there is also i.MX RT 1050 EVKB board that does support Ethernet and has an unpopulated CAN

Hey, I am trying to establish a bluetooth mesh using the Raspberry Pi 3 (bluez meshctl) as the provisioner and the nrf52 boards as the nodes. The nodes have to periodically send sensor data (LPN) to

Hi Aymeric, There is a bare metal flexcan driver in ext/hal/nxp/imx/drivers that you can use as a starting point. You can create a shim to adapt it to the Zephyr CAN API, similar to what has been done

257:bug 121:priority: low 97:priority: medium 6:priority: high 32:area: Networking 29:Coverity 16:area: Bluetooth 13:platform: nRF 12:area: Kernel 11:area: Logging 11:area: Drivers 11:area:

Reg is specifying which chip select to use. In your dts snippet since you have a cs-gpio I assumed that there is a single CS and so reg should be 0 instead of 1. - k

268:bug 126:priority: low 105:priority: medium 8:priority: high 39:Coverity 39:area: Networking 15:area: Bluetooth 13:area: Kernel 12:nRF 11:area: Logging 11:area: Drivers 11:area: ARM 10:area:

Hi all, I'm new to Zephyr's project, I tested some of the samples on a couples of boards. For my project, I need a board on which Zephyr would support CAN & TCP/IP Stack. I only found Zephyr CAN

Hah, it works after reg is changed to <0>. Thank you, Kumar! By the way, what does "reg=<0>" mean for the sensor bmi160 here? Regards, Jun On 2/12/19, 19:36, "Kumar Gala"

I’m guessing this is because the reg should be set to 0 and not 1. So it should be: bmi160@0 { … reg = <0>; ... }; - k

Hi all, I’m trying to add a sensor board to a STM32F4 discovery board for a prototype, i.e., adding a BMI160 sensor to the SPI1 bus. To do that, I’ve modified the

I am responsible for this oversight in the documentation. If you wouldn't mind sending a fix I would be happy to review it. Thanks.

Hi Ryan, I will take a look at the PRs and add reviewers. Feel free to join the TSC call tomorrow to raise awareness and discuss. The release manager for this release is Kumar Gala from

Hello, I have 2 PRs open to add two new development boards to Zephyr. I would like to see if it is possible to get them added before v1.14 is

Some Bug details: 268:bug 124:priority: low 109:priority: medium 6:priority: high 42:Coverity 41:area: Networking 15:area: Bluetooth 14:area: Drivers 13:nRF 12:area: Kernel 11:area: