nRF5340 QSPI isn't receiving data

[SimpleSoft]

Hello,

I'm using nRF5340 (as part of the U-blox NORA-B106 module) with Zephyr RTOS and latest SDK.

in the project file, I have: CONFIG_NRFX_QSPI=y
in device tree, I have:

    qspi_default: qspi_default {
        group1 {
            psels = <NRF_PSEL(QSPI_SCK, 1, 14)>,
                <NRF_PSEL(QSPI_CSN, 1, 12)>,
                <NRF_PSEL(QSPI_IO0, 1, 15)>,
                <NRF_PSEL(QSPI_IO1, 1, 13)>;
            bias-pull-up;
        };
    };

&qspi {
    status = "okay";
    pinctrl-0 = <&qspi_default>;
    pinctrl-1 = <&qspi_sleep>;
    pinctrl-names = "default", "sleep";
    compatible = "nordic,nrf-qspi";
    fm25v10: fm25v10gtrr@0 {
        compatible = "nordic,qspi-nor";
        reg = <0>;
        /* fm25v10 supports only pp and pp */
        writeoc = "pp";
        /* fm25v10 supports all readoc options */
        readoc = "fastread";
        sck-frequency = <40000000>;
        label = "FM25V10";
        jedec-id = [c2 24 00];
        size = <131072>;
    };
};

Pinout checked by the logic analyzer and I can see that QSPI is sending commands to read SR 0x05 and to read JEDEC ID ( 0x9F) and SPI flash sending data back correctly. But QSPI controller always gets 0's (I did check registers CINSTRDAT0 and CINSTRDAT1).

In GPIO IN mode, with PIN1.15 (MISO) I can see data toggling by connecting to VCC or GND.

VDD connected to 3.3V .

What can be the issue with QSPI controller?

[Susheel Nuguru]

I do not see anything obviously suspicious in the way you defined the qspi.

Not sure if the bias-pull-up is required but most of the samples does not seem to have this pull in the qspi_default in the pinctrl definition.

        readoc = "fastread";

I did not manage to see any external flash sample using fastread for readoc. Are you sure this is right?

Where did you get the overlay settings for FM25V10? Is this from the manufacturer?

[SimpleSoft]

Thank you for your answer.

"fastread" means using 1bit reading.

Here: zephyr/dts/bindings/mtd/nordic,qspi-nor.yaml
- "fastread"        # Single data line SPI, FAST_READ (0x0B)

Nevertheless, QSPI can't initialize - ChipID returns 0s, but SPI send data correctly back.

Overlay setting composed by me.

[Susheel Nuguru]

Then it is a bit of unknown territory for us as we do not have U-blox NORA-B106  to test. If you wait until next week, I can ask my colleague who comes back from vacation if he has seen anything like this or any other debugging direction to suggest.

[Susheel Nuguru]

My colleague helped me point out that we do not support fm25v10 with SPI and fm25v10 does not support QSPI so it solbes the mystery of why it does not work with qspi setting.

[SimpleSoft]

Thank you for your feedback. But the problem is not with FM25V10 itself, but with the QSPI controller.

When I send 0x9F command, CINSTRDAT0 and CINSTRDAT1 still contain 0x00, even if I short MISO to VCC. By oscilloscope, i see that CS/MISO/CLK outputs are correct.

I can attach another QSPI flash, but I'm sure - the problem will remain.