nRF54H20 SPI CS assert issue

[Anuj Pathak]

Hi

I'm trying to communicate with ICM45686 using nRF54H20 and SPI CLK, MISO, MOSI state appear correct but CS pin is not asserting/deasserting 

following it the scope capture, Yellow CS, Green Clock, Blue MOSI, Purple is MISO.
Note: this is only one capture and CS behaviour is completely noisy (undeterministic)


Following are Pin ctrl and spi133 node definition from zephyr.dts

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

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

&spi133 {
	status = "okay";
	pinctrl-0 = <&spi133_default>;
	pinctrl-1 = <&spi133_sleep>;
	pinctrl-names = "default", "sleep";
	memory-regions = <&cpuapp_dma_region>;
	cs-gpios = <&gpio2 7 (GPIO_ACTIVE_LOW)>;
};

And i'm using SPI_SHELL commands as follows

spi conf spi133 200000
spi transceive spi133 0xF2 0x55

[Hung Bui]

Hi Anuj,

Could you try to test the CS pin on other GPIOs ? 

On the DK pin 2.7 is used for RTS UART136, have you checked if UART136 is not active and the pin is not used by UART ? 
Could you send us your board's device tree files ? 

Could you try to reproduce using one of our spim sample for example nrfx_spim/blocking ? 

[Anuj Pathak]

The issue is resolved, it turns out to be a pin conflict issue during board migration