What is the usage for reginit.bin, bht_ini.bin, and bht_ini_p.bin files in Lattice project?
Q1: What are reginit.bin, bht_ini.bin, and bht_ini_p.bin used for?
A1: These files are used for simulation only to initialize certain
internal memories in the RISC‑V design.
Q2: Are these .bin files required for Radiant implementation or bitstream
generation?
A2: No. For hardware implementation, the corresponding RAMs are initialized to
zero by default, so these files are not required.
Q3: Why do I see an error when opening the Pre‑Synthesis Constraint
Editor?
A3: The Pre‑Synthesis Constraint Editor relies on a third‑party HDL parser that
performs strict file checks. If the HDL references these .bin files and they
are missing, the tool reports an error even though they are not needed for
implementation.
Q4: Why doesn’t this issue occur in some projects?
A4: When a project is generated directly from Propel Builder, these .bin files
are automatically copied into the project directory. The issue typically occurs
when the design is manually imported into an existing Radiant project.
Q5: How can I resolve the issue?
A5: Either generate the Radiant project directly from Propel Builder, or
manually copy the required .bin files into the same directory as the project’s
.rdf file.
Q6: Does this indicate a problem with the design?
A6: No. This is a tooling behavior related to file parsing and does not indicate
a functional issue with the design.
Related Articles
What to Expect from Lattice Support?
Lattice Technical Support Expectation Please be advised that highest priority for Lattice Technical Support will be given to 1. Software which is not working as expected or suspected bugs. We recommend that customers use the latest software tools and ...
Case Classification Mindmap
Case Category Case Sub-Category 2 Case Sub-Category 3 Case Sub-Category 4 Device & Architecture Clocking Network I/O (HPIO, WRIO) Logic Blocks (LUTs, Registers) Delay Cell Power Management Platform Manager Device / Part Selection Software Primitives ...