Fedora 27 not boot on BBB

[sakurai]

2018-03-13 8:18 GMT+09:00 Peter Robinson <pbrobinson(a)gmail.com&gt;:
>  On Mon, Mar 12, 2018 at 10:47 PM, sakurai <sakurai(a)pugpug.org&gt;
> wrote:
> > Hi Peter,
> >
> > Thank you for your prompt comment.
> > I removed uEnv.txt but following message was displayed. 
 (snip)
>  I don't know what you've done to now, you're likely possibly better
>  off starting again with arm-image-installer to setup the image again
>  with am335x_evm and then try booting with the boot button held down. 
I tried again using arm-image-installer by following command.

>  fedora-arm-image-installer
> --image=Fedora-Server-armhfp-27-1.6-sda.raw.xz --target=am335x_evm --media=/dev/sdd
> --norootpass --resizefs --addconsole --selinux=off 
Not am335x_boneblack? Anyway I installed using arm335x_evm this time.

My boot loader may be new because Angstrom will not boot without
holding the boot button.

>  You might also want to give the full output. 
Here is the full output.

U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
mmc_send_cmd : timeout: No status update
reading u-boot.img
reading u-boot.img


U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14)

I2C:   ready
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  No NAND device found!!!
0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment

musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot:  0
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
micro SD card found
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
reading uEnv.txt
** Unable to read file uEnv.txt **
gpio: pin 55 (gpio 55) value is 1
** File not found /boot/uImage **
U-Boot#

--
SAKURAI, Atsushi <sakurai(a)pugpug.org&gt;

[Dennis Gilmore]

El mar, 13-03-2018 a las 22:51 +0900, sakurai escribió:
>  2018-03-13 8:18 GMT+09:00 Peter Robinson
> <pbrobinson(a)gmail.com&gt;:
>  > On Mon, Mar 12, 2018 at 10:47 PM, sakurai <sakurai(a)pugpug.org&gt;
>  > wrote:
>  > > Hi Peter,
>  > > 
>  > > Thank you for your prompt comment.
>  > > I removed uEnv.txt but following message was displayed.
>  
>   (snip)
>  > 
>  > I don't know what you've done to now, you're likely possibly better
>  > off starting again with arm-image-installer to setup the image
>  > again
>  > with am335x_evm and then try booting with the boot button held
>  > down.
>  
>  I tried again using arm-image-installer by following command.
>  
>  > fedora-arm-image-installer --image=Fedora-Server-armhfp-27-1.6-
>  > sda.raw.xz --target=am335x_evm --media=/dev/sdd --norootpass --
>  > resizefs --addconsole --selinux=off
>  
>  Not am335x_boneblack? Anyway I installed using arm335x_evm this time.
>  
>  My boot loader may be new because Angstrom will not boot without
>  holding the boot button.
>  
>  > You might also want to give the full output.
>  
>  Here is the full output.
>  
>  U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14) 
This is not the Fedora u-boot. if you hold the boot key does it boot?

Dennis

[Peter Robinson]

On Tue, Mar 13, 2018 at 1:51 PM, sakurai <sakurai(a)pugpug.org&gt; wrote:
>  2018-03-13 8:18 GMT+09:00 Peter Robinson
> <pbrobinson(a)gmail.com&gt;:
> > On Mon, Mar 12, 2018 at 10:47 PM, sakurai <sakurai(a)pugpug.org&gt; wrote:
> >> Hi Peter,
> >>
> >> Thank you for your prompt comment.
> >> I removed uEnv.txt but following message was displayed.
>   (snip)
> >
> > I don't know what you've done to now, you're likely possibly better
> > off starting again with arm-image-installer to setup the image again
> > with am335x_evm and then try booting with the boot button held down.
>
>  I tried again using arm-image-installer by following command.
>
> > fedora-arm-image-installer --image=Fedora-Server-armhfp-27-1.6-sda.raw.xz
> --target=am335x_evm --media=/dev/sdd --norootpass --resizefs --addconsole --selinux=off
>
>  Not am335x_boneblack? Anyway I installed using arm335x_evm this time.
>
>  My boot loader may be new because Angstrom will not boot without
>  holding the boot button.
>
> > You might also want to give the full output.
>
>  Here is the full output.
>
>  U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14)
>  musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
>  musb-hdrc: MHDRC RTL version 2.0
>  musb-hdrc: setup fifo_mode 4
>  musb-hdrc: 28/31 max ep, 16384/16384 memory
>  USB Peripheral mode controller at 47401000 using PIO, IRQ 0
>  musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
>  musb-hdrc: MHDRC RTL version 2.0
>  musb-hdrc: setup fifo_mode 4
>  musb-hdrc: 28/31 max ep, 16384/16384 memory
>  USB Host mode controller at 47401800 using PIO, IRQ 0
>  OMAP SD/MMC: 0
>  mmc_send_cmd : timeout: No status update
>  reading u-boot.img
>  reading u-boot.img
>
>
>  U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14) 
As Dennis had already stated this isn't Fedora's u-boot, what you see
is as I would expect, basically the problem here is dealing with the
boot button correctly.

[sakurai]

Hi Dennis and Peter,

Of course I tried both pushing button and without it, but the result
was the same.
I remember the specification of the first version of the boot program
was designed  as what you said.
I probably re-programmed the boot program according to the Ubuntu
without pushing the boot button
 in order to boot from SD card.

-- 
桜井 <sakurai(a)pugpug.org&gt;


2018-03-14 1:58 GMT+09:00 Peter Robinson <pbrobinson(a)gmail.com&gt;:
> On Tue, Mar 13, 2018 at 1:51 PM, sakurai <sakurai(a)pugpug.org&gt; wrote:
>> 2018-03-13 8:18 GMT+09:00 Peter Robinson <pbrobinson(a)gmail.com&gt;:
>>> On Mon, Mar 12, 2018 at 10:47 PM, sakurai <sakurai(a)pugpug.org&gt; wrote:
>>>> Hi Peter,
>>>>
>>>> Thank you for your prompt comment.
>>>> I removed uEnv.txt but following message was displayed.
>>  (snip)
>>>
>>> I don't know what you've done to now, you're likely possibly
better
>>> off starting again with arm-image-installer to setup the image again
>>> with am335x_evm and then try booting with the boot button held down.
>>
>> I tried again using arm-image-installer by following command.
>>
>>> fedora-arm-image-installer --image=Fedora-Server-armhfp-27-1.6-sda.raw.xz
--target=am335x_evm --media=/dev/sdd --norootpass --resizefs --addconsole --selinux=off
>>
>> Not am335x_boneblack? Anyway I installed using arm335x_evm this time.
>>
>> My boot loader may be new because Angstrom will not boot without
>> holding the boot button.
>>
>>> You might also want to give the full output.
>>
>> Here is the full output.
>>
>> U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14)
>> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
>> musb-hdrc: MHDRC RTL version 2.0
>> musb-hdrc: setup fifo_mode 4
>> musb-hdrc: 28/31 max ep, 16384/16384 memory
>> USB Peripheral mode controller at 47401000 using PIO, IRQ 0
>> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
>> musb-hdrc: MHDRC RTL version 2.0
>> musb-hdrc: setup fifo_mode 4
>> musb-hdrc: 28/31 max ep, 16384/16384 memory
>> USB Host mode controller at 47401800 using PIO, IRQ 0
>> OMAP SD/MMC: 0
>> mmc_send_cmd : timeout: No status update
>> reading u-boot.img
>> reading u-boot.img
>>
>>
>> U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14)
>
> As Dennis had already stated this isn't Fedora's u-boot, what you see
> is as I would expect, basically the problem here is dealing with the
> boot button correctly.

[Peter Robinson]

On Sun, Mar 18, 2018 at 12:37 AM, sakurai <sakurai(a)pugpug.org&gt; wrote:
>  Hi Dennis and Peter,
>
>  Of course I tried both pushing button and without it, but the result
>  was the same.
>  I remember the specification of the first version of the boot program
>  was designed  as what you said.
>  I probably re-programmed the boot program according to the Ubuntu
>  without pushing the boot button
>   in order to boot from SD card. 
I'm not sure what we can do if you've reprogrammed it, one thing you
can do is if you can boot off the OS that's on the emmc you can dd out
the first few MB of the emmc to remove that version of u-boot at which
it would use the one on the mSD without the need of the boot button.
I've had numerous reports of F-27 GA working just fine on the BBB.

Peter

> 2018-03-14 1:58 GMT+09:00 Peter Robinson <pbrobinson(a)gmail.com&gt;:
>> On Tue, Mar 13, 2018 at 1:51 PM, sakurai <sakurai(a)pugpug.org&gt; wrote:
>>> 2018-03-13 8:18 GMT+09:00 Peter Robinson <pbrobinson(a)gmail.com&gt;:
>>>> On Mon, Mar 12, 2018 at 10:47 PM, sakurai <sakurai(a)pugpug.org&gt;
wrote:
>>>>> Hi Peter,
>>>>>
>>>>> Thank you for your prompt comment.
>>>>> I removed uEnv.txt but following message was displayed.
>>>  (snip)
>>>>
>>>> I don't know what you've done to now, you're likely possibly
better
>>>> off starting again with arm-image-installer to setup the image again
>>>> with am335x_evm and then try booting with the boot button held down.
>>>
>>> I tried again using arm-image-installer by following command.
>>>
>>>> fedora-arm-image-installer --image=Fedora-Server-armhfp-27-1.6-sda.raw.xz
--target=am335x_evm --media=/dev/sdd --norootpass --resizefs --addconsole --selinux=off
>>>
>>> Not am335x_boneblack? Anyway I installed using arm335x_evm this time.
>>>
>>> My boot loader may be new because Angstrom will not boot without
>>> holding the boot button.
>>>
>>>> You might also want to give the full output.
>>>
>>> Here is the full output.
>>>
>>> U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14)
>>> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
SoftConn)
>>> musb-hdrc: MHDRC RTL version 2.0
>>> musb-hdrc: setup fifo_mode 4
>>> musb-hdrc: 28/31 max ep, 16384/16384 memory
>>> USB Peripheral mode controller at 47401000 using PIO, IRQ 0
>>> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
SoftConn)
>>> musb-hdrc: MHDRC RTL version 2.0
>>> musb-hdrc: setup fifo_mode 4
>>> musb-hdrc: 28/31 max ep, 16384/16384 memory
>>> USB Host mode controller at 47401800 using PIO, IRQ 0
>>> OMAP SD/MMC: 0
>>> mmc_send_cmd : timeout: No status update
>>> reading u-boot.img
>>> reading u-boot.img
>>>
>>>
>>> U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14)
>>
>> As Dennis had already stated this isn't Fedora's u-boot, what you see
>> is as I would expect, basically the problem here is dealing with the
>> boot button correctly.

[Matthias Runge]

On Mon, Mar 19, 2018 at 05:59:58AM +0000, Peter Robinson wrote:
>  On Sun, Mar 18, 2018 at 12:37 AM, sakurai <sakurai(a)pugpug.org&gt;
> wrote:
>  > Hi Dennis and Peter,
>  >
>  > Of course I tried both pushing button and without it, but the result
>  > was the same.
>  > I remember the specification of the first version of the boot program
>  > was designed  as what you said.
>  > I probably re-programmed the boot program according to the Ubuntu
>  > without pushing the boot button
>  >  in order to boot from SD card.
>  
>  I'm not sure what we can do if you've reprogrammed it, one thing you
>  can do is if you can boot off the OS that's on the emmc you can dd out
>  the first few MB of the emmc to remove that version of u-boot at which
>  it would use the one on the mSD without the need of the boot button.
>  I've had numerous reports of F-27 GA working just fine on the BBB.
>   
/me nods. I'm running F27 on a Beaglebone Black. I did not do anything
specific, other than following the guides (for f21/22/23, don't remember?).
I probably followed this guide[1].
Afterwards, it just works without an issue.

[1]
https://fedoraproject.org/wiki/Architectures/ARM/F21/Installation#For_the...


Matthias
-- 
Matthias Runge <mrunge(a)matthias-runge.de&gt;

[sakurai]

Hi Matthias,

Thank you for your information. I probably did "Copying U-Boot to eMMC
on the BBB" procedure
for Ubuntu in the page what you shown. I will try this later.

-- 
桜井 <sakurai(a)pugpug.org&gt;


2018-03-20 22:39 GMT+09:00 Matthias Runge <mrunge(a)matthias-runge.de&gt;:
> On Mon, Mar 19, 2018 at 05:59:58AM +0000, Peter Robinson wrote:
>> On Sun, Mar 18, 2018 at 12:37 AM, sakurai <sakurai(a)pugpug.org&gt; wrote:
>> > Hi Dennis and Peter,
>> >
>> > Of course I tried both pushing button and without it, but the result
>> > was the same.
>> > I remember the specification of the first version of the boot program
>> > was designed  as what you said.
>> > I probably re-programmed the boot program according to the Ubuntu
>> > without pushing the boot button
>> >  in order to boot from SD card.
>>
>> I'm not sure what we can do if you've reprogrammed it, one thing you
>> can do is if you can boot off the OS that's on the emmc you can dd out
>> the first few MB of the emmc to remove that version of u-boot at which
>> it would use the one on the mSD without the need of the boot button.
>> I've had numerous reports of F-27 GA working just fine on the BBB.
>>
>
> /me nods. I'm running F27 on a Beaglebone Black. I did not do anything
> specific, other than following the guides (for f21/22/23, don't remember?).
> I probably followed this guide[1].
> Afterwards, it just works without an issue.
>
> [1]
https://fedoraproject.org/wiki/Architectures/ARM/F21/Installation#For_the...
>
>
> Matthias
> --
> Matthias Runge <mrunge(a)matthias-runge.de&gt;
> _______________________________________________
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org