[U-Boot] [PATCH] Trimslice config: update for Trimslice so SPI flash works

[Tom Warren]

Stephen,

> -----Original Message-----
> From: Stephen Warren [mailto:swarren at wwwdotorg.org]
> Sent: Thursday, September 01, 2016 3:47 PM
> To: Tom Warren <TWarren at nvidia.com>; Steve Arnold
> <nerdboy422 at gmail.com>
> Cc: Stephen Arnold <sarnold at vctlabs.com>; u-boot at lists.denx.de; Stephen L
> Arnold <nerdboy at gentoo.org>; Simon Glass <sjg at chromium.org>
> Subject: Re: [U-Boot] [PATCH] Trimslice config: update for Trimslice so SPI flash
> works
> 
> On 09/01/2016 04:36 PM, Tom Warren wrote:
> > Steve/Stephen,
> >
> >> -----Original Message-----
> >> From: Stephen Warren [mailto:swarren at wwwdotorg.org]
> >> Sent: Tuesday, July 26, 2016 2:57 PM
> >> To: Steve Arnold <nerdboy422 at gmail.com>
> >> Cc: Stephen Arnold <sarnold at vctlabs.com>; u-boot at lists.denx.de;
> >> Stephen L Arnold <nerdboy at gentoo.org>; Tom Warren
> >> <TWarren at nvidia.com>; Simon Glass <sjg at chromium.org>
> >> Subject: Re: [U-Boot] [PATCH] Trimslice config: update for Trimslice
> >> so SPI flash works
> >>
> >> On 07/26/2016 03:45 PM, Steve Arnold wrote:
> >>> So is there a fix to be had by maybe shifting both
> >>> CONFIG_SPL_TEXT_BASE and CONFIG_SYS_TEXT_BASE a little bit?
> >>>
> >>> Steve
> >>>
> >>> On Tue, Jul 26, 2016 at 2:14 PM, Stephen Warren
> >>> <swarren at wwwdotorg.org <mailto:swarren at wwwdotorg.org>> wrote:
> >>>
> >>>     On 07/26/2016 12:49 PM, Steve Arnold wrote:
> >>>
> >>>         I did mention it was black and showed nothing on serial console
> >>>         with the
> >>>         default values, ie, building as-is doesn't even show u-boot
> >>>         trying to
> >>>         load (after flashing it to the SPI flash the last thing you see is
> >>>         "Resetting...").  Power it back up and nothing happens, no
> >>>         u-boot, nada.
> >>>
> >>>
> >>>     It looks like there's some issue if the total flash image size is
> >>>     over 512KiB. (The physical flash chip is 1MiB). I'm investigating
> >>>     whether this is expected and what to do about it. The change to
> >>>     CONFIG_SYS_TEXT_BASE accidentally solves this, since it currently
> >>>     happens to shrink the image size enough not to hit this apparent limit.
> >>
> >> Changing CONFIG_SPL_TEXT_BASE won't have any effect on this; size
> >> matters not location.
> >>
> >> As I mentioned, changing CONFIG_SYS_TEXT_BASE currently avoids the
> >> issue, but hopefully we can find something better.
> >
> > Was this ever resolved? If so please post an updated patch. I' like to get this
> out of my Patchwork queue.
> 
> It was superseded by "ARM: tegra: fix trimslice environment location", which is
> already applied.
Ah, missed that. Thanks!


-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------