spi_nrfx_spim: configure: Failed to initialize nrfx driver: 0bad0004 on custom nRF54l15 board

[HannahPadd]

Good day,

I am currently working on adding support for the nRF54l15 SoC and adding support for multiple imu sensors to be connected at once. However, I have been unable to get any form of spi to work on our custom board. When running the transceive function I get this error: spi_nrfx_spim: configure: Failed to initialize nrfx driver: 0bad0004.

Devicetree Configuration

&pinctrl {
	/omit-if-no-ref/ spi00_default: spi00_default {
		group1 {
			psels = <NRF_PSEL(SPIM_SCK, 2, 1)>,
					<NRF_PSEL(SPIM_MOSI, 2, 2)>;
		};

		group2 {
			psels = <NRF_PSEL(SPIM_MISO, 2, 4)>;
			bias-pull-up;
		};
	};

	/omit-if-no-ref/ spi00_sleep: spi00_sleep {
		group1 {
			psels = <NRF_PSEL(SPIM_SCK, 2, 1)>,
					<NRF_PSEL(SPIM_MOSI, 2, 2)>,
					<NRF_PSEL(SPIM_MISO, 2, 4)>;
			low-power-enable;
		};
	};
};

&spi00 {
	status = "okay";
	compatible = "nordic,nrf-spim";
	pinctrl-0 = <&spi00_default>;
	pinctrl-1 = <&spi00_sleep>;
	pinctrl-names = "default", "sleep";

	imu_spi: imu_spi@0 {
		status = "okay";
		compatible = "vnd,spi-device";
		label = "imu-spi";
		reg = <0>;
		spi-max-frequency = <DT_FREQ_M(16)>;
	};
};

I'd like to note that there are multiple imu devices connected and we control their CS via a shift register. I have confirmed that only one CS is low when performing read/write over spi. I can provide more info if needed.

[Vidar Berg]

Hello,

The error code corresponds to NRFX_ERROR_INVALID_PARAM, so it something with the input parameters passed to the SPI init function that causes it to return early with this error. Are you able to step through the function to see what it is failing? I am also happy to debug this here if you can provide me a minimal version of your project.

Best regards,

Vidar

[HannahPadd]

Heyo, 

My apologies for the delayed response. 

Here is the code: https://github.com/HannahPadd/Glove_imu_test

I managed to past the SPI driver error by making sure the SPI speed is set correctly. However, I am still not getting any response from my connected device.

[Vidar Berg]

Hi,

Good to hear that you were able to determine which parameter was invalid. As for why the sensor is not responding, this is a bit more challenging for me to debug since I don't have the hardware. Is the RX buffer filled with 1's or 0's, and have you tried to probe the bus lines with a scope or logic analyser to confirm that the commands are sent correctly on the TX line?

[HannahPadd]

Heyo,

I want to start with apologizing for the late response.

It turned out to be a signal integrity issue which we fixed by setting the drive mode in the devicetree.

nordic,drive-mode = <NRF_DRIVE_EOE1>;

In the pinctrl for the spi default node. This fixed our signal integrity and we can now read all our sensors.

This is what it would look like if anyone is also running into the same issue.

	/omit-if-no-ref/ spi00_default: spi00_default {
		group1 {
			psels = <NRF_PSEL(SPIM_SCK, 2, 1)>,
				<NRF_PSEL(SPIM_MOSI, 2, 2)>;
			nordic,drive-mode = <NRF_DRIVE_E0E1>;
		};

		group2 {
			psels = <NRF_PSEL(SPIM_MISO, 2, 4)>;
			bias-pull-up;
		};
	};

[Vidar Berg]

Good to hear that you found the problem, thank you for taking the time to report back. The extra drive strength may be necessary at higher frequencies or when testing with long leads.