SPRUIW9C October 2021 – March 2024 TMS320F280033 , TMS320F280034 , TMS320F280034-Q1 , TMS320F280036-Q1 , TMS320F280036C-Q1 , TMS320F280037 , TMS320F280037-Q1 , TMS320F280037C , TMS320F280037C-Q1 , TMS320F280038-Q1 , TMS320F280038C-Q1 , TMS320F280039 , TMS320F280039-Q1 , TMS320F280039C , TMS320F280039C-Q1
After the new firmware has been programmed to Flash, the user application code needs to determine when appropriate to switchover to the new firmware. The techniques to determine this difference between real-time critical firmware running on the CPU and CLA, and these techniques are beyond the scope of this document. The techniques are described in the LFU system reference design guide.
The device supports two register bits that can be set or reset to indicate that the LFU switchover is in progress on the CPU (LFUConfig.LFU_CPU) and CLA (LFUConfig.LFU_CLA1). These bits do not impact any hardware logic on the device. For example, LFUConfig.LFU_CPU can be set by the user application code at the start of switchover, and then tested in the initialization code in main(). This can enable only the LFU switchover specific initialization to be performed (for example, PIE vector table swap, LS0/LS1 RAM memory swap), while bypassing all other initialization that typically happens after a device reset.