Restart after system off if the sensor driver is not suspended (Zephyr OS)

RE: Restart after system off if the sensor driver is not suspended (Zephyr OS)

Hossein Kasaei — Fri, 27 Oct 2023 20:24:35 GMT

After a long time I found out that this phenomena only occurs for the LIS2DH driver, may be a bug or something. I rather to suspend the driver before entering system off.

RE: Restart after system off if the sensor driver is not suspended (Zephyr OS)

Vidar Berg — Mon, 31 Jul 2023 08:35:57 GMT

[quote user="Hossein Kasaei"]The point is, before the sensor error log, there is a i2c_nrfx_twi error, maybe i2c driver is suspended earlier than the sensor driver, which causes i2c read error.[/quote]

Could you please place a breakpoint at the PM_DEVICE_ACTION suspend function in these locations:

1. https://github.com/nrfconnect/sdk-zephyr/blob/2331b76b9b463377f3fc6f6ac08f8f5e6a32bccc/drivers/sensor/lis2dh/lis2dh.c#L451

2. https://github.com/nrfconnect/sdk-zephyr/blob/2331b76b9b463377f3fc6f6ac08f8f5e6a32bccc/drivers/i2c/i2c_nrfx_twim.c#L342

Or, if you use TWI, at: https://github.com/nrfconnect/sdk-zephyr/blob/2331b76b9b463377f3fc6f6ac08f8f5e6a32bccc/drivers/i2c/i2c_nrfx_twi.c#L249

This way, we can determine which function is being called first.

RE: Restart after system off if the sensor driver is not suspended (Zephyr OS)

Hossein Kasaei — Fri, 28 Jul 2023 14:35:53 GMT

Yes as you can see I'm reading sensor values once before entering the deep sleep and the readings are fine :

*** Booting Zephyr OS build v3.1.99-ncs1 ***
Polling at 0.5 Hz
#1 @ 397 ms: x -0.612864 , y -0.153216 , z 9.959040
Going to sleep after 3 sec...
[00:00:00.390,533] <inf> lis2dh: fs=2, odr=0x1 lp_en=0x8 scale=9576
Deep Sleep Starts now
[00:00:03.406,951] <err> i2c_nrfx_twi: Error on I2C line occurred for message 0
[00:00:03.407,012] <err> lis2dh: failed to read reg_crtl1
[00:00:03.407,043] <err> pm: Device lis3dh@19 did not enter suspended state (-5)

The point is, before the sensor error log, there is a i2c_nrfx_twi error, maybe i2c driver is suspended earlier than the sensor driver, which causes i2c read error.

RE: Restart after system off if the sensor driver is not suspended (Zephyr OS)

Vidar Berg — Fri, 28 Jul 2023 11:41:27 GMT

Have you verified that you are able to read values from the sensor before entering System OFF? If you look at the SUSPEND action in the driver (link), you can see it tries to read some register from the sensor before putting it to sleep. So I'm wondering if the communication has been working at all.

RE: Restart after system off if the sensor driver is not suspended (Zephyr OS)

Hossein Kasaei — Thu, 27 Jul 2023 15:05:29 GMT

I increased the stack size and I'm facing these errors :

*** Booting Zephyr OS build v3.1.99-ncs1  ***
Polling at 0.5 Hz
#1 @ 266 ms: x -0.612864 , y 0.612864 , z 10.571904
Going to sleep after 3 sec...
[00:00:00.259,094] <inf> lis2dh: fs=2, odr=0x1 lp_en=0x8 scale=9576
Deep Sleep Starts now
[00:00:03.275,512] <err> i2c_nrfx_twi: Error on I2C line occurred for message 0
[00:00:03.275,543] <err> lis2dh: failed to read reg_crtl1
[00:00:03.275,573] <err> pm: Device lis3dh@19 did not enter suspended state (-5)
*** Booting Zephyr OS build v3.1.99-ncs1  ***
Polling at 0.5 Hz
#1 @ 401 ms: x -0.766080 , y -0.153216 , z 9.499392
Going to sleep after 3 sec...

which is I think something related to the sensor driver, it might be running some code in the background in a thread, cause when I run k_sleep in the main thread, it logs :
[00:00:00.259,094] <inf> lis2dh: fs=2, odr=0x1 lp_en=0x8 scale=9576
and after 3 seconds it might be still running, so putting device into deep sleep interrupt it's operation and the i2c and sensor driver face errors which indicate that it is better to suspend the driver (which suspend it's thread) so it won't face any error.

RE: Restart after system off if the sensor driver is not suspended (Zephyr OS)

Vidar Berg — Thu, 27 Jul 2023 14:20:48 GMT

I'm not sure why you get a stack overflow in the 'idle' thread. Either way, please try to increase the stack size for this thread by adding CONFIG_IDLE_STACK_SIZE=<new stack size> to your prj.conf and see if it helps. The default is 320 bytes.

RE: Restart after system off if the sensor driver is not suspended (Zephyr OS)

Hossein Kasaei — Thu, 27 Jul 2023 14:13:36 GMT

after enabling mentioned config this is the new log :

[00:00:03.275,482] <err> os: ***** MPU FAULT *****
[00:00:03.275,512] <err> os: Stacking error (context area might be not valid)
[00:00:03.275,512] <err> os: Data Access Violation
[00:00:03.275,512] <err> os: MMFAR Address: 0x20001678
[00:00:03.275,543] <err> os: r0/a1: 0x088324ff r1/a2: 0x4eb7b419 r2/a3: 0xdc5f7d29
[00:00:03.275,573] <err> os: r3/a4: 0x49e0b6dc r12/ip: 0xe53dc749 r14/lr: 0x2b23e114
[00:00:03.275,573] <err> os: xpsr: 0xafd52000
[00:00:03.275,573] <err> os: Faulting instruction address (r15/pc): 0x5db9d8f3
[00:00:03.275,604] <err> os: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
[00:00:03.275,634] <err> os: Current thread: 0x20000658 (idle)
[00:00:04.461,700] <err> fatal_error: Resetting system

RE: Restart after system off if the sensor driver is not suspended (Zephyr OS)

Vidar Berg — Thu, 27 Jul 2023 10:16:50 GMT

The crashlog indicates that you had a stack overflow in one of your threads. Please add CONFIG_DEBUG_THREAD_INFO=y to your prj.conf to get the name of the thread.

RE: Restart after system off if the sensor driver is not suspended (Zephyr OS)

Hossein Kasaei — Thu, 27 Jul 2023 09:25:57 GMT

I turned on the log and I'm getting these errors :

*** Booting Zephyr OS build v3.1.99-ncs1 ***
Polling at 0.5 Hz
#1 @ 266 ms: x -0.153216 , y -0.153216 , z 9.805824
Going to sleep after 3 sec...
[00:00:00.259,124] <inf> lis2dh: fs=2, odr=0x1 lp_en=0x8 scale=9576
Deep Sleep Starts now
[00:00:03.275,512] <err> os: ***** MPU FAULT *****
[00:00:03.275,543] <err> os: Stacking error (context area might be not valid)
[00:00:03.275,543] <err> os: Data Access Violation
[00:00:03.275,573] <err> os: MMFAR Address: 0x200015f8
[00:00:03.275,573] <err> os: r0/a1: 0x34f155bf r1/a2: 0x00c52802 r2/a3: 0x7d679934
[00:00:03.275,604] <err> os: r3/a4: 0xc0ebe905 r12/ip: 0x5c1b1937 r14/lr: 0x0a8008e8
[00:00:03.275,604] <err> os: xpsr: 0x2406de00
[00:00:03.275,634] <err> os: Faulting instruction address (r15/pc): 0x8bc6d297
[00:00:03.275,634] <err> os: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
[00:00:03.275,665] <err> os: Current thread: 0x20000628 (unknown)
[00:00:04.461,730] <err> fatal_error: Resetting system
*** Booting Zephyr OS build v3.1.99-ncs1 ***
Polling at 0.5 Hz
#1 @ 266 ms: x -0.153216 , y -0.306432 , z 9.959040
Going to sleep after 3 sec...

RE: Restart after system off if the sensor driver is not suspended (Zephyr OS)

Vidar Berg — Thu, 27 Jul 2023 07:32:45 GMT

Hi,

The RESETPIN bit is set, indicating that the last reset was a pinreset. But did you make sure to read the register after this happened:

[quote user=""]The problem is, whenever I put the chip in system off mode, It will reset immediately[/quote]

RE: Restart after system off if the sensor driver is not suspended (Zephyr OS)

Hossein Kasaei — Wed, 26 Jul 2023 19:25:05 GMT

Hi Vidar,

While my code was running, I ran the command you said in the terminal and I read : 0x40000400: 00000001. How do you interpret that ?

RE: Restart after system off if the sensor driver is not suspended (Zephyr OS)

Vidar Berg — Tue, 25 Jul 2023 11:16:07 GMT

Hi,

None of the pins appear to be configured with sense enabled, which makes me think the wake-up is caused by something else. Please read the RESETREAS after the device failed to stay in system off to see if the 'OFF' bit is set. You can do this with the "$ nrfjprog --memrd 0x40000400 " command (Note that the chip can't enter system OFF when it's in debug interface mode).

RE: Restart after system off if the sensor driver is not suspended (Zephyr OS)

Hossein Kasaei — Tue, 25 Jul 2023 07:53:51 GMT

Hi,

Thanks for your response. I checked the pin configuration before and after suspending the sensor driver, but it seems it doesn't change any pin configuration :

RE: Restart after system off if the sensor driver is not suspended (Zephyr OS)

Vidar Berg — Mon, 24 Jul 2023 11:09:01 GMT

Hello,

GPIOs that are configured as input with sense enabled can trigger wake-up from System OFF. Therefore, I assume the LIS2DH driver is configuring GPIOs with sense enabled, and that is what causes your device to immediately wake up again when you haven't suspended it.

I suggest you compare the pin configurations in VS code before and after suspending the device.

Best regards,

Vidar