Mateusz Hołenko

It looks like `mono` can't find the `libdl.so` file. Perhaps it's the `.2` postfix in the filename. I'll look into that deeper, but a quick workaround is to add a...

Is this still an issue? I've just tried running the script in a clean docker image of Ubuntu 21.10: ``` $ wget https://dl.antmicro.com/projects/renode/builds/renode-latest.linux-portable.tar.gz $ tar -xf renode-latest.linux-portable.tar.gz $ cd renode_1.12.0+20220407gitdd39ce44_portable...

Hi @wohlbier, in Renode warnings about unhandled accesses to peripherals do not necessary mean serious problems. This is caused by the fact that platforms are often implemented partially as not...

Hi @jjpark78, thanks for reporting the issue. Could you share the compiled binary and exact scripts/platforms you use? This would make it easier to investigate the problem.

Hi @swetland! The current model of `LiteX_Framebuffer.cs` supports the 8-bit CSR LiteX configuration in which multi-byte registers are split into 32-bit sub-registers with only lowest 8-bit of meaningful data. This...

And thanks for reporting the issue - we'll need to harden this layer to avoid crashing Renode and reporting a meaningful error instead.

This is a configuration of LiteX itself (it's called `--csr-data-width`: https://github.com/enjoy-digital/litex/blob/master/litex/soc/integration/soc_core.py#L328). Back in the days, when Renode models were created, the 8-bit CSR width configuration was the default one and...

@mithro All LiteX peripherals (i.e., those which names start with `LiteX_`) without the `_CSR32.cs` suffix are the one supporting the 8-bit CSR width configuration. The ones with the suffix support...

@swetland We'll verify the layout of registers for LiteX peripherals models and check if they need upgrading.

@swetland, in dc7e33b1b956e03fd4170dd586533f9b05b4b588 we added a model of the LiteX frame buffer supporting the 32-bit CSR width configuration. We are now working on updating the script for automatic generation of...