Hi everyone,
we have recently encountered the following enigmatic problem:
There is a bootloader that uses the SPI_MASTER (4.3.20) App with DMA configuration and soon after jumps into the main application with the same SPI_MASTER App configuration. Somehow that blocks the SPI.
BUT: If we change the SPI_MASTER configuration in bootloader or in the application to "direct", then it works!.
Unfortunately, we cannot change either. The product is already out with the bootloader in DMA and the new application was coded with DMA as well and won't work correctly in "direct" mode.
So far we tried to reset the DMA manually again in application with no luck. Any brighter ideas? Thanks!
we have recently encountered the following enigmatic problem:
There is a bootloader that uses the SPI_MASTER (4.3.20) App with DMA configuration and soon after jumps into the main application with the same SPI_MASTER App configuration. Somehow that blocks the SPI.
BUT: If we change the SPI_MASTER configuration in bootloader or in the application to "direct", then it works!.
Unfortunately, we cannot change either. The product is already out with the bootloader in DMA and the new application was coded with DMA as well and won't work correctly in "direct" mode.
So far we tried to reset the DMA manually again in application with no luck. Any brighter ideas? Thanks!