[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Dom0 kernel for Xen4.6 on R-Car H2 (LAGER)



Hello Ian Campbell, Iurii Konavalenko, Oleksandr Tyshchenko,
Hello xen-devel!

Thanks for the earlier help.  I managed to get further, but still cannot see 
Dom0 booting.
There is also an error in configuring the console.
Here comes my boot-log, including setting up the U-Boot configuration.

Thanks again!

Max Ferger

----- 8< -----

LAGER SPI_LOADER V0.28 2014.09.29
DEVICE S25FL512


U-Boot 2014.10-00441-gf7ca1f7-dirty (Oct 19 2015 - 12:32:17)

CPU: Renesas Electronics R8A7790 rev 2.0
Board: Lager
I2C:   ready
DRAM:  2 GiB
SF: Detected S25FL512S_256K with page size 512 Bytes, erase size 256 KiB, total 
64 MiB
In:    serial
Out:   serial
Err:   serial
Net:   Please set MAC address
sh_eth
Error: sh_eth address not set.

=> env default -a -f
## Resetting to default environment
=> env set baudrate 38400
=> env set stderr serial
=> env set stdin serial
=> env set stdout serial
=>
=> env set ethaddr 2e:09:0a:00:6d:c9
=> env set ipaddr 192.168.0.5
=> env set serverip 192.168.0.15
=> env set gatewayip 192.168.0.15
=> env set netmask 255.255.255.0
=> env set hostname lager
=> env set dnsip
=> env set dnsip2
=> env set ip 
${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:eth0::${dnsip}:${dnsip2}
=>
=> env set load_xen  'tftp 0x70007fc0 xen-uImage;            env set xen_addr 
${fileaddr}; env set xen_size ${filesize}'
=> env set load_dtb  'tftp 0x70f00000 r8a7790-lager-xen.dtb; env set dtb_addr 
${fileaddr}; env set dtb_size ${filesize}'
=> env set load_dom0 'tftp 0x72000000 zImage-uImage;         env set dom0_addr 
${fileaddr}; env set dom0_size ${filesize}'
=> env set load_xsm  'tftp 0x74000000 xenpolicy;             env set xsm_addr 
${fileaddr}; env set xsm_size ${filesize}'
=>
=>
=> env set fdt_addr_resize    'fdt addr ${dtb_addr}; fdt resize'
=> env set dtb 'run load_dtb fdt_addr_resize'
=>
=> # env set fdt_dom0_mknode 'fdt mknode /chosen/modules module@0x${dom0_addr} 
|| help'
Unknown command '#' - try 'help'
=> # env set fdt_dom0_compat 'fdt set /chosen/modules/module@0x${dom0_addr} 
compatible xen,linux-zimage xen,multiboot-module'
Unknown command '#' - try 'help'
=> env set fdt_dom0_reg    'fdt set /chosen/modules/module@0x${dom0_addr} reg 
<0x${dom0_addr} 0x${dom0_size}>'
=> env set dom0 'run load_dom0 fdt_dom0_reg'
=>
=> # env set fdt_xsm_mknode 'fdt mknode /chosen/modules module@0x${xsm_addr} || 
help'
Unknown command '#' - try 'help'
=> # env set fdt_xsm_compat 'fdt set /chosen/modules/module@0x${xsm_addr} 
compatible xen,linux-zimage xen,multiboot-module'
Unknown command '#' - try 'help'
=> env set fdt_xsm_reg    'fdt set /chosen/modules/module@0x${xsm_addr} reg 
<0x${xsm_addr} 0x${xsm_size}>'
=> env set xsm 'run load_xsm fdt_xsm_reg'
=>
=> env set fdt_print 'fdt print /chosen'
=>
=> env set xen 'run load_xen; bootm ${xen_addr} - ${dtb_addr}'
=>
=> env set bootcmd  run dtb dom0 xsm fdt_print xen
=> env print
baudrate=38400
bootcmd=run dtb dom0 xsm fdt_print xen
bootdelay=3
dom0=run load_dom0 fdt_dom0_reg
dtb=run load_dtb fdt_addr_resize
ethaddr=2e:09:0a:00:6d:c9
fdt_addr_resize=fdt addr ${dtb_addr}; fdt resize
fdt_dom0_reg=fdt set /chosen/modules/module@0x${dom0_addr} reg <0x${dom0_addr} 
0x${dom0_size}>
fdt_print=fdt print /chosen
fdt_xsm_reg=fdt set /chosen/modules/module@0x${xsm_addr} reg <0x${xsm_addr} 
0x${xsm_size}>
gatewayip=192.168.0.15
hostname=lager
ip=192.168.0.5:192.168.0.15:192.168.0.15:255.255.255.0:lager:eth0:::
ipaddr=192.168.0.5
load_dom0=tftp 0x72000000 zImage-uImage; env set dom0_addr ${fileaddr}; env set 
dom0_size ${filesize}
load_dtb=tftp 0x70f00000 r8a7790-lager-xen.dtb; env set dtb_addr ${fileaddr}; 
env set dtb_size ${filesize}
load_xen=tftp 0x70007fc0 xen-uImage; env set xen_addr ${fileaddr}; env set 
xen_size ${filesize}
load_xsm=tftp 0x74000000 xenpolicy; env set xsm_addr ${fileaddr}; env set 
xsm_size ${filesize}
netmask=255.255.255.0
serverip=192.168.0.15
stderr=serial
stdin=serial
stdout=serial
xen=run load_xen; bootm ${xen_addr} - ${dtb_addr}
xsm=run load_xsm fdt_xsm_reg

Environment size: 1161/262140 bytes
=> run bootcmd
sh_eth Waiting for PHY auto negotiation to complete... done
sh_eth: 100Base/Half
Using sh_eth device
TFTP from server 192.168.0.15; our IP address is 192.168.0.5
Filename 'r8a7790-lager-xen.dtb'.
Load address: 0x70f00000
Loading: #########
         378.9 KiB/s
done
Bytes transferred = 42399 (a59f hex)
sh_eth:1 is connected to sh_eth.  Reconnecting to sh_eth
sh_eth Waiting for PHY auto negotiation to complete... done
sh_eth: 100Base/Half
Using sh_eth device
TFTP from server 192.168.0.15; our IP address is 192.168.0.5
Filename 'zImage-uImage'.
Load address: 0x72000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ############################
         702.1 KiB/s
done
Bytes transferred = 3133784 (2fd158 hex)
sh_eth:1 is connected to sh_eth.  Reconnecting to sh_eth
sh_eth Waiting for PHY auto negotiation to complete... done
sh_eth: 100Base/Half
Using sh_eth device
TFTP from server 192.168.0.15; our IP address is 192.168.0.5
Filename 'xenpolicy'.
Load address: 0x74000000
Loading: ##
         132.8 KiB/s
done
Bytes transferred = 9561 (2559 hex)
chosen {
        bootargs = "ignore_loglevel rw root=/dev/nfs ip=dhcp";
        stdout-path = "/serial@e6c40000";
        xen,xen-bootargs = "console=dtuart dtuart=/soc/serial@e6c50000 
dom0_mem=1G";
        xen,dom0-bootargs = "console=hvc0 vmalloc=384M 
video=HDMI-A-1:1920x1080-32@60 
ip=192.168.0.5:192.168.0.15:192.168.0.15:255.255.255.0:lager:eth0::: 
root=/dev/nfs rw nfsroot=192.168.0.15:/nfsroot rootwait clk_ignore_unused";
        modules {
                #address-cells = <0x00000001>;
                #size-cells = <0x00000001>;
                module@0x72000000 {
                        reg = <0x72000000 0x002fd158>;
                        compatible = "multiboot,kernel", "multiboot,module";
                };
                module@0x74000000 {
                        reg = <0x74000000 0x00002559>;
                        compatible = "xen,xsm-policy", "multiboot,module";
                };
        };
};
sh_eth:1 is connected to sh_eth.  Reconnecting to sh_eth
sh_eth Waiting for PHY auto negotiation to complete... done
sh_eth: 100Base/Half
Using sh_eth device
TFTP from server 192.168.0.15; our IP address is 192.168.0.5
Filename 'xen-uImage'.
Load address: 0x70007fc0
Loading: #################################################################
         #################################################################
         #####################################
         650.4 KiB/s
done
Bytes transferred = 852948 (d03d4 hex)
## Booting kernel from Legacy Image at 70007fc0 ...
   Image Name:   XEN4.6-LAGER
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    852884 Bytes = 832.9 KiB
   Load Address: 90000000
   Entry Point:  90000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 70f00000
   Booting using the fdt blob at 0x70f00000
   Loading Kernel Image ... OK
   reserving fdt memory region: addr=70f00000 size=b000
   Loading Device Tree to 407f2000, end 407fffff ... 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: 0000000040000000 - 000000007fffffff
(XEN) RAM: 0000000140000000 - 00000001ffffffff
(XEN)
(XEN) MODULE[0]: 00000000407f2000 - 00000000407fd000 Device Tree
(XEN) MODULE[1]: 0000000072000000 - 00000000722fd158 Kernel
(XEN) MODULE[2]: 0000000074000000 - 0000000074002559 XSM
(XEN)  RESVD[0]: 0000000070f00000 - 0000000070f0b000
(XEN)  RESVD[1]: 000000007ff9a000 - 000000007ff9a120
(XEN)  RESVD[2]: 00000000407f2000 - 00000000407fd000
(XEN)
(XEN) Command line: console=dtuart dtuart=/soc/serial@e6c50000 dom0_mem=1G
(XEN) Placing Xen at 0x000000007fc00000-0x000000007fe00000
(XEN) Update BOOTMOD_XEN from 0000000090000000-000000009011b701 => 
000000007fc00000-000000007fd1b701
(XEN) Xen heap: 00000001f8000000-0000000200000000 (32768 pages)
(XEN) Dom heap: 1015808 pages
(XEN) Domain heap initialised
(XEN) Platform: Renesas R-Car Gen2
(XEN) Looking for dtuart at "/soc/serial@e6c50000", options ""
(XEN) Unable to find device "/soc/serial@e6c50000"
(XEN) Bad console= option 'dtuart'
 __  __            _  _    __    ___
 \ \/ /___ _ __   | || |  / /_  / _ \
  \  // _ \ '_ \  | || |_| '_ \| | | |
  /  \  __/ | | | |__   _| (_) | |_| |
 /_/\_\___|_| |_|    |_|(_)___(_)___/

(XEN) Xen version 4.6.0 (aen@) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 
4.8.2-16ubuntu4) 4.8.2) debug=y Thu Oct 15 15:17:47 CEST 2015
(XEN) Latest ChangeSet: Mon Oct 5 15:33:39 2015 +0100 git:b24ad7b
(XEN) Processor: 413fc0f2: "ARM Limited", variant: 0x3, 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 40000000 01240000 02102211
(XEN)  ISA Features: 02101110 13112111 21232041 11112131 10011142 00000000
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 10000 KHz
(XEN) GICv2 initialization:
(XEN)         gic_dist_addr=00000000f1001000
(XEN)         gic_cpu_addr=00000000f1002000
(XEN)         gic_hyp_addr=00000000f1004000
(XEN)         gic_vcpu_addr=00000000f1006000
(XEN)         gic_maintenance_irq=25
(XEN) GICv2: 416 lines, 8 cpus, secure (IID 0200043b).
(XEN) XSM Framework v1.0.0 initialized
(XEN) xsm: Policy len = 0x0000000000002559 start at 0x0000000074000000
(XEN) Flask: 64 avtab hash slots, 236 rules.
(XEN) Flask: 64 avtab hash slots, 236 rules.
(XEN) Flask:  3 users, 3 roles, 36 types, 2 bools
(XEN) Flask:  12 classes, 236 rules
(XEN) Flask:  Starting in permissive mode.
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Allocated console ring of 64 KiB.
(XEN) VFP implementer 0x41 architecture 4 part 0x30 variant 0xf rev 0x0
(XEN) Bringing up CPU1
(XEN) CPU1 never came online
(XEN) Failed to bring up CPU 1 (error -5)
(XEN) Bringing up CPU2
(XEN) CPU2 never came online
(XEN) Failed to bring up CPU 2 (error -5)
(XEN) Bringing up CPU3
(XEN) CPU3 never came online
(XEN) Failed to bring up CPU 3 (error -5)
(XEN) Bringing up CPU4
(XEN) CPU4 never came online
(XEN) Failed to bring up CPU 4 (error -5)
(XEN) Bringing up CPU5
(XEN) CPU5 never came online
(XEN) Failed to bring up CPU 5 (error -5)
(XEN) Bringing up CPU6
(XEN) CPU6 never came online
(XEN) Failed to bring up CPU 6 (error -5)
(XEN) Bringing up CPU7
(XEN) CPU7 never came online
(XEN) Failed to bring up CPU 7 (error -5)
(XEN) Brought up 1 CPUs
(XEN) P2M: 40-bit IPA
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80003558
(XEN) I/O virtualisation disabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading kernel from boot module @ 0000000072000000
(XEN) Allocating 1:1 mappings totalling 1024MB for dom0:
(XEN) BANK[0] 0x00000048000000-0x00000070000000 (640MB)
(XEN) BANK[1] 0x000001d8000000-0x000001f0000000 (384MB)
(XEN) Grant table range: 0x0000007fc00000-0x0000007fc72000
(XEN) DT: no ranges; cannot enumerate
(XEN) Device tree generation failed (-22).
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Could not set up DOM0 guest OS
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
----- 8< -----


Mit freundlichen GrÃÃen / Kind regards

Leopold Kostal GmbH & Co. KG
Automobil Elektrik / Automotive Electrical Systems 

Max Ferger 
AEN5 Vorentwicklung Produktinnovationen
Advance Development Innovative Products

Hauert 16, 44227 Dortmund
Deutschland / Germany
Telefon: +49 231 7588 965
E-Mail: m.ferger@xxxxxxxxxx

Internet: http://www.kostal.com

-----Original Message-----
From: Ian Campbell [mailto:ian.campbell@xxxxxxxxxx]
Sent: Donnerstag, 15. Oktober 2015 16:28
To: Ferger, Max <M.Ferger@xxxxxxxxxx>; xen-devel@xxxxxxxxxxxxx
Cc: Iurii Konovalenko <iurii.konovalenko@xxxxxxxxxxxxxxx>; Oleksandr Tyshchenko 
<oleksandr.tyshchenko@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Dom0 kernel for Xen4.6 on R-Car H2 (LAGER)

On Thu, 2015-10-15 at 14:17 +0000, Ferger, Max wrote:
> 
> I just managed to get Xen 4.6.0 on my R-Car H2 LAGER board to show up 
> boot messages, as appended.
> But it refuses my intended Dom0 kernel â some Yocto/Poky built with 
> meta -renesas configuration.
>  
> Is there a known-good Dom0 kernel for this board?
> Hopefully one that I may re-create with something like bitbake?
> What about an automotive solution?
>  
> Thank you very much in advance!
>  
> Max Ferger
[...]
> (XEN) RAM: 0000000040000000 - 000000007fffffff
> (XEN) RAM: 0000000140000000 - 00000001ffffffff
> (XEN)
> (XEN) MODULE[0]: 00000000407f3000 - 00000000407fd000 Device Tree
> (XEN)  RESVD[0]: 0000000070f00000 - 0000000070f0a000
> (XEN)  RESVD[1]: 000000007ff9a000 - 000000007ff9a120
> (XEN)  RESVD[2]: 00000000407f3000 - 00000000407fd000 [...]
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Missing kernel boot module?

You don't appear to have passed a dom0 kernel to Xen. e.g. it is not listed as 
a MODULE[N].

See
http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions#Booting_Xen
 which describes how to setup the DTB to reference the kernel boot module etc.

It would also be useful if you would post your complete boot script.

Also, I'm CCing the original contributors of the Lager support, since we don't 
have much knowledge of this specific platform or where to get kernels from etc.

Ian.

> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Could not set up DOM0 guest OS
> (XEN) ****************************************
> (XEN)
> (XEN) Reboot in five seconds...
> [Nothing happens any more]
> ----- 8< -----
>  [...]



Leopold KOSTAL GmbH & Co. KG - Sitz LÃdenscheid, Registergericht Iserlohn HRA 
2854, phG Kostal Verwaltungsgesellschaft mbH, Registergericht Iserlohn HRB 4061 
- USt-Id-Nr./Vat No.: DE 125800885
Post- und Werksanschrift: An der Bellmerei 10, D-58513 LÃdenscheid * Telefon: 
+49 2351 16-0 * Telefax: +49 2351 16-2400 Bellmerei
GeschÃftsfÃhrung: Dipl.-Oec. Andreas Kostal (Vorsitzender), Dipl.-Kfm. Helmut 
Kostal, Dipl.-Ing. Marwin Kinzl, Dr.-Ing. Ludger Laufenberg, Dipl.-Kfm. Ulrich 
Zimmermann

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.