Hi,
I'm working with an P2041RDB, I can boot from NOR with hypervisor without pb.
Now I try to boot from RAM.
- start U-boot
- tftp HV , HV FDT, board FDT, kernel , rootfs in RAM
The Hypervisor start, get FDT but the kernel don't start ...
I check in RAM guest memory at @0 and @0x01300000 => It's fill with 0x00 => no data
In HV FDT tree ,I have :
fdt list /part1 guest-image
guest-image = <0x00000000 0x22a72866 0x00000000 0x00000000 0x00000000 0x00700000>
fdt list /part1 linux-rootfs
linux-rootfs = <0x00000000 0x2006a066 0x00000000 0x01300000 0x00000000 0x05d00000>
The @ of the kernel /rootfs are good (0x22a72866 0x2006a066), I have check with imi cmd in U-boot
U-boot/kernel etc are from SDK 1.5
It's seems like the address is'nt pass correctly to the hypervisor, but in the log It the good one.
If somebody have an idea, thanks
Sophie
LOG :
bootm $hv_addr - $boardfdt_addr (bootm 20003a66 - 22a6a266)
WARNING: adjusting available memory to 30000000
## Booting kernel from Legacy Image at 20003a66 ...
Image Name:
Image Type: PowerPC Linux Kernel Image (uncompressed)
Data Size: 418584 Bytes = 408.8 KiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 22a6a266
Booting using the fdt blob at 0x22a6a266
Loading Kernel Image ... OK
OK
Loading Device Tree to 03fe4000, end 03fff37f ... OK
ERROR: could not find compatible node fsl-usb2-mph or fsl-usb2-dr: FDT_ERR_NOTFOUND.
[0] =======================================
[0] Freescale Hypervisor 3.0-001
[0] Hypervisor command line: config-addr=0x20000666 console=ttyS0,115200
[0] malloc_init: using 15799 KiB at 0xf1092480 - 0xf1ffffff
[0] dt_read_aliases: Alias pci0 points to non-existent /pcie@ffe200000
[0] dt_read_aliases: Alias pci2 points to non-existent /pcie@ffe202000
[0] loading binary image from 0x2006a066 to 0x1300000
[0] loading binary image from 0x22a72866 to 0
[0] branching to guest p1-linux, 1 cpus
[0] starting primary guest in supervisor mode
HV>
Solved! Go to Solution.
In the dts file the parameter zero-pma :"If present causes the PMA to be initialized to zeros during the cold boot of a system."
You have to remove it if you want to boot Hypervisor with image in RAM.
Hi,
Does anybody know if the Hypervisor clear the RAM before loading uImage ?
sophie
In the dts file the parameter zero-pma :"If present causes the PMA to be initialized to zeros during the cold boot of a system."
You have to remove it if you want to boot Hypervisor with image in RAM.
Hi Sophie
I am facing issue ,booting the Hypervisor from RAM.
Would you please let me know the exact RAM addresses you used while tftp HV , HV FDT, board FDT, kernel , rootfs in RAM?
Did you configure any specific boot args at U-boot?
Also,did you use same kernel/rootfs image for guest and host?
Thanks
Amit.