DeviceTree Errors on QSPI

[fgeldenh]

The following Pin definitions for QSPI result in Errors during build using NRF Connect SDK. This exact configuration is working on a custom design using nRF5 SDK using the QSPI driver.

If I change the Port1 Pins to Port 0, then it is OK. What is wrong with using Port1 pins on NRF Connect?

qspi_default: qspi_default {
group1 {
psels = <NRF_PSEL(QSPI_SCK, 1, 09)>,
<NRF_PSEL(QSPI_IO0, 0, 04)>,
<NRF_PSEL(QSPI_IO1, 0, 26)>,
<NRF_PSEL(QSPI_IO2, 0, 25)>,
<NRF_PSEL(QSPI_IO3, 1, 08)>,
<NRF_PSEL(QSPI_CSN, 0, 27)>;
};
};

qspi_sleep: qspi_sleep {
group1 {
psels = <NRF_PSEL(QSPI_SCK, 1, 09)>,
<NRF_PSEL(QSPI_IO0, 0, 04)>,
<NRF_PSEL(QSPI_IO1, 0, 26)>,
<NRF_PSEL(QSPI_IO2, 0, 25)>,
<NRF_PSEL(QSPI_IO3, 1, 08)>,
<NRF_PSEL(QSPI_CSN, 0, 27)>;
low-power-enable;
};

[dejans]

Hi,

Which NCS version do you use?

The following Pin definitions for QSPI result in Errors during build using NRF Connect SDK.

Could you please provide error log?

Best regards,
Dejan

[fgeldenh]

I am using NCS 2.0. I attach my custom board relevant files as well as the output log.

I also managed to reproduce the same issue by using the spi_flash sample with the nrf52840dk_nrf52840 board. If I change any pin in the nrf52840dk_nrf52840-pinctrl.dtsi file to use port 1, then I get the same result. For some reason the build does not like me to use PORT 1 for qspi pins.

3660.files.zip

[dejans]

Hi,

I have tested your configuration. I have seen the same behavior as you described it. 
You should avoid using leading zeros for pin numbers.

The line

<NRF_PSEL(QSPI_IO3, 1, 08)>,

should be 

<NRF_PSEL(QSPI_IO3, 1, 8)>,

Best regards,
Dejan

[fgeldenh]

Thank You - what a silly mistake. Should have tried that myself.