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

• Related Articles

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

  When the default folder structure of the project is followed, user will be able to see all of the icons on Propel Builder Tool bar from the Switch Verification and SoC Design to the Propel SDK button.

• 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 ...

• 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 ...

• 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 ...

• 6904 - Propel 2022.1 and below: Why does Propel 2022.1 OpenOCD debug configuration show "+" when scanning the device?

  Description: When doing OpenOCD debug on Propel 2022.1 and lower versions, users might encounter an issue when scanning the device. The device dropdown upon scanning will show the "+" sign only instead of the targeted device. Solution: For Propel ...