-
Notifications
You must be signed in to change notification settings - Fork 305
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
qemu环境下运行问题 #208
Comments
Please provide more information, like the QEMU version, Ubuntu version, and ArceOS commit ID. |
Ubuntu22.04 |
It seems to not work on older versions of QEMU, you can build a newer version (>= 8.0.0) manually. See https://www.qemu.org/download/ for build instructions. |
This is because #195 has deprecated legacy SBI console output. You can fix it by upgrading OpenSBI to at least v1.3 without rebuilding QEMU. diff --git a/scripts/make/qemu.mk b/scripts/make/qemu.mk
index b7b8db6c..a296a967 100644
--- a/scripts/make/qemu.mk
+++ b/scripts/make/qemu.mk
@@ -29,7 +29,7 @@ qemu_args-x86_64 := \
qemu_args-riscv64 := \
-machine $(machine) \
- -bios default \
+ -bios opensbi-1.3-rv-bin/share/opensbi/lp64/generic/firmware/fw_dynamic.elf \
-kernel $(OUT_BIN)
qemu_args-aarch64 := \ |
在运行make ARCH=riscv64 A=examples/helloworld run后,只能进入openSBI并打印其log。
![Screenshot 2024-12-05 012227](https://private-user-images.githubusercontent.com/85930270/392499468-bda358d0-2489-43b1-a799-132f607c7bef.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNjEzNDMsIm5iZiI6MTczOTI2MTA0MywicGF0aCI6Ii84NTkzMDI3MC8zOTI0OTk0NjgtYmRhMzU4ZDAtMjQ4OS00M2IxLWE3OTktMTMyZjYwN2M3YmVmLmpwZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDA4MDQwM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWMzZWRmODhlYTFmMmE1MGNjOWY4MTc3N2JjNzk4MGIzOWRjYzJlNWQ0ZTAzZjY4ZDY0OWVjODgzOTdiZDlhZDkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.TwfjvthzirTorcMa9z4H276Jfp9nbXSGm71gKLEgu_c)
The text was updated successfully, but these errors were encountered: