quad-enable-requirements = "NONE" does not compile for NRF QSPI driver

RE: quad-enable-requirements = "NONE" does not compile for NRF QSPI driver

Kazi Afroza Sultana — Tue, 28 Oct 2025 11:19:26 GMT

Hello,

This problem is fixed here drivers: flash: nrf_qspi_nor: Fix compilation with QER set to NONE by anangl · Pull Request #98387 · zephyrproject-rtos/zephyr · GitHub you can look at.

Thanks.

Kazi

RE: quad-enable-requirements = "NONE" does not compile for NRF QSPI driver

reavertm — Sat, 18 Oct 2025 22:05:55 GMT

> No, it doesn't. If you have CONFIG_SPI_NOR_SFDP_DEVICETREE set in config, sfdp-bpf and other sfdp-* properties will not be ignored.

You sound quite confident about it but I think you are mistaken.

CONFIG_SPI_NOR_.. is for jedec,spi-nor driver, not for nordic,qspi-nor driver.

And compatible = "jedec,spi-nor" cannot be used under qspi devicetree node. Logical, as spi-nor is different driver.

I can see callback setting only:

#if defined(CONFIG_FLASH_JESD216_API)
.sfdp_read = qspi_sfdp_read,
.read_jedec_id = qspi_read_jedec_id,
#endif /* CONFIG_FLASH_JESD216_API */

Other drivers do call jesd216_bfp_read_support() to parse command opcodes, nordic,qspi-nor does not.

Logic analyzer also doesn't show any "enable 32bit addrs" commands being sent, as would have been retrieved from sfdp-bpf property.

In fact, this is another "problem" - "enter 32bit addressing" command is only sent when enter-4byte-addr devicetree property is defined. I think it should have been sent when "address-size-32" property is set (either from hardcoded default value, devicetree property or SFDPD). But that one can be configured at least.

I think the nordic,qspi-nor would benefit from being able to define command opcodes for "enabling quad operations". Not all flash modules do that via status register - in ex memory in question MT25QL01GBBB doesn't - we switched to W25Q01JV because of this.

RE: quad-enable-requirements = "NONE" does not compile for NRF QSPI driver

Kazi Afroza Sultana — Fri, 17 Oct 2025 10:35:04 GMT

''If I'm reading code for driver well, nordic,qspi-nor ignores sfdp-bpf and other sfdp-* properties, right?''

No, it doesn't. If you have CONFIG_SPI_NOR_SFDP_DEVICETREE set in config, sfdp-bpf and other sfdp-* properties will not be ignored.

''They are for jedec,jesd216 driver?''

MCU Boot with sysbuild with SPI external flash

Yes. nordic,qspi-nor can also utilize these properties when configured to do so.

''That driver jedec,jesd216 can be used as fully functional QSPI driver?
Or it;s merely a driver trait-of sort that can use to mark in devicetree that given module supports SFDPD (in ex at runtime) for jedec,spi-nor driver?
Finally, can jedec,spi-nor be used as full-fledged QSPI driver?''

There is much specific information about this.The standard practice is to use nordic,qspi-nor for QSPI peripherals on Nordic SoCs.

I will discuss internally and will get back to you when there is an update.

RE: quad-enable-requirements = "NONE" does not compile for NRF QSPI driver

Kazi Afroza Sultana — Fri, 17 Oct 2025 09:06:01 GMT

Hello,

There is no official list of known good QSPI flash memories that could be used with nrf5340.

The nordic QSPI NOR driver in Zephyr expects a ''quad-enable-requirements'' property in the device tree. When it is set to ''NONE'' ( like in your devicetree), it leads to linker error.

You may try to use a supported value like ''S2B1v1'' in the device tree

&qspi {
    flash_disk: mt25ql01gb@0 {
        compatible = "nordic,qspi-nor";
        reg = <0>;
        writeoc = "pp4io";
        readoc = "read4io";
        sck-frequency = <8000000>;
        jedec-id = [20 ba 21];
        address-size-32;
        quad-enable-requirements = "S2B1v1"; // Try this as a workaround
        size = <0x8000000>;
        has-dpd;
        t-enter-dpd = <10000>;
        t-exit-dpd = <30000>;
    };
};

RE: quad-enable-requirements = "NONE" does not compile for NRF QSPI driver

reavertm — Wed, 15 Oct 2025 08:37:39 GMT

Well, it doesn't say anything about supported flash modules. It can send custom instructions, which I guess means it's all up to QSPI driver, rather than the chip, to support external peripheral over QSPI.

I have some other, more general questions as well, in context of latest released at the time of writing nRF Connect SDK 3.1.1.

If I'm reading code for driver well, nordic,qspi-nor ignores sfdp-bpf and other sfdp-* properties, right?
They are for jedec,jesd216 driver?
That driver jedec,jesd216 can be used as fully functional QSPI driver?
Or it;s merely a driver trait-of sort that can use to mark in devicetree that given module supports SFDPD (in ex at runtime) for jedec,spi-nor driver?
Finally, can jedec,spi-nor be used as full-fledged QSPI driver?

RE: quad-enable-requirements = "NONE" does not compile for NRF QSPI driver

Turbo J — Wed, 15 Oct 2025 06:28:25 GMT

The the technical manual for the CPU is called "Product Specification" or short PS.

RE: quad-enable-requirements = "NONE" does not compile for NRF QSPI driver

reavertm — Tue, 14 Oct 2025 17:15:25 GMT

Thanks for reply. What is PS? Product Support? You mean I should ask Nordic or there is a link I can check? If so, can you paste it?

RE: quad-enable-requirements = "NONE" does not compile for NRF QSPI driver

Turbo J — Tue, 14 Oct 2025 15:48:32 GMT

The QSPI peripherial is VERY picky about its hardware support, that error might be intentional.

Check the PS - your chip may not be accessible for this hardware.