u-boot 2014.10 GA on it's way to F-21

[Peter Robinson]

Hi All,

Just a heads up that the u-boot 2014.10 GA is on it's way to Fedora 21.

https://admin.fedoraproject.org/updates/uboot-tools-2014.10-1.fc21

This release contains numerous fixes and improvements over the
currently shipping release including, but by no means limited to:
* Upstream generic distro support (huge thanks to Dennis Gilmore and
Steven Warren for their tireless work to get this upstream
* AllWinner suppport for A10*/A13/A20 devices (huge thanks to Hans for
this tireless work on this)
* Numerous other improvements too long to name.

New devices that we now enable in this release, in no particular order, include:

AllWinner:
A10-OLinuXino-Lime
A10s-OLinuXino-M
A13-OLinuXino
A13-OLinuXinoM
A20-OLinuXino_MICRO
Bananapi
Cubieboard
Cubieboard2
Cubietruck
Mele_A1000
Mele_A1000G
Mini-X
Mini-X-1Gb

Tegra:
jetson-tk1

i.MX6
cm_fx6 (Utilite)
riotboard

It's not yet in nightly builds but I'm going to request it for the
next Beta TC compose.

Known issues:
* Panda is not yet ported to generic distro support

Please test and provide feedback.

Peter

[Adam Goode]

Hopefully I did something wrong, but it's not working at all for me on
the beaglebone black:

Here is what I get when I try to boot from eMMC:

U-Boot SPL 2014.10-gc4b8756-dirty (Oct 15 2014 - 08:57:04)
omap_hsmmc_send_cmd: timedout waiting on cmd inhibit to clear
spl: mmc init failed: err - -19
### ERROR ### Please RESET the board ###



Here is what I get when I make a new SD card from the latest minimal image:


U-Boot 2014.10-gc4b8756-dirty (Oct 15 2014 - 08:57:04)

       Watchdog enabled
I2C:   ready
DRAM:  512 MiB
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Error - No Valid Environment Area found
*** Warning - bad CRC, using default environment

Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:2...
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Card did not respond to voltage select!
Booting from nand ...

no devices available

no devices available
Bad Linux ARM zImage magic!




When I am in the uboot command processor, I cannot select the internal
eMMC at all:

U-Boot# mmc dev 1
Card did not respond to voltage select!



Previously, I was booting with no problems from either eMMC or SD with F21.



Thanks,

Adam


On Wed, Oct 15, 2014 at 6:34 AM, Peter Robinson <pbrobinson(a)gmail.com&gt; wrote:
>  Hi All,
>
>  Just a heads up that the u-boot 2014.10 GA is on it's way to Fedora 21.
>
>  https://admin.fedoraproject.org/updates/uboot-tools-2014.10-1.fc21
>
>  This release contains numerous fixes and improvements over the
>  currently shipping release including, but by no means limited to:
>  * Upstream generic distro support (huge thanks to Dennis Gilmore and
>  Steven Warren for their tireless work to get this upstream
>  * AllWinner suppport for A10*/A13/A20 devices (huge thanks to Hans for
>  this tireless work on this)
>  * Numerous other improvements too long to name.
>
>  New devices that we now enable in this release, in no particular order, include:
>
>  AllWinner:
>  A10-OLinuXino-Lime
>  A10s-OLinuXino-M
>  A13-OLinuXino
>  A13-OLinuXinoM
>  A20-OLinuXino_MICRO
>  Bananapi
>  Cubieboard
>  Cubieboard2
>  Cubietruck
>  Mele_A1000
>  Mele_A1000G
>  Mini-X
>  Mini-X-1Gb
>
>  Tegra:
>  jetson-tk1
>
>  i.MX6
>  cm_fx6 (Utilite)
>  riotboard
>
>  It's not yet in nightly builds but I'm going to request it for the
>  next Beta TC compose.
>
>  Known issues:
>  * Panda is not yet ported to generic distro support
>
>  Please test and provide feedback.
>
>  Peter
>  _______________________________________________
>  arm mailing list
>  arm(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/arm

[Peter Robinson]

A minor bug and is fixed in uboot-tools-2014.10-3.fc21

Peter

On Sat, Oct 18, 2014 at 9:04 PM, Adam Goode <adam(a)spicenitz.org&gt; wrote:
>  Hopefully I did something wrong, but it's not working at all for
> me on
>  the beaglebone black:
>
>  Here is what I get when I try to boot from eMMC:
>
>  U-Boot SPL 2014.10-gc4b8756-dirty (Oct 15 2014 - 08:57:04)
>  omap_hsmmc_send_cmd: timedout waiting on cmd inhibit to clear
>  spl: mmc init failed: err - -19
>  ### ERROR ### Please RESET the board ###
>
>
>
>  Here is what I get when I make a new SD card from the latest minimal image:
>
>
>  U-Boot 2014.10-gc4b8756-dirty (Oct 15 2014 - 08:57:04)
>
>         Watchdog enabled
>  I2C:   ready
>  DRAM:  512 MiB
>  NAND:  0 MiB
>  MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
>  *** Error - No Valid Environment Area found
>  *** Warning - bad CRC, using default environment
>
>  Net:   <ethaddr> not set. Validating first E-fuse MAC
>  cpsw, usb_ether
>  Hit any key to stop autoboot:  0
>  switch to partitions #0, OK
>  mmc0 is current device
>  Scanning mmc 0:2...
>  Failed to mount ext2 filesystem...
>  ** Unrecognized filesystem type **
>  Failed to mount ext2 filesystem...
>  ** Unrecognized filesystem type **
>  Failed to mount ext2 filesystem...
>  ** Unrecognized filesystem type **
>  Failed to mount ext2 filesystem...
>  ** Unrecognized filesystem type **
>  Failed to mount ext2 filesystem...
>  ** Unrecognized filesystem type **
>  Failed to mount ext2 filesystem...
>  ** Unrecognized filesystem type **
>  Failed to mount ext2 filesystem...
>  ** Unrecognized filesystem type **
>  Failed to mount ext2 filesystem...
>  ** Unrecognized filesystem type **
>  Card did not respond to voltage select!
>  Booting from nand ...
>
>  no devices available
>
>  no devices available
>  Bad Linux ARM zImage magic!
>
>
>
>
>  When I am in the uboot command processor, I cannot select the internal
>  eMMC at all:
>
>  U-Boot# mmc dev 1
>  Card did not respond to voltage select!
>
>
>
>  Previously, I was booting with no problems from either eMMC or SD with F21.
>
>
>
>  Thanks,
>
>  Adam
>
>
>  On Wed, Oct 15, 2014 at 6:34 AM, Peter Robinson <pbrobinson(a)gmail.com&gt; wrote:
> > Hi All,
> >
> > Just a heads up that the u-boot 2014.10 GA is on it's way to Fedora 21.
> >
> > https://admin.fedoraproject.org/updates/uboot-tools-2014.10-1.fc21
> >
> > This release contains numerous fixes and improvements over the
> > currently shipping release including, but by no means limited to:
> > * Upstream generic distro support (huge thanks to Dennis Gilmore and
> > Steven Warren for their tireless work to get this upstream
> > * AllWinner suppport for A10*/A13/A20 devices (huge thanks to Hans for
> > this tireless work on this)
> > * Numerous other improvements too long to name.
> >
> > New devices that we now enable in this release, in no particular order, include:
> >
> > AllWinner:
> > A10-OLinuXino-Lime
> > A10s-OLinuXino-M
> > A13-OLinuXino
> > A13-OLinuXinoM
> > A20-OLinuXino_MICRO
> > Bananapi
> > Cubieboard
> > Cubieboard2
> > Cubietruck
> > Mele_A1000
> > Mele_A1000G
> > Mini-X
> > Mini-X-1Gb
> >
> > Tegra:
> > jetson-tk1
> >
> > i.MX6
> > cm_fx6 (Utilite)
> > riotboard
> >
> > It's not yet in nightly builds but I'm going to request it for the
> > next Beta TC compose.
> >
> > Known issues:
> > * Panda is not yet ported to generic distro support
> >
> > Please test and provide feedback.
> >
> > Peter
> > _______________________________________________
> > arm mailing list
> > arm(a)lists.fedoraproject.org
> > https://admin.fedoraproject.org/mailman/listinfo/arm

[Yaakov Selkowitz]

On 2014-10-24 12:21, Peter Robinson wrote:
>  A minor bug and is fixed in uboot-tools-2014.10-3.fc21 
Does this also fix booting on the Pandaboard?

http://fpaste.org/144729/

-- 
Yaakov Selkowitz
Associate Software Engineer, ARM
Red Hat, Inc.

[Peter Robinson]

On Fri, Oct 24, 2014 at 6:31 PM, Yaakov Selkowitz <yselkowi(a)redhat.com&gt; wrote:
>  On 2014-10-24 12:21, Peter Robinson wrote:
> >
> > A minor bug and is fixed in uboot-tools-2014.10-3.fc21
>
>
>  Does this also fix booting on the Pandaboard? 
Not yet

[Adam Goode]

This is still present with -3. It looks like this version of U-Boot is
not capable of booting from the internal eMMC on beaglebone black.

U-Boot SPL 2014.10-g4647503-dirty (Oct 24 2014 - 16:47:41)
omap_hsmmc_send_cmd: timedout waiting on cmd inhibit to clear
spl: mmc init failed: err - -19
### ERROR ### Please RESET the board ###


I found at least another thread about this issue, from version 2014.07:
https://www.mail-archive.com/[e-mail]/msg04279.html


Adam

On Fri, Oct 24, 2014 at 1:21 PM, Peter Robinson <pbrobinson(a)gmail.com&gt; wrote:
>  A minor bug and is fixed in uboot-tools-2014.10-3.fc21
>
>  Peter
>
>  On Sat, Oct 18, 2014 at 9:04 PM, Adam Goode <adam(a)spicenitz.org&gt; wrote:
> > Hopefully I did something wrong, but it's not working at all for me on
> > the beaglebone black:
> >
> > Here is what I get when I try to boot from eMMC:
> >
> > U-Boot SPL 2014.10-gc4b8756-dirty (Oct 15 2014 - 08:57:04)
> > omap_hsmmc_send_cmd: timedout waiting on cmd inhibit to clear
> > spl: mmc init failed: err - -19
> > ### ERROR ### Please RESET the board ###
> >
> >
> >
> > Here is what I get when I make a new SD card from the latest minimal image:
> >
> >
> > U-Boot 2014.10-gc4b8756-dirty (Oct 15 2014 - 08:57:04)
> >
> >        Watchdog enabled
> > I2C:   ready
> > DRAM:  512 MiB
> > NAND:  0 MiB
> > MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> > *** Error - No Valid Environment Area found
> > *** Warning - bad CRC, using default environment
> >
> > Net:   <ethaddr> not set. Validating first E-fuse MAC
> > cpsw, usb_ether
> > Hit any key to stop autoboot:  0
> > switch to partitions #0, OK
> > mmc0 is current device
> > Scanning mmc 0:2...
> > Failed to mount ext2 filesystem...
> > ** Unrecognized filesystem type **
> > Failed to mount ext2 filesystem...
> > ** Unrecognized filesystem type **
> > Failed to mount ext2 filesystem...
> > ** Unrecognized filesystem type **
> > Failed to mount ext2 filesystem...
> > ** Unrecognized filesystem type **
> > Failed to mount ext2 filesystem...
> > ** Unrecognized filesystem type **
> > Failed to mount ext2 filesystem...
> > ** Unrecognized filesystem type **
> > Failed to mount ext2 filesystem...
> > ** Unrecognized filesystem type **
> > Failed to mount ext2 filesystem...
> > ** Unrecognized filesystem type **
> > Card did not respond to voltage select!
> > Booting from nand ...
> >
> > no devices available
> >
> > no devices available
> > Bad Linux ARM zImage magic!
> >
> >
> >
> >
> > When I am in the uboot command processor, I cannot select the internal
> > eMMC at all:
> >
> > U-Boot# mmc dev 1
> > Card did not respond to voltage select!
> >
> >
> >
> > Previously, I was booting with no problems from either eMMC or SD with F21.
> >
> >
> >
> > Thanks,
> >
> > Adam
> >
> >
> > On Wed, Oct 15, 2014 at 6:34 AM, Peter Robinson <pbrobinson(a)gmail.com&gt; wrote:
> >> Hi All,
> >>
> >> Just a heads up that the u-boot 2014.10 GA is on it's way to Fedora 21.
> >>
> >> https://admin.fedoraproject.org/updates/uboot-tools-2014.10-1.fc21
> >>
> >> This release contains numerous fixes and improvements over the
> >> currently shipping release including, but by no means limited to:
> >> * Upstream generic distro support (huge thanks to Dennis Gilmore and
> >> Steven Warren for their tireless work to get this upstream
> >> * AllWinner suppport for A10*/A13/A20 devices (huge thanks to Hans for
> >> this tireless work on this)
> >> * Numerous other improvements too long to name.
> >>
> >> New devices that we now enable in this release, in no particular order, include:
> >>
> >> AllWinner:
> >> A10-OLinuXino-Lime
> >> A10s-OLinuXino-M
> >> A13-OLinuXino
> >> A13-OLinuXinoM
> >> A20-OLinuXino_MICRO
> >> Bananapi
> >> Cubieboard
> >> Cubieboard2
> >> Cubietruck
> >> Mele_A1000
> >> Mele_A1000G
> >> Mini-X
> >> Mini-X-1Gb
> >>
> >> Tegra:
> >> jetson-tk1
> >>
> >> i.MX6
> >> cm_fx6 (Utilite)
> >> riotboard
> >>
> >> It's not yet in nightly builds but I'm going to request it for the
> >> next Beta TC compose.
> >>
> >> Known issues:
> >> * Panda is not yet ported to generic distro support
> >>
> >> Please test and provide feedback.
> >>
> >> Peter
> >> _______________________________________________
> >> arm mailing list
> >> arm(a)lists.fedoraproject.org
> >> https://admin.fedoraproject.org/mailman/listinfo/arm

[Robert Nelson]

On Mon, Oct 27, 2014 at 7:37 PM, Adam Goode <adam(a)spicenitz.org&gt; wrote:
>  This is still present with -3. It looks like this version of U-Boot
> is
>  not capable of booting from the internal eMMC on beaglebone black.
>
>  U-Boot SPL 2014.10-g4647503-dirty (Oct 24 2014 - 16:47:41)
>  omap_hsmmc_send_cmd: timedout waiting on cmd inhibit to clear
>  spl: mmc init failed: err - -19
>  ### ERROR ### Please RESET the board ### 
Which "config" did you guys build against for 2014.10, i had to do
this small change to get the eMMC to also work:

https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v...

diff --git a/configs/am335x_evm_defconfig b/configs/am335x_evm_defconfig
index 2e5aeaa..4cc7e19 100644
--- a/configs/am335x_evm_defconfig
+++ b/configs/am335x_evm_defconfig
@@ -1,5 +1,4 @@
CONFIG_SPL=y
-CONFIG_SYS_EXTRA_OPTIONS="NAND"
-CONFIG_CONS_INDEX=1
+CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1"
+S:CONFIG_ARM=y
+S:CONFIG_TARGET_AM335X_EVM=y

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

[Adam Goode]

A one-line change to the specfile fixed eMMC booting for me (also
tested with booting from SD card):

Change "make am335x_evm_config" to "make am335x_boneblack_config".

I believe this is the correct config, as shown here:
http://git.denx.de/?p=u-boot.git;a=commitdiff;h=b6ab550413b6b64d0024e9dec...

If this breaks the beaglebone white, you might need to introduce a new
board in the RPM.


Adam

On Mon, Oct 27, 2014 at 8:44 PM, Robert Nelson <robertcnelson(a)gmail.com&gt; wrote:
>  On Mon, Oct 27, 2014 at 7:37 PM, Adam Goode
> <adam(a)spicenitz.org&gt; wrote:
> > This is still present with -3. It looks like this version of U-Boot is
> > not capable of booting from the internal eMMC on beaglebone black.
> >
> > U-Boot SPL 2014.10-g4647503-dirty (Oct 24 2014 - 16:47:41)
> > omap_hsmmc_send_cmd: timedout waiting on cmd inhibit to clear
> > spl: mmc init failed: err - -19
> > ### ERROR ### Please RESET the board ###
>
>  Which "config" did you guys build against for 2014.10, i had to do
>  this small change to get the eMMC to also work:
>
>
> https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v...
>
>  diff --git a/configs/am335x_evm_defconfig b/configs/am335x_evm_defconfig
>  index 2e5aeaa..4cc7e19 100644
>  --- a/configs/am335x_evm_defconfig
>  +++ b/configs/am335x_evm_defconfig
>  @@ -1,5 +1,4 @@
>  CONFIG_SPL=y
>  -CONFIG_SYS_EXTRA_OPTIONS="NAND"
>  -CONFIG_CONS_INDEX=1
>  +CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1"
>  +S:CONFIG_ARM=y
>  +S:CONFIG_TARGET_AM335X_EVM=y
>
>  Regards,
>
>  --
>  Robert Nelson
>  http://www.rcn-ee.com/

[Adam Goode]

I filed a bug for the beaglebone black eMMC problem:
https://bugzilla.redhat.com/show_bug.cgi?id=1161619


Adam


On Sun, Nov 2, 2014 at 11:32 PM, Adam Goode <adam(a)spicenitz.org&gt; wrote:
>  A one-line change to the specfile fixed eMMC booting for me (also
>  tested with booting from SD card):
>
>  Change "make am335x_evm_config" to "make am335x_boneblack_config".
>
>  I believe this is the correct config, as shown here:
>  http://git.denx.de/?p=u-boot.git;a=commitdiff;h=b6ab550413b6b64d0024e9dec...
>
>  If this breaks the beaglebone white, you might need to introduce a new
>  board in the RPM.
>
>
>  Adam
>
>  On Mon, Oct 27, 2014 at 8:44 PM, Robert Nelson <robertcnelson(a)gmail.com&gt; wrote:
> > On Mon, Oct 27, 2014 at 7:37 PM, Adam Goode <adam(a)spicenitz.org&gt; wrote:
> >> This is still present with -3. It looks like this version of U-Boot is
> >> not capable of booting from the internal eMMC on beaglebone black.
> >>
> >> U-Boot SPL 2014.10-g4647503-dirty (Oct 24 2014 - 16:47:41)
> >> omap_hsmmc_send_cmd: timedout waiting on cmd inhibit to clear
> >> spl: mmc init failed: err - -19
> >> ### ERROR ### Please RESET the board ###
> >
> > Which "config" did you guys build against for 2014.10, i had to do
> > this small change to get the eMMC to also work:
> >
> >
> https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v...
> >
> > diff --git a/configs/am335x_evm_defconfig b/configs/am335x_evm_defconfig
> > index 2e5aeaa..4cc7e19 100644
> > --- a/configs/am335x_evm_defconfig
> > +++ b/configs/am335x_evm_defconfig
> > @@ -1,5 +1,4 @@
> > CONFIG_SPL=y
> > -CONFIG_SYS_EXTRA_OPTIONS="NAND"
> > -CONFIG_CONS_INDEX=1
> > +CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1"
> > +S:CONFIG_ARM=y
> > +S:CONFIG_TARGET_AM335X_EVM=y
> >
> > Regards,
> >
> > --
> > Robert Nelson
> > http://www.rcn-ee.com/

[Peter Robinson]

Already got one locally being tested, should be pushed tomorrow.

Peter

On Fri, Nov 7, 2014 at 2:06 PM, Adam Goode <adam(a)spicenitz.org&gt; wrote:
>  I filed a bug for the beaglebone black eMMC problem:
>  https://bugzilla.redhat.com/show_bug.cgi?id=1161619
>
>
>  Adam
>
>
>  On Sun, Nov 2, 2014 at 11:32 PM, Adam Goode <adam(a)spicenitz.org&gt; wrote:
> > A one-line change to the specfile fixed eMMC booting for me (also
> > tested with booting from SD card):
> >
> > Change "make am335x_evm_config" to "make
> am335x_boneblack_config".
> >
> > I believe this is the correct config, as shown here:
> >
> http://git.denx.de/?p=u-boot.git;a=commitdiff;h=b6ab550413b6b64d0024e9dec...
> >
> > If this breaks the beaglebone white, you might need to introduce a new
> > board in the RPM.
> >
> >
> > Adam
> >
> > On Mon, Oct 27, 2014 at 8:44 PM, Robert Nelson <robertcnelson(a)gmail.com&gt;
> wrote:
> >> On Mon, Oct 27, 2014 at 7:37 PM, Adam Goode <adam(a)spicenitz.org&gt; wrote:
> >>> This is still present with -3. It looks like this version of U-Boot is
> >>> not capable of booting from the internal eMMC on beaglebone black.
> >>>
> >>> U-Boot SPL 2014.10-g4647503-dirty (Oct 24 2014 - 16:47:41)
> >>> omap_hsmmc_send_cmd: timedout waiting on cmd inhibit to clear
> >>> spl: mmc init failed: err - -19
> >>> ### ERROR ### Please RESET the board ###
> >>
> >> Which "config" did you guys build against for 2014.10, i had to do
> >> this small change to get the eMMC to also work:
> >>
> >>
> https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v...
> >>
> >> diff --git a/configs/am335x_evm_defconfig b/configs/am335x_evm_defconfig
> >> index 2e5aeaa..4cc7e19 100644
> >> --- a/configs/am335x_evm_defconfig
> >> +++ b/configs/am335x_evm_defconfig
> >> @@ -1,5 +1,4 @@
> >> CONFIG_SPL=y
> >> -CONFIG_SYS_EXTRA_OPTIONS="NAND"
> >> -CONFIG_CONS_INDEX=1
> >> +CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1"
> >> +S:CONFIG_ARM=y
> >> +S:CONFIG_TARGET_AM335X_EVM=y
> >>
> >> Regards,
> >>
> >> --
> >> Robert Nelson
> >> http://www.rcn-ee.com/

[Peter Robinson]

Hi Adam,

Problem should now be fixed with -5

Can you test and provide karma so we can get it in GA.

https://admin.fedoraproject.org/updates/FEDORA-2014-14716/uboot-tools-201...

On Tue, Oct 28, 2014 at 12:37 AM, Adam Goode <adam(a)spicenitz.org&gt; wrote:
>  This is still present with -3. It looks like this version of U-Boot
> is
>  not capable of booting from the internal eMMC on beaglebone black.
>
>  U-Boot SPL 2014.10-g4647503-dirty (Oct 24 2014 - 16:47:41)
>  omap_hsmmc_send_cmd: timedout waiting on cmd inhibit to clear
>  spl: mmc init failed: err - -19
>  ### ERROR ### Please RESET the board ###
>
>
>  I found at least another thread about this issue, from version 2014.07:
>  https://www.mail-archive.com/[e-mail]/msg04279.html
>
>
>  Adam
>
>  On Fri, Oct 24, 2014 at 1:21 PM, Peter Robinson <pbrobinson(a)gmail.com&gt; wrote:
> > A minor bug and is fixed in uboot-tools-2014.10-3.fc21
> >
> > Peter
> >
> > On Sat, Oct 18, 2014 at 9:04 PM, Adam Goode <adam(a)spicenitz.org&gt; wrote:
> >> Hopefully I did something wrong, but it's not working at all for me on
> >> the beaglebone black:
> >>
> >> Here is what I get when I try to boot from eMMC:
> >>
> >> U-Boot SPL 2014.10-gc4b8756-dirty (Oct 15 2014 - 08:57:04)
> >> omap_hsmmc_send_cmd: timedout waiting on cmd inhibit to clear
> >> spl: mmc init failed: err - -19
> >> ### ERROR ### Please RESET the board ###
> >>
> >>
> >>
> >> Here is what I get when I make a new SD card from the latest minimal image:
> >>
> >>
> >> U-Boot 2014.10-gc4b8756-dirty (Oct 15 2014 - 08:57:04)
> >>
> >>        Watchdog enabled
> >> I2C:   ready
> >> DRAM:  512 MiB
> >> NAND:  0 MiB
> >> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> >> *** Error - No Valid Environment Area found
> >> *** Warning - bad CRC, using default environment
> >>
> >> Net:   <ethaddr> not set. Validating first E-fuse MAC
> >> cpsw, usb_ether
> >> Hit any key to stop autoboot:  0
> >> switch to partitions #0, OK
> >> mmc0 is current device
> >> Scanning mmc 0:2...
> >> Failed to mount ext2 filesystem...
> >> ** Unrecognized filesystem type **
> >> Failed to mount ext2 filesystem...
> >> ** Unrecognized filesystem type **
> >> Failed to mount ext2 filesystem...
> >> ** Unrecognized filesystem type **
> >> Failed to mount ext2 filesystem...
> >> ** Unrecognized filesystem type **
> >> Failed to mount ext2 filesystem...
> >> ** Unrecognized filesystem type **
> >> Failed to mount ext2 filesystem...
> >> ** Unrecognized filesystem type **
> >> Failed to mount ext2 filesystem...
> >> ** Unrecognized filesystem type **
> >> Failed to mount ext2 filesystem...
> >> ** Unrecognized filesystem type **
> >> Card did not respond to voltage select!
> >> Booting from nand ...
> >>
> >> no devices available
> >>
> >> no devices available
> >> Bad Linux ARM zImage magic!
> >>
> >>
> >>
> >>
> >> When I am in the uboot command processor, I cannot select the internal
> >> eMMC at all:
> >>
> >> U-Boot# mmc dev 1
> >> Card did not respond to voltage select!
> >>
> >>
> >>
> >> Previously, I was booting with no problems from either eMMC or SD with F21.
> >>
> >>
> >>
> >> Thanks,
> >>
> >> Adam
> >>
> >>
> >> On Wed, Oct 15, 2014 at 6:34 AM, Peter Robinson <pbrobinson(a)gmail.com&gt;
> wrote:
> >>> Hi All,
> >>>
> >>> Just a heads up that the u-boot 2014.10 GA is on it's way to Fedora 21.
> >>>
> >>> https://admin.fedoraproject.org/updates/uboot-tools-2014.10-1.fc21
> >>>
> >>> This release contains numerous fixes and improvements over the
> >>> currently shipping release including, but by no means limited to:
> >>> * Upstream generic distro support (huge thanks to Dennis Gilmore and
> >>> Steven Warren for their tireless work to get this upstream
> >>> * AllWinner suppport for A10*/A13/A20 devices (huge thanks to Hans for
> >>> this tireless work on this)
> >>> * Numerous other improvements too long to name.
> >>>
> >>> New devices that we now enable in this release, in no particular order,
> include:
> >>>
> >>> AllWinner:
> >>> A10-OLinuXino-Lime
> >>> A10s-OLinuXino-M
> >>> A13-OLinuXino
> >>> A13-OLinuXinoM
> >>> A20-OLinuXino_MICRO
> >>> Bananapi
> >>> Cubieboard
> >>> Cubieboard2
> >>> Cubietruck
> >>> Mele_A1000
> >>> Mele_A1000G
> >>> Mini-X
> >>> Mini-X-1Gb
> >>>
> >>> Tegra:
> >>> jetson-tk1
> >>>
> >>> i.MX6
> >>> cm_fx6 (Utilite)
> >>> riotboard
> >>>
> >>> It's not yet in nightly builds but I'm going to request it for the
> >>> next Beta TC compose.
> >>>
> >>> Known issues:
> >>> * Panda is not yet ported to generic distro support
> >>>
> >>> Please test and provide feedback.
> >>>
> >>> Peter
> >>> _______________________________________________
> >>> arm mailing list
> >>> arm(a)lists.fedoraproject.org
> >>> https://admin.fedoraproject.org/mailman/listinfo/arm

[Adam Goode]

Works great for me! Thanks.

Does anyone have a beaglebone white? I'm still worried that this fix
will break that board.


Adam


On Thu, Nov 13, 2014 at 7:13 AM, Peter Robinson <pbrobinson(a)gmail.com&gt; wrote:
>  Hi Adam,
>
>  Problem should now be fixed with -5
>
>  Can you test and provide karma so we can get it in GA.
>
>  https://admin.fedoraproject.org/updates/FEDORA-2014-14716/uboot-tools-201...
>
>  On Tue, Oct 28, 2014 at 12:37 AM, Adam Goode <adam(a)spicenitz.org&gt; wrote:
> > This is still present with -3. It looks like this version of U-Boot is
> > not capable of booting from the internal eMMC on beaglebone black.
> >
> > U-Boot SPL 2014.10-g4647503-dirty (Oct 24 2014 - 16:47:41)
> > omap_hsmmc_send_cmd: timedout waiting on cmd inhibit to clear
> > spl: mmc init failed: err - -19
> > ### ERROR ### Please RESET the board ###
> >
> >
> > I found at least another thread about this issue, from version 2014.07:
> > https://www.mail-archive.com/[e-mail]/msg04279.html
> >
> >
> > Adam
> >
> > On Fri, Oct 24, 2014 at 1:21 PM, Peter Robinson <pbrobinson(a)gmail.com&gt; wrote:
> >> A minor bug and is fixed in uboot-tools-2014.10-3.fc21
> >>
> >> Peter
> >>
> >> On Sat, Oct 18, 2014 at 9:04 PM, Adam Goode <adam(a)spicenitz.org&gt; wrote:
> >>> Hopefully I did something wrong, but it's not working at all for me on
> >>> the beaglebone black:
> >>>
> >>> Here is what I get when I try to boot from eMMC:
> >>>
> >>> U-Boot SPL 2014.10-gc4b8756-dirty (Oct 15 2014 - 08:57:04)
> >>> omap_hsmmc_send_cmd: timedout waiting on cmd inhibit to clear
> >>> spl: mmc init failed: err - -19
> >>> ### ERROR ### Please RESET the board ###
> >>>
> >>>
> >>>
> >>> Here is what I get when I make a new SD card from the latest minimal image:
> >>>
> >>>
> >>> U-Boot 2014.10-gc4b8756-dirty (Oct 15 2014 - 08:57:04)
> >>>
> >>>        Watchdog enabled
> >>> I2C:   ready
> >>> DRAM:  512 MiB
> >>> NAND:  0 MiB
> >>> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> >>> *** Error - No Valid Environment Area found
> >>> *** Warning - bad CRC, using default environment
> >>>
> >>> Net:   <ethaddr> not set. Validating first E-fuse MAC
> >>> cpsw, usb_ether
> >>> Hit any key to stop autoboot:  0
> >>> switch to partitions #0, OK
> >>> mmc0 is current device
> >>> Scanning mmc 0:2...
> >>> Failed to mount ext2 filesystem...
> >>> ** Unrecognized filesystem type **
> >>> Failed to mount ext2 filesystem...
> >>> ** Unrecognized filesystem type **
> >>> Failed to mount ext2 filesystem...
> >>> ** Unrecognized filesystem type **
> >>> Failed to mount ext2 filesystem...
> >>> ** Unrecognized filesystem type **
> >>> Failed to mount ext2 filesystem...
> >>> ** Unrecognized filesystem type **
> >>> Failed to mount ext2 filesystem...
> >>> ** Unrecognized filesystem type **
> >>> Failed to mount ext2 filesystem...
> >>> ** Unrecognized filesystem type **
> >>> Failed to mount ext2 filesystem...
> >>> ** Unrecognized filesystem type **
> >>> Card did not respond to voltage select!
> >>> Booting from nand ...
> >>>
> >>> no devices available
> >>>
> >>> no devices available
> >>> Bad Linux ARM zImage magic!
> >>>
> >>>
> >>>
> >>>
> >>> When I am in the uboot command processor, I cannot select the internal
> >>> eMMC at all:
> >>>
> >>> U-Boot# mmc dev 1
> >>> Card did not respond to voltage select!
> >>>
> >>>
> >>>
> >>> Previously, I was booting with no problems from either eMMC or SD with F21.
> >>>
> >>>
> >>>
> >>> Thanks,
> >>>
> >>> Adam
> >>>
> >>>
> >>> On Wed, Oct 15, 2014 at 6:34 AM, Peter Robinson <pbrobinson(a)gmail.com&gt;
> wrote:
> >>>> Hi All,
> >>>>
> >>>> Just a heads up that the u-boot 2014.10 GA is on it's way to Fedora
> 21.
> >>>>
> >>>> https://admin.fedoraproject.org/updates/uboot-tools-2014.10-1.fc21
> >>>>
> >>>> This release contains numerous fixes and improvements over the
> >>>> currently shipping release including, but by no means limited to:
> >>>> * Upstream generic distro support (huge thanks to Dennis Gilmore and
> >>>> Steven Warren for their tireless work to get this upstream
> >>>> * AllWinner suppport for A10*/A13/A20 devices (huge thanks to Hans for
> >>>> this tireless work on this)
> >>>> * Numerous other improvements too long to name.
> >>>>
> >>>> New devices that we now enable in this release, in no particular order,
> include:
> >>>>
> >>>> AllWinner:
> >>>> A10-OLinuXino-Lime
> >>>> A10s-OLinuXino-M
> >>>> A13-OLinuXino
> >>>> A13-OLinuXinoM
> >>>> A20-OLinuXino_MICRO
> >>>> Bananapi
> >>>> Cubieboard
> >>>> Cubieboard2
> >>>> Cubietruck
> >>>> Mele_A1000
> >>>> Mele_A1000G
> >>>> Mini-X
> >>>> Mini-X-1Gb
> >>>>
> >>>> Tegra:
> >>>> jetson-tk1
> >>>>
> >>>> i.MX6
> >>>> cm_fx6 (Utilite)
> >>>> riotboard
> >>>>
> >>>> It's not yet in nightly builds but I'm going to request it for
> the
> >>>> next Beta TC compose.
> >>>>
> >>>> Known issues:
> >>>> * Panda is not yet ported to generic distro support
> >>>>
> >>>> Please test and provide feedback.
> >>>>
> >>>> Peter
> >>>> _______________________________________________
> >>>> arm mailing list
> >>>> arm(a)lists.fedoraproject.org
> >>>> https://admin.fedoraproject.org/mailman/listinfo/arm

[Marcin Juszkiewicz]

W dniu 13.11.2014 o 15:14, Adam Goode pisze:
>  Works great for me! Thanks.
>  
>  Does anyone have a beaglebone white? I'm still worried that this fix
>  will break that board. 
I did not followed thread but have working BBW somewhere. can you point
me to SD card image which I can use to test?

[Adam Goode]

If you follow these instructions, you can make an SD card:
https://fedoraproject.org/wiki/Architectures/ARM/F21/Installation#Scripted


Adam


On Thu, Nov 13, 2014 at 11:08 AM, Marcin Juszkiewicz <
mjuszkiewicz(a)redhat.com&gt; wrote:

>  W dniu 13.11.2014 o 15:14, Adam Goode pisze:
>  > Works great for me! Thanks.
>  >
>  > Does anyone have a beaglebone white? I'm still worried that this fix
>  > will break that board.
>
>  I did not followed thread but have working BBW somewhere. can you point
>  me to SD card image which I can use to test?
>  _______________________________________________
>  arm mailing list
>  arm(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/arm
>

[Paul Whalen]

----- Original Message -----
>  Works great for me! Thanks.
>  
>  Does anyone have a beaglebone white? I'm still worried that this fix
>  will break that board. 
Works okay on the Beaglebone White using the F21 TC1 Minimal image. Hit 
a couple of errors at the beginning, but the system came up fine.

U-Boot SPL 2014.10 (Nov 11 2014 - 07:35:06)
No AC power, disabling frequency switch
MMC: block number 0x100 exceeds max(0x0)
MMC: block number 0x200 exceeds max(0x0)
*** Error - No Valid Environment Area found
Using default environment
...


Paul
 

>  
>  
>  Adam
>  
>  
>  On Thu, Nov 13, 2014 at 7:13 AM, Peter Robinson <pbrobinson(a)gmail.com&gt; wrote:
>  > Hi Adam,
>  >
>  > Problem should now be fixed with -5
>  >
>  > Can you test and provide karma so we can get it in GA.
>  >
>  >
> https://admin.fedoraproject.org/updates/FEDORA-2014-14716/uboot-tools-201...
>  >
>  > On Tue, Oct 28, 2014 at 12:37 AM, Adam Goode <adam(a)spicenitz.org&gt; wrote:
>  >> This is still present with -3. It looks like this version of U-Boot is
>  >> not capable of booting from the internal eMMC on beaglebone black.
>  >>
>  >> U-Boot SPL 2014.10-g4647503-dirty (Oct 24 2014 - 16:47:41)
>  >> omap_hsmmc_send_cmd: timedout waiting on cmd inhibit to clear
>  >> spl: mmc init failed: err - -19
>  >> ### ERROR ### Please RESET the board ###
>  >>
>  >>
>  >> I found at least another thread about this issue, from version 2014.07:
>  >> https://www.mail-archive.com/[e-mail]/msg04279.html
>  >>
>  >>
>  >> Adam
>  >>
>  >> On Fri, Oct 24, 2014 at 1:21 PM, Peter Robinson <pbrobinson(a)gmail.com&gt;
>  >> wrote:
>  >>> A minor bug and is fixed in uboot-tools-2014.10-3.fc21
>  >>>
>  >>> Peter
>  >>>
>  >>> On Sat, Oct 18, 2014 at 9:04 PM, Adam Goode <adam(a)spicenitz.org&gt;
> wrote:
>  >>>> Hopefully I did something wrong, but it's not working at all for me
> on
>  >>>> the beaglebone black:
>  >>>>
>  >>>> Here is what I get when I try to boot from eMMC:
>  >>>>
>  >>>> U-Boot SPL 2014.10-gc4b8756-dirty (Oct 15 2014 - 08:57:04)
>  >>>> omap_hsmmc_send_cmd: timedout waiting on cmd inhibit to clear
>  >>>> spl: mmc init failed: err - -19
>  >>>> ### ERROR ### Please RESET the board ###
>  >>>>
>  >>>>
>  >>>>
>  >>>> Here is what I get when I make a new SD card from the latest minimal
>  >>>> image:
>  >>>>
>  >>>>
>  >>>> U-Boot 2014.10-gc4b8756-dirty (Oct 15 2014 - 08:57:04)
>  >>>>
>  >>>>        Watchdog enabled
>  >>>> I2C:   ready
>  >>>> DRAM:  512 MiB
>  >>>> NAND:  0 MiB
>  >>>> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
>  >>>> *** Error - No Valid Environment Area found
>  >>>> *** Warning - bad CRC, using default environment
>  >>>>
>  >>>> Net:   <ethaddr> not set. Validating first E-fuse MAC
>  >>>> cpsw, usb_ether
>  >>>> Hit any key to stop autoboot:  0
>  >>>> switch to partitions #0, OK
>  >>>> mmc0 is current device
>  >>>> Scanning mmc 0:2...
>  >>>> Failed to mount ext2 filesystem...
>  >>>> ** Unrecognized filesystem type **
>  >>>> Failed to mount ext2 filesystem...
>  >>>> ** Unrecognized filesystem type **
>  >>>> Failed to mount ext2 filesystem...
>  >>>> ** Unrecognized filesystem type **
>  >>>> Failed to mount ext2 filesystem...
>  >>>> ** Unrecognized filesystem type **
>  >>>> Failed to mount ext2 filesystem...
>  >>>> ** Unrecognized filesystem type **
>  >>>> Failed to mount ext2 filesystem...
>  >>>> ** Unrecognized filesystem type **
>  >>>> Failed to mount ext2 filesystem...
>  >>>> ** Unrecognized filesystem type **
>  >>>> Failed to mount ext2 filesystem...
>  >>>> ** Unrecognized filesystem type **
>  >>>> Card did not respond to voltage select!
>  >>>> Booting from nand ...
>  >>>>
>  >>>> no devices available
>  >>>>
>  >>>> no devices available
>  >>>> Bad Linux ARM zImage magic!
>  >>>>
>  >>>>
>  >>>>
>  >>>>
>  >>>> When I am in the uboot command processor, I cannot select the internal
>  >>>> eMMC at all:
>  >>>>
>  >>>> U-Boot# mmc dev 1
>  >>>> Card did not respond to voltage select!
>  >>>>
>  >>>>
>  >>>>
>  >>>> Previously, I was booting with no problems from either eMMC or SD with
>  >>>> F21.
>  >>>>
>  >>>>
>  >>>>
>  >>>> Thanks,
>  >>>>
>  >>>> Adam
>  >>>>
>  >>>>
>  >>>> On Wed, Oct 15, 2014 at 6:34 AM, Peter Robinson
> <pbrobinson(a)gmail.com&gt;
>  >>>> wrote:
>  >>>>> Hi All,
>  >>>>>
>  >>>>> Just a heads up that the u-boot 2014.10 GA is on it's way to
> Fedora 21.
>  >>>>>
>  >>>>> https://admin.fedoraproject.org/updates/uboot-tools-2014.10-1.fc21
>  >>>>>
>  >>>>> This release contains numerous fixes and improvements over the
>  >>>>> currently shipping release including, but by no means limited to:
>  >>>>> * Upstream generic distro support (huge thanks to Dennis Gilmore
> and
>  >>>>> Steven Warren for their tireless work to get this upstream
>  >>>>> * AllWinner suppport for A10*/A13/A20 devices (huge thanks to Hans
> for
>  >>>>> this tireless work on this)
>  >>>>> * Numerous other improvements too long to name.
>  >>>>>
>  >>>>> New devices that we now enable in this release, in no particular
> order,
>  >>>>> include:
>  >>>>>
>  >>>>> AllWinner:
>  >>>>> A10-OLinuXino-Lime
>  >>>>> A10s-OLinuXino-M
>  >>>>> A13-OLinuXino
>  >>>>> A13-OLinuXinoM
>  >>>>> A20-OLinuXino_MICRO
>  >>>>> Bananapi
>  >>>>> Cubieboard
>  >>>>> Cubieboard2
>  >>>>> Cubietruck
>  >>>>> Mele_A1000
>  >>>>> Mele_A1000G
>  >>>>> Mini-X
>  >>>>> Mini-X-1Gb
>  >>>>>
>  >>>>> Tegra:
>  >>>>> jetson-tk1
>  >>>>>
>  >>>>> i.MX6
>  >>>>> cm_fx6 (Utilite)
>  >>>>> riotboard
>  >>>>>
>  >>>>> It's not yet in nightly builds but I'm going to request it
> for the
>  >>>>> next Beta TC compose.
>  >>>>>
>  >>>>> Known issues:
>  >>>>> * Panda is not yet ported to generic distro support
>  >>>>>
>  >>>>> Please test and provide feedback.
>  >>>>>
>  >>>>> Peter
>  >>>>> _______________________________________________
>  >>>>> arm mailing list
>  >>>>> arm(a)lists.fedoraproject.org
>  >>>>> https://admin.fedoraproject.org/mailman/listinfo/arm
>  _______________________________________________
>  arm mailing list
>  arm(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/arm

[Dennis Gilmore]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 13 Nov 2014 09:14:19 -0500
Adam Goode <adam(a)spicenitz.org&gt; wrote:

>  Works great for me! Thanks.
>  
>  Does anyone have a beaglebone white? I'm still worried that this fix
>  will break that board.
>  
>  
>  Adam
>  
I tested on my beaglebone white before i submitted the update. it works
fine.

Dennis
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQIcBAEBAgAGBQJUZp1UAAoJEH7ltONmPFDRhYgQAKPpoPMK6WykAtL0afBTe4BR
> LWdCFwks9AH6EZDzwKmdvD57FfYbNdCx1dkwzzDEDdzm8eBMJmoaaX8FztZupNCc
> IAWj2QT08rwoYbBg2EXiHApesR4nDMhYEb6O7HUMW4Ok3E2J8/E7jKEi+XxO7qCa
> 7Vi/8tWqPgicVQaJaVjecY6IR162cSGYYw+rTdW7MRnAFaNwYqvDRpQhFxclQv9w
> Y+eUxbB4EyIlUL3kyF8PJaVJ4EKDMqALB/dd9b9Kr47pHOW79coEoS41jJs28fGN
> M53owMb0AgUpBrFm9MrlAcm0WUv2e/gRggLJl6o4P7o+YKa4TODRjUnzPLsFSeM8
> FQMHuFPph76lBK0FZ9liYb9lK5WY/LU7q89IOT53665UlLY07SPxiIqfNS8QpHcW
> cWW7Sf6m/894dGiXBX3iXJUbaCvwqJCxo7L/mXe0lpdvTr1iADXOjmX/lsYyZDwH
> Y/faVXLVJpU2Rkb8vzfimlFnrzu5YbsWnyK0QHHgPknbNfLTHXvy7t7/ZYbUZ57D
> YIg5vx4aJSMGgkdtrJddTCaGgnFro/Taxtb0wo/G2C1XpJLU3b4yHDTEWymyjxnF
> TGGuTxZHIjWSCJm9w/vdWJO5/R449I6gKhLnhjeVJUtcSgqjTSrHX0mOSPMZBPH3
> IJwbFZisk79ewvcqS6aB
> =/2R2
> -----END PGP SIGNATURE-----
>

[Jeffrey Ollie]

On Fri, Nov 14, 2014 at 6:24 PM, Dennis Gilmore <dennis(a)ausil.us&gt; wrote:
>  On Thu, 13 Nov 2014 09:14:19 -0500
>  Adam Goode <adam(a)spicenitz.org&gt; wrote:
>
> > Works great for me! Thanks.
> >
> > Does anyone have a beaglebone white? I'm still worried that this fix
> > will break that board.
>
>  I tested on my beaglebone white before i submitted the update. it works
>  fine. 
I just got my BeagleBone Black out again and the new u-boot seems to
be working fine.  I even overwrote the old MLO and u-boot.img on the
internal eMMC and things still worked fine.

-- 
Jeff Ollie