[Xen-devel] Problems running Xen 4.4 on OMAP5432 evm

["Kapania, Ashish" <akapania@xxxxxx>]

Hi,

I am trying to run Xen (+ Linux dom0) on OMAP5432 evm and have been having
trouble just booting xen itself. The xen wiki does not have build instructions
for OMAP5432 but the source code seems to have support for it so I am assuming
that board is supported. I am using xen RELEASE-4.4.0 git tag to build a xen
image. Here's my build command-line:

make dist-xen XEN_TARGET_ARCH=arm32 CROSS_COMPILE=arm-linux-gnueabihf- 
CONFIG_EARLY_PRINTK=omap5432

I am using uboot 2014.01 with tweaks to put A15 in hypervisor mode and am
using Linux 3.8 kernel (with xen related CONFIGs turned on).

When I boot xen, I see the A15 hangs in setup_pagetables() function in 
arch/arm/mm.c
file. Here's the UART log I get with earlyprintk turned on:

UART log:
===========================================================================
U-Boot# fatload mmc 0 0x825f0000 omap5-uevm.dtb
reading omap5-uevm.dtb
27990 bytes read in 8 ms (3.3 MiB/s)
U-Boot# fatload mmc 0 0x80300000 zImage
reading zImage
5039880 bytes read in 270 ms (17.8 MiB/s)
U-Boot# fatload mmc 0 0xE0000000 uXen
reading uXen
656208 bytes read in 40 ms (15.6 MiB/s)
U-Boot# setenv fdt_high 0x84000000
U-Boot# fdt addr 0x825f0000
U-Boot# fdt resize
U-Boot# fdt chosen
U-Boot# fdt set /chosen \#address-cells <1>
U-Boot# fdt set /chosen \#size-cells <1>
U-Boot# fdt set /chosen xen,dom0-bootargs "elevator=noop console=hvc0,115200n8 
root=/dev/mmcblk0p2 rw rootwait earlyprintk=xen fixrtc";
U-Boot# fdt set /chosen xen,xen-bootargs "nosmp=true bootscrub=false 
dom0_mem=256M console=dtuart dtuart=serial2 earlyprintk=xen";
U-Boot# fdt mknod /chosen modules
U-Boot# fdt set /chosen/modules comptaible "xen,linux-zimage" 
"xen,multiboot-module"
U-Boot# fdt set /chosen/modules reg <0x80300000 0x4cf000>
U-Boot# fdt print /chosen
chosen {
        xen,xen-bootargs = "nosmp=true bootscrub=false dom0_mem=256M 
console=dtuart dtuart=serial2 earlyprintk=xen";
        xen,dom0-bootargs = "elevator=noop console=hvc0,115200n8 
root=/dev/mmcblk0p2 rw rootwait earlyprintk=xen fixrtc";
        #size-cells = <0x00000001>;
        #address-cells = <0x00000001>;
        modules {
                reg = <0x80300000 0x004cf000>;
                comptaible = "xen,linux-zimage", "xen,multiboot-module";
        };
};
U-Boot# bootm 0xE0000000 - 0x825F0000
## Booting kernel from Legacy Image at e0000000 ...
   Image Name:   Xen
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    656144 Bytes = 640.8 KiB
   Load Address: f0000000
   Entry Point:  f0000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 825f0000
   Booting using the fdt blob at 0x825f0000
   Loading Kernel Image ... OK
   reserving fdt memory region: addr=825f0000 size=7000
   Loading Device Tree to 83ff6000, end 83ffffff ... OK

Starting kernel ...

- UART enabled -
- CPU 00000000 booting -
- Xen starting in Hyp mode -
- Zero BSS -
- Setting up control registers -
- Turning on paging -
- Ready -
Checking for initrd in /chosen
RAM: 0000000080000000 - 00000000feffffff

MODULE[1]: 0000000083ff6000 - 0000000083ffd000 
 RESVD[0]: 00000000825f0000 - 00000000825f7000
 RESVD[1]: 0000000083ff6000 - 0000000083ffd000

Command line: dom0_mem=256M console=dtuart dtuart=serial2 earlyprintk=xen
Placing Xen at 0x00000000fee00000-0x00000000ff000000

===========================================================================

Any ideas on what I might be doing wrong ? Maybe I am missing some patch
that is required to run xen on omap5432 ?

Thanks,
Ashish

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