Hi Stefano,
I have done almost the same thing but with toolchain
version 4.6.3. The dtb file is being recognized during compiling xen as is
evident from the output below. But still is not being recognized by the Fast
Model and it shows the same error.
...
arm-linux-gnueabihf-ld -marmelf_linux_eabi -T xen.lds
-N prelink.o \
ÂÂÂÂÂ ÂÂÂ
/home/phoenix/Desktop/xen-unstable.git-xen-arm-4.3-3-e2cb352/xen/.xen-syms.0.o
-o /home/phoenix/Desktop/xen-unstable.git-xen-arm-4.3-3-e2cb352/xen/.xen-syms.1
arm-linux-gnueabihf-nm -n
/home/phoenix/Desktop/xen-unstable.git-xen-arm-4.3-3-e2cb352/xen/.xen-syms.1 |
/home/phoenix/Desktop/xen-unstable.git-xen-arm-4.3-3-e2cb352/xen/tools/symbols
>/home/phoenix/Desktop/xen-unstable.git-xen-arm-4.3-3-e2cb352/xen/.xen-syms.1.S
make -f
/home/phoenix/Desktop/xen-unstable.git-xen-arm-4.3-3-e2cb352/xen/Rules.mk
/home/phoenix/Desktop/xen-unstable.git-xen-arm-4.3-3-e2cb352/xen/.xen-syms.1.o
make[3]: Entering directory `/home/phoenix/Desktop/xen-unstable.git-xen-arm-4.3-3-e2cb352/xen/arch/arm'
arm-linux-gnueabihf-gcc -D__ASSEMBLY__ -include
/home/phoenix/Desktop/xen-unstable.git-xen-arm-4.3-3-e2cb352/xen/include/xen/config.h
-O1 -fno-omit-frame-pointer -marm -g -fno-strict-aliasing -Wall
-Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable
-fno-builtin -fno-common -Wredundant-decls -iwithprefix include -Werror
-Wno-pointer-arith -pipe
-I/home/phoenix/Desktop/xen-unstable.git-xen-arm-4.3-3-e2cb352/xen/include
-fno-stack-protector -fno-exceptions -Wnested-externs -msoft-float
-mcpu=cortex-a15 -mfpu=vfpv3 -mfloat-abi=softfp -DGCC_HAS_VISIBILITY_ATTRIBUTE
-fno-optimize-sibling-calls -g -D__XEN__ -include
/home/phoenix/Desktop/xen-unstable.git-xen-arm-4.3-3-e2cb352/xen/include/xen/config.h
-DVERBOSE -fno-omit-frame-pointer -DCONFIG_FRAME_POINTER -MMD -MF
..xen-syms.1.o.d -DCONFIG_DTB_FILE=\"/home/phoenix/Desktop/xen-unstable.git-xen-arm-4.3-3-e2cb352/vexpress-v2p-ca15-tc1.dtb\"
-c /home/phoenix/Desktop/xen-unstable.git-xen-arm-4.3-3-e2cb352/xen/.xen-syms.1.S
-o
/home/phoenix/Desktop/xen-unstable.git-xen-arm-4.3-3-e2cb352/xen/.xen-syms.1.o
...
Regards
Shubham Khandelwal
-----Original Message-----
From: Stefano Stabellini [mailto:stefano.stabellini@xxxxxxxxxxxxx]
Sent: Monday, April 01, 2013 5:29 PM
To: Khandelwal, Shubham
Cc: 'xen-arm@xxxxxxxxxxxxx'; Datta, Souvik; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [XenARM] Running Xen ARM on Fast Model
On Mon, 1 Apr 2013, Khandelwal, Shubham wrote:
> Hi All,
>
> I am trying to run Xen on ARM v4.3.3, on ARM Fast
Models for the versatile express platform, but I have run into some errors.
>
> I have compiled the Linux kernel 3.8 rc3 as a dom0
image using linaro tool chain and the config parameters as mentioned here
> http://xenbits.xen.org/people/sstabellini/config
>
> I have also exported the the variable
CONFIG_DTB_FILE to the location of the device tree file which is taken from
>
http://xenbits.xen.org/gitweb/?p=people/sstabellini/device-trees.git;a=blob_plain;f=vexpress-v2p-ca15-tc1.dtb;hb=HEAD
while
> compiling Xen
>
> I am getting No Valid device tree error as shown
below
Are you sure that CONFIG_DTB_FILE was exported correctly?
Something as simple as that, could be the cause of the
issue.
In my build script I have:
CONFIG_DTB_FILE=/path/to/vexpress-v2p-ca15-tc1.dtb make
-C xen XEN_TARGET_ARCH=arm32 debug=y CROSS_COMPILE=/path/to/gcc-4.6.0-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-
