Adding a new processor model and more detailed build instructions #113
Replies: 1 comment 4 replies
-
Hi @TheCopperMind ! Indeed the currently provided build instructions are very sparse, and i'll take a look at how i can improve that. In the meantime, i'd say your best bet is to
Using Qt's own IDE QtCreator can also simplify the process, since it already has registration of the various Qt components built-in. In any case, feel free to shoot me an e-mail or raise an issue if things get stuck. Next, on adding processor models. That is also a TODO in the wiki, which i should probably get done some day! At the moment, the lackluster answer is that the best way to add processor models is to look at the existing ones and copy the structure of how they've been included into the program. For changing them, your best bet is to read through one of the implementations to get a feel for the VSRTL API. Hopefully it should be familiar if you've done a bit of work with HDLs before. Lastly, I've also been toying with the idea of using Verilator generated processors as a backend for Ripes. With the current mechanism (using VSRTL), we get the added benefit of a visualization. However, VSRTL is not a fully-fledged HDL and users may find it difficult to express some constucts in it. For an example, see this branch, where the PicoRV32 processor is integrated into the Ripes environment. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I'm a master student and I'm starting my thesis on RISC-V multithreading extensions, and I think Ripes would be awesome to work with as part of that!
I think it would be great to have a guide on how to add new processor models or how to change the existing ones. I also believe a more detailed guide on the build process would be convenient, as I've tried to build the project for a while to no avail.
Beta Was this translation helpful? Give feedback.
All reactions