From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Mon, 6 May 2019 09:28:34 -0400 Subject: [U-Boot] [ARMv8] kernel entry point In-Reply-To: References: Message-ID: <20190506132834.GR31207@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Mon, May 06, 2019 at 01:06:45PM +0000, Pankaj Bansal wrote: > Hi Tom et. Al, > > I am facing an issue while booting linux on our ARMv8 based platform. > In our platform DDR address starts from 0x80000000. > If I make the linux kernel entry point 0x80080000 in mkimage, then linux boots fine. > BUT, if I make the linux image entry point as 0x81000000 in mkimage, the kernel doesn't boot. > > => bootm 0xa0000000 - 0xa1000000 > ## Current stack ends at 0xfbb24400 ## Booting kernel from Legacy Image at a0000000 ... > Image Name: linux > Image Type: AArch64 Linux Kernel Image (gzip compressed) > Data Size: 9110442 Bytes = 8.7 MiB > Load Address: 81000000 > Entry Point: 81000000 > Verifying Checksum ... OK > ## Flattened Device Tree blob at a1000000 > Booting using the fdt blob at 0xa1000000 > Uncompressing Kernel Image ... OK > using: FDT > reserving fdt memory region: addr=80000000 size=10000 > Loading Device Tree to 000000009fff6000, end 000000009ffff2f8 ... OK > ## Transferring control to Linux (at address 81000000)... > > Starting kernel ... > > I get no kernel logs after this. I am failing to understand why. > Can you please help me in debugging this issue? Why are you using a legacy image on AArch64 at all? You should be using either the kernel Image (and booti) or a FIT image. -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: