QSPI not clearing "BUSY"

RE: QSPI not clearing "BUSY"

Kenneth — Wed, 03 Apr 2019 20:35:09 GMT

Thanks for updating the case with verified answer, I would not have thought of that. Good to hear you solved it.

RE: QSPI not clearing "BUSY"

Adam Gerken — Tue, 02 Apr 2019 15:57:37 GMT

Alright, so apparently, writes need to be in multiples of 4 bytes?! I totally missed that, but looking at the flash's data sheet it makes sense.

RE: QSPI not clearing "BUSY"

Adam Gerken — Tue, 02 Apr 2019 14:40:46 GMT

Ok, thinking out lout here:

In nrfx_qspi_init m_cb.interrupt_driven is set to false, and interrupts are disabled.

In nrfx_qspi_task_perform if interrupt_driven is true, it fails out, if it's false, it sets interrupt_driven to true, and enables the interrupts.

Nothing I can find ever disables the interrupts or sets interrupt_driven back to false, thus causing this to return NRFX_ERROR_BUSY every time. This would kind of explain my issue, I guess. I'm curious how the qspi example does a write than a read without setting interrupt_driven back to false though.

RE: QSPI not clearing "BUSY"

Adam Gerken — Mon, 01 Apr 2019 20:11:55 GMT

Yeah, makes sense. Moving the interrupt priority level up each step, up to 0, didn't change anything, neither did removing everything else from my project.

Thanks for trying though.

RE: QSPI not clearing "BUSY"

Kenneth — Mon, 01 Apr 2019 19:59:32 GMT

[quote user="Adam Gerken"]Will this interrupt not trigger if there is a higher one pending or something?[/quote]

Higher level interrupts must finish executing before the lower level interrupt handlers will run yes. Not sure if I have any good suggestion other than either increase the priority of the qspi to see if that changes things and/or disable other modules in your application until you can see a change?

RE: QSPI not clearing "BUSY"

Adam Gerken — Mon, 01 Apr 2019 19:22:04 GMT

I initially thought the same thing, but the transfer is being called from my main function right now. The interrupt level is 6, the only others I changed are higher than that. Will this interrupt not trigger if there is a higher one pending or something? I have handlers for all the other ones so I'm not sure what it could be.

I thought this was curious in nrfx_qspi.c around line 148 in nrfx_qspi_init()

/* QSPI interrupt is disabled because the device should be enabled in polling mode (wait for activate
       task event ready)*/
    nrf_qspi_int_disable(NRF_QSPI, NRF_QSPI_INT_READY_MASK);

This line is also in the qspi example, but the qspi_handler works just fine in that example.

RE: QSPI not clearing "BUSY"

Kenneth — Mon, 01 Apr 2019 12:57:38 GMT

Can it be a interrupt priority issue, for instance that you are trying to call qspi transfer from an interrupt with same priority as the qspi_handler() is pending?

Also make sure to set m_qspi_finished as volatile.

RE: QSPI not clearing "BUSY"

Adam Gerken — Fri, 29 Mar 2019 17:56:46 GMT

Actually, it looks like it just checks the status register and sets the write bit, but never sends any data. Still returns error 0 though: