-
Notifications
You must be signed in to change notification settings - Fork 257
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
Zephyr DTS and Renode LiteEth address mismatch #42
Comments
@kaolpr There is a tool for generating a renode configuration from a LiteX CSV file here -> https://github.com/litex-hub/litex-renode |
I know and it's very handy, already checked it out. The only think I wanted to point out with this issue is that Renode + Litex + Zephyr simulation looks like a great match and would be nice if it could work out-of-the-box. But I fully understand it's not a bug and one can not consider it a reason for any modifications (yet, this discussion will be here if anyone was looking for Zephyr + LiteEth + Renode). |
Thanks for the comment, @kaolpr! As you probably already know, LiteX is in fact a SoC builder which means it can generate many different configurations. Renode, due to its modularity, is great to simulate such situation as platform configuration is described in a simple text repl file. You are totally right though, that it might be surprising at first. There is, however, a solution to your problem that should satisfy everyone. |
I added the Zephyr-specific platform and script in 8383ccf. Hope it solves the problem! |
I recently started my adventure with Renode and one of my first attempts was to get working
samples/net/echo
from Zephyr onlitex_vexriscv
CPU with Renode LiteEth simulation. Unfortunately that was not as straightforward as one could expect.It turns out that there are different addresses hardcoded for LiteEth in Zephyr DTS and here:
renode/platforms/cpus/litex_common.repl
Line 26 in d95794c
It's hard to say it's a bug, but for me, as a newcomer, it was challenging (yet very educational) to figure out what's wrong. Maybe you could make it compatible out-of-the-box?
The text was updated successfully, but these errors were encountered: