Re: Failed to launch xen on J6 evm

Re: Failed to launch xen on J6 evm

[Korupol, Naveen (EXT)]

Hi Ian/Team

It finally looks like xen and dom0 are stable, but the cli seems tricky.

I can switch between xen/dom0 but cannot execute xm cmds...

Any idea where I went wrong? Please find the log below - thanks

Regards
Naveen

\x01
U-Boot SPL 2015.04-rc1 (Mar 10 2015 - 13:35:08)
DRA752 ES1.1
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img


U-Boot 2015.04-rc1 (Mar 10 2015 - 13:35:08)

CPU  : DRA752 ES1.1
Board: DRA7xx
I2C:   ready
DRAM:  1.5 GiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

SCSI:  SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst
scanning bus for devices...
Found 0 device(s).
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
reading uEnv.txt
** Unable to read file uEnv.txt **
** File not found /boot/zImage **
switch to partitions #0, OK
mmc1(part 0) is current device
SD/MMC found on device 1
** Unrecognized filesystem type **
** No partition table - mmc 1 **
U-Boot# setenv dtb_addr_r 0x825f0000
U-Boot#
U-Boot# setenv xen_addr_r 0x90000000
U-Boot#
U-Boot# setenv kernel_addr_r 0xa0000000
U-Boot#
U-Boot# setenv xen_bootargs 'dom0_mem=128M console=dtuart dtuart=serial0 dom0_max_vcpus=2 bootscrub=0 flask_enforcing=1 noreboot early_printk'
U-Boot#
U-Boot# setenv dom0_bootargs 'console=hvc0 root=/dev/mmcblk0p2 rw rootwait fixrtc'
U-Boot#
U-Boot# fatload mmc 0:1 $dtb_addr_r dra7-evm.dtb
reading dra7-evm.dtb
93457 bytes read in 12 ms (7.4 MiB/s)
U-Boot#
U-Boot# fatload mmc 0:1 $xen_addr_r xen-uImage
reading xen-uImage
754588 bytes read in 65 ms (11.1 MiB/s)
U-Boot#
U-Boot# fatload mmc 0:1 $kernel_addr_r uImage
reading uImage
4911296 bytes read in 398 ms (11.8 MiB/s)
U-Boot#
U-Boot# setenv fdt_high 0x84000000
U-Boot#
U-Boot# fdt addr $dtb_addr_r
U-Boot#
U-Boot# fdt resize
U-Boot#
U-Boot# fdt set /chosen '#address-cells' <1>
U-Boot#
U-Boot# fdt set /chosen '#size-cells' <1>
U-Boot#
U-Boot# fdt set /chosen xen,xen-bootargs \"$xen_bootargs\"
U-Boot#
U-Boot# fdt resize
U-Boot#
U-Boot# fdt set /chosen xen,dom0-bootargs \"$dom0_bootargs\"
U-Boot# fdt mknode /chosen module@0
U-Boot#
U-Boot# fdt set /chosen/module@0 compatible xen,linux-zimage xen,multiboot-module
U-Boot#
U-Boot# fdt set /chosen/module@0 reg <$kernel_addr_r 0x4b0000>
U-Boot#
U-Boot# fdt print /chosen
chosen {
        xen,dom0-bootargs = "console=hvc0 root=/dev/mmcblk0p2 rw rootwait fixrtc";
        xen,xen-bootargs = "dom0_mem=128M console=dtuart dtuart=serial0 dom0_max_vcpus=2 bootscrub=0 flask_enforcing=1 noreboot early_printk";
        #size-cells = <0x00000001>;
        #address-cells = <0x00000001>;
        module@0 {
                reg = <0xa0000000 0x004b0000>;
                compatible = "xen,linux-zimage", "xen,multiboot-module";
        };
};
U-Boot# bootm $xen_addr_r - $dtb_addr_r
## Booting kernel from Legacy Image at 90000000 ...
   Image Name:   Xen.Trial.16
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    754524 Bytes = 736.8 KiB
   Load Address: 80200000
   Entry Point:  80200000
   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=17000
   Loading Device Tree to 83fe6000, end 83ffffff ... OK

Starting kernel ...

 Xen 4.5.0
(XEN) Xen version 4.5.0 (root@) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 4.9.1-16ubuntu6) 4.9.1) debug=y Wed Mar 11 12:14:52 PDT 2015
(XEN) Latest ChangeSet:
(XEN) Processor: 412fc0f2: "ARM Limited", variant: 0x2, part 0xc0f, rev 0x2
(XEN) 32-bit Execution:
(XEN)   Processor Features: 00001131:00011011
(XEN)     Instruction Sets: AArch32 A32 Thumb Thumb-2 ThumbEE Jazelle
(XEN)     Extensions: GenericTimer Security
(XEN)   Debug Features: 02010555
(XEN)   Auxiliary Features: 00000000
(XEN)   Memory Model Features: 10201105 20000000 01240000 02102211
(XEN)  ISA Features: 02101110 13112111 21232041 11112131 10011142 00000000
(XEN) Platform: TI DRA7
(XEN) Set AuxCoreBoot1 to 00000000dfe0004c (0020004c)
(XEN) Set AuxCoreBoot0 to 0x20
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27
(XEN) Using generic timer at 6144 KHz
(XEN) GICv2 initialization:
(XEN)         gic_dist_addr=0000000048211000
(XEN)         gic_cpu_addr=0000000048212000
(XEN)         gic_hyp_addr=0000000048214000
(XEN)         gic_vcpu_addr=0000000048216000
(XEN)         gic_maintenance_irq=25
(XEN) GICv2: 192 lines, 2 cpus, secure (IID 0000043b).
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) I/O virtualisation disabled
(XEN) Allocated console ring of 16 KiB.
(XEN) VFP implementer 0x41 architecture 4 part 0x30 variant 0xf rev 0x0
(XEN) Bringing up CPU1
(XEN) CPU 1 booted.
(XEN) Brought up 2 CPUs
(XEN) P2M: 40-bit IPA
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80003558
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading kernel from boot module @ 00000000a0000000
(XEN) Allocating 1:1 mappings totalling 128MB for dom0:
(XEN) BANK[0] 0x000000a8000000-0x000000b0000000 (128MB)
(XEN) Loading zImage from 00000000a0000040 to 00000000afa00000-00000000afeaf080
(XEN) Loading dom0 DTB to 0x00000000af800000-0x00000000af8158dc
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 280kB init memory.
(XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switch input to DOM0)
(XEN) Physical memory information:
(XEN)     Xen heap: 196108kB free
(XEN)     heap[20]: 1211404kB free
(XEN)     Dom heap: 1211404kB free
(XEN) Physical memory information:
(XEN)     Xen heap: 196108kB free
(XEN)     heap[20]: 1211404kB free
(XEN)     Dom heap: 1211404kB free
(XEN) Physical memory information:
(XEN)     Xen heap: 196108kB free
(XEN)     heap[20]: 1211404kB free
(XEN)     Dom heap: 1211404kB free
(XEN) Physical memory information:
(XEN)     Xen heap: 196108kB free
(XEN)     heap[20]: 1211404kB free
(XEN)     Dom heap: 1211404kB free
(XEN) Physical memory information:
(XEN)     Xen heap: 196108kB free
(XEN)     heap[20]: 1211404kB free
(XEN)     Dom heap: 1211404kB free
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switch input to DOM0)
(XEN) Physical memory information:
(XEN)     Xen heap: 196108kB free
(XEN)     heap[20]: 1211404kB free
(XEN)     Dom heap: 1211404kB free

Please note my new email address Naveen.Korupol@ext.us.panasonic.com. The old address will be available until September 15, 2015.

Re: Failed to launch xen on J6 evm

[M A Young]

On Wed, 11 Mar 2015, Korupol, Naveen (EXT) wrote:

> Hi Ian/Team
> 
> It finally looks like xen and dom0 are stable, but the cli seems tricky.
> 
> I can switch between xen/dom0 but cannot execute xm cmds...

xm was dropped in xen 4.5. Use xl instead.

	Michael Young

Re: Failed to launch xen on J6 evm

[Ian Campbell]

On Wed, 2015-03-11 at 19:38 +0000, Korupol, Naveen (EXT) wrote:

As Michael says, xm doesn't exist any more (and never existed on ARM),
use xl. But, are you even getting a dom0 cli prompt? It doesn't look
like it.

> (XEN) Std. Loglevel: All
> (XEN) Guest Loglevel: All
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
> (XEN) Freed 280kB init memory.
> (XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switch input to DOM0)

Is there no dom0 output from this point on?

Have you enabled CONFIG_XEN in your dom0 kernel config, along with all
the other Xen option, in particular CONFIG_HVC_XEN?

You will also want to arrange for a getty process to run on hvc0 so you
can login.

> (XEN) Physical memory information:
> (XEN)     Xen heap: 196108kB free
> (XEN)     heap[20]: 1211404kB free
> (XEN)     Dom heap: 1211404kB free
> (XEN) Physical memory information:
> (XEN)     Xen heap: 196108kB free
> (XEN)     heap[20]: 1211404kB free
> (XEN)     Dom heap: 1211404kB free
> (XEN) Physical memory information:
> (XEN)     Xen heap: 196108kB free
> (XEN)     heap[20]: 1211404kB free
> (XEN)     Dom heap: 1211404kB free
> (XEN) Physical memory information:
> (XEN)     Xen heap: 196108kB free
> (XEN)     heap[20]: 1211404kB free
> (XEN)     Dom heap: 1211404kB free
> (XEN) Physical memory information:
> (XEN)     Xen heap: 196108kB free
> (XEN)     heap[20]: 1211404kB free
> (XEN)     Dom heap: 1211404kB free
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
> (XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switch input to DOM0)
> (XEN) Physical memory information:
> (XEN)     Xen heap: 196108kB free
> (XEN)     heap[20]: 1211404kB free
> (XEN)     Dom heap: 1211404kB free
> 
> Please note my new email address Naveen.Korupol@ext.us.panasonic.com. The old address will be available until September 15, 2015.

Re: Failed to launch xen on J6 evm

[Korupol, Naveen (EXT)]

Hi Ian

CONFIG_XEN iand CONFIG_HVC_XEN are enabled =y in .config
other config settings seem to be in line.

getty was not properly setup in my dom0 settings - thanks

Regards
Naveen
Please note my new email address Naveen.Korupol@ext.us.panasonic.com. The old address will be available until September 15, 2015.

Re: Failed to launch xen on J6 evm

[Korupol, Naveen (EXT)]

Hi Ian

I cannot see dom0 login prompt.
I presume its unable to find the rootfs itself where the getty settings are present and I tried to include initramfs but that gave me a different elf related error.

Is there any dom0 kernel and rootfs pair that I can use to test this setup for armhf rather than building locally?
Kindly let me know if the boot params are still correct: - thanks

xen-bootargs           dom0_mem=512M console=dtuart dtuart=serial0 dom0_max_vcpus=2 bootscrub=0 flask_enforcing=1 noreboot early_printk
dom0-bootargs       console=hvc0 psci=enable clk_ignore_unused root=/dev/mmcblk0p2 rw rootwait init=/sbin/init nomodeset earlyprintk=xen debug maxcpus=8 loglevel=10

my boot hangs as per log below: ( ctrl+aaa still moves between xen  and dom0 consoles, I can query * in xen console that shows all that system info...any clues from there??)

Starting kernel ...

 Xen 4.5.0
(XEN) Xen version 4.5.0 (root@) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 4.9.1-16ubuntu6) 4.9.1) debug=y Wed Mar 11 12:14:52 PDT 2015
(XEN) Latest ChangeSet: 
(XEN) Processor: 412fc0f2: "ARM Limited", variant: 0x2, part 0xc0f, rev 0x2
(XEN) 32-bit Execution:
(XEN)   Processor Features: 00001131:00011011
(XEN)     Instruction Sets: AArch32 A32 Thumb Thumb-2 ThumbEE Jazelle
(XEN)     Extensions: GenericTimer Security
(XEN)   Debug Features: 02010555
(XEN)   Auxiliary Features: 00000000
(XEN)   Memory Model Features: 10201105 20000000 01240000 02102211
(XEN)  ISA Features: 02101110 13112111 21232041 11112131 10011142 00000000
(XEN) Platform: TI DRA7
(XEN) Set AuxCoreBoot1 to 00000000dfe0004c (0020004c)
(XEN) Set AuxCoreBoot0 to 0x20
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27
(XEN) Using generic timer at 6144 KHz
(XEN) GICv2 initialization:
(XEN)         gic_dist_addr=0000000048211000
(XEN)         gic_cpu_addr=0000000048212000
(XEN)         gic_hyp_addr=0000000048214000
(XEN)         gic_vcpu_addr=0000000048216000
(XEN)         gic_maintenance_irq=25
(XEN) GICv2: 192 lines, 2 cpus, secure (IID 0000043b).
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) I/O virtualisation disabled
(XEN) Allocated console ring of 16 KiB.
(XEN) VFP implementer 0x41 architecture 4 part 0x30 variant 0xf rev 0x0
(XEN) Bringing up CPU1
(XEN) CPU 1 booted.
(XEN) Brought up 2 CPUs
(XEN) P2M: 40-bit IPA
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80003558
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading kernel from boot module @ 00000000a0000000
(XEN) Allocating 1:1 mappings totalling 512MB for dom0:
(XEN) BANK[0] 0x000000b0000000-0x000000d0000000 (512MB)
(XEN) Loading zImage from 00000000a0000040 to 00000000b7a00000-00000000b7e89aa0
(XEN) Loading dom0 DTB to 0x00000000b8000000-0x00000000b801593c
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 280kB init memory.

Regards
Naveen
 
-----Original Message-----
From: Korupol, Naveen (EXT) 
Sent: Thursday, March 12, 2015 10:01 AM
To: Ian Campbell; Korupol, Naveen (EXT)
Cc: M A Young; xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] Failed to launch xen on J6 evm

Hi Ian

CONFIG_XEN iand CONFIG_HVC_XEN are enabled =y in .config other config settings seem to be in line.

getty was not properly setup in my dom0 settings - thanks

Regards
Naveen

Failed to launch xen on J6 evm

[Korupol, Naveen (EXT)]

[-- Attachment #1.1: Type: text/plain, Size: 2629 bytes --]

Hi

I am using J6 evm.

Tried to launch xen and it fails after reporting starting kernel.
I tried to change the load addresses and
played with couple different u-boots and file system images...but still on square 1.

I would like to know if this is a known issue with J6 EVM and
If there are any probable fixes/hints for bringing up XEN on J6 evm.

Here is the boot log where it hangs...

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

U-Boot SPL 2013.04 (Sep 24 2014 - 00:00:28)
DRA752 ES1.1
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2013.04 (Sep 24 2014 - 00:00:28)

CPU  : DRA752 ES1.1
Board: DRA7xx
I2C:   ready
DRAM:  1.5 GiB
WARNING: Caches not enabled
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot:  0

..
..
setenv dtb_addr_r 0x825f0000
setenv xen_addr_r 0x90000000
setenv kernel_addr_r 0xa0000000
..
..

fatload mmc 0:1 $dtb_addr_r dra7-evm.dtb
fatload mmc 0:1 $xen_addr_r xenuImage
..
..

DRA752 EVM # fdt print /chosen
chosen {
        xen,dom0-bootargs = "console=hvc0 root=/dev/mmcblk0p2 rw rootwait fixrtc";
        xen,xen-bootargs = "dom0_mem=128M sync_console console=dtuart dtuart=serial2 noreboot";
        #size-cells = <0x00000001>;
        #address-cells = <0x00000001>;
        module@0 {
                reg = <0xa0000000 0x004b0000>;
                compatible = "xen,linux-zimage", "xen,multiboot-module";
        };
};


DRA752 EVM # bootm $xen_addr_r - $dtb_addr_r
## Booting kernel from Legacy Image at 90000000 ...
   Image Name:   Xen.Trial.12
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    754524 Bytes = 736.8 KiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 825f0000
   Booting using the fdt blob at 0x825f0000
   Loading Kernel Image ... OK
OK
   reserving fdt memory region: addr=825f0000 size=17000
   Loading Device Tree to 83fe6000, end 83ffffff ... OK

Starting kernel ...

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Thanks
Naveen Korupol

Panasonic Automotive Systems Company of America
Panasonic Corporation of North America
37101 Corporate Drive,
Farmington Hills, MI 48331

T 248.324.6737
F 248.324.6893
korupoln@us.panasonic.com<mailto:korupoln@us.panasonic.com>





Please note my new email address Naveen.Korupol@ext.us.panasonic.com. The old address will be available until September 15, 2015.

[-- Attachment #1.2: Type: text/html, Size: 10137 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Re: Failed to launch xen on J6 evm

[Ian Campbell]

On Fri, 2015-03-06 at 20:03 +0000, Korupol, Naveen (EXT) wrote:
> I am using J6 evm.

What is one of them?

> played with couple different u-boots

Does your u-boot launch the kernel (AKA Xen in this case) in NS.HYP
mode?

> If there are any probable fixes/hints for bringing up XEN on J6 evm.

Given where things are apparently hanging I think the first step would
be to enable early printk for your platform.

See docs/misc/arm/early-printk.txt and the long ifeq chain in
xen/arch/arm/Rules.mk.

If the UART on your platform is one of the existing ones in
xen/arch/arm/arm*/debug*.inc then this is pretty easy.

If not then you just need to provide two ASM macros early_uart_ready and
early_uart_transmit which is pretty trivial for every UART I've ever
seen -- see the existing debug*.inc for examples.

Ian.

Re: Failed to launch xen on J6 evm

[Korupol, Naveen (EXT)]

Hi Ian

I am (awesome) glad to see your response.


[IC] J6 EVM?
[NK] is a TI (& Spectrum Digital) evaluation board built on OMAP 5 architecture which has 2 ARM Cortex-A15 core(s), 2 Cortex-M4 cores and SGX544 3D graphics core(s).

[IC] enable early_printk
[NK] now I have enabled early_printk, I see that processor is not in hyp mode as you correctly envisioned.

Starting kernel ...

- UART enabled -
- CPU 00000000 booting -
- Xen must be entered in NS Hyp mode -
- Boot failed -

I took my current U-Boot from:
>>>> Xen needs to be started in non-secure HYP mode. Use this U-Boot Git repository:
>>>> git clone git://github.com/jwrdegoede/u-boot-sunxi.git
And compiled it for dra7xx_evm_config.

Is there any specific U-Boot for ARM with this HYP mode already enabled correctly?
If not, I would appreciate any links to help me update my current u-boot to have this setting enabled.

Thanks
Naveen Korupol


-----Original Message-----
From: Ian Campbell [mailto:ian.campbell@citrix.com]
Sent: Monday, March 09, 2015 5:55 AM
To: Korupol, Naveen (EXT)
Cc: xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] Failed to launch xen on J6 evm

On Fri, 2015-03-06 at 20:03 +0000, Korupol, Naveen (EXT) wrote:
> I am using J6 evm.

What is one of them?

> played with couple different u-boots

Does your u-boot launch the kernel (AKA Xen in this case) in NS.HYP mode?

> If there are any probable fixes/hints for bringing up XEN on J6 evm.

Given where things are apparently hanging I think the first step would be to enable early printk for your platform.

See docs/misc/arm/early-printk.txt and the long ifeq chain in xen/arch/arm/Rules.mk.

If the UART on your platform is one of the existing ones in xen/arch/arm/arm*/debug*.inc then this is pretty easy.

If not then you just need to provide two ASM macros early_uart_ready and early_uart_transmit which is pretty trivial for every UART I've ever seen -- see the existing debug*.inc for examples.

Ian.



Please note my new email address Naveen.Korupol@ext.us.panasonic.com. The old address will be available until September 15, 2015.

Re: Failed to launch xen on J6 evm

[Ian Campbell]

On Mon, 2015-03-09 at 16:51 +0000, Korupol, Naveen (EXT) wrote:

Please don't top post and try and configure your MUA for normal ">"
based quoting. Anything else just gets too hard to follow after a little
back and forth.

> Is there any specific U-Boot for ARM with this HYP mode already enabled correctly?

It's generally pretty platform specific, rather than architecture
specific how to do this unfortunately.

> If not, I would appreciate any links to help me update my current
> u-boot to have this setting enabled.

I think you had identified a very similar board, so you might have some
luck with looking at the u-boot used on that.

In mainline u-boot support for hyp mode started appearing throughout
2014. So probably the first step would be to try and get a more recent
(e.g. mainline) u-boot onto your board.

You should ask the people who make the board for support with this
and/or look around for a community around the platform you are using.

Ian.

Re: Failed to launch xen on J6 evm

[M A Young]

On Mon, 9 Mar 2015, Korupol, Naveen (EXT) wrote:

> Hi Ian
> 
> I am (awesome) glad to see your response.
> 
> 
> [IC] J6 EVM?
> [NK] is a TI (& Spectrum Digital) evaluation board built on OMAP 5 architecture which has 2 ARM Cortex-A15 core(s), 2 Cortex-M4 cores and SGX544 3D graphics core(s).
> 
> [IC] enable early_printk
> [NK] now I have enabled early_printk, I see that processor is not in hyp mode as you correctly envisioned.
> 
> Starting kernel ...
> 
> - UART enabled -
> - CPU 00000000 booting -
> - Xen must be entered in NS Hyp mode -
> - Boot failed -
> 
> I took my current U-Boot from:
> >>>> Xen needs to be started in non-secure HYP mode. Use this U-Boot Git repository:
> >>>> git clone git://github.com/jwrdegoede/u-boot-sunxi.git
> And compiled it for dra7xx_evm_config.
> 
> Is there any specific U-Boot for ARM with this HYP mode already enabled correctly?
> If not, I would appreciate any links to help me update my current u-boot to have this setting enabled.

You can get uboot from the U-Boot website is at
http://www.denx.de/wiki/U-Boot
which might have HYP enabled for your board, but you are probably 
going to have to edit the uboot code to enable it, for example by 
comparing the settings for a board that does have HYP enabled.

	Michael Young

Re: Failed to launch xen on J6 evm

[Korupol, Naveen (EXT)]

Hi

Got some progress in loading xen hyp and then sits blank.

Here is the log:


U-Boot SPL 2015.04-rc1 (Mar 10 2015 - 13:35:08)
DRA752 ES1.1
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img


U-Boot 2015.04-rc1 (Mar 10 2015 - 13:35:08)

CPU  : DRA752 ES1.1
Board: DRA7xx
I2C:   ready
DRAM:  1.5 GiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

SCSI:  SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst
scanning bus for devices...
Found 0 device(s).
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot:  0
U-Boot# fatload mmc 0:1 ${loadaddr} boot.scr
reading boot.scr
1012 bytes read in 3 ms (329.1 KiB/s)
U-Boot#
U-Boot# source ${loadaddr}
## Executing script at 82000000
reading dra7-evm.dtb
93417 bytes read in 12 ms (7.4 MiB/s)
reading xen-uImage
656284 bytes read in 57 ms (11 MiB/s)
reading uImage
4911296 bytes read in 400 ms (11.7 MiB/s)
## Booting kernel from Legacy Image at 90000000 ...
   Image Name:   Xen.Trial.15
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    656220 Bytes = 640.8 KiB
   Load Address: 80200000
   Entry Point:  80200000
   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=17000
   Loading Device Tree to 83fe6000, 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 -
(XEN) Checking for initrd in /chosen
(XEN) RAM: 0000000080000000 - 00000000dfffffff
(XEN)
(XEN) MODULE[0]: 0000000083fe6000 - 0000000083ffd000 Device Tree
(XEN) MODULE[1]: 00000000a0000000 - 00000000a04b0000 Kernel
(XEN)  RESVD[0]: 00000000825f0000 - 0000000082607000
(XEN)  RESVD[1]: 0000000083fe6000 - 0000000083ffd000
(XEN)
(XEN) Command line: dom0_mem=128M sync_console console=dtuart dtuart=serial2 noreboot early_printk
(XEN) Placing Xen at 0x00000000dfe00000-0x00000000e0000000
(XEN) Update BOOTMOD_XEN from 0000000080200000-00000000802e7701 => 00000000dfe00000-00000000dfee7701
(XEN) Xen heap: 00000000d2000000-00000000de000000 (49152 pages)
(XEN) Dom heap: 344064 pages
(XEN) Domain heap initialised
(XEN) Looking for UART console serial2

Thanks
Naveen
Please note my new email address Naveen.Korupol@ext.us.panasonic.com. The old address will be available until September 15, 2015.

Re: Failed to launch xen on J6 evm

[Korupol, Naveen (EXT)]

Hi

Some more progress and then PANIC.. says (XEN) GICv2: Cannot find the maintenance IRQ

Here is the log:

U-Boot SPL 2015.04-rc1 (Mar 10 2015 - 13:35:08)
DRA752 ES1.1
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img


U-Boot 2015.04-rc1 (Mar 10 2015 - 13:35:08)

CPU  : DRA752 ES1.1
Board: DRA7xx
I2C:   ready
DRAM:  1.5 GiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

SCSI:  SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst
scanning bus for devices...
Found 0 device(s).
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot:  0
U-Boot# setenv dtb_addr_r 0x825f0000
U-Boot#
U-Boot# setenv xen_addr_r 0x90000000
U-Boot#
U-Boot# setenv kernel_addr_r 0xa0000000
U-Boot#
U-Boot# setenv dom0_bootargs 'console=hvc0 root=/dev/mmcblk0p2 rw rootwait fixrtc'
U-Boot#
U-Boot# setenv xen_bootargs 'dom0_mem=1024M loglvl=all guest_loglvl=all com1=115200,8n1 console=com1'
U-Boot#
U-Boot# fatload mmc 0:1 $dtb_addr_r dra7-evm.dtb
reading dra7-evm.dtb
93417 bytes read in 11 ms (8.1 MiB/s)
U-Boot#
U-Boot# fatload mmc 0:1 $xen_addr_r xen-uImage
reading xen-uImage
656284 bytes read in 58 ms (10.8 MiB/s)
U-Boot#
U-Boot# fatload mmc 0:1 $kernel_addr_r uImage
reading uImage
4911296 bytes read in 399 ms (11.7 MiB/s)
U-Boot#
U-Boot# setenv fdt_high 0x84000000
U-Boot#
U-Boot# fdt addr $dtb_addr_r
U-Boot#
U-Boot# fdt resize
U-Boot#
U-Boot# fdt set /chosen '#address-cells' <1>
U-Boot#
U-Boot# fdt set /chosen '#size-cells' <1>
U-Boot#
U-Boot# fdt set /chosen xen,xen-bootargs \"$xen_bootargs\"
U-Boot#
U-Boot# fdt resize
U-Boot#
U-Boot# fdt set /chosen xen,dom0-bootargs \"$dom0_bootargs\"
U-Boot# fdt mknode /chosen module@0
U-Boot#
U-Boot# fdt set /chosen/module@0 compatible xen,linux-zimage xen,multiboot-module
U-Boot#
U-Boot# fdt set /chosen/module@0 reg <$kernel_addr_r 0x4b0000>
U-Boot#
U-Boot# bootm $xen_addr_r - $dtb_addr_r
## Booting kernel from Legacy Image at 90000000 ...
   Image Name:   Xen.Trial.15
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    656220 Bytes = 640.8 KiB
   Load Address: 80200000
   Entry Point:  80200000
   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=17000
   Loading Device Tree to 83fe6000, 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 -
(XEN) Checking for initrd in /chosen
(XEN) RAM: 0000000080000000 - 00000000dfffffff
(XEN)
(XEN) MODULE[0]: 0000000083fe6000 - 0000000083ffd000 Device Tree
(XEN) MODULE[1]: 00000000a0000000 - 00000000a04b0000 Kernel
(XEN)  RESVD[0]: 00000000825f0000 - 0000000082607000
(XEN)  RESVD[1]: 0000000083fe6000 - 0000000083ffd000
(XEN)
(XEN) Command line: dom0_mem=1024M loglvl=all guest_loglvl=all com1=115200,8n1 console=com1
(XEN) Placing Xen at 0x00000000dfe00000-0x00000000e0000000
(XEN) Update BOOTMOD_XEN from 0000000080200000-00000000802e7701 => 00000000dfe00000-00000000dfee7701
(XEN) Xen heap: 00000000d2000000-00000000de000000 (49152 pages)
(XEN) Dom heap: 344064 pages
(XEN) Domain heap initialised
(XEN) No console
(XEN) Bad console= option 'com1'
 Xen 4.5.0
(XEN) Xen version 4.5.0 (root@) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 4.9.1-16ubuntu6) 4.9.1) debug=n Mon Mar  9 09:10:18 PDT 2015
(XEN) Latest ChangeSet:
(XEN) Processor: 412fc0f2: "ARM Limited", variant: 0x2, part 0xc0f, rev 0x2
(XEN) 32-bit Execution:
(XEN)   Processor Features: 00001131:00011011
(XEN)     Instruction Sets: AArch32 A32 Thumb Thumb-2 ThumbEE Jazelle
(XEN)     Extensions: GenericTimer Security
(XEN)   Debug Features: 02010555
(XEN)   Auxiliary Features: 00000000
(XEN)   Memory Model Features: 10201105 20000000 01240000 02102211
(XEN)  ISA Features: 02101110 13112111 21232041 11112131 10011142 00000000
(XEN) Platform: TI DRA7
(XEN) Set AuxCoreBoot1 to 00000000dfe0004c (0020004c)
(XEN) Set AuxCoreBoot0 to 0x20
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27
(XEN) Using generic timer at 6144 KHz
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) GICv2: Cannot find the maintenance IRQ
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...


Thanks
Naveen

Please note my new email address Naveen.Korupol@ext.us.panasonic.com. The old address will be available until September 15, 2015.

Re: Failed to launch xen on J6 evm

[Ian Campbell]

On Tue, 2015-03-10 at 20:52 +0000, Korupol, Naveen (EXT) wrote:
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) GICv2: Cannot find the maintenance IRQ

This suggests that your DTB does not describe the maintenance interrupt
on the interrupt controller node.

Ian.