On 2018-11-06 11:32, Peter Maydell wrote: > On 6 November 2018 at 09:40, Thomas Huth <th...@redhat.com> wrote: >> >> Hi, >> >> does anybody know whether the "canon-a1100" machine in QEMU is still >> usable, or rather how it can be used at all? >> >> According to >> http://lists.infradead.org/pipermail/barebox/2014-July/020327.html there >> should be support for "-serial stdio" and on >> https://lists.gnu.org/archive/html/qemu-devel/2013-10/msg02969.html >> there is a link to a firmware image ... but when I try to use it, there >> is simply no output on stdio... >> >> Is there a way this machine can still be tested in QEMU? > > I have an image in my test set: > $ ~/test-images/digic/runme ./build/x86/arm-softmmu/qemu-system-arm > Switch to console [cs0] > > > barebox 2013.12.0-00160-g2e82c4a #507 Thu Dec 12 12:42:43 MSK 2013 > > > Board: Canon PowerShot A1100 IS > digic-gpio c0220000.gpio: probed gpiochip-1 with base 0 > cfi_flash f8000000.flash: found cfi flash at f8000000, size 4194304 > malloc space: 0x00100000 -> 0x002fffff (size 2 MiB) > Open /dev/env0 No such file or directory > no valid environment found on /dev/env0. Using default environment > running /env/bin/init... > canon> / > > Command line is: > > ${QEMU} \ > -M canon-a1100 -serial stdio -display none \ > --machine firmware="$TESTDIR"/canon-a1100-rom1.bin > > filename suggests that's the same firmware image you link to? > > $ md5sum ~/test-images/digic/canon-a1100-rom1.bin > 66e76691cbd8b140549c878ae3849147
Thanks for the hint! My image had a different md5sum, so I think it's just a bad version that I've downloaded. I've finally also managed to compile barebox on my own with these steps: tar -xaf barebox-....tar.bz2 cd barebox-... cp ./arch/arm/configs/canon-a1100_defconfig .config make CROSS_PREFIX=arm-linux-gnu- ARCH=arm CC=arm-linux-gnu-gcc \ LD=arm-linux-gnu-ld OBJCOPY=arm-linux-gnu-objcopy olddefconfig make CROSS_PREFIX=arm-linux-gnu- ARCH=arm CC=arm-linux-gnu-gcc \ LD=arm-linux-gnu-ld OBJCOPY=arm-linux-gnu-objcopy -j8 And that version indeed prints some output via its emulated serial console to stdio :-) CC-ing some "tests/docker" people in case somebody wants to turn that into a docker-based test, too... Thomas
