-
Notifications
You must be signed in to change notification settings - Fork 40
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
Multicore simulation and execution #127
Comments
Hi, I think the buildroot login: message is holded by SBT because it doens't has a line return.
It is through litex. See for instance : Also, this may interest you : |
Hi, The problem with the welcome to buildroot wasn't fixed with the root but I will try to use the intellij to see what results may came up. As for the litex, I was wandering if there was a way to produce a verilog (or some other king of HDL file) so that I can use it with a different program. |
For litex itself, i don't know if you can just ask it a verilog out, as it is used more like a all in one solution instead. |
Can I do it though your repo in some way? Compile a file for example with Intellij and have a verilog file at the end |
Yes you can. |
Hi, what simulation arguments did you used ? |
Hello, |
decompiled which file ? |
The linux.dtb. I produced the .dts file, added the configuration and then compiled it back to .dtb |
Good evening,
I am trying to run the simulation file located in src/main/scala/naxriscv/platform/tilelinkdemo/SocSim.scala using the commands exactly as they are inside the file. The simulation starts normally but after a long time it get stack after displaying [info] Welcome to Buildroot.
If I kill the execution, then a message pops up that says:
[warn] Canceling execution...
[info] buildroot login:
Do you know to fix that? I have tried also to use the same commands with --nax-count 1 and without a nax-count flag and I get exactly the same results.
Also, I can't find a way to create a dual core SoC to use on an FPGA. Is there a way to do it or it isn't supported yet?
Thank you very much!
The text was updated successfully, but these errors were encountered: