NRF52840dk - Unable to get ism330dhcx on SPI working

RE: NRF52840dk - Unable to get ism330dhcx on SPI working

Jared — Mon, 08 May 2023 13:27:40 GMT

Hi,

I see that you've posted the question in the discussion on Github, I think this issue is a driver issue. Hopefully some of the developers can either provide a fix or explain why this happens.

regards

Jared

RE: NRF52840dk - Unable to get ism330dhcx on SPI working

flamerten — Wed, 03 May 2023 16:12:10 GMT

Hi Jared

Thanks for helping with the issue. Although from an initial viewpoint the problem is fixed, I still run into a problem as the IMU does not pass the device_is_ready stage.

[00:00:00.377,807] <inf> basic_IMU: Unable to retrieve IMU
[00:00:00.250,488] <inf> ISM330DHCX: chip id 0x0, chip id should be 0x6b
[00:00:00.250,518] <dbg> ISM330DHCX: ism330dhcx_init_chip: Invalid chip id 0x0
[00:00:00.250,549] <dbg> ISM330DHCX: ism330dhcx_init: failed to initialize chip
*** Booting Zephyr OS build v3.2.99-ncs2 ***
[00:00:00.250,640] <inf> basic_IMU: Error: Device "ism330dhcx@0" is not ready; check the driver initialization logs for errors.

[00:00:00.250,640] <inf> basic_IMU: Unable to retrieve IMU

I have looked deeper into the fix made and I have noticed that the user had an additional line at line 107 that my version of Zephyr does not have. This line fails compilation.

data->ctx_spi.mdelay = (stmdev_mdelay_ptr) stmemsc_mdelay;

EDIT: To solve this, I updated the ST ISM330DHCX driver, specifically the one found at hal_st/sensor/stmemsc/ism330dhcx_STdC/driver at master · zephyrproject-rtos/hal_st (github.com) and also updated the ISM drivers provided by Zephyr. So I'm not too sure why there is still the issue. I am able to use SPI with another microcontroller which eliminates any wiring issues

I will request for more information from the user on the Github repo, and update if there was any fix made. Im not too sure why the line was not originally in my version of Zephyr. Can you confirm that this is a Zephyr Driver issue, and not solely restricted to the particular board I am using?

RE: NRF52840dk - Unable to get ism330dhcx on SPI working

Jared — Wed, 03 May 2023 11:54:46 GMT

Hi,

There was a new fix applied to the driver that seems to be directed to this bug, can you try to apply the fix and see if it fixed your issue? At my end it seems to have fixed the bug, but the program still doesn't reach main(), I think it's because I don't have the sensor connected. Can you confirm?

regards

Jared

RE: NRF52840dk - Unable to get ism330dhcx on SPI working

Jared — Thu, 27 Apr 2023 13:58:38 GMT

Hi,

For some reason only parts of the zip was downloaded last time, I now see that the whole project is already included. I'm able to reproduce your issue on my end.

Looks like some of the parameters that is passed to transceive() in spi_transceive() is causing the fault. I'm not entirely sure which, let me get back to you on this,

regards

Jared

RE: NRF52840dk - Unable to get ism330dhcx on SPI working

flamerten — Thu, 27 Apr 2023 12:14:23 GMT

Hi Jared, may i know what details of the project are needed? I have provided all the relevant files in the zip file in the comment above. The development board is the NRF52840DK and the exact sensor I was using is Adafruit ISM330DHCX

RE: NRF52840dk - Unable to get ism330dhcx on SPI working

Jared — Thu, 27 Apr 2023 12:01:51 GMT

Hi,

Could you share your project?

I would like to reproduce this on my end.

regards

Jared

RE: NRF52840dk - Unable to get ism330dhcx on SPI working

flamerten — Tue, 25 Apr 2023 13:32:58 GMT

Hi Jared

Attached below is my project directory, with the latest build devzone.nordicsemi.com/.../basic_5F00_imu.zip

RE: NRF52840dk - Unable to get ism330dhcx on SPI working

Jared — Tue, 25 Apr 2023 13:18:01 GMT

Hi,

Can you share your build folder?

regards
Jared

RE: NRF52840dk - Unable to get ism330dhcx on SPI working

flamerten — Mon, 24 Apr 2023 13:38:28 GMT

Hi Jared

In the main program, I only call printk()

Yes I have tried using addr2line and I have found the issue, which looks like its from the SPI driver. For reference, I have include the link to these lines.

https://github.com/zephyrproject-rtos/zephyr/blob/63e7f106eac5047313b96bfe06377b54d450fd66/include/zephyr/drivers/spi.h#L595

https://github.com/zephyrproject-rtos/zephyr/blob/63e7f106eac5047313b96bfe06377b54d450fd66/drivers/sensor/ism330dhcx/ism330dhcx_spi.c#L57

Im trying to understand why this error is being caused, It seems spi_transceive_dt() is not successful due to a driver issue.

PS C:\ncs\myapps\basic_imu\build> addr2line -e zephyr/zephyr.elf 0x0000d6d2
C:/ncs/v2.3.0/zephyr/include/zephyr/drivers/spi.h:595
PS C:\ncs\myapps\basic_imu\build> addr2line -e zephyr/zephyr.elf 0x0000d72f
C:/ncs/v2.3.0/zephyr/drivers/sensor/ism330dhcx/ism330dhcx_spi.c:57

RE: NRF52840dk - Unable to get ism330dhcx on SPI working

Jared — Mon, 24 Apr 2023 13:01:18 GMT

Hi,

Are you only calling printk() in your program, nothing else?

Could you try what my colleague Edvin is suggesting in this thread? Use addr2line and the Faulting instruction address to pinpoint what function is causing the assert in your code,

regards

Jared

RE: NRF52840dk - Unable to get ism330dhcx on SPI working

flamerten — Mon, 24 Apr 2023 11:26:31 GMT

Hello as an update, I enabled logging to see the output of the Sensor API and Sensor Driver.

Here are the results. It seems to go into an infinite loop, though Im not exactly sure where the error is coming from.

[00:00:00.376,464] <err> os: ***** BUS FAULT *****
[00:00:00.376,495] <err> os: Precise data bus error
[00:00:00.376,495] <err> os: BFAR Address: 0xff4672b5
[00:00:00.376,525] <err> os: r0/a1: 0x00005285 r1/a2: 0x00000010 r2/a3: 0xff4672b5
[00:00:00.376,525] <err> os: r3/a4: 0x2000286c r12/ip: 0x20002884 r14/lr: 0x0000d71b
[00:00:00.376,556] <err> os: xpsr: 0x01000000
[00:00:00.376,556] <err> os: Faulting instruction address (r15/pc): 0x0000d6be
[00:00:00.376,586] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
[00:00:00.376,617] <err> os: Current thread: 0x200008d0 (main)

RE: NRF52840dk - Unable to get ism330dhcx on SPI working

nordicator_prim3 — Fri, 21 Apr 2023 18:31:22 GMT

Perhaps the SPI driver for that device is getting hung somewhere. Have you tried reading the driver and placing some printk's to see if it's getting through the driver's init function? If it were to hang in the init function, then the device would never boot, so you wouldn't see your Hello World or anything else that happens in main.c.