Re: Can rawhide image boot on Beagle Bone Black?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Robert,

On 07/16/2015 10:24 PM, Robert Nelson wrote:
On Thu, Jul 16, 2015 at 8:40 AM, Zamir SUN <zsun@xxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxx
zsun in #fedora-zh #openshift on freenode.net
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux ARM (Vger)]     [Linux ARM]     [ARM Kernel]     [Fedora User Discussion]     [Older Fedora Users Discussion]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

Powered by Linux