[SPI] not device ready

RE: [SPI] not device ready

runsiv — Thu, 04 Jul 2024 08:40:55 GMT

I had another look at our application. Instead of running with 2x buffers, could you try the implementation we did on SPI lesson on devacademy

For some reason it looks like you are getting a "1" on the MOSI line after sending the register address

Regards

Runar

RE: [SPI] not device ready

Robotics Gun — Tue, 02 Jul 2024 21:26:32 GMT

As you mentioned, GPIO HIGH level Voltage of SPI Pins are
nRF52-DK: 3.15V
STM F301RB: 3.59V

Hmm interesting. Do you think this can cause the issue?

RE: [SPI] not device ready

runsiv — Tue, 02 Jul 2024 12:28:56 GMT

Thank you. What is the gpio voltage you are running? I just noticed that it was lower then the STM you compared it to.

Regards

Runar

RE: [SPI] not device ready

Robotics Gun — Tue, 02 Jul 2024 07:41:28 GMT

I followed your instruction to use zephyr official driver for icm-42688.

Setting up the soft-reset and clear reset flag done successfully.

Especially reading the reset flag is done through MISO pin and it's done properly.

Hmm. Very interesting. I hope I am making a silly mistake but I can't figure it out. Please help 🙃

#include <zephyr/types.h>
#include <zephyr/drivers/gpio.h>0
#include <zephyr/drivers/spi.h>
#include <zephyr/sys/util.h>
#include <zephyr/drivers/sensor.h> // sensor driver

/* 1000 msec = 1 sec */
#define SLEEP_TIME_MS 1000
#define ICM42688P_SPI_NODE DT_NODELABEL(icm42688)
#define ICM42670P_SPI_CS_DT_SPEC SPI_CS_GPIOS_DT_SPEC_GET(DT_NODELABEL(reg_icm42688))

int main(void)
{
	printk("sensor: Hello.\n");

	const struct device *spi_dev = DEVICE_DT_GET(ICM42688P_SPI_NODE);
	const struct gpio_dt_spec spim_cs_gpio = ICM42670P_SPI_CS_DT_SPEC;
	if (!device_is_ready(spi_dev))
	{
		printk("sensor: device not ready.\n");
		return 0;
	}
	else
	{
		printk("sensor: device ready.\n");
	}

	// while (true)
	// {

	// 	k_sleep(K_MSEC(1000));
	// }

	return 0;
}

RE: [SPI] not device ready

runsiv — Mon, 01 Jul 2024 13:55:34 GMT

Ah that maks more sense. I would recommend that you change your application to use the ICM42688 while you test now. So that the correct driver is enabled. If you switch to ICM42688 in your application, do you see any difference in the result?
I will need to ask a colleage regarding the MOSI high until next byte

Regards

Runar

RE: [SPI] not device ready

Robotics Gun — Mon, 01 Jul 2024 09:57:22 GMT

Sorry. I didn't mentioned that I used ICM42688 for testing before PCB arrive.
So it's WHO AM I register value should be 0x47.

When you see the waveform from STM32 MOSI line(=Green Colored) stay HIGH until next byte clock starts. Is it possible to have it in nRF?

If yes, how to?

RE: [SPI] not device ready

runsiv — Mon, 01 Jul 2024 09:08:46 GMT

I had a look in the datasheet. Are you sure you are using the ICM42670? I would expect whoami to be 0x67 according to both the driver and the datasheet. https://github.com/nrfconnect/sdk-zephyr/blob/main/drivers/sensor/tdk/icm42670/icm42670_reg.h#L259

Regards

Runar

RE: [SPI] not device ready

Robotics Gun — Mon, 01 Jul 2024 05:13:39 GMT

I solved the issue with nRF SPI master/slave example.

But I faced another issue.

I am using a sensor with its WHO AM I register value is 0x47.

However, I keep receiving data from it 0x4C.

To verify that the sensor unit has no issue, I tested with STM32.

Please check it below oscilloscope waveform and decode value.

[STM32]: sensor response with correct value

[nRF52-DK]: sensor response with wrong value

So we can conclude that the sensor has no problem. I used the same jumber cables and same oscilloscope setup.

Here's the device tree and C code

icm42670p: &spi2 {
	compatible = "nordic,nrf-spi";
	// compatible = "nordic,nrf-spim";
	status = "okay";
	pinctrl-0 = <&spi1_default>;
	pinctrl-names = "default";
	cs-gpios = <&gpio0 15 GPIO_ACTIVE_LOW>;
	overrun-character = <1>;
	reg_icm42670p: reg_icm42670p@0 {
		reg = <0>;
	};

	max-frequency = <DT_FREQ_M(8)>;
};

/**
 * The first bit of the first byte contains the Read/Write bit and indicates the Read (1) operation
 * The first bit of the first byte contains the Read/Write bit and indicates the Write (0) operation.
 */
int spi_read_register(const struct device *spi_dev, const struct spi_config *spi_cfg, uint8_t address, uint8_t *data, size_t len)
{
    uint8_t tx_buf = REG_SPI_READ_BIT | address; // Set read bit
    printk("tx_buf: %x\n", tx_buf);

    struct spi_buf tx_bufs = {
        .buf = &tx_buf,
        .len = 1,
    };

    struct spi_buf_set tx = {
        .buffers = &tx_bufs,
        .count = 1
    };
    
    // size determined by tx buffer size
    struct spi_buf rx_buf[2] = {
        {
            .buf = NULL,
            // .len = 1,
            .len = sizeof(tx_buf),
        },
        {
            .buf = data,
            .len = len,
        }};

    const struct spi_buf_set rx = {
        .buffers = rx_buf,
        // .count = ARRAY_SIZE(rx_buf),
        .count = 2,
        .count = 2,
    };

    int ret = spi_transceive(spi_dev, spi_cfg, &tx, &rx);
    if (ret == 0)
    {
        printk("Read from address: 0x%x, received data: 0x%x\n", address, *data);
    }
    else
    {
        printk("SPI transceive error: %d\n", ret);
    }

    return ret;
}

RE: [SPI] not device ready

runsiv — Thu, 27 Jun 2024 11:19:21 GMT

Could you enable logging and build your application with optimized for debug and post the log?

Could you also show me your overlay?

Regards

Runar