Re: Memory access between application task and driver using printk

There appears to be problems in the code you copy-pasted, so it is hard to say for sure what is going on in your actual code. See below for a few notes. On Mon, Nov 16, 2015 at 11:28 AM, Inderjit Singh wrote: > Hi, > > I have a strange behaviour regarding memory

Memory access between application task and driver using printk

Hi, I have a strange behaviour regarding memory access between my user application and the driver i have developed I'd like to get some clarification on. The development is all used on or1k arch. On the application side, I have a buffer declared as: #define PACKET_SIZE 256 volatile uint8_t