6217 - Radiant: Why is Radiant not working on VMWare?

• Related Articles

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

  Description: This is a known issue in Radiant v2022.1 and v2023.1. The ECO editor for memory initialization is not reflected in updated bitstream. Solution: To workaround this issue, you may revert back to Radiant v3.2 or request a software patch for ...

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

• 6832 - Radiant / Diamond: Why does max fanout limit in the Synthesis Design Strategy setting not working on reset/clock net?

  The maximum fanout in Synthesis Design Strategy is only followed by the logic in the design wherein clock and reset nets are excluded or does not strictly following it. To add fanout limit specific on reset and clock nets, use the attribute below: ...

• 6268 - Radiant: Does Radiant has linter?

  Description: We do not have a linter feature on Radiant. The RTL code is checked by the software when either updated or has been inserted in the project and then gives the appropriate message result (info/warning/error) on the output window. ...

• 7242 - Radiant versions 2023.1 and newer: Why is there a MAP DRC update on 2023.1 and newer versions of Radiant that blocks the compilation of designs with all configuration ports disabled?

  In the Nexus series of devices, if you intend to utilize JTAG ports as GPIO by de-asserting JTAG_EN, then there must be another dual-use pin (e.g. I2C) that remains in “persisted” mode (e.g. I2C must stay as I2C and not become a GPIO). Keeping I2C ...