TIDUEY4D August 2022 – December 2022
Table 3-1 lists the key target executable files that will be needed to run the LFU examples. The locations of the projects, the specific project build configurations that need to be used to build the output executables, and the locations where the output executables need to be placed are also mentioned.
FILE/FOLDER NAME | CONTROL LOOP RUNS ON? | PROJECT BUILD CONFIGURATION | DESCRIPTION |
---|---|---|---|
flashapi_ex2_sci_kernel.out | NA | BANK0_LDFU_ROM | Output file after building the flashapi_ex2_sci_kernel project, which is the Custom Bootloader (the project will be located at <C2000Ware_DigitalPower_SDK_path>\solutions\tidm_02011\f28004x\examples\flash\CCS) |
flashapi_ex2_sci_kernel.out | .NA | BANK1_LDFU_ROM | Same as above |
buck_F28004x_lfuBANK0FLASH.txt | CPU | BANK0_FLASH | Output file post conversion to .txt of the buck_F28004x_lfu project, which is the Application (the project will be located at <C2000Ware_DigitalPower_SDK_path>\solutions\tidm_02011\f28004x\ccs) Project is built with compiler pre-defined symbol BUCK_CONTROL_RUNNING_ON_CPU Copy the generated .txt file to <C2000Ware_DigitalPower_SDK_path>\c2000ware\utilities\flash_programmers\serial_flash_programmer |
buck_F28004x_lfuBANK1FLASH.txt | CPU | BANK1_FLASH | Same as above |
buck_F28004x_lfu_controlloopBANK0FLASH.txt | CPU | BANK0_FLASH | Output file post conversion to .txt of the buck_F28004x_lfu_controlloop project, which is the Application (the project will be located at <C2000Ware_DigitalPower_SDK_path>\solutions\tidm_02011\f28004x\ccs) Project is built with compiler pre-defined symbol BUCK_CONTROL_RUNNING_ON_CPU Copy the generated .txt file to <C2000Ware_DigitalPower_SDK_path>\c2000ware\utilities\flash_programmers\serial_flash_programmer |
buck_F28004x_lfu_controlloopBANK1FLASH.txt | CPU | BANK1_FLASH | Same as above |
buck_F28004x_lfuBANK0FLASH_cla.txt | CLA | BANK0_FLASH | Output file post conversion to .txt of the buck_F28004x_lfu project, which is the Application (the project will be located at <C2000Ware_DigitalPower_SDK_path>\solutions\tidm_02011\f28004x\ccs) Project is built with compiler pre-defined symbol BUCK_CONTROL_RUNNING_ON_CLA. Resulting .txt is renamed to include an “_cla” Copy the generated .txt file to <C2000Ware_DigitalPower_SDK_path>\c2000ware\utilities\flash_programmers\serial_flash_programmer |
buck_F28004x_lfuBANK1FLASH_cla.txt | CLA | BANK1_FLASH | Same as above |
buck_F28004x_lfu_controlloopBANK0FLASH_cla.txt | CLA | BANK0_FLASH | Output file post conversion to .txt of the buck_F28004x_lfu_controlloop project, which is the Application (the project will be located at <C2000Ware_DigitalPower_SDK_path>\solutions\tidm_02011\f28004x\ccs) Project is built with compiler pre-defined symbol BUCK_CONTROL_RUNNING_ON_CLA. Resulting .txt is renamed to include an “_cla” Copy the generated .txt file to <C2000Ware_DigitalPower_SDK_path>\c2000ware\utilities\flash_programmers\serial_flash_programmer |
buck_F28004x_lfu_controlloopBANK1FLASH_cla.txt | CLA | BANK1_FLASH | Same as above |
serial_flash_programmer_appln.exe | .exe | - | This is the host side serial flash programmer executable for loading the Application to Flash on the target device It is present at <C2000Ware_DigitalPower_SDK_path>\c2000ware\utilities\flash_programmers\serial_flash_programmer |
FILE/FOLDER NAME | CONTROL LOOP RUNS ON? | PROJECT BUILD CONFIGURATION | DESCRIPTION |
---|---|---|---|
flash_kernel_ex3_sci_flash_kernel.out | NA | BANK0_LDFU | Output file after building the flash_kernel_ex3_sci_flash_kernel project, which is the Custom Bootloader (the project will be located at <C2000Ware_DigitalPower_SDK_path>\solutions\tidm_02011\f28003x\examples\flash\CCS) |
flash_kernel_ex3_sci_flash_kernel.out | .NA | BANK1_LDFU | Same as above |
buck_F28003x_lfuBANK0FLASH.txt | CPU | BANK0_FLASH | Output file post
conversion to .txt of the buck_F28003x_lfu project, which is
the Application (the project will be located at
<C2000Ware_DigitalPower_SDK_path>\solutions\tidm_02011\f28003x\ccs)
Project is built with compiler pre-defined symbol BUCK_CONTROL_RUNNING_ON_CPU Copy the generated .txt file to <C2000Ware_DigitalPower_SDK_path>\c2000ware\utilities\flash_programmers\serial_flash_programmer |
buck_F28003x_lfuBANK1FLASH.txt | CPU | BANK1_FLASH | Same as above |
buck_F28003x_lfuBANK0FLASH_cla.txt | CLA | BANK0_FLASH | Output file post
conversion to .txt of the buck_F28003x_lfu project, which is
the Application (the project will be located at
<C2000Ware_DigitalPower_SDK_path>\solutions\tidm_02011\f28003x\ccs)
Project is built with compiler pre-defined symbol BUCK_CONTROL_RUNNING_ON_CLA. Resulting .txt is renamed to include an “_cla” Copy the generated .txt file to <C2000Ware_DigitalPower_SDK_path>\c2000ware\utilities\flash_programmers\serial_flash_programmer |
buck_F28003x_lfuBANK1FLASH_cla.txt | CLA | BANK1_FLASH | Same as above |
serial_flash_programmer_appln.exe | .exe | - | This is the host side
serial flash programmer executable for loading the Application to
Flash on the target device It is present at<C2000Ware_DigitalPower_SDK_path>\c2000ware\utilities\flash_programmers\serial_flash_programmer |
The buck_F28003x_lfu project also contains a BANK0_FLASH_BANK10COPY build configuration, which is an alternate configuration where the application is always built to be Loaded to Bank1 and Run from Bank0. In this configuration, BANK1_TO_0COPY is a pre-defined symbol which allows the modified functionality to be implemented.
Similarly, the flash_kernel_ex3_sci_flash_kernel project also contains a BANK0_LDFU_BANK1TO0COPY build configuration, which is an alternate configuration that supports the use-case above i.e. where the application is always built to be Loaded to Bank1 and Run from Bank0. In this configuration, BANK1_TO_0COPY is a pre-defined symbol which allows the modified functionality to be implemented.
This allows the developer to build an image for LFU without having to know which Bank the image is going to reside in. The downside to this is the Bank1 to Bank0 copy, which needs to occur before activating the new image. This copy is done by the Flash kernel. This takes up time, during which the application cannot be running.