Propel and RISC-V: Why ECO-editor system memory initialization is not working in Radiant software v2022.1 and v2023.1?

• Related Articles

• Radiant: Why does the eco_config_memory command not working on scripting flow?

  The eco_config_memory command only works when used via Radiant GUI flow since the ECO editor is readily available in the software. When using non-GUI project flow (TCL), the ECO editor must be called using "ecoc" command and the ECO commands should ...

• Lattice Radiant: How do I Write values to ROM after implementation using ECO Editor

  In order to use the ECO editor tcl command, you must get the mem_id value from the ECO GUI. The tcl command was meant to record/repeat the operation of the GUI. There is no other way than to use the GUI first to check the id values. Here is the ...

• Diamond / Radiant / Propel: long startup time, stuck at "initializing device data"

  Description: When launching Lattice software, some license checks will be performed that may take some time depending on the user's system configuration. This FAQ summarizes the known solutions to shorten the startup time. Solution: 1) Checking the ...

• Radiant: Why is Radiant not working on VMWare?

  Radiant software requires OpenGL rendering (Qt5OpenGL.dll). The VMware machine doesn't have a 'true' graphics card and therefore has no OpenGL features. An OpenCL software library (mesa3d for windows) to emulate the OpenGL library can be found in ...

• Lattice Diamond/ECO Editor: Error - ChipCheck: comp CLOCK_i and $COMP_44 have incompatible VCC requirements.

  Description: In Lattice Diamond ECO Editor prompted DRC Error after assigning IO pin on the signal probe and unable to assign other IO_type. Error - ChipCheck: comp CLOCK_i and $COMP_33 have incompatible VCC requirements. Solution: To workaround this ...