You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I've been trying to port RISCBoy to the Riegel FPGA computer without much luck so far.
I'm wondering if this repo is still supposed to be in a working state as I had to change a reference from hazard5_cpu to hazard5_cpu_1port to get it to build.
With the nextpnr --placer sa option it seems to be hanging here:
Or maybe I'm not being patient enough. I was able to get it to build with the heap placer and blinky works but I'm not seeing anything on the UART. Unfortunately I don't have any of the supported boards to test this on. Any tips would be appreciated.
Yes I think this repo has suffered from the fact that the "tests" for libfpga live here, and I possibly bumped libfpga at some point without re-running the RISCBoy system-level tests. Let's see if I can find anything obvious.
Thanks. It's exciting to see activity on this project again.
I'm still not seeing any bootloader output to the UART so I'm probably doing something wrong. I'll keep testing your updates and debugging the issue because it would be great to have this working on Riegel, Eis and Keks. In the meantime I'm keeping my fork up-to-date in case you'd like to have a look.
Hi. I've been trying to port RISCBoy to the Riegel FPGA computer without much luck so far.
I'm wondering if this repo is still supposed to be in a working state as I had to change a reference from hazard5_cpu to hazard5_cpu_1port to get it to build.
With the nextpnr
--placer sa
option it seems to be hanging here:Or maybe I'm not being patient enough. I was able to get it to build with the heap placer and blinky works but I'm not seeing anything on the UART. Unfortunately I don't have any of the supported boards to test this on. Any tips would be appreciated.
The fork with (non-working) Riegel support is here: https://github.com/machdyne/RISCBoy
The text was updated successfully, but these errors were encountered: