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

Hello, I am going to try out the 6LoWPAN/802.15.4 stack on Zephyr OS - what boards would be reasonable picks for testing that? I can see the EFR32 board is supported - is that a good choice and

Hi, I'm not able to provision any sample code using Bluez v5.49 #meshctl in case of latest master branch i.e v1.13rc2. Other observations: 1) Using #nRFMesh App (iOS) everything is Ok. 2) In case of

Hi Justin, actually I made it yesterday (adopted stm32 code), at least it is looks like that it is working somehow (both direction), but also it need some testing. However Im still missing IRQ and DMA

Hi Jiri, I have a good bit of a SPI driver done. It needs the reading side completed and tested. For my purposes I only did the writing side. Would you like to take it from where I left off or do you

Right, but we need to get to the bottom of this faults and what is causing them on master. Vikrant, Phil, can you please share with us how to reproduce the issue? Carles From:<devel@...> on

Hi Phil, Yes, you are right. If we used v1.12.99 then didn't get any MPU fault or Kernel OOPS. Thanks !!

Hi Manu, There are 3 configurations possible when you build Zephyr: Controller only. The controller exposes HCI over UART, USB or SPI including DTM commands if enabled Host only. The

The shell application takes console commands, what you need is HCI Test mode over UART. On a nRF52840,you will need to use both the UART instances, one for console and the other for a HCI "tap" or

Vinayak, Carles. Thanks for the responses. Permit me to clarify 1.Carles: what you suggest might be what I am looking for- the ability to have a standard host+controller on the nrf52, and the

> While I was certainly able to expose an hci H4 link to the controller, I was not able to make the DTM mode co-exist with my application code. Could you ellaborate on how you are accessing H4 from

Hi there, If you enable: BT_CTLR_DTM=y CONFIG_BT_CTLR_DTM_HCI=y then you can build the BLE shell (tests/Bluetooth/shell) and have access to DTM. Use the “test_tx”, “test_rx” and

Hi all: We have an application running on the nrf52840. As we approach production, I am desirous of enabling DTM mode for in-line BLE testing. While I was certainly able to expose an hci H4 link to