[meta-xilinx] Address location for binaries...
Alan DuBoff
aland at softorchestra.com
Tue Feb 18 22:23:49 PST 2014
> There's a 0x40 byte u-boot header preceeding the kernel image. Loading it at
> 0x79C0 will thus place the kernel entry point at 0x8000.
Below is what I'm getting when I try 0x79c0...same thing I get when I use 0x8000
--
Cheers,
Alan
Hit any key to stop autoboot: 0
Copying Linux from SD to RAM...
Device: SDHCI
Manufacturer ID: 28
OEM: 4245
Name:
Tran Speed: 50000000
Rd Block Len: 512
SD version 2.0
High Capacity: Yes
Capacity: 14.9 GiB
Bus Width: 4-bit
reading uImage
2858912 bytes read
reading devicetree.dtb
5817 bytes read
reading uramdisk.image.gz
3694172 bytes read
## Booting kernel from Legacy Image at 03000000 ...
Image Name:
Image Type: ARM Linux Kernel Image (gzip compressed)
Data Size: 2858848 Bytes = 2.7 MiB
Load Address: 000079c0
Entry Point: 000079c0
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02000000 ...
Image Name:
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 3694108 Bytes = 3.5 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 02a00000
Booting using the fdt blob at 0x02a00000
Uncompressing Kernel Image ... Error: Bad gzipped data
GUNZIP: uncompress, out-of-mem or overwrite error - must RESET board to recover
resetting ...
More information about the meta-xilinx
mailing list