Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Verilator #334

Merged
merged 4 commits into from
Mar 8, 2022
Merged

Verilator #334

merged 4 commits into from
Mar 8, 2022

Conversation

PedroAntunes178
Copy link
Contributor

Verification runs with cache. Warning is still displayed, but the simulation no longer exits due to warnings.

There is a problem, when just running "make sim SIMULATOR=verilator RUN_EXTMEM=1" the simulation ends with a CPU trap condition. This does not occur in the old simulation.
Running "make sim SIMULATOR=verilator RUN_EXTMEM=1 INIT_MEM=0" works as expected.

Probably, the console, when using the cache, always has to be called with the "-f" flag in order to send the firmware binary file. Just like it happens with INIT_MEM=0. I have to check if this is true and then make the changes for it to happen.

@PedroAntunes178
Copy link
Contributor Author

RUN_EXTMEM=1 indeed sets INIT_MEM=0
solved the problem by including the simulation.mk before adding the "-f" flag to the command that calls the console. But I think a better solution might be to call the Makefile under the console directory.

@jjts jjts merged commit 614523a into IObundle:verilator Mar 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants