Re: [Xen-devel] Problems in running XenARM on Cortex-A15 Fast Models

[XiaoGuang Wang <xjtuwxg@xxxxxxxxx>]

2013/9/20 Ian Campbell <ian.campbell@xxxxxxxxxx>

On Fri, 2013-09-20 at 11:31 -0400, XiaoGuang Wang wrote:
> 2013/9/19 Ian Campbell <ian.campbell@xxxxxxxxxx>
>         On Thu, 2013-09-19 at 18:36 -0400, XiaoGuang Wang wrote:
>         >
>         > 2013/9/19 Ian Campbell <ian.campbell@xxxxxxxxxx>
>         >         Please don't top post.
>         > Sorry!
>         >
>         >         On Thu, 2013-09-19 at 10:56 -0400, XiaoGuang Wang
>         wrote:
>         >
>         >         > So I don't know why I cannot bring up x-term
>         windows when I
>         >         start xen
>         >         > on fast models. Normally, will it start x-term
>         windows if I
>         >         do the
>         >         > command like:
>         >         > model_shell
>         >         >
>         >
>         FastModels/FastModelsPortfolio_7.0/examples/RTSM_VE/Build_Cortex-A15x1/Linux64-Release-GCC-4.1/cadi_system_Linux64-Release-GCC-4.1.so xen.git/xen/xen.axp
>         >
>         >
>         >         AFAIK the model won't open the xterm until something
>         reads or
>         >         writes the
>         >         related serial port. So if you haven't configured
>         your console
>         >         correctly
>         >         then they may never show up.
>         >
>         >         What is your hypervisor command line (in the DTS)?
>         >
>         >         You could also try using
>         CONFIG_EARLY_PRINTK=fastmodel when
>         >         building
>         >         Xen.
>         >
>         >         Ian.
>         >
>         >
>         > Hi Ian,
>         >
>         >
>         > It still doesn't appear. I download xen-4.4 (also try
>         xen-4.3.0) and
>         > compile it with this script:
>         >
>         >
>         > xiaoguang@dophine:~/works/arm/xen/xen-4.3.0$ cat
>         compile-xen.sh
>         > CONFIG_EARLY_PRINTK=fastmodel
>         >
>         CONFIG_DTB_FILE=/home/xiaoguang/works/arm/xen/vexpress-v2p-ca15-tc1.dtb
>
>
>         unless you use "export" these aren't actually exposed to
>         subprocesses,
>         such as the make invocation.
>
>         I just put these directly on the make command line, as you've
>         done for
>         XEN_TARGET_ARCH and CROSS_COMPILE.
> Yes. I try it like this, but it still doesn't work:
> $ CONFIG_EARLY_PRINTK=fastmodel
> CONFIG_DTB_FILE=/home/xiaoguang/works/arm/xen/vexpress-v2p-ca15-tc1.dtb make -C xen XEN_TARGET_ARCH=arm32 CROSS_COMPILE=/usr/bin/arm-linux-gnueabi-

Try with them after the make command. i.e. exactly the same place as
you've got the XEN_TARGET_ARCH setting. There are subtle semantic
differences to make between environment variables and variables set on
the make command line.

I compile it like this, but there still only a "Fast Models - CLCD" windows appear.

$ make dist-xen XEN_TARGET_ARCH=arm32 CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- CONFIG_EARLY_PRINTK=fastmodel CONFIG_DTB_FILE=/home/xiaoguang/works/arm/xen/vexpress-v2p-ca15-tc1.dtb

And I run xen with the following command:

$ model_shell ~/ARM/FastModelsPortfolio_8.2/examples/FVP_VE/Build_Cortex-A15x1/Linux64-Release-GCC-4.4/cadi_system_Linux64-Release-GCC-4.4.so xen-4.3.0/xen/xen -C motherboard.flashloader0.fname=zImage

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel