[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Question about running Xen 4.4 on Arndale board
Thanks for your comments. I tried with Tod's comment of dtb and Julien's patch. But no difference. env setting: -----------------------------------
setenv kernel_addr_r 0x60000000 setenv xen_addr_r 0x50000000 setenv dtb_addr_r 0x42000000 fatload mmc 0:2 $kernel_addr_r /zImage fatload mmc 0:2 $xen_addr_r /xen-uImage
fatload mmc 0:2 $dtb_addr_r /exynos5420-arndale-octa.dtb fdt addr $dtb_addr_r fdt resize setenv xen_bootargs 'sync_console console=dtuart dtuart=/serial@12C20000' setenv dom0_bootargs 'console=hvc0 ignore_loglevel psci_enable clk_ignore_unused root=/dev/mmcblk1p3'
fdt set /chosen xen,xen-bootargs \"$xen_bootargs\" fdt set /chosen xen,dom0-bootargs \"$dom0_bootargs\" fdt mknode /chosen modules fdt set /chosen/modules '#address-cells' <1>
fdt set /chosen/modules '#size-cells' <1> fdt mknode /chosen/modules module@0 fdt set /chosen/modules/module@0 compatible "xen,linux-zimage" "xen,multiboot-module"
fdt set /chosen/modules/module@0 reg <$kernel_addr_r 0x00a00000> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ÂÂ bootm $xen_addr_r - $dtb_addr_r ----------------------------------- Log: ============================= U-Boot 2012.07 (Feb 15 2014 - 17:29:55) for ARNDALE OCTA CPU: Exynos5420 Rev2.0 [Samsung SOC on SMP Platform Base on ARM CortexA15]
APLL = 800MHz, KPLL = 600MHz MPLL = 532MHz, BPLL = 800MHz Board: ARNDALE OCTA DRAM: Â2 GiB WARNING: Caches not enabled TrustZone Enabled BSP
BL1 version:Â Checking Boot Mode ... SDMMC MMC: Â S5P_MSHC2: 0, S5P_MSHC0: 1 MMC Device 0: 3.7 GiB MMC Device 1: 3.6 GiB MMC Device 2: MMC Device 2 not found
there are pending interrupts 0x00000001 *** Warning - bad CRC, using default environment In: Â Âserial Out: Â serial Err: Â serial Net: Â No ethernet found.
(Re)start USB... USB: Â Register 1313 NbrPorts 3 USB EHCI 1.00 scanning bus for devices... The request port(2) is not configured The request port(2) is not configured
3 USB Device(s) found    Âscanning bus for storage devices... 0 Storage Device(s) found    Âscanning usb for ethernet devices... 1 Ethernet Device(s) found Hit any key to stop autoboot: Â0Â
reading boot.scr 989 bytes read Running bootscript from mmc0:2 ... ## Executing script at 22000000 reading /zImage 2606416 bytes read
reading /xen-uImage 557904 bytes read reading /exynos5420-arndale-octa.dtb 31105 bytes read ## Booting kernel from Legacy Image at 50000000 ...
 ÂImage Name:   ÂImage Type:  ARM Linux Kernel Image (uncompressed)  ÂData Size:  Â557840 Bytes = 544.8 KiB  ÂLoad Address: 80200000  ÂEntry Point: Â80200000
 ÂVerifying Checksum ... OK ## Flattened Device Tree blob at 42000000  ÂBooting using the fdt blob at 0x42000000  ÂLoading Kernel Image ... OK OK  Âreserving fdt memory region: addr=42000000 size=8000
 ÂLoading Device Tree to 2fff5000, end 2fffffff ... OK Starting kernel ... ======================= It is very wired that CONFIG_EARLY_PRINTK is not working.
If the patch is correct, is xen dead just at starting or totally wrong place of image? Best, Hyonyoung
On Mon, Apr 14, 2014 at 12:31 PM, Julien Grall <julien.grall@xxxxxxxxxx> wrote:
------------------------------------- Graduate School of Convergence IT, Korea University Research Professor, Hyonoung Choi, Ph.D. Â Graduate School of Convergence IT, Korea University, 5-Ga, Anam-Dong, Sungbuk-Gu, Seoul 136-701, Republic of Korea. TelÂÂÂ : +82-(0)2-3290-3640 Mobile : +82-(0)10-5353-0414 E-mail : neongas@xxxxxxxxxxx, commani@xxxxxxxxx ------------------------------------- _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |