Hi, FYI, With v1.12.99 I'm mot facing any MPU FAULT issue (while testing for #onoff_level_lighting_vnd_app) It has last commit -> ba6763a187a347cfc825a2bece78e7d1ef28772d That means something after

Hi, We have just merged PR https://github.com/zephyrproject-rtos/zephyr/pull/9776 which moves SOC definitions out of the arch/ directory to the top level to be side by side with boards,

Hi, I'm working on a project in Zephyr that will use GPS to get the location of a device. Until now the GPS data has been fethed using serial drivers directly, but we're looking into the

Never mind.. found this fantastic youtube video in the `Enable SPI driver` thread that helped solve the issue: https://youtu.be/vioi4OsmB_U -Gurpreet

Hi All, I'm trying to build the I2C sample programs or those that use I2C for the nrf52, but keep seeing the following error. Is there something I need to do to enable using I2C from the chip? I

Hi again, I just tried a few of the examples from the nRF5_SDK_15 (open_bootloader_usb_mbr_pca10059_debug.hex and ble_connectivity_s140_usb_hci_pca10059.hex). Same issue. I am starting to think my

Hi Vinayak, Sorry - just getting back to this problem now. I have double-checked that SB2 is intact and that VBUS_nRF (measured at SB2) is at ~5.20V. I have a hard time measuring if VBUS_nRF is

Hi, We are pleased to announce the release of Zephyr kernel version 1.13.0. Major enhancements with this release include: · Extensible and Pluggable Tracing Support ·

----- Forwarded message -----

Chuck, The only thing I needed to configure is the spi config struct (freq, spi mode of operation & cs) and it just worked out of the box. But to be honest the only place where I used the NRF SPI is

Jan, Thanks, missed that typo. Fixed that, but same result. For the moment, I'm not worried about the data or behavior of the SPI device. Just want to see a driver transaction complete...data comes

Hi Chuck, Looks like you configured MOSI & MISO to the same pin (8) is this intentional? As far as I know the NRF52840 does not support 3-wire (shared MISO/MOSI pin) SPI mode. Regards, Jan

Vinayak, Jan, et. al. Thanks again for your combined help on this. Just ran into a pothole and I thinks its a simple config issue on my part. I have a simple spi write set up and it appears to be

Hi evebody: Last days I was working with Zephyr testing some samples. In the beggining I started in a PC of 64bits with a Windows 8.1 Enterprise 32bits and I found some problems that I can´t solve.

Sorry once again. Im trying to work with DMA. How ever when I try to bind the dma I receive MPU FAULT. Platform is SAME70 - custom board. My code: printk("a0 %s\n", CONFIG_SPI_SAM_DMA_NAME);

Hi, Im trying to work with DMA. How ever when I try to bind the dma I receive MPU FAULT. My code: printk("a0 %s\n", CONFIG_SPI_SAM_DMA_NAME); dev_cfg->dev_dma =

Hi, We are almost there, RC3 was just tagged. From a bug count perspective we are ready to release, from now on only high priority bug fixes will be merged, in addition to any documentation and

Hello, This is the (day late) email for the 5 September 2018 Zephyr Development News. HTML is available here: https://foundries.io/insights/2018/09/05/zephyr-news-20180905/ As usual, contents are

Hello Joakim, Looks like the nRF52840-DK board is supported for the RPL-node sample. - Mike

Hey Carles, it’s been a while since I encountered this issue, so I don’t know the exact commit I used. I tried to run the Peripheral Bluetooth samples on a nrf52840_pca10056 board. I also got