Page 1 of 1

qemu

Posted: 2024-03-07 0:39
by freetoair
Hi !
Is RV1103/06 supported in qemu ?

Re: qemu

Posted: 2024-03-07 2:09
by Crocodile
freetoair wrote: 2024-03-07 0:39 Hi !
Is RV1103/06 supported in qemu ?

Hello, unfortunately, QEMU does not support rv1103/1106 at the moment. Adding support for luckfox-pico on QEMU would require significant effort, and there are currently no plans to support QEMU.

Re: qemu

Posted: 2024-04-28 23:43
by jnunez
Hey guys please do this, it is frustrating having to deal with issues when trying to cross-compile and not being able to get support from the project; in my case I am trying to cross compile swi-prolog, but I am getting a seg-fault that I can gdb into which reveals a problem with the `qsort_r` function in uclibc-ng but cannot see exactly why. I would like to get some support and having the possibility to provide a qemu image with the whole setup would be of huge help.

Re: qemu

Posted: 2024-04-29 11:26
by Crocodile
jnunez wrote: 2024-04-28 23:43 Hey guys please do this, it is frustrating having to deal with issues when trying to cross-compile and not being able to get support from the project; in my case I am trying to cross compile swi-prolog, but I am getting a seg-fault that I can gdb into which reveals a problem with the `qsort_r` function in uclibc-ng but cannot see exactly why. I would like to get some support and having the possibility to provide a qemu image with the whole setup would be of huge help.
It's unfortunate that the RV1106 used by luckfox-pico isn't a fully open platform. The main reason for using uclibc as the toolchain for cross-compilation is due to the need to link with Rockchip's multimedia and NPU libraries to access the special IP cores in the chip, for which there is no relevant documentation available.

To create a qemu image for luckfox-pico, incorporating unique features such as the NPU, multimedia libraries, and fast MCU booting, we would need complete documentation to understand how to proceed. Additionally, the tool rkImgMaker, used for creating kernel images, is only available as a binary file. This tool is crucial for the subsequent kernel loading process.

Given our lack of experience in creating qemu images and the inadequacy of available documentation, we're unable to proceed with creating a qemu image. Therefore, if there is a need for kernel debugging, it's advisable to explore alternative solutions.

Re: qemu

Posted: 2024-05-21 8:35
by jnunez
Crocodile wrote: 2024-04-29 11:26
jnunez wrote: 2024-04-28 23:43 Hey guys please do this, it is frustrating having to deal with issues when trying to cross-compile and not being able to get support from the project; in my case I am trying to cross compile swi-prolog, but I am getting a seg-fault that I can gdb into which reveals a problem with the `qsort_r` function in uclibc-ng but cannot see exactly why. I would like to get some support and having the possibility to provide a qemu image with the whole setup would be of huge help.
It's unfortunate that the RV1106 used by luckfox-pico isn't a fully open platform. The main reason for using uclibc as the toolchain for cross-compilation is due to the need to link with Rockchip's multimedia and NPU libraries to access the special IP cores in the chip, for which there is no relevant documentation available.

To create a qemu image for luckfox-pico, incorporating unique features such as the NPU, multimedia libraries, and fast MCU booting, we would need complete documentation to understand how to proceed. Additionally, the tool rkImgMaker, used for creating kernel images, is only available as a binary file. This tool is crucial for the subsequent kernel loading process.

Given our lack of experience in creating qemu images and the inadequacy of available documentation, we're unable to proceed with creating a qemu image. Therefore, if there is a need for kernel debugging, it's advisable to explore alternative solutions.
Thank you for taking the time to reply, however I still think having a subset of the board without the NPU would still help, please consider that option as well; just the ARM processor would be a boon!