Qemu support for mcimx6ul-evk machine

Qemu support for mcimx6ul-evk machine

[Pratik Parvati]

[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]

Hi Support team,

Lately, I am trying to get Linux up on qemu-arm *mcimx6ul-evk* machine
using buildroot. I have generated all the images required for my target
machine. Following are the steps I followed for building images on
buildroot (*version: buildroot-2016.11.1*).

$ make freescale_imx6ulevk_defconfig
$ make nconfig

I have selected the packages required for my qemu build and then built the
images using command

$ make

in "*output/images"* I see the following images generated,
*boot.vfat,  imx6ul-14x14-evk.dtb,  rootfs.ext2,  rootfs.ext4,
rootfs.tar,  sdcard.img,  u-boot.bin,  u-boot.imx,  zImage*.

I am referring this <https://dzone.com/articles/an-arm-image-with-buildroot>
article to replicate the same for mcimx6ul-evk. I ran the below command to
boot Linux on my target machine

$ qemu-system-arm -M mcimx6ul-evk -m 512M -kernel output/images/zImage
-monitor stdio -drive file=output/images/rootfs.ext2,format=raw

I don't see Linux booting on the serial0 console without any logs. can
someone please help me how to resolve this? Or am I missing something here?

Note: The qemu(*version: qemu-4.1.0*) is built for arm target using below
commands.

$ ./configure --target-list=arm-softmmu --enable-sdl
$ make
$ sudo make install

Thanks & Regards,
Pratik

[-- Attachment #2: Type: text/html, Size: 2288 bytes --]

Re: Qemu support for mcimx6ul-evk machine

[Peter Maydell]

On Thu, 14 Nov 2019 at 05:12, Pratik Parvati <pratikp@vayavyalabs.com> wrote:
>
> Hi Support team,

There is no 'support team' -- you're just talking to other
users and to developers on this mailing list :-)

> I am referring this article to replicate the same for mcimx6ul-evk. I ran the below command to boot Linux on my target machine
>
> $ qemu-system-arm -M mcimx6ul-evk -m 512M -kernel output/images/zImage -monitor stdio -drive file=output/images/rootfs.ext2,format=raw
>
> I don't see Linux booting on the serial0 console without any logs. can someone please help me how to resolve this? Or am I missing something here?

You haven't provided a dtb file to QEMU, which is
usually needed for the kernel to identify what
hardware it is running on and to find devices
like the serial port.

I also suspect that that -drive option is not doing
anything useful (you haven't specified what it plugs
into and I don't think the mcimx6ul-evk will assume
you meant an SD card image by default), but that
won't prevent initial boot so you can leave that
problem for later.


thanks
-- PMM

Re: Qemu support for mcimx6ul-evk machine

[Pratik Parvati]

[-- Attachment #1.1: Type: text/plain, Size: 1771 bytes --]

Hi Peter,

Thanks for the reply.

I have run the qemu command with dtb file

$ qemu-system-arm -M mcimx6ul-evk -m 512M -kernel output/images/zImage
-monitor stdio -dtb output/images/imx6ul-14x14-evk.dtb

I am seeing a serial0 console popping up but there is no log on the
console. I see something like this

[image: serial0.png]

There is no rootfs now So, I should at least see logs with a kernel panic
at the end. I wonder why I am not seeing any linux boot logs on the
console. Did I miss anything in the command?

Thanks & Regards,
Pratik


On Thu, Nov 14, 2019 at 3:49 PM Peter Maydell <peter.maydell@linaro.org>
wrote:

> On Thu, 14 Nov 2019 at 05:12, Pratik Parvati <pratikp@vayavyalabs.com>
> wrote:
> >
> > Hi Support team,
>
> There is no 'support team' -- you're just talking to other
> users and to developers on this mailing list :-)
>
> > I am referring this article to replicate the same for mcimx6ul-evk. I
> ran the below command to boot Linux on my target machine
> >
> > $ qemu-system-arm -M mcimx6ul-evk -m 512M -kernel output/images/zImage
> -monitor stdio -drive file=output/images/rootfs.ext2,format=raw
> >
> > I don't see Linux booting on the serial0 console without any logs. can
> someone please help me how to resolve this? Or am I missing something here?
>
> You haven't provided a dtb file to QEMU, which is
> usually needed for the kernel to identify what
> hardware it is running on and to find devices
> like the serial port.
>
> I also suspect that that -drive option is not doing
> anything useful (you haven't specified what it plugs
> into and I don't think the mcimx6ul-evk will assume
> you meant an SD card image by default), but that
> won't prevent initial boot so you can leave that
> problem for later.
>
>
> thanks
> -- PMM
>

[-- Attachment #1.2: Type: text/html, Size: 2783 bytes --]

[-- Attachment #2: serial0.png --]
[-- Type: image/png, Size: 5898 bytes --]

Re: Qemu support for mcimx6ul-evk machine

[Peter Maydell]

On Thu, 14 Nov 2019 at 10:43, Pratik Parvati <pratikp@vayavyalabs.com> wrote:
>
> Hi Peter,
>
> Thanks for the reply.
>
> I have run the qemu command with dtb file
>
> $ qemu-system-arm -M mcimx6ul-evk -m 512M -kernel output/images/zImage -monitor stdio -dtb output/images/imx6ul-14x14-evk.dtb
>
> I am seeing a serial0 console popping up but there is no log on the console. I see something like this
>
>
>
> There is no rootfs now So, I should at least see logs with a kernel panic at the end. I wonder why I am not seeing any linux boot logs on the console. Did I miss anything in the command?


It doesn't look obviously wrong. Possibly either:
 * it's the wrong dtb for this board (though the filename
   looks right)
 * the kernel is not configured correctly
 * the kernel is trying to access some device that QEMU
   doesn't model and crashing

Generally bootup problems all manifest in about the same way:
the kernel dies before managing to print anything to serial.
You need to debug them the same way you'd debug board bringup
on real hardware -- the QEMU gdbstub can sometimes be helpful.

thanks
-- PMM

Re: Qemu support for mcimx6ul-evk machine

[Alex Bennée]

Pratik Parvati <pratikp@vayavyalabs.com> writes:

> Hi Support team,
>
> Lately, I am trying to get Linux up on qemu-arm *mcimx6ul-evk* machine
> using buildroot. I have generated all the images required for my target
> machine. Following are the steps I followed for building images on
> buildroot (*version: buildroot-2016.11.1*).
>
> $ make freescale_imx6ulevk_defconfig
> $ make nconfig
>
> I have selected the packages required for my qemu build and then built the
> images using command
>
> $ make
>
> in "*output/images"* I see the following images generated,
> *boot.vfat,  imx6ul-14x14-evk.dtb,  rootfs.ext2,  rootfs.ext4,
> rootfs.tar,  sdcard.img,  u-boot.bin,  u-boot.imx,  zImage*.
>
> I am referring this <https://dzone.com/articles/an-arm-image-with-buildroot>
> article to replicate the same for mcimx6ul-evk. I ran the below command to
> boot Linux on my target machine
>
> $ qemu-system-arm -M mcimx6ul-evk -m 512M -kernel output/images/zImage
> -monitor stdio -drive file=output/images/rootfs.ext2,format=raw

Currently you have the monitor set to stdio so you won't see any output
from the serial port. You can configure serial output to multiplex with
the monitor with the command line option:

  -serial mon:stdio

and toggle between the two with C-a c

>
> I don't see Linux booting on the serial0 console without any logs. can
> someone please help me how to resolve this? Or am I missing something here?
>
> Note: The qemu(*version: qemu-4.1.0*) is built for arm target using below
> commands.
>
> $ ./configure --target-list=arm-softmmu --enable-sdl
> $ make
> $ sudo make install
>
> Thanks & Regards,
> Pratik


--
Alex Bennée

Re: Qemu support for mcimx6ul-evk machine

[Peter Maydell]

On Thu, 14 Nov 2019 at 11:17, Alex Bennée <alex.bennee@linaro.org> wrote:
>
>
> Pratik Parvati <pratikp@vayavyalabs.com> writes:
> > $ qemu-system-arm -M mcimx6ul-evk -m 512M -kernel output/images/zImage
> > -monitor stdio -drive file=output/images/rootfs.ext2,format=raw
>
> Currently you have the monitor set to stdio so you won't see any output
> from the serial port. You can configure serial output to multiplex with
> the monitor with the command line option:
>
>   -serial mon:stdio
>
> and toggle between the two with C-a c

It should appear in the graphical window by default, I think.

thanks
-- PMM