From mboxrd@z Thu Jan 1 00:00:00 1970 From: Drew Fustini Date: Thu, 29 Apr 2021 17:35:27 -0700 Subject: [Buildroot] [PATCH 0/4] Support for the Beagle-V platform In-Reply-To: References: <20210429074636.724046-1-thomas.petazzoni@bootlin.com> Message-ID: <20210430003527.GA132765@x1> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On Thu, Apr 29, 2021 at 02:39:16PM +0200, Erico Nunes wrote: > On Thu, Apr 29, 2021 at 9:47 AM Thomas Petazzoni > wrote: > > slight annoyance is that the bootloader > > pre-flashed on the board doesn't work as-is, just due to an incorrect > > fdt_addr_r environment variable value. So reflashing the bootloader > > with what has been built by Buildroot is necessary (but is trivial to > > do using Xmodem). > > I would like to try this but I have some questions: > Are you able to still boot the reference Fedora image after flashing > the custom bootloader? > Also, if it is just a matter of updating fdt_addr_r, could it just be > updated in the u-boot environment instead? > And finally, should that be reported as an issue in the starfive > u-boot so maybe they can release another build with that fixed? I think that is a good idea so I have opened an issue to track resolving this in future production of BeagleV Starlight boards. Thanks, Drew [1] https://github.com/starfive-tech/freelight-u-sdk/issues/18