LIS2DH Trigger Giving z_arm_mpu_fault()LIS2

[NautDesigner]

Running the Zephyr LIS2DH sample program on a custom board works fine until I configure it to use the trigger and then it throws the z_arm_mpu_fault() error. It doesn't matter if I have it use it's own thread or the global thread. 

Any idea what could be causing this?

[Simon]

Could you try set CONFIG_LOG=y, and CONFIG_RESET_ON_FATAL_ERROR=n. Then check the log to see the line that caused the issue (use addr2line).

The issue may be due to a stack overflow, check out the ticket Stack Overflow for more information how to resolve the issue then.

Best regards,

Simon

[NautDesigner]

Turning on those settings I get the following:

[00:00:00.203,613] [0m<inf> lis2dh: int1 on GPIO_0.06[0m
[00:00:00.204,071] [1;31m<err> os: Exception occurred in Secure State[0m
[00:00:00.204,528] [1;31m<err> os: ***** HARD FAULT *****[0m
[00:00:00.204,925] [1;31m<err> os: Fault escalation (see below)[0m
[00:00:00.205,383] [1;31m<err> os: ***** BUS FAULT *****[0m
[00:00:00.205,780] [1;31m<err> os: Precise data bus error[0m
[00:00:00.206,207] [1;31m<err> os: BFAR Address: 0x50008158[0m
[00:00:00.206,665] [1;31m<err> os: r0/a1: 0x00000000 r1/a2: 0x000485ac r2/a3: 0x00000000[0m
[00:00:00.207,275] [1;31m<err> os: r3/a4: 0x00000001 r12/ip: 0x0000a000 r14/lr: 0x0003620d[0m
[00:00:00.207,916] [1;31m<err> os: xpsr: 0x21000000[0m
[00:00:00.208,343] [1;31m<err> os: s[ 0]: 0x00000000 s[ 1]: 0x00000000 s[ 2]: 0x00000000 s[ 3]: 0x00000000[0m
[00:00:00.209,106] [1;31m<err> os: s[ 4]: 0x00000000 s[ 5]: 0x00000000 s[ 6]: 0x00000000 s[ 7]: 0x00000000[0m
[00:00:00.209,838] [1;31m<err> os: s[ 8]: 0x00000000[00:00:00.203,338] [0m<inf> lis2dh: int1 on GPIO_0.06[0m

[Simon]

It seems like you got help with this here: https://devzone.nordicsemi.com/f/nordic-q-a/73838/lis2dh-int1-triggers-on-nrf9160. Should we close this case?

[NautDesigner]

How do you specify the 2nd interrupt pin? By adding a comma after the first irq-gpios?

[Simon]

Yes, that's how you do it. Check how it's done here: https://github.com/nrfconnect/sdk-zephyr/blob/v2.4.99-ncs2/boards/arm/nrf9160_innblue21/nrf9160_innblue21_common.dts#L98.

It is often helpful to search trough NCS/Zephyr to figure out how stuff are done, either by using the search tools of an IDE, or the git grep command. Now I simply typed in git grep irq-gpios in the Zephyr repo and found the above.

Best regards,

Simon

[Jared]

FYI opened a bug about this: https://github.com/zephyrproject-rtos/zephyr/issues/34794

I think previously if INT2 was not defined, it would fail gracefully. Something in the device tree API has changed which causes Zephyr to fault.

[NautDesigner]

Thanks for the help.