The boot thread uses DMA for common memory bootloader instance. However, the DMA driver open & close in controlled in the main thread.

This introduces synchronization issues like the Drivers_close, effectively closing DMA driver, gets executed before the boot thread is completely done with loading all the images.

This issue came into light from supporting a recent customer debug.

Customer reported the DMA stuck on enabling DMA in the Bootloader module of their Stage2/DM application. If the Drivers_close function is commented in the main thread then the issue doesn't come.

The issue is reproducible locally with the attached patch on top of the clean MCU+ SDK v10.00.00.14.

If the fix patch is applied then the issue doesn't come.