Hello, I was wondering about where did void casting for functions like memcpy, memset comes from. Could commit messages for this point to specific rule? -- pozdrawiam Szymon K. Janc

You have to buy it. This fairly new publication might help you: https://arxiv.org/abs/1809.00821 Kind regards, Reto

<bewithsathish@...> wrote: The important thing is it must be set before you include the boilerplate file.

It seems set(BOARD qemu_cortex_m3) has to be in the beginning of the file after cmake version. It works. -- Regards, Sathishkumar D

Hi all, I am Sathishkumar. I am experimenting with zephyr and learning to contribute to it. I am coming form Linux and feels home with kconfig, dts, etc. As per the application primer, I have

Hi, last night I have discovered that I have messed up variables and I have tried to assign value to constant variable -> that is the reason why I have received the MPU fault. Best regards, Jiri po

Hi, In my case the MPU falut was stable. But in your case it looks like some race condition issue. Try to reorganise the initialisation or add some delays. Regards Jiri Dne po 17. 9. 2018 15:39

Hi Jiri, After replying to your email, I once again started testing thoroughly. And yes, once again I got MPU fault. Regards, Vikrant

Hi Vincent, Im open minded 8-). I have implemented SPI driver with polling - seems to be working fine for moth ways. But configuration stuff need some recheck and only one CS is supported. I have

Hi Jiri, I'm was planning a SPI driver for the SAM4S and later on the SAMe70. I have sufficient boards to test the SPI driver, with displays, flash, IMU and transceivers on them to push its

HI Jiri, After latest sync with master, I've not faced MPU FAULT issue while testing. But it could be there. With v1.13, it could be suddenly pops-up without any reason (as a app developer) Thanks for

Hello, RPL (mesh routing) technology over 802.15.4 has been supported in Zephyr from the beginning. Originally it was taken from Contiki OS and

Hello, when I am compiling sensor.h in a cpp file, I have following error 5 times: /home/.../zephyr/include/sensor.h: In function ‘int sensor_trigger_set(device*, sensor_trigger*,

FYI, Zephyr is not MISRA-C compliant as Zephyr currently uses several GNU C extensions. Some little work is ongoing to at least make Zephyr more C99 compliant. MISRA-C Rule 1 (required): "All code

Hello, when I am compiling sensor.h in a cpp file, I have following error 5 times: /home/.../zephyr/include/sensor.h: In function ‘int sensor_trigger_set(device*,

Hi, I have one practical question regarding MISRA-C standard. Where I can get the standard as a regular coder? I can buy one for £15 + VAT, but I dont thing that every body want to buy it. Is there

Hi, have you found a solution? Few days ago I have reported similar problem with MPU fault but with Atmel (Microchip) SAME70 chip. It is cased by binding DMA. dev_cfg->dev_dma =

Hi, Agree, it's worth to fill an issue regarding this. Regards, Flavio Ceolin

Hi, Yes, it indeed works that way. That said I don't consider that as a solution. The value in the Kconfig file comes from the app's prj.conf and I don't want to hard-code the path there. I would

Hi Reto, Yeah, last time I've checked it was requiring the MISRA-C standard converted to a pure text. The problem is that we can distribute MISRA-C. Though, I'll check if the standard is only