Creating the External Memory Programming File - 3.1 English

UltraScale Architecture Soft Error Mitigation Controller LogiCORE IP Product Guide (PG187)

Document ID
Release Date
3.1 English

If the solution requires external data storage to support error classification, an additional Tcl script is called to post-process special write_bitstream output files into a SPI flash programming file.

The makedata.tcl script is generated in the example project. After bitstream generation is complete, locate the script on disk, and source this script in the Tcl Console.

source <path to component_name>_ex/imports/makedata.tcl
source sem_ultra_0_ex/imports/makedata.tcl

Next, locate the implementation results directory. Click the Design Runs tab, select the implementation run, and note the Run directory indicated in the Implementation Run Properties window. From the Tcl Console, navigate to the implementation results directory to run the makedata script over the write_bitstream output files.

cd <path to component_name>_ex/<component_name>_ex.runs/impl_1
cd sem_ultra_0_ex/sem_ultra_0_ex.runs/impl_1

Next, execute the commands outlined in these steps. For monolithic devices, only one *.ebd file is generated by write_bitstream and this filename is passed as an argument. For UltraScale SSI devices, a separate *.ebd file is generated for each SLR in the device.

Note: In 2017.1, classification feature is not supported in UltraScale+ SSI devices.

To pack the essential bits data from all *.ebd files into one SPI flash data file, a space-separated list of *.ebd filenames are passed as arguments.

makedata -ebd <ebd filename(s)> datafile

Example for monolithic devices:

makedata -ebd sem_ultra_0_example_design.ebd datafile

Example for SSI devices with three SLR:

makedata -ebd sem_ultra_0_example_design_0.ebd sem_ultra_0_example_design_1.ebd sem_ultra_0_example_design_2.ebd datafile

The command creates the VMF, BIN, and MCS files.