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

Re: [Xen-devel] RT Xen on ARM - R-Car series



Andrii,

I have attempted to update the bootloader from the srec files created by the bitbake command.

I believe I have been able to update it, but I am still obtaining the same results. The serial output is shown below:

[    0.000161] NOTICE:  BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.17
[    0.005721] NOTICE:  BL2: PRR is R-Car H3 Ver2.0
[    0.010304] NOTICE:  BL2: Board is Starter Kit Rev1.0
[    0.015331] NOTICE:  BL2: Boot device is HyperFlash(80MHz)
[    0.020757] NOTICE:  BL2: LCM state is CM
[    0.024802] NOTICE:  BL2: AVS setting succeeded. DVFS_SetVID=0x53
[    0.030786] NOTICE:  BL2: DDR3200(rev.0.28)NOTICE:  [COLD_BOOT]NOTICE:  ..0
[    0.059996] NOTICE:  BL2: DRAM Split is 4ch
[    0.063882] NOTICE:  BL2: QoS is default setting(rev.0.18)
[    0.069381] NOTICE:  BL2: Lossy Decomp areas
[    0.073559] NOTICE:       Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570
[    0.080643] NOTICE:       Entry 1: DCMPAREACRAx:0x40000000 DCMPAREACRBx:0x0
[    0.087555] NOTICE:       Entry 2: DCMPAREACRAx:0x20000000 DCMPAREACRBx:0x0
[    0.094470] NOTICE:  BL2: v1.3(release):b15fefa
[    0.098960] NOTICE:  BL2: Built : 12:21:32, Dec 28 2018
[    0.104147] NOTICE:  BL2: Normal boot
[    0.107788] NOTICE:  BL2: dst=0xe6322210 src="" len=512(0x200)
[    0.114335] NOTICE:  BL2: dst=0x43f00000 src="" len=6144(0x1800)
[    0.120797] NOTICE:  BL2: dst=0x44000000 src="" len=65536(0x10000)
[    0.128022] NOTICE:  BL2: dst=0x44100000 src="" len=524288(0x80000)
[    0.138503] NOTICE:  BL2: dst=0x50000000 src="" len=1048576(0x100000)


U-Boot 2015.04 (Dec 28 2018 - 02:46:24)

CPU: Renesas Electronics R8A7795 rev 2.0
Board: H3ULCB
I2C:   ready
DRAM:  3.9 GiB
MMC:   sh-sdhi: 0, sh-sdhi: 1
In:    serial
Out:   serial
Err:   serial
Net:   ravb
Hit any key to stop autoboot:  0
=> setenv bootargs
=> setenv serverip 192.168.1.100
=> tftp 0x48080000 xen-h3ulcb.uImage
ravb Waiting for PHY auto negotiation to complete......... TIMEOUT !
Half
Using ravb device
TFTP from server 192.168.1.100; our IP address is 192.168.1.40
Filename 'xen-h3ulcb.uImage'.
Load address: 0x48080000
Loading: *
ARP Retry count exceeded; starting again
ravb:0 is connected to ravb.  Reconnecting to ravb
ravb Waiting for PHY auto negotiation to complete......... TIMEOUT !
Half

ARP Retry count exceeded; starting again
ravb:0 is connected to ravb.  Reconnecting to ravb
ravb Waiting for PHY auto negotiation to complete... done
ravb: 1000Base/Full
Using ravb device
TFTP from server 192.168.1.100; our IP address is 192.168.1.40
Filename 'xen-h3ulcb.uImage'.
Load address: 0x48080000
Loading: ###########################################################
         25.4 MiB/s
done
Bytes transferred = 852368 (d0190 hex)
=> tftp 0x48000000 Image-r8a7795-h3ulcb-xen-local.dtb
ravb:0 is connected to ravb.  Reconnecting to ravb
ravb Waiting for PHY auto negotiation to complete..... done
ravb: 1000Base/Full
Using ravb device
TFTP from server 192.168.1.100; our IP address is 192.168.1.40
Filename 'Image-r8a7795-h3ulcb-xen-local.dtb'.
Load address: 0x48000000
Loading: #####
         11.7 KiB/s
done
Bytes transferred = 63778 (f922 hex)
=> tftp 0x7a000000 h3ulcb-image
ravb:0 is connected to ravb.  Reconnecting to ravb
ravb Waiting for PHY auto negotiation to complete... done
ravb: 1000Base/Full
Using ravb device
TFTP from server 192.168.1.100; our IP address is 192.168.1.40
Filename 'h3ulcb-image'.
Load address: 0x7a000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ########################################
         2.1 MiB/s
done
Bytes transferred = 15843840 (f1c200 hex)
=> bootm 0x48080000 - 0x48000000
## Booting kernel from Legacy Image at 48080000 ...
   Image Name:   XEN
   Image Type:   AArch64 Linux Kernel Image (uncompressed)
   Data Size:    852304 Bytes = 832.3 KiB
   Load Address: 78080000
   Entry Point:  78080000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 48000000
   Booting using the fdt blob at 0x48000000
   Loading Kernel Image ... OK
   Using Device Tree in place at 0000000048000000, end 0000000048012921

Starting kernel ...

</end output>

I have noticed that the uboot date has not changed from 2015.04 although the build date is from the last time I ran a bitbake command.

I do not know what version of uboot should be used without breaking the current compiling versions.

Are there any other modifications that I can attempt?

Thank you very much for your time and patience.

Best regards,

Jairo



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

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