Booting qnx os with qemu

Question

Booting qnx os with qemu

asifsid-32 opened this issue 3 years ago · comments

Hello,

I am trying to boot QNX OS on top of qemu using QNX IFS (aarch64).

Following command is being used -

qemu-system-aarch64 -machine xlnx-zcu102 -m 1G -kernel IFS.bin -drive file=filesystem.qcow2,if=none,id=drv0 -nographic -serial mon:stdio

Using this it gives a shutdown error and the kernel does not load.

Can someone help how we can boot the QNX kernel on top of qemu with xilinx machine ?

Thanks

Edgar E. Iglesias · Answer 1 · Thu Apr 29 2021 00:21:58 GMT+0800 (China Standard Time)

Hi,

A couple of questions:

What do you have in the IFS.bin binary? Is there only the QNX OS expected to run at EL1? Or is there SW that expects to run at EL3? The command-line will depend on that.

Are you able to run this on real HW? Are you in that case running it together with ARM Trusted Firmware and the PMU FW from Xilinx? or are you using something else?

Best regards,
Edgar

asifsid-32 · Answer 2 · Thu Apr 29 2021 18:53:41 GMT+0800 (China Standard Time)

Hii @edgarigl

Thanks for the comment.
We were able to boot the QNX OS on QEMU with xilinx machine using the following command -

./qemu-system-aarch64 -M xlnx-zcu102 -m 8G -serial mon:stdio -display none -device loader,file=QNX-IFS.bin,cpu-num=0 -global xlnx,zynqmp-boot.cpu-num=0 -global xlnx,zynqmp-boot.use-pmufw=true

Regards
Asif

Edgar E. Iglesias · Answer 3 · Fri Apr 30 2021 02:58:04 GMT+0800 (China Standard Time)

Hi!

I suggest that you don't use the xlnx-zcu102 machine but our more complete device-tree based machine, those are a lot more complete.
You're going to need to build the device-trees from here:
https://github.com/Xilinx/qemu-devicetrees

There's more information here:
https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/821395464/QEMU+User+Documentation

To run something like a binary from EL3, here's an example command-line:
qemu-system-aarch64 -M arm-generic-fdt -serial stdio -display none -m 2G -hw-dtb dts/LATEST/SINGLE_ARCH/zcu102-arm.dtb -device loader,file=QNX-IFS.bin,cpu-num=0 -device loader,addr=0xfd1a0104,data=0x8000000e,data-len=4

If you need to run with ATF and perhaps the PMU FW, I can provide other examples but it would be good to get more details about your QNX-IFS.bin, i.e what address does it expect to start from? address 0? What EL level?

Best regards,
Edgar

asifsid-32 · Answer 4 · Fri Apr 30 2021 18:35:33 GMT+0800 (China Standard Time)

Hii @edgarigl

Thanks for the inputs.
We are trying to configure/generate IPI interrupts for which we have created a separate issue (Link-). Here we are trying to run everything in the same core.

Can you please suggest something on how we can configure the interrupt ?

Regards
Asif

Edgar E. Iglesias · Answer 5 · Sun May 02 2021 14:59:21 GMT+0800 (China Standard Time)

The interrupt you mentioned is not yet connected in the xlnx-zcu102 model, we'll have to fix that in upstream. In the meantime you'll need to use the device-tree machines.

asifsid-32 · Answer 6 · Sun May 02 2021 21:06:41 GMT+0800 (China Standard Time)

The interrupt you mentioned is not yet connected in the xlnx-zcu102 model, we'll have to fix that in upstream. In the meantime you'll need to use the device-tree machines.

Hii @edgarigl

Thanks for the reply !

Can you please help us with the steps and qemu command we need to follow for using device-tree machines for configuring interrupts ?
IPI interrupts can be configured/generated using device-tree machines ? If yes, how can we do IPI interrupts or any other interrupts ?
When can we expect the IPI in upstream ?
On actual hardware also IPI is not working. Any possible reasons for this ?

Regards
Asif

asifsid-32 · Answer 7 · Mon May 03 2021 22:24:34 GMT+0800 (China Standard Time)

Hi!

I suggest that you don't use the xlnx-zcu102 machine but our more complete device-tree based machine, those are a lot more complete.
You're going to need to build the device-trees from here:
https://github.com/Xilinx/qemu-devicetrees

There's more information here:
https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/821395464/QEMU+User+Documentation

To run something like a binary from EL3, here's an example command-line:
qemu-system-aarch64 -M arm-generic-fdt -serial stdio -display none -m 2G -hw-dtb dts/LATEST/SINGLE_ARCH/zcu102-arm.dtb -device loader,file=QNX-IFS.bin,cpu-num=0 -device loader,addr=0xfd1a0104,data=0x8000000e,data-len=4

If you need to run with ATF and perhaps the PMU FW, I can provide other examples but it would be good to get more details about your QNX-IFS.bin, i.e what address does it expect to start from? address 0? What EL level?

Best regards,
Edgar

Hello Edgar,

Please find attached the minimal-build file used for generating the QNX-IFS. Address related info can be checked in build file.
EL level i am not sure as i am new to this.

I tried the command suggested by you -

qemu-system-aarch64 -M arm-generic-fdt -serial stdio -display none -m 2G -hw-dtb dts/LATEST/SINGLE_ARCH/zcu102-arm.dtb -device loader,file=QNX-IFS.bin,cpu-num=0 -device loader,addr=0xfd1a0104,data=0x8000000e,data-len=4

but it is not booting the kernel and just hangs after executing. Any other suggestions for interrupts configuration ?
minimal-build.txt

Thanks
Asif

Edgar E. Iglesias · Answer 8 · Tue May 04 2021 14:32:29 GMT+0800 (China Standard Time)

Hi,

Can you try adding -machine linux=yes, e.g:

qemu-system-aarch64 -M arm-generic-fdt -serial stdio -display none -m 2G -hw-dtb dts/LATEST/SINGLE_ARCH/zcu102-arm.dtb -device loader,file=QNX-IFS.bin,cpu-num=0 -device loader,addr=0xfd1a0104,data=0x8000000e,data-len=4 -machine linux=yes

Best regards,
Edgar

asifsid-32 · Answer 9 · Sat May 08 2021 19:05:15 GMT+0800 (China Standard Time)

Hii @edgarigl

I tried the above command with -machine linux=yes, but it is not booting the kernel and just hangs after executing. Any other suggestions for interrupts configuration ?

Regards
Asif

Anton Kochkov · Answer 10 · Tue Sep 13 2022 09:31:40 GMT+0800 (China Standard Time)

@asifsid-32 have you had any luck with this?

charantejaabbavathini · Answer 11 · Wed Feb 07 2024 09:52:27 GMT+0800 (China Standard Time)

Hi @edgarigl @asifsid-32,

I have tried to boot the qnx os aarch64 using
qemu-system-aarch64 -M xlnx-zcu102 -m 8G -serial mon:stdio -display none -device loader,file=QNX-IFS.bin,cpu-num=0 -global xlnx,zynqmp-boot.cpu-num=0 -global xlnx,zynqmp-boot.use-pmufw=true

Here is the output of the above command:
~/qnx710/output$ qemu-system-aarch64 -M xlnx-zcu102 -m 8G -serial mon:stdio -display none -device loader,file=QNX-IFS.bin,cpu-num=0 -global xlnx,zynqmp-boot.cpu-num=0 -global xlnx,zynqmp-boot.use-pmufw=true
pulseaudio: set_sink_input_volume() failed
pulseaudio: Reason: Invalid argument
pulseaudio: set_sink_input_mute() failed
pulseaudio: Reason: Invalid argument
qemu-system-aarch64: warning: global xlnx,zynqmp-boot.cpu-num has invalid class name
qemu-system-aarch64: warning: global xlnx,zynqmp-boot.use-pmufw has invalid class name
QEMU: Terminated

I think, the qemu is up but its unable to boot the OS. The QNX-IFS.bin file is only qnx image file. Am I missing something to pass like the binary file boot.bin or should i include the boot.bin in the QNX-IFS.bin? Any leads would be helpful.

Hi @asifsid-32, how did you generate the QNX_IFS.bin, did you get it from zcu102 bsp or does it also has the boot.bin and IFS together in the same file.
I have issues booting the OS. Any help would be appreciated!

Thank you!