qspi_nor: Failed to schedule device sleep: -16

[robsrick]

Hi

I'm using nrf toolchain/sdk 2.5.2.

Got a strange problem with my QSPI NOR flash interface.  when i run flash_erase i get error message "qspi_nor: Failed to schedule device sleep: -16" pretty much immediately. but the flash does seem to erase correctly.

in func qspi_erase() in nrf_qspi_nor.c if i put a breakpoint on ln689 which calls qspi_device_uninit(dev) and wait for 20+ seconds i do not receive the error. This corresponds roughly with whole long a full flash erase takes for my mx25r0835f flash chip. It looks like the qspi drivers aren't waiting for the flash to actually erase before deinit?

qspi_wait_for_completion returns immediately if that is relevant?

Any idea how i can resolve this issue?

Regards

Robert

call to flash_erase, where flash_dev points to the dts device below, address=0 and size = 1048576

return flash_erase(flash_dev, address, size);

Relevant section of my dts:

&qspi {

    compatible= "nordic,nrf-qspi";

    status = "okay";

    pinctrl-0 = <&qspi_default>;

    pinctrl-1 = <&qspi_sleep>;

    pinctrl-names = "default", "sleep";

    mx25r08: mx25r0835f@0 {

        compatible = "nordic,qspi-nor";

        reg = <0>;

        sck-frequency = <50000000>;

        jedec-id = [ c2 28 14  ];

        size = <0x0800000>; /* flash capacity in bits */

        has-dpd;

        t-enter-dpd = <10000>;

        t-exit-dpd = <35000>;

    };

};

[Sigurd Hellesvik]

Hi,

You can see this with a simple sample where you only write/erase from external flash, right?

Do you have a nRF52840DK?
If so, can you test the same code on the nRF52840DK, to see if you see the same error on that?
It would be useful to test if the error is related to the specific external flash or the firmware.

Regards,
Sigurd Hellesvik

[robsrick]

Hi,

Using a DK with the built in flash does not result in this error so it seems to be linked to the flash chip I've got on my custom board.

The test code i've got set up is simply erasing and writing to the flash in a single thread.

Regards

Robert

[robsrick]

thanks!

[BertL]

It seems that i'm running into the same issue with sdk 2.6.0. I'm writing to a littlefs partition on external flash connected through qspi and sometimes I also get the pm_device_runtime_put failed: -16 error in the logs. When this happens the write seems to fail and the consumption of the device goes from 30 uA to almost 1mA.

I expect that this happens when littlefs has to erase a sector on the flash.

Hope that there is a solution soon, if I can test anything, just let me know!

[BertL]

For now I'm using the suggestion of robsrick to add a 250ms sleep before qspi_wait_for_completion in the qspi_erase function. With this hack, the issue cannot be reproduced anymore.

Of course I'm very interested in a proper fix ;)

[Sigurd Hellesvik]

I have noted down your experience on our internal ticket as well BertL.

[BertL]

Thanks Sigurd Hellesvik ! I'm available for testing/debugging if necessary

[BertL]

Just tested with SDK 2.6.1, but the issue is still there. Any updates Sigurd Hellesvik ? Let me know if more information is needed.

[Sigurd Hellesvik]

The internal ticket I made for this issue is still waiting for our developers.

Thanks for letting me know that the issue is still present in v2.6.1