[HELP] New to this : trying to run it on qemu under wsl
- Dominant language
- C
- Stars
- 4k
- Forks
- 1.7k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 237
Description
### Description
I am trying to load a build of nuttx using qemu-system-riscv64
I have built nuttx for star64 target
then I do :
/usr/bin/qemu-system-riscv64 -nographic --machine sifive_u -m 2 -kernel /m
nt/c/devtools/nuttxspace/nuttx/nuttx
qemu-system-riscv64: Some ROM regions are overlapping
These ROM regions might have been loaded by direct user request or by default.
They could be BIOS/firmware images, a guest kernel, initrd or some other file loaded into guest memory.
Check whether you intended to load all this guest code, and whether it has been built to load to the correct addresses.
The following two regions overlap (in the memory address space):
/usr/share/qemu/opensbi-riscv64-generic-fw_dynamic.bin (addresses 0x0000000080000000 - 0x0000000080042c40)
fdt (addresses 0x0000000080000000 - 0x000000008000130b)
image is clashing with SBI in Qemu
tried loading it while relocating the nuttx image with but could not load
/usr/bin/qemu-system-riscv64 -nographic --machine sifive_u -m 2 -device guest-loader,kernel=/mnt/c/devtools/nuttxspace/nuttx/nuttx,addr=0x0000000080042c41
qemu-system-riscv64: -device guest-loader,kernel=/mnt/c/devtools/nuttxspace/nuttx/nuttx,addr=0x0000000080042c41: Cannot load specified image /mnt/c/devtools/nuttxspace/nuttx/nuttx
I could run qemu with the raw image, and it just stayed there running on the terminal with :
/usr/bin/qemu-system-riscv64 -nographic --machine sifive_u -m 2 -bios /mnt/c/devtools/nuttxspace/nuttx/nuttx
had to kill the qemu process
with this last command don't know if it was really executing anything. I suspect I have to run this with the Qemu SBI in order to acess the serial port on the nuttx side and get a prompt
I am new to all this. I need some pointers
and also qemu
### Verification
- [x] I have verified before submitting the report.
Contributor guide
Research direction
Start by reproducing the qemu-system-riscv64 commands in the issue with the star64 NuttX image under WSL, then inspect the NuttX star64 target configuration and QEMU's sifive_u machine setup. Done means identifying a supported boot command and confirming that NuttX reaches a visible serial prompt rather than only leaving QEMU running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100