Problem was caused by trying to do all of this deinitialisation in the USB mount changed callback, which comes from the USB task. Doing it from a separate task resolved the issues and allowed me to deinitialise everything as required.

What is the correct way to safely and orderly terminate TinyUSB MSC after the drive is ejected on the host, and fully deinitialise and release the card and SDMMC peripheral for our application to then use?

After ejection, while the card is then usable by our application, removing the card from the ...

Problem solved. I have achieved 102.5 KB/s with 2M PHY after disabling all logging output.

With 1M PHY this drops to 68.6 KB/s (a bit above the 500 Kbps (63 KB/s) given in the README).

I've been experimenting with the throughput_app BLE example and have found that changing the PHY from 1M to 2M does nothing to increase the reported throughput value. Is this expected?

I had expected there to be a significant increase in throughput at the application level when using the 2M PHY ...

We managed to fix our issue.

In one of the modules of our application, we had a uint8_t* global that was initialised to point to a const string. We were then modifying that variable, meaning we were modifying constant program data. Changing the variable to an array that is initialised to the value ...

We're still having this issue and have made no further progress on it. Does anyone have any ideas?

Thanks.

I'm using ESP-IDF version 5.0.2.

Checking with the Eclipse debugger, EXCAUSE is set to 4, which I guess is the latter of your two points (Level1InterruptCause). Just to see if it would change anything I increased the interrupt watchdog timeout to 10 seconds, but that didn't have any impact. Let me know if there's any other info you ...

This issue has recurred in the same was as explained above, again after having made no specific changes to the related code (as this feature had been finished and working).

I don't have any further information to give or look for on this. The call to esp_image_verify() inside esp_ota_end() is ...

So I had another look at this again today, and found that the problem has gone away on both of the boards I was using (both of which yesterday had OTA updates not working in the way described above), despite not making any further changes to try and fix this.

In terms of your question, I don't ...