5 Flashing Demo

In case of only OSPI memory boot mode, use the complete file to flash the binary in windows PC. There are some slight differences of flashing tools between HS-FS device and HS-SE device, as shown in Table 5-1. The difference is FS device flashing based on no-boot mode and corresponding file will initialize the DDR, but SE device will not. You can find the complete sample flashing tools as attachment.

Table 5-1 Flashing Tools for OSPI Boot Mode Only

HS-FS Device	HS-SE Device
Binary/ Configuration.txt Launch_fs.js flash_blackhawk560_NOboot.ccxml uart_j721e_evm_flash_programmer_release.xer5f	Binary/ Configuration.txt Launch_se.js flash_blackhawk560_OSPIboot.ccxml uart_j721e_evm_flash_programmer_release.xer5f

The flashing machine should have already installed the CCS environment, the launch.js file should point to the DDR configuration folder, and the CCS ccxml file should point to CCS target configuration file with correct chip and emulation model. You can find more details here.

In windows PC, using win+R and input cmd to open the command windows, then enter the following command to start the flashing:

${ccs_install_path}\ccs_base\scripting\bin\dss.bat Launch_fs/se.js

The log as below when flash is complete:

D:\user\Desktop \Flash_Burn>C:\ti\ccs1000\ccs\\ccs_base\scripting\bin\dss.bat  Launch_se.js
Loaded FPGA Image: C:\ti\ccs1000\ccs\ccs_base\common\uscif\dtc_top.jbc
Connecting to MCU Cortex_R5_0!
Starting Flashing !
Flashing image/se/app of size 738712 at offset 921600
Running the OSPI load program from R5!
Flashing image/se/app3_0 of size 1064196 at offset 1970176
Running the OSPI load program from R5!
Flashing image/se/lateapp1 of size 7772252 at offset 16113664
Running the OSPI load program from R5!
Flashing image/se/lateapp2 of size 7336400 at offset 24502272
Running the OSPI load program from R5!
Burning is complete, happy to go !!!
Press Key to Continue … …