Standardized Jam STAPL Files
Setting the security bit during programming is controlled by the DO_SECURE procedure. If this flag is set, then all devices that are being programmed will have their security bits set. If the flag is not set, no devices will have their security bits set. See the following examples of setting the security bit in the command-line players.
Don't set security
==================
Jam STAPL Player: jam -aPROGRAM file_name.jam
Jam STAPL Bytecode Player: jbi -aPROGRAM file_name.jbc
Set security
============
Jam STAPL Player: jam -aPROGRAM -dDO_SECURE=1 file_name.jam
Jam STAPL Bytecode Player: jbi -aPROGRAM -dDO_SECURE=1 file_name.jbc
Pre-Standardized Jam1.1 Files
Setting the security bit during programming is controlled by two initialization variables: DO_SECURE and DO_SECURE_ALL. If neither variable is set, the security bits will not be set. If the DO_SECURE_ALL flag is set, then all devices that are being programmed will have their security bits set; additionally, if the DO_SECURE flag is set, the devices will have their security bit set as specified in design entry. See the following examples of setting the security bit in the command-line players.
Don't set security
==================
Jam STAPL Player: jam -dDO_PROGRAM=1 file_name.jam
Jam STAPL Bytecode Player: jbi -dDO_PROGRAM=1 file_name.jbc
Set security
============
Jam STAPL Player: jam -dDO_PROGRAM=1 -dDO_SECURE_ALL=1 file_name.jam
Jam STAPL Bytecode Player: jbi -dDO_PROGRAM=1 -dDO_SECURE_ALL=1 file_name.jbc
Set security as set in the original design files
================================================
Jam STAPL Player: jam -dDO_PROGRAM=1 -dDO_SECURE=1 file_name.jam
Jam STAPL Bytecode Player: jbi -dDO_PROGRAM=1 -dDO_SECURE=1 file_name.jbc