From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: giuseppe.levi@gmail.com
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: qemu and barebox
Date: Wed, 18 Jul 2018 12:53:09 -0700 [thread overview]
Message-ID: <CAHQ1cqH0YLC7C70gB2retS0TYusWhTavnV=+X4O-NjXDpV08-w@mail.gmail.com> (raw)
In-Reply-To: <CAPPP46RVU698Uo_Ej2O8N7HETKRGG6aZDkpFA69Ox+tR3DdcGw@mail.gmail.com>
On Wed, Jul 18, 2018 at 11:51 AM Giuseppe Levi <giuseppe.levi@gmail.com> 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@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-07-18 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 13:02 Giuseppe Levi
2018-07-18 13:44 ` Roland Hieber
2018-07-18 14:03 ` Alessandro Rubini
2018-07-18 18:50 ` Giuseppe Levi
2018-07-18 19:53 ` Andrey Smirnov [this message]
2018-07-18 20:39 ` Alessandro Rubini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHQ1cqH0YLC7C70gB2retS0TYusWhTavnV=+X4O-NjXDpV08-w@mail.gmail.com' \
--to=andrew.smirnov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=giuseppe.levi@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox