7100 - Propel Builder: Why is the Switch Verification and SOC Design icon greyed out and the Radiant/Diamond and Propel icons are missing?

• Related Articles

• 7230 - Lattice Propel: Why is my Propel Builder soft IP not available/missing in IP Catalog?

  Description: Observing some soft IP version is not available to select in Propel Builder IP Catalog. Solution: This is an expected behavior. Lattice Propel Builder IP Server will only list out the specific compatible soft IP version. If you open an ...

• 6223 - Propel: Why does Radiant not start when invoked via Propel Builder?

  Kindly check in the Propel Builder tool settings if the Radiant software directory is already set. In Propel Builder, go to Designs>Options>Directories and set the Radiant location to <radiant install path>/lscc/radiant/<version>

• 7133 - Propel Builder: Error (suppressible): xxx/lib/latticesemi.com/ip/cpu0/2.2.0/rtl/cpu0.sv(515): (vlog-2388) '<protected>' already declared in this scope (<protected>) at <protected>(<protected>).

  Description: User may encounter cpu.v compilation error in Model Sim if directly run the Simulation Wizard from Radiant software for any RISC-V project. Solution: The correct method is to leverage the verification tool provided in Propel Builder to ...

• 7053 - Propel: Why I unable to run debugger with Propel SDK on my RISC-V Project?

  Description: 1. RISC-V reset vector is fixed at address 0x00000000, thus instruction memory must start at address 0x0. 2. RISC-V instruction port is a read only port. To run debugger with Propel SDK, the SoC design must support writes to the ...

• 7712 - Propel Builder v2024.2: Why adding AXI4 component to a design increases the minimum address range of other AHBL/APB peripheral IP to 4K

  Description: In Propel Builder v2024.2, an enhancement was made to AXI components, setting a minimum address depth of 4KB. This change ensures that AXI4 transactions operate within a 4KB address boundary, promoting efficient data transfer and ...