From: Tom Rini Date: Tue, 26 Mar 2019 12:21:57 -0400 Subject: [U-Boot] [PATCH] configs: ti: Move FIT image load address to avoid overwrite In-Reply-To: <20190326151201.487-1-afd@ti.com> References: <20190326151201.487-1-afd@ti.com> Message-ID: <20190326162157.GU18421@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 Tue, Mar 26, 2019 at 10:12:01AM -0500, Andrew F. Davis wrote: > The FIT image is loaded to 0x8700_0000 followed by extracting from that > several large images also into the 0x8x00_0000 range. Large images > can end up overwriting the FIT image as it is being extracted from. > Move the FIT load address clear out to 0x9000_0000, this will require > a board to have at least 256MB of DRAM, if less then more careful > planning will be required for that platform. > > Signed-off-by: Andrew F. Davis > --- > include/configs/ti_armv7_common.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/include/configs/ti_armv7_common.h b/include/configs/ti_armv7_common.h > index 1e2a62dd6f..828fb1b2a5 100644 > --- a/include/configs/ti_armv7_common.h > +++ b/include/configs/ti_armv7_common.h > @@ -52,7 +52,7 @@ > > #define DEFAULT_FIT_TI_ARGS \ > "boot_fit=0\0" \ > - "fit_loadaddr=0x87000000\0" \ > + "fit_loadaddr=0x90000000\0" \ > "fit_bootfile=fitImage\0" \ > "update_to_fit=setenv loadaddr ${fit_loadaddr}; setenv bootfile ${fit_bootfile}\0" \ > "loadfit=run args_mmc; bootm ${loadaddr}#${fdtfile};\0" \ What are the large images that are being extracted and can we just use them in-place instead? -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: