From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Thu, 29 Apr 2021 16:26:31 +0200 Subject: [Buildroot] [PATCH 0/4] Support for the Beagle-V platform In-Reply-To: References: <20210429074636.724046-1-thomas.petazzoni@bootlin.com> <20210429150143.276e4aec@windsurf> <20210429154834.5b70c1a1@windsurf> Message-ID: <20210429162631.22bb7084@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Thu, 29 Apr 2021 15:52:14 +0200 Erico Nunes wrote: > > > Ok, thanks, I will give it a try anyway. > > > I noticed that the manual build instructions in > > > https://wiki.seeedstudio.com/BeagleV-Make-File-System-Compile-uboot-Kernal/#compile-u-boot > > > suggest a CONFIG_SYS_TEXT_BASE=0x80020000 change and as far as I see > > > this is not in the build here, so maybe that could be related too. > > > > The kernel is relocated to 80020000 by U-Boot before booting, in the > > configuration I'm providing. See the boot log in the cover letter: > > > > """ > > Moving Image from 0x84000000 to 0x80200000, end=80f1b000 > > """ > > This is 0x80200000, not 0x80020000. Ah, you're right (of course). The U-Boot configuration I'm using from the U-Boot defconfig provided by Starfive indeed has CONFIG_SYS_TEXT_BASE=0x80200000 and not the 0x80020000 you're mentioning. I'll give it a try. But I just checked, and the image that was already flashed on my Beagle-V was using 0x80200000 to load the kernel. Best regards, Thomas -- Thomas Petazzoni, co-owner and CEO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com