the error code is not 0x10 but 0x1D. Bad display.
So this is an error mutex failure. Weird too but not related to memory
what can cause a mutex error on destroy exactly ? When Destroy is requested, nothing can happen after so why is mutex not "freeable" anyway ?
Globally, I find that CX3 firmware and or hardware include some cases that once reached, device is dead and only solution is to unplug. That is painfull and not very reliable.
I'd like to have a feature where device is "resetted" COMPLETLY BUT not disconnected.
For example : EP0 error, dead no more EP0 communication after (hardware error), can't do nothing. here , impossible Mutex to get, dead, no more dma use even for destroying the current one.
Any solution or workaround ? BR
Please post the snippet in which you called the DMADestroy.