[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] Bringing up xen on omap5432
Hi,
 I am trying to bring up xen on omap5432 and running into some issues. I pretty much followed the following. Build Xen: # git clone git://xenbits.xen.org/xen.git # cd xen # make dist-xen XEN_TARGET_ARCH=arm32 CROSS_COMPILE=arm-linux-gnueabihf- CONFIG_EARLY_PRINTK=omap5432 Create uImage for Xen: Â# mkimage -A arm -T kernel -a 0x90000000 -e 0x90000000 -C none -d "xen/xen" xen-uImage 2)Create a dtb file using the following command Âmake ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- omap5-uevm.dtb 3)Build Uboot following instructions at https://eewiki.net/display/linuxonarm/OMAP5432+uEVM#OMAP5432uEVM-microSDboot But when I try to boot I am running into an undefined instruction exception. U-Boot# bootm $xen_addr_r - $dtb_addr_r ## Booting kernel from Legacy Image at 90000000 ...  ÂImage Name:   ÂImage Type:  ARM Linux Kernel Image (uncompressed)  ÂData Size:  Â721756 Bytes = 704.8 KiB  ÂLoad Address: 90000000  ÂEntry Point: Â90000000  Â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=d000  ÂLoading Device Tree to 8fff0000, end 8fffffff ... OK Starting kernel ... undefined instruction pc : [<fef910e8>]  lr : [<fef5d75c>] sp : fdf3cbd0 Âip : 48211080 fp : 900b035c r10: fdf3e2fc Âr9 : fdf3cef8 r8 : 00000000 r7 : fefa4090 Âr6 : 90000000 r5 : 00000000 Âr4 : 8fff0000 r3 : 48212000 Âr2 : 00000006 r1 : 00043fff Âr0 : 00063fff Flags: nZCv ÂIRQs off ÂFIQs off ÂMode SVC_32 Resetting CPU ... resetting ... On a side note how do I do an objdump of the xen and u-boot code to get to the instruction that is causing the crash? Any instruction on how to add debug instrumentation to u-boot would also help. Thanks! Surya Satyavolu _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |