Radiant setup fails to build with Radiant 2.2.1.239.2

[stnolting]

Radiant setup fails to build with Radiant 2.2.1.239.2

[turbinenreiter]

I just realized that this error message looks more like one of the tools within Radiant is broken, and given the fact that I run it on Fedora 34 instead of Ubuntu 16.04(!), which is Radiants supported Linux distro, I guess the issue is not to be found in this project. I got the osflow toolchain working in the meantime. I think this can be closed.

[umarcor]

@turbinenreiter I suggest checking whether package redhat-lsb is installed. Some years ago, that was required for running some vendor tools on Fedora.

[turbinenreiter]

redhat-lsb

I installed it, same issue.

[turbinenreiter]

malloc_consolidate(): unaligned fastbin chunk detected

Still same issue. I will try this on a Radiant-support OS later to confirm that this is an OS issue rather than an neorv32 issue :D

[turbinenreiter]

Can be closed, it worked on other OS, so the problem is on my (unsupported) OS.

[stnolting]

Hey there!

I do not have Radiant version 2.2 so I cannot reproduce your setup.
The default Radiant setup from setups/radiant works with Radiant 2.1 and I just tested it using the latest Radiant 3.0 version - successfully.

Seems like your design has some timing errors (5). Have you been prompted to execute the last step (export) even though there are timing errors? Maybe this crashed something., because the physical constraint warning for the flash_sdi_i does not really make sense here... 🤔

If you do not want to update to Radiant 3.0, you could try the more sophisticated Sinplify Pro synthesis engine instead of the default Lattice Synthesis Engine (LSE). From my experience Sinplify Pro provides faster (but larger) design results. Maybe this could eliminate the timing error issue.

To switch to Sinplify Pro:

• in the file list on the right right click on the implementation (imp_1 (Lattice LSE)
• in the drop-down menu select "properties"
• in the project properties click on "Lattice LSE" in the "Synthesis Tool: Lattice LSE" line
• select Sinplify Pro in the drop-down menu and close the dialog
• rerun everything by clicking on "Run All" (green arrow)

[stnolting]

I just realized that this error message looks more like one of the tools within Radiant is broken, and given the fact that I run it on Fedora 34 instead of Ubuntu 16.04(!), which is Radiants supported Linux distro, I guess the issue is not to be found in this project. I got the osflow toolchain working in the meantime. I think this can be closed.

Good point!

However, I suggest to try Sinplify before updating Radiant or any OS-related thing. 😉

[turbinenreiter]

I tried Sinplify and also got the same error message. I think the issue is incompatibility between my host OS and Radiant. Thanks for the help!

[stnolting]

I think there is an issue in rtl/processor_templates/neorv32_ProcessorTop_UP5KDemo.vhd, which is currently used by the Radiant example setup: the flash_sdi_i signal is defined in the entity but not actually used in the design. This should not be a problem for Radiant, but maybe this is the cause of your export problem. I will fix that.

[stnolting]

Should be fixed now (fingers crossed) 😉

[stnolting]

Is this still up-to-date or can this be closed? 🤔