[U-Boot] Falcon boot breaks on DRA7 because of commit b9c8ccab "env_mmc.c: Allow environment to be used within SPL"

[Tom Rini <trini@konsulko.com>]

On Tue, Jan 24, 2017 at 04:35:58PM +0100, Jean-Jacques Hiblot wrote:
> 
> 
> On 24/01/2017 16:17, Tom Rini wrote:
> >On Tue, Jan 24, 2017 at 10:26:38AM +0100, Jean-Jacques Hiblot wrote:
> >
> >>Hi Tom,
> >>
> >>I'm using a TI DRA7 platform and the falcon boot from MMC is broken
> >>with v2017. The reason is that the standard "boot_os" is used to
> >>tell whether the falcon mode should be used or not, but we can't
> >>access it. The root cause is that the environment is stored in a
> >>eMMC which is dev 1 not dev 0 on those platforms.
> >>
> >>What is the purpose of commit b9c8ccab. Is it because we want to
> >>initialize only one MMC device in the SPL to reduce the boot time ?
> >Please note that b9c8ccaba77b has been in since April 2014, so this is
> >not some new behavior.
> I had noticed that it's quite old indeed. I didn't mean that it's a
> regression. I'm just puzzled by the commit. what is its purpose ?
> why is SPL not using  CONFIG_SYS_MMC_ENV_DEV ?

Because in SPL we do not have both MMC devices initialized.  We register
the one we booted from and thus it is device 0 to U-Boot in this case.
I suspect the rest of the issues stem from this quirk, or something
having broken around this quirk.  Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170124/229dd813/attachment.sig>