Before the two last lines that return from the interrupt, can you try adding this? l32r a14, .GPIO_STATUS_REG l32i a14, a14, 0 memw The idea is that the interrupt acknowledge may be 'stuck' in a load/store unit of the CPU or somewhere in a peripheral, and hasn't properly executed yet before the inte...

I used a webserver to serve those files, including a cgi to receive the hex values from the browser. Code is in the git repo (need to git clone this url for it to work) if you want to take a look, but be warned, I never really cleaned up that code.

Note that you probably leak memory by commenting out these free() calls...

If you're in an ISR, calling any function that uses a (non-ISR-specific) FreeRTOS function is illegal. You use two UART functions in your ISR, of which at least the latter likely uses a FreeRTOS function. Suggest you use the ISR to set a semaphore instead, then spin up a task to block on that semaph...

Yes, the hardware should be able to do that.

I think on these boards the red LED is directly connected to power. Try to measure if the 3.3V power rails is there. If not, you may have shorted out something, blowing something else up.

Gotcha. I don't see anything wrong with your setup from what you posted, but I'd bet that whatever is wrong has something to do with the code somehow re-initializing the pins the flash is connected to, or otherwise stopping them from working to transfer flash data.

Suggest you mail sales at espressif dot com for this, as I don't think any of our RF engineers are on this forum.

No, that's a perfectly feasible way to do things, especially useful if the code that handles the interrupts is similar between timers.