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
Error running 'hello' #24
Comments
@zhemao Can you address this, since you updated the images last. |
Oh crap, it looks like the DefaultFPGASmallConfig has virtual memory turned off now. So of course it's not going to work with the new pk, which requires virtual memory. I can fix this in my outstanding PR for the serial tether change. It might take a while for that to make it in. @jsren If you don't want to wait, you can go to rocket-chip/src/main/scala/coreplex/Configs.scala and edit the WithSmallCores config. If you change "UseVM" and "UseUser" to true and recompile the boot image, it should work. |
@zhemao @davidbiancolin Cheers! |
I've been following the tutorial for pushing rocket modifications to the FPGA on my Zedboard using the default ZynqConfig configuration, and when I go to run the example hello program I get a similar error to what @jsren found:
Somehow it seems to think that the amount of memory the program wants is greater than available, but this also happens when I increase memory size (and I don't see how hello could need more than 256MB of memory anyway). This doesn't happen with the image that comes with the repository, but it does happen if I rebuild boot.bin according to the tutorial, or fetch it with make fetch-images. Edit: Correction: This seems to not be happening anymore, even if I allocate more memory than the board has. I'm not sure what changed. |
This has been fixed by 9a0b82d. |
I've (hopefully!) followed the excellent readme and have downloaded the pre-built binaries for my Zybo board. When I ssh into it and attempt to run
./fesvr-zynq pk hello
however, I'm presented with:../machine/minit.c:26: assertion failed: EXTRACT_FIELD(ms, MSTATUS_VM) == VM_CHOICE
I've searched through GitHub - looks like the latest source for riscv-pk has an assert
https://github.com/riscv/riscv-pk/blob/8006d004a59618ce455c4365c09e138b06ca7b70/machine/minit.c#L26
whereas the source linked
The Zybo build was last tested with [this version ](https://github.com/ucb-bar/rocket-chip/commit/2f71a3da5a7d41b4aa2c7a617902f2aee8f2cbe1)of the toolchain.
instead just tests and continues?https://github.com/riscv/riscv-pk/blob/d37b50edf5faee2fe41a2586479ddab7c8a2ec9b/pk/minit.c#L24
Not sure if that's relevant, whether the assert is actually meant to pass or whether this actually relates to bbl?
Cheers
The text was updated successfully, but these errors were encountered: