Re: [Zephyr-users] assertion fail in nordic nrf5 i2c driver

Manu R

Carles, appreciate the response. 
That was definitely one of my experiments to try. 
However, we have had a relatively stable base with r1.12 and I am not sure we can change to 1.13 without some regression testing. 

I will certainly try 1.13 and update you. 

(A different issue I see in the driver is related to the power consumption being high(~1ma) for ~1.2s after i2c transactions are done. Any idea what that might be?)
Thanks a lot, I appreciate the help. 

On Tue, Oct 9, 2018 at 12:58 AM Cufi, Carles <Carles.Cufi@...> wrote:

Hi Manu,


The I2C driver has since been completely rewritten to use nrfx, our common driver codebase.

Would it be possible for you to try with current master (or at least 1.13) to see if you still face the issues you mention?




From: users@... <users@...> On Behalf Of Manu R
Sent: 08 October 2018 18:56
To: devel@...; users@...
Subject: [Zephyr-users] assertion fail in nordic nrf5 i2c driver


Hi all, 

I am using a lis2dh12 with a nrf52840, and am on occasion seeing an assertion. 

It happens in the i2c_nrf5_read


err=0 txd=0 rxd=0 stopped=0 errsrc=0x0

ASSERTION FAIL [data->stopped] @ <snip>/zephyr_new/drivers/i2c/i2c_nrf5.c:142:


We are based off of 5890004ea72066fb4b1e8100bb289fb5a00646a5 ( r 1.12)


Can someone shed light on whats happening? It looks like I am waiting for the EVENTS_STOPPED to hit in the isr, but seeing the data->stopped is not set, perhaps its not?

Are there any remedies? It looks like this condition should be benign, am I mistaken?




Join { to automatically receive all group messages.