Basically I want to emulate a typical setup with boot + 2x rootfs + data on qemuarm, so I can properly test that my configs etc are populated correctly on /data running on standard runqemu script from yocto. I followed QEMU, the FAST! processor emulator but ran into problems, since I am running the…

[image] emilm: qemu-system-arm -m 512M You need to set this to 1G because that is what is recorded in the device tree after you removed the patch. Otherwise the OS will try to write into memory which doesn’t exist.

We use all of the qemu targets internally in our Q/A so they should all work, but might require getting the variables correct. We do provide custom machines for our testing, and you can take a look here, [image] mendersoftware/meta-mender Yocto Project meta layer for the Mender client. C…

Thanks for the quick response I try: MACHINE = “vexpress-qemu” INHERIT += “mender-full-ubi” … MENDER_STORAGE_TOTAL_SIZE_MB = “2048” MENDER_DATA_PART_SIZE_MB = “512” Then I get “MENDER_MTDIDS must be defined”. I add: MENDER_MTDIDS = “nor0=40000000.flash” Then I get: | DEBUG: Python functio…

[image] emilm: INHERIT += “mender-full-ubi” You do not need this for the vexpress-qemu

Is there a reason why there is no qemuarm but vexpress? The reason is that it has it’s own patch to reduce to 256M RAM and other things I don’t want, like the custom kernel config. Is it straight forward to use qemuarm as a machine or is it something I should worry about? Thanks!

Yes, it is because qemuarm doesn’t support U-Boot, only direct kernel boot. We need to be able to test U-Boot inside QEMU.

Understood, thanks. What do you suggest if I need more than 256M RAM? I was thinking of pulling out the bits so it works with UBOOT/GRUB without being vexpress specific, so it’s not constrained to that RAM etc. Or is it enough to override the recipe with a patch file with the same name? (meta-mend…

You will need the revert that patch yes, and also change this line . I was doing this very recently myself for some debugging work, so I know it works.

Thanks again. I did: SRC_URI_remove = " file://reduce-memory-to-256m.patch" In my layer which has higher priority. Then I saw that it was untouched, which is what I want, right?: memory@60000000 { device_type = “memory”; reg = <0x60000000 0x40000000>; }; However, it never manages to load , …

How are you launching QEMU? Can you give me the full output?

Vanilla qemuarm full multi partition emulation?

General Discussions

mirzak December 9, 2019, 1:01pm 4

You do not need this for the vexpress-qemu

Yocto qemu uboot error (mmc.o failed to build) when trying to build qemu which supports both mender and possibility of additional network interfaces

Topic		Replies	Views
U-boot compilation for qemu-flash failed General Discussions	13	1722	May 28, 2020
Yocto qemu uboot error (mmc.o failed to build) when trying to build qemu which supports both mender and possibility of additional network interfaces General Discussions yocto , qemu	3	917	October 21, 2022
Testing Mender with QEMU ARM64 Yocto Project	0	254	November 14, 2025
QEMU, the FAST! processor emulator (deprecated) Yocto Project yocto , sumo , rocko , thud , warrior , zeus , dunfell	0	8464	March 27, 2019
Building for demo with machine=qemux86-64 General Discussions qemu , qemux86-64	3	1698	May 24, 2022

Vanilla qemuarm full multi partition emulation?

Related topics