7/20/2020 9:27 AM | |
Joined: 4/28/2015 Last visit: 6/28/2024 Posts: 578 Rating: (43) |
It used to work, but I didn't try in a longer while, so it might be broken again. I would recommend following the yocto manual regarding qemu usage and then report if that works or fails, and how. Note, though, that a qemu target will not provide the same I/Os like the real device. It's enough to test applications that do disk and network I/O, but not those that need the specific ones of the IOT2000 (e.g. those on the Arduino connector). |
7/20/2020 10:26 AM | |
Posts: 5 Rating: (0) |
Hm, ok. If I understood it right, I need a qemux86 image that is created, to run qemu. It seems like this image is not created by default when I built the example image. How can I create such image with kas? |
7/20/2020 11:21 AM | |
Joined: 4/28/2015 Last visit: 6/28/2024 Posts: 578 Rating: (43) |
No, the idea of qemu enablement in yocto/oe is actually to use the generated target image inside an accordingly configured qemu instance. That description comes with the iot2000.conf (machine config) via the QB vars you found. Now, the trickier part is starting qemu via yocto's runqemu script. Try using it from the kas shell so that all needed variables are set. |
7/20/2020 12:17 PM | |
Posts: 5 Rating: (0) |
Ok, thanks. This helps a lot already. Now I get the error, that a
is missing. Do I understand it right, that this file should have been created in the building process with the information from iot2000.conf-file? I tried to copy the iot2000.conf file into the deploy-directory as an iot2000.qemuboot.conf, but I get the error, that the file does not contain section headers. |
Last edited by: Valle342 at: 07/20/2020 12:36:44 |
|
7/20/2020 4:26 PM | |
Posts: 5 Rating: (0) |
Ok, so I was able to create the qemuboot.conf-file. I enabled it by adding the line
in the meta-iot2000-example/conf/layer.conf Furthermore I needed to specify the QB_SYSTEM_NAME in the meta-iot2000-bsp/conf/machine/iot2000.conf file like that:
And then build again. Now I have a different issue. I enter the kas-shell as you suggest and then I get these two errors:
The first one I just don't understand and the second one I can not accomplish on my centOS7. It seems like tar1.26 is the newest version on that OS. If I do the same thing in the kas-docker, I come to the point mentioned here: https://github.com/siemens/meta-iot2000/issues/118, but then I get the error:
the directory that actually exists is:
But I don't know where to explain that to the builder. Maybe it is a little hopeless what I am doing here, but if there is someone who can help I would really appreciate that. Best regards |
7/23/2020 4:22 PM | |
Joined: 4/28/2015 Last visit: 6/28/2024 Posts: 578 Rating: (43) |
Thanks for digging into this! Here is the missing piece in the puzzle:
There is no "qemu-system-i586". Then runqemu works, provided you have qemu installed on your host. Otherwise run
in the kas shell first. Recommended options for runqemu: kvm slirp. The former makes it faster (virtualization rather than emultion), the latter avoids the sudo. I'm not yet sure where to put the IMAGE_CLASSES var, bsp or example layer. My current impression is, it should also go into the machine conf. Patch welcome to fix all that, maybe also to add some paragraph to the README! |
Last edited by: jan-k at: 07/23/2020 16:24:00 |
|
Follow us on