Hi team, I am planning to test Fedora 23 ARM on Beagle Bone black from the early image. So I downloaded Fedora-Xfce-armhfp-23-20150715-sda.raw.xz from http://koji.fedoraproject.org/koji/taskinfo?taskID=10371084 and flash it into a TF card. During the flashing, I find such error: = Writing image complete! = Writing MLO for beaglebone.... dd: failed to open ‘/tmp/root/usr/share/uboot/beaglebone/MLO’: No such file or directory = Writing u-boot.img for beaglebone.... dd: failed to open ‘/tmp/root/usr/share/uboot/beaglebone/u-boot.img’: No such file or directory

= Installation Complete! Insert into the beaglebone and boot. $ And then I just try to boot Beagle Bone Black from the image and find it do not work. The serial output is as following: U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) reading args spl_load_image_fat_os: error reading image args, err - -1 reading u-boot.img reading u-boot.img U-Boot 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - readenv() failed, using default environment 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 gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 0 ** File not found uEnv.txt ** Checking if uenvcmd is set ... uenvcmd was not defined in uEnv.txt ... gpio: pin 56 (gpio 56) value is 0 gpio: pin 55 (gpio 55) value is 0 gpio: pin 54 (gpio 54) value is 0 mmc1(part 0) is current device then it boot to my system on emmc. So am I wrong in some steps? Or the image just can not boot up on Beagle Bone Black by design?

Hi Robert, On 07/16/2015 10:24 PM, Robert Nelson wrote: > On Thu, Jul 16, 2015 at 8:40 AM, Zamir SUN <zsun(a)fedoraproject.org&gt; wrote: >> Hi team, >> I am planning to test Fedora 23 ARM on Beagle Bone black from the early >> image. So I downloaded Fedora-Xfce-armhfp-23-20150715-sda.raw.xz from >> http://koji.fedoraproject.org/koji/taskinfo?taskID=10371084 and flash it >> into a TF card. >> >> During the flashing, I find such error: >> >> = Writing image complete! >> = Writing MLO for beaglebone.... >> dd: failed to open ‘/tmp/root/usr/share/uboot/beaglebone/MLO’: No such >> file >> or directory >> = Writing u-boot.img for beaglebone.... >> dd: failed to open ‘/tmp/root/usr/share/uboot/beaglebone/u-boot.img’: No >> such file or directory > > Looks like your task above, missed these crucial boot files.. > Thanks for your reminder. I checked and find that on F22 the file lies in beaglebone, but in F23 the directory is renamed to am335x_boneblack so the fedora-arm-installer script no longer works. I will manually finish the steps and continue my testing.

> >> >> = Installation Complete! Insert into the beaglebone and boot. >> $ >> And then I just try to boot Beagle Bone Black from the image and find it >> do >> not work. The serial output is as following: >> U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) >> reading args >> spl_load_image_fat_os: error reading image args, err - -1 >> reading u-boot.img >> reading u-boot.img >> >> >> U-Boot 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) >> >> I2C: ready >> DRAM: 512 MiB >> NAND: 0 MiB >> MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 >> *** Warning - readenv() failed, using default environment >> >> 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 >> gpio: pin 54 (gpio 54) value is 1 >> SD/MMC found on device 0 >> ** File not found uEnv.txt ** >> Checking if uenvcmd is set ... >> >> uenvcmd was not defined in uEnv.txt ... >> gpio: pin 56 (gpio 56) value is 0 >> gpio: pin 55 (gpio 55) value is 0 >> gpio: pin 54 (gpio 54) value is 0 >> mmc1(part 0) is current device >> >> then it boot to my system on emmc. So am I wrong in some steps? Or the >> image >> just can not boot up on Beagle Bone Black by design? > > That old factory bootloader in the eMMC doesn't know about how to deal > with newer extlinux image's. > > Regards, > -- Zamir SUN zsun(a)fedoraproject.org zsun in #fedora-zh #openshift on freenode.net _______________________________________________ arm mailing list arm(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm

On 07/17/2015 01:10 AM, Paul Whalen wrote: > ----- Original Message ----- >> Hi Robert, >> >> On 07/16/2015 10:24 PM, Robert Nelson wrote: >>> On Thu, Jul 16, 2015 at 8:40 AM, Zamir SUN <zsun(a)fedoraproject.org&gt; >>> wrote: >>>> Hi team, >>>> I am planning to test Fedora 23 ARM on Beagle Bone black from the >>>> early >>>> image. So I downloaded Fedora-Xfce-armhfp-23-20150715-sda.raw.xz from >>>> http://koji.fedoraproject.org/koji/taskinfo?taskID=10371084 and >>>> flash it >>>> into a TF card. >>>> >>>> During the flashing, I find such error: >>>> >>>> = Writing image complete! >>>> = Writing MLO for beaglebone.... >>>> dd: failed to open ‘/tmp/root/usr/share/uboot/beaglebone/MLO’: No such >>>> file >>>> or directory >>>> = Writing u-boot.img for beaglebone.... >>>> dd: failed to open >>>> ‘/tmp/root/usr/share/uboot/beaglebone/u-boot.img’: No >>>> such file or directory >>> >>> Looks like your task above, missed these crucial boot files.. >>> >> Thanks for your reminder. >> I checked and find that on F22 the file lies in beaglebone, but in F23 >> the directory is renamed to am335x_boneblack so the fedora-arm-installer >> script no longer works. >> >> I will manually finish the steps and continue my testing. > Hi Paul, > There is a new version of the script in rawhide, you can also created > a symlink > and use the new name. > > There are few others things that might be missing like serial console > detection, > so will likely need to add that to the extlinux.conf. > > So far in my testing the 4.2 kernel seems to have an issue with mSD, > but does find > the eMMC on the beaglebone black. Let us know how it goes for you! > Yes I find it can not boot and just fall back to dracut. I even tried to switch to another TF card to make sure it is not caused by the card, but the result is the same. I was planning to have a confirm today and then saw your reply. So do you have a bug id for this so that I can post my log there? And here is my log http://paste.fedoraproject.org/245362/ Zamir > Paul > > >> >>> >>>> >>>> = Installation Complete! Insert into the beaglebone and boot. >>>> $ >>>> And then I just try to boot Beagle Bone Black from the image and >>>> find it >>>> do >>>> not work. The serial output is as following: >>>> U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) >>>> reading args >>>> spl_load_image_fat_os: error reading image args, err - -1 >>>> reading u-boot.img >>>> reading u-boot.img >>>> >>>> >>>> U-Boot 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) >>>> >>>> I2C: ready >>>> DRAM: 512 MiB >>>> NAND: 0 MiB >>>> MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 >>>> *** Warning - readenv() failed, using default environment >>>> >>>> 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 >>>> gpio: pin 54 (gpio 54) value is 1 >>>> SD/MMC found on device 0 >>>> ** File not found uEnv.txt ** >>>> Checking if uenvcmd is set ... >>>> >>>> uenvcmd was not defined in uEnv.txt ... >>>> gpio: pin 56 (gpio 56) value is 0 >>>> gpio: pin 55 (gpio 55) value is 0 >>>> gpio: pin 54 (gpio 54) value is 0 >>>> mmc1(part 0) is current device >>>> >>>> then it boot to my system on emmc. So am I wrong in some steps? Or the >>>> image >>>> just can not boot up on Beagle Bone Black by design? >>> >>> That old factory bootloader in the eMMC doesn't know about how to deal >>> with newer extlinux image's. >>> >>> Regards, >>> >> >> -- >> Zamir SUN >> zsun(a)fedoraproject.org >> zsun in #fedora-zh #openshift on freenode.net >> _______________________________________________ >> arm mailing list >> arm(a)lists.fedoraproject.org >> https://admin.fedoraproject.org/mailman/listinfo/arm

On Tue, Jul 21, 2015 at 2:30 PM, Zamir SUN <zsun(a)fedoraproject.org&gt; wrote: > Just an update that the problem (can not boot into TF card) still happens on > Fedora-Xfce-armhfp-23-20150720 (4.2.0-0.rc2.git2.1.fc23). Can you retry a newer image, anything post Jul 22nd should be fine. I've dropped all the non-upstream patches we were carrying (from Robert's repo) just in case they were causing issues. In terms of features I'm not sure they give us much, for me (minimal install on eMMC) they work and fix a crash I was seeing with SPI. If it still fails can you fpaste the entire boot output (u-boot and kernel) please? Peter > On 07/17/2015 08:55 PM, Zamir SUN wrote: >> >> >> >> On 07/17/2015 01:10 AM, Paul Whalen wrote: >>> >>> ----- Original Message ----- >>>> >>>> Hi Robert, >>>> >>>> On 07/16/2015 10:24 PM, Robert Nelson wrote: >>>>> >>>>> On Thu, Jul 16, 2015 at 8:40 AM, Zamir SUN <zsun(a)fedoraproject.org&gt; >>>>> wrote: >>>>>> >>>>>> Hi team, >>>>>> I am planning to test Fedora 23 ARM on Beagle Bone black from the >>>>>> early >>>>>> image. So I downloaded Fedora-Xfce-armhfp-23-20150715-sda.raw.xz from >>>>>> http://koji.fedoraproject.org/koji/taskinfo?taskID=10371084 and >>>>>> flash it >>>>>> into a TF card. >>>>>> >>>>>> During the flashing, I find such error: >>>>>> >>>>>> = Writing image complete! >>>>>> = Writing MLO for beaglebone.... >>>>>> dd: failed to open ‘/tmp/root/usr/share/uboot/beaglebone/MLO’: No such >>>>>> file >>>>>> or directory >>>>>> = Writing u-boot.img for beaglebone.... >>>>>> dd: failed to open >>>>>> ‘/tmp/root/usr/share/uboot/beaglebone/u-boot.img’: No >>>>>> such file or directory >>>>> >>>>> >>>>> Looks like your task above, missed these crucial boot files.. >>>>> >>>> Thanks for your reminder. >>>> I checked and find that on F22 the file lies in beaglebone, but in F23 >>>> the directory is renamed to am335x_boneblack so the fedora-arm-installer >>>> script no longer works. >>>> >>>> I will manually finish the steps and continue my testing. >>> >>> >> Hi Paul, >>> >>> There is a new version of the script in rawhide, you can also created >>> a symlink >>> and use the new name. >>> >>> There are few others things that might be missing like serial console >>> detection, >>> so will likely need to add that to the extlinux.conf. >>> >>> So far in my testing the 4.2 kernel seems to have an issue with mSD, >>> but does find >>> the eMMC on the beaglebone black. Let us know how it goes for you! >>> >> Yes I find it can not boot and just fall back to dracut. I even tried to >> switch to another TF card to make sure it is not caused by the card, but >> the result is the same. I was planning to have a confirm today and then >> saw your reply. So do you have a bug id for this so that I can post my >> log there? >> >> And here is my log http://paste.fedoraproject.org/245362/ >> >> Zamir >> >> >>> Paul >>> >>> >>>> >>>>> >>>>>> >>>>>> = Installation Complete! Insert into the beaglebone and boot. >>>>>> $ >>>>>> And then I just try to boot Beagle Bone Black from the image and >>>>>> find it >>>>>> do >>>>>> not work. The serial output is as following: >>>>>> U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) >>>>>> reading args >>>>>> spl_load_image_fat_os: error reading image args, err - -1 >>>>>> reading u-boot.img >>>>>> reading u-boot.img >>>>>> >>>>>> >>>>>> U-Boot 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) >>>>>> >>>>>> I2C: ready >>>>>> DRAM: 512 MiB >>>>>> NAND: 0 MiB >>>>>> MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 >>>>>> *** Warning - readenv() failed, using default environment >>>>>> >>>>>> 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 >>>>>> gpio: pin 54 (gpio 54) value is 1 >>>>>> SD/MMC found on device 0 >>>>>> ** File not found uEnv.txt ** >>>>>> Checking if uenvcmd is set ... >>>>>> >>>>>> uenvcmd was not defined in uEnv.txt ... >>>>>> gpio: pin 56 (gpio 56) value is 0 >>>>>> gpio: pin 55 (gpio 55) value is 0 >>>>>> gpio: pin 54 (gpio 54) value is 0 >>>>>> mmc1(part 0) is current device >>>>>> >>>>>> then it boot to my system on emmc. So am I wrong in some steps? Or the >>>>>> image >>>>>> just can not boot up on Beagle Bone Black by design? >>>>> >>>>> >>>>> That old factory bootloader in the eMMC doesn't know about how to deal >>>>> with newer extlinux image's. >>>>> >>>>> Regards, >>>>> >>>>

> We tried the 20150724 minimal image with newer uboot. However, it will stay > in "Starting kernel ..." for over 2 hours now. Can you edit the extlinux/extlinux.conf file on the boot partition. Add "console=ttyO0" to the end of the line that begins with append and see if it helps on the console output.

> And Tonghui just remind me that, both of us are using BeagleBone Black Rev. > C. It shouldn't make any difference, all mine are A5 from memory. > $ sha256sum Fedora-Minimal-armhfp-23-20150724-sda.raw.xz > c0adb38849018bd0e6a2ebf5312c2e2ab4527371e824fc219bc1317c4af3fb85 > Fedora-Minimal-armhfp-23-20150724-sda.raw.xz > > minicom output > > U-Boot 2015.07 (Jul 16 2015 - 16:35:19 +0000) > > Watchdog enabled > I2C: ready > DRAM: 512 MiB > MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 > *** Warning - bad CRC, using default environment > > Net: <ethaddr> not set. Validating first E-fuse MAC > Phy 0 not found > cpsw, usb_ether > Hit any key to stop autoboot: 0 > switch to partitions #0, OK > mmc0 is current device > Scanning mmc 0:1... > Found /extlinux/extlinux.conf > Retrieving file: /extlinux/extlinux.conf > 560 bytes read in 12 ms (44.9 KiB/s) > Ignoring unknown command: ui > Ignoring malformed menu command: autoboot > Ignoring malformed menu command: hidden > Ignoring unknown command: totaltimeout > Fedora-Minimal-armhfp-23-20150724 Boot Options. > 1: Fedora-Minimal-armhfp-23-20150724 (4.2.0-0.rc3.git3.1.fc23.armv7hl) > Enter choice: 1: Fedora-Minimal-armhfp-23-20150724 > (4.2.0-0.rc3.git3.1.fc23.armv7hl) > Retrieving file: /initramfs-4.2.0-0.rc3.git3.1.fc23.armv7hl.img > 38345269 bytes read in 2094 ms (17.5 MiB/s) > Retrieving file: /vmlinuz-4.2.0-0.rc3.git3.1.fc23.armv7hl > 5797256 bytes read in 329 ms (16.8 MiB/s) > append: ro root=UUID=4dae36bb-26da-473b-b8cc-fc2a87cd7923 > Retrieving file: /dtb-4.2.0-0.rc3.git3.1.fc23.armv7hl/am335x-boneblack.dtb > 31013 bytes read in 24 ms (1.2 MiB/s) > Kernel image @ 0x82000000 [ 0x000000 - 0x587588 ] > ## Flattened Device Tree blob at 88000000 > Booting using the fdt blob at 0x88000000 > Loading Ramdisk to 8db6e000, end 8ffffa35 ... OK > Loading Device Tree to 8db63000, end 8db6d924 ... OK > > Starting kernel ... > > > > > On 07/24/2015 09:59 PM, Peter Robinson wrote: >> >> On Tue, Jul 21, 2015 at 2:30 PM, Zamir SUN <zsun(a)fedoraproject.org&gt; wrote: >>> >>> Just an update that the problem (can not boot into TF card) still happens >>> on >>> Fedora-Xfce-armhfp-23-20150720 (4.2.0-0.rc2.git2.1.fc23). >> >> >> Can you retry a newer image, anything post Jul 22nd should be fine. >> >> I've dropped all the non-upstream patches we were carrying (from >> Robert's repo) just in case they were causing issues. In terms of >> features I'm not sure they give us much, for me (minimal install on >> eMMC) they work and fix a crash I was seeing with SPI. >> >> If it still fails can you fpaste the entire boot output (u-boot and >> kernel) please? >> >> Peter >> >>> On 07/17/2015 08:55 PM, Zamir SUN wrote: >>>> >>>> >>>> >>>> >>>> On 07/17/2015 01:10 AM, Paul Whalen wrote: >>>>> >>>>> >>>>> ----- Original Message ----- >>>>>> >>>>>> >>>>>> Hi Robert, >>>>>> >>>>>> On 07/16/2015 10:24 PM, Robert Nelson wrote: >>>>>>> >>>>>>> >>>>>>> On Thu, Jul 16, 2015 at 8:40 AM, Zamir SUN <zsun(a)fedoraproject.org&gt; >>>>>>> wrote: >>>>>>>> >>>>>>>> >>>>>>>> Hi team, >>>>>>>> I am planning to test Fedora 23 ARM on Beagle Bone black from the >>>>>>>> early >>>>>>>> image. So I downloaded Fedora-Xfce-armhfp-23-20150715-sda.raw.xz >>>>>>>> from >>>>>>>> http://koji.fedoraproject.org/koji/taskinfo?taskID=10371084 and >>>>>>>> >>>>>>>> flash it >>>>>>>> into a TF card. >>>>>>>> >>>>>>>> During the flashing, I find such error: >>>>>>>> >>>>>>>> = Writing image complete! >>>>>>>> = Writing MLO for beaglebone.... >>>>>>>> dd: failed to open ‘/tmp/root/usr/share/uboot/beaglebone/MLO’: No >>>>>>>> such >>>>>>>> file >>>>>>>> or directory >>>>>>>> = Writing u-boot.img for beaglebone.... >>>>>>>> dd: failed to open >>>>>>>> ‘/tmp/root/usr/share/uboot/beaglebone/u-boot.img’: No >>>>>>>> such file or directory >>>>>>> >>>>>>> >>>>>>> >>>>>>> Looks like your task above, missed these crucial boot files.. >>>>>>> >>>>>> Thanks for your reminder. >>>>>> I checked and find that on F22 the file lies in beaglebone, but in F23 >>>>>> the directory is renamed to am335x_boneblack so the >>>>>> fedora-arm-installer >>>>>> script no longer works. >>>>>> >>>>>> I will manually finish the steps and continue my testing. >>>>> >>>>> >>>>> >>>> Hi Paul, >>>>> >>>>> >>>>> There is a new version of the script in rawhide, you can also created >>>>> a symlink >>>>> and use the new name. >>>>> >>>>> There are few others things that might be missing like serial console >>>>> detection, >>>>> so will likely need to add that to the extlinux.conf. >>>>> >>>>> So far in my testing the 4.2 kernel seems to have an issue with mSD, >>>>> but does find >>>>> the eMMC on the beaglebone black. Let us know how it goes for you! >>>>> >>>> Yes I find it can not boot and just fall back to dracut. I even tried to >>>> switch to another TF card to make sure it is not caused by the card, but >>>> the result is the same. I was planning to have a confirm today and then >>>> saw your reply. So do you have a bug id for this so that I can post my >>>> log there? >>>> >>>> And here is my log http://paste.fedoraproject.org/245362/ >>>> >>>> >>>> Zamir >>>> >>>> >>>>> Paul >>>>> >>>>> >>>>>> >>>>>>> >>>>>>>> >>>>>>>> = Installation Complete! Insert into the beaglebone and boot. >>>>>>>> $ >>>>>>>> And then I just try to boot Beagle Bone Black from the image and >>>>>>>> find it >>>>>>>> do >>>>>>>> not work. The serial output is as following: >>>>>>>> U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) >>>>>>>> reading args >>>>>>>> spl_load_image_fat_os: error reading image args, err - -1 >>>>>>>> reading u-boot.img >>>>>>>> reading u-boot.img >>>>>>>> >>>>>>>> >>>>>>>> U-Boot 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) >>>>>>>> >>>>>>>> I2C: ready >>>>>>>> DRAM: 512 MiB >>>>>>>> NAND: 0 MiB >>>>>>>> MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 >>>>>>>> *** Warning - readenv() failed, using default environment >>>>>>>> >>>>>>>> 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 >>>>>>>> gpio: pin 54 (gpio 54) value is 1 >>>>>>>> SD/MMC found on device 0 >>>>>>>> ** File not found uEnv.txt ** >>>>>>>> Checking if uenvcmd is set ... >>>>>>>> >>>>>>>> uenvcmd was not defined in uEnv.txt ... >>>>>>>> gpio: pin 56 (gpio 56) value is 0 >>>>>>>> gpio: pin 55 (gpio 55) value is 0 >>>>>>>> gpio: pin 54 (gpio 54) value is 0 >>>>>>>> mmc1(part 0) is current device >>>>>>>> >>>>>>>> then it boot to my system on emmc. So am I wrong in some steps? Or >>>>>>>> the >>>>>>>> image >>>>>>>> just can not boot up on Beagle Bone Black by design? >>>>>>> >>>>>>> >>>>>>> >>>>>>> That old factory bootloader in the eMMC doesn't know about how to >>>>>>> deal >>>>>>> with newer extlinux image's. >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>> > > -- > Zamir SUN > zsun(a)fedoraproject.org > zsun in #fedora-zh #openshift on freenode.net