ECP5: Why cant i disable bitstream encryption after i have enabled in Lattice Diamond?

ECP5: Why cant i disable bitstream encryption after i have enabled in Lattice Diamond?

Description:

A known issue in certain Lattice Diamond flows may prevent bitstream encryption settings from being fully cleared after they have been enabled for an ECP5 project. As a result, the generated bitstream may continue to be signed even though encryption appears to have been disabled in the project settings.

 

Solution:

As a workaround, manually remove the .bek and .sec files from the project directory and then regenerate the bitstream.

Removing these files clears the previously stored security and encryption information, allowing Diamond to generate a new bitstream without signing. After deleting the .bek and .sec files and regenerating the design, the resulting bitstream is generated without bitstream signing/encryption enabled.