On Wed, Jul 18, 2018 at 11:51 AM Giuseppe Levi <giuseppe.levi@xxxxxxxxx> wrote: > > Ok tried with CROSS_COMPILE=arm-linux-gnueabi- this should be 32bit arm > then: qemu-system-arm -m 256M -machine virt -display none -serial > stdio -kernel barebox > > hangs..... any idea ? Should I use a different machine ? > NOTE: All of the below pertains to upstream QEMU You are running QEMU emulating "mach-virt", which is a special generic ARM machine in QEMU against a Barebox built for AT91. Last time I checked former can only be configured to have Cortex-A15 (ARMv7), A53 or A57(ARMv8) as a CPU, whereas the latter is ARM9 (ARMv5), not to mention that memory map layout for all of the peripherals _and_ type of IP blocks used is very different. Unless I am getting something very wrong, I'd be very much surprised if it actually worked for you. As for using a different machine, I don't think that would help. AFAIK, what you are trying to do is not currently supported. > It would be very complex to create a White Rabbit virtual machine ? > (HW description is open) Not sure if I'd say it would be "complex", but time consuming for sure. It took me a couple of weeks of work to add enough i.MX7 support to QEMU for it would be able to boot stock Linux and I had a headstart because QEMU already supported i.MX6 when I started. I haven't looked at QEMU tree for probably 4 months, so my knowledge is a bit outdated, but AFAIK, while ARM9 CPU emulation is availible, there's no AT91 SoC specific IP blocks emulation that it supports. So, at a bare minimum, just to see some serial in QEMU, you are looking at implementing your AT91 machine with its memory map, UART IP block emulation plus any peripherals that have to be emulated to "fool" Barebox into booting. Thanks, Andrey Smirnov _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
