[fedora-arm] U-Boot not working with imx6

Discussion:

Andrew Gillis

2017-05-22 23:06:46 UTC

I am using an imx6 SoM from SolidRun. We have purchased a large number of
these and mostly they work fine.

I tried to update to Fedora 25 and now a few of them won't boot. (most work
fine)

All my SoMs are all supposed to be the same but some must be different.
Both worked fine with an older version of Fedora

Is there any way to just force a boot from MMC1 with no checks?

I tried to update to the u-boot from Fedora 26 just to see if that would
help. It does not.

This is what I get with the "bad" ones

U-Boot SPL 2016.09.01 (Oct 19 2016 - 14:40:29)
Trying to boot from unknown boot device
SPL: Unsupported Boot Device!
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

The ones that boot correctly do this

U-Boot SPL 2016.09.01 (Oct 19 2016 - 14:40:29)
Trying to boot from MMC1

U-Boot 2016.09.01 (Oct 19 2016 - 14:40:29 +0000)

CPU: Freescale i.MX6DL rev1.3 996 MHz (running at 792 MHz)
CPU: Commercial temperature grade (0C to 95C) at 28C
Reset cause: POR
Board: MX6 Hummingboard
DRAM: 1 GiB
MMC: FSL_SDHC: 0
*** Warning - bad CRC, using default environment

--
Andrew Gillis
Small Green Computer
603-488-0617

Nicolas Chauvet

2017-05-23 07:06:18 UTC

Permalink

Post by Andrew Gillis
I am using an imx6 SoM from SolidRun. We have purchased a large number of
these and mostly they work fine.
I tried to update to Fedora 25 and now a few of them won't boot. (most work
fine)
All my SoMs are all supposed to be the same but some must be different. Both
worked fine with an older version of Fedora
Is there any way to just force a boot from MMC1 with no checks?
I tried to update to the u-boot from Fedora 26 just to see if that would
help. It does not.
This is what I get with the "bad" ones
U-Boot SPL 2016.09.01 (Oct 19 2016 - 14:40:29)
Trying to boot from unknown boot device
SPL: Unsupported Boot Device!
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###
The ones that boot correctly do this
U-Boot SPL 2016.09.01 (Oct 19 2016 - 14:40:29)
Trying to boot from MMC1
U-Boot 2016.09.01 (Oct 19 2016 - 14:40:29 +0000)
CPU: Freescale i.MX6DL rev1.3 996 MHz (running at 792 MHz)
CPU: Commercial temperature grade (0C to 95C) at 28C
Reset cause: POR
Board: MX6 Hummingboard
DRAM: 1 GiB
MMC: FSL_SDHC: 0
*** Warning - bad CRC, using default environment

It means that it's using the default environment because no custom env
was ever saved.
try (on the devices that do not boot)
resetenv
savenv

--
-

Nicolas (kwizart)
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email

Andrew Gillis

2017-05-23 19:26:59 UTC

Permalink

Thanks that didn't work but it turns out the new version of u-boot doesn't
work correctly if the SRC_SBMR1 value is not set. The old version figured
it out somehow.

I modified u-boot to always boot from the MMC and now it works fine. Thanks
for your help.

-Andrew

Post by Nicolas Chauvet

work

Post by Andrew Gillis
fine)
All my SoMs are all supposed to be the same but some must be different.

Both

Post by Andrew Gillis
worked fine with an older version of Fedora
Is there any way to just force a boot from MMC1 with no checks?
I tried to update to the u-boot from Fedora 26 just to see if that would
help. It does not.
This is what I get with the "bad" ones
U-Boot SPL 2016.09.01 (Oct 19 2016 - 14:40:29)
Trying to boot from unknown boot device
SPL: Unsupported Boot Device!
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###
The ones that boot correctly do this
U-Boot SPL 2016.09.01 (Oct 19 2016 - 14:40:29)
Trying to boot from MMC1
U-Boot 2016.09.01 (Oct 19 2016 - 14:40:29 +0000)
CPU: Freescale i.MX6DL rev1.3 996 MHz (running at 792 MHz)
CPU: Commercial temperature grade (0C to 95C) at 28C
Reset cause: POR
Board: MX6 Hummingboard
DRAM: 1 GiB
MMC: FSL_SDHC: 0
*** Warning - bad CRC, using default environment

It means that it's using the default environment because no custom env
was ever saved.
try (on the devices that do not boot)
resetenv
savenv
--
-
Nicolas (kwizart)

--
Andrew Gillis
Small Green Computer
603-488-0617

Nicolas Chauvet

2017-05-23 21:46:14 UTC

Permalink

So it means that you probably need to report the problem to u-boot
upstream as a normal u-boot binary should discover the right boot
device without additional tweak.
Or do you have a link to the report ?

Post by Andrew Gillis
Thanks that didn't work but it turns out the new version of u-boot doesn't
work correctly if the SRC_SBMR1 value is not set. The old version figured it
out somehow.
I modified u-boot to always boot from the MMC and now it works fine. Thanks
for your help.
-Andrew

Post by Nicolas Chauvet

It means that it's using the default environment because no custom env
was ever saved.
try (on the devices that do not boot)
resetenv
savenv
--
-
Nicolas (kwizart)

--
Andrew Gillis
Small Green Computer
603-488-0617

--
-

Nicolas (kwizart)
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists.fedoraproje