On 2/23/21 7:06 PM, Daniel Schwierzeck wrote:
Am Dienstag, den 23.02.2021, 15:19 +0100 schrieb Reinoud Zandijk:
Hi Daniel,
On Tue, Feb 23, 2021 at 01:03:05AM +0100, Daniel Schwierzeck wrote:
Am Montag, den 22.02.2021, 20:56 +0100 schrieb Reinoud Zandijk:
If I remove it, the machine just spins in Qemu, no output,
nothing.
If I add
it, it works fine again. I found out by bisecting. I have no idea
why
the
tests aren't picking this up. Could it be a qemu/gcc/binutils
combination
issue? A symbol not set as expected?
qemu 5.1.0
gcc 8.3.0
binutils 2.32
which board config did you try exactly? malta or maltael?
Both malta and maltael have the same behaviour. And yeah, for maltael
i needed
the u-boot-swap.bin indeed! That was not that obvious at first but
trial and
error showed it.
How are the tests performed? Are the actual u-boot images passed as
compiled
with `-bios' to qemu and that alone? Or are the tests also sneaking
in the FDT
to qemu? By f.e. appending them?
we use the images as built by the default configs. We don't use "-bios"
but "-drive if=pflash,file=${U_BOOT_BUILD_DIR}/flash.img,format=raw" to
emulate NOR flash and to be closer to hardware.
flash.img is created with that script:
https://gitlab.denx.de/u-boot/u-boot-test-hooks/-/blob/master/bin/flash.qemu_gen_padded_image
Hello Daniel,
thanks for pointing out how the Gitlab CI test is run.
This looks a bit different to doc/board/emulation/qemu-mips.rst where
'-pflash flash' is used as argument.
Do you want to update the man-page to use -drive instead of -pflash?
Best regards
Heinrich
