A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
This does not block boot for 3 minutes. Please check the Note below the flow chart in the TRM and extract here:
DMSC ROM sets up a 3-minute watchdog timer (MCU_RTI0) timeout. During this time, the MCU boot needs to get completed, otherwise a WDT reset will occur. Once the R5 image is loaded (SBL/SPL), DMSC ROM will restart the watchdog timer for additional 3 minutes upon entering the R5 SBL. The customer-provided MCU image needs to load and install the TI-provided SYSFW image into the DMSC, which will manage the watchdog timer during run time.
If customer set UART boot mode for first boot and QSPI boot mode for secondary boot. After Uart booting, he must wait for 3 minutes then it entered the QSPI boot mode.
If he set QSPI boot mode directly, then it boot immediately.
Considering UART boot as primary boot mode and SPI boot as secondary boot mode, If in-case UART boot fails due to any reason , Switching to SPI boot mode will happen immediately after concluding failure , ROM will not wait for 3minutes duration to switch to SPI boot mode.
3minutes duration is for system to recover from unrecoverable failures where it enters panic mode and WDT expiry happens after 3 minutes.
Its like fresh boot where system starts with UART.
Customer set the primary boot for flashing app image. He wants to enter the secondary bootloader immediately when not flashing app image, but in fact, he must wait for 3 minutes the watchdog is timeout, then it enter the QSPI boot.
As Ajay pointed out the time out is there for system to recover (from unrecoverable failures) and not for bootloader to wait until WDT expires. Please let us know if this clarifies.
