7490 - Radiant: How to modify the bitstream USERCODE via scripting flow?

Users can perform USERCODE modification of the generated bitstream via our deployment tool (ddtcmd.exe) scripting flow.

 

Here is an example TCL script:

==========================

#change directory to where the deployment tool can be invoked:

cd C:/lscc/radiant/2023.2/programmer/bin/nt64

#deployment tool commands

exec ddtcmd -oft -bit -dev LIFCL-40 -if "C:/Users/jmanguba/Desktop/Temp/Radiant/8bit_counter/impl1/8_bit_counter_impl1.bit" -overwriteues on "AAAACCCC" -of "C:/Users/jmanguba/Desktop/Temp/Radiant/8bit_counter/impl1/8_bit_counter_impl1_2nd.bit"

==========================

Example output:

Details on the deployment tool commands used:

exec ddtcmd : invoke deployment tool

-oft <file type>: indicates the file type.

-bit : indicates the file type output to be bitstream.

-dev <device name> : fpga device of the bitstream.

-if <input file path> : file path of the input bitstream

-overwriteues on <value> : Overwrites (or replaces) the USERCODE value contained in the input file with the hex value passed in.

-of <output file path> : file path of the output bitstream.

For more information, check the "Running the Deployment Tool from the Command Line" section of the Lattice Radiant Help.

• Related Articles

• 6205 - Radiant: How to use the TCL command "prj_add_source" to include a list of files on Radiant project based on file type via scripting flow?

  Here is an example TCL script on how to automate adding of files, based on file type, to a Radiant project via scripting flow: #set the directory to a variable where you want to get the files. set dir /home/jmangubat/ #use glob command to filter the ...

• 6203 - Radiant: Why does the eco_config_memory command not working on scripting flow?

  The eco_config_memory command only works when used via Radiant GUI flow since the ECO editor is readily available in the software. When using non-GUI project flow (TCL), the ECO editor must be called using "ecoc" command and the ECO commands should ...

• 7322 - Radiant & Diamond Non-GUI Flow: Why does the GUI flow of Radiant generate some messages that do not appear in the non-GUI flow?

  Description: This article describes the difference between the messages generated in GUI flow vs. non-GUI flow of Radiant and Diamond software. Solution: In GUI flow, when opening a project, adding a new file, or editing an input file and saving the ...

• 7143 - Radiant: How to save design phase report files via TCL scripting each time the design is recompiled?

  There is no specific command to retain the log files every time you recompile each design phase. As a workaround, the user can use the "file copy" tcl command after each design phase to copy the logs to a different folder from each design phase and ...

• 7361 - Radiant: Why does Radiant generate bitstream that contains unusual or garbled characters?

  Description: When generating a bitstream on Radiant, there have been reports where the generated bitstream includes unusual or garbled characters that are not appropriate for device programming. Solution: This issue might occur if the project path is ...