Apparently this did not make it to the list. Guess this is because my list membership was not approved yet then.
2015-01-25 11:30 GMT+01:00 Frans Meulenbroeks fransmeulenbroeks@gmail.com:
Hi,
I was trying to see which of the ARM boards I had lying around would boot FC21. I followed these instructions:
http://fedoraproject.org/wiki/Architectures/ARM/F21/Installation
With these I managed to boot FC21 successfully on
- orange pi (A20, similar to banana pi)
- pandaboard
- beaglebone white
However, although according to the instructions the same MLO and u-boot are to be used for beaglebone black, it does not boot there, although the very same card works with beaglebone white. I have added a serial port to the BBB and captured the boot log. See at the end of this message. Anyone an idea what is wrong?
While at it: According to http://fedoraproject.org/wiki/Architectures/ARM/F21/Installation/Hardware_St... beagleboard XM also works but there is no u-boot data in the image for XM. Suggestions for this?
And I noticed the u-boot dir also contains a u-boot for the Mele A1000. I wanted to try that one the A2000 which is identical hw, but it did not work (and I do not have serial for the A2000) Anyone a suggestion.
I also noticed beagleboard being in the uboot folder but it was not listed on the pages referred to above, Should this work?
Lastly I noticed in the image a boot.scr and a boot.cmd file (slightly different). These seem to be some generic code to boot into a number of boards, but I could not find instructions how to use/invoke this. Is that going to be useful for me? How should I use it?
Thanks, Frans
PS: subscription to the list is pending approval, please also reply directly. Thanks.
---- boot log from beaglebone black ----
U-Boot SPL 2013.04-dirty (May 06 2013 - 16:12:47) 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 (May 06 2013 - 16:12:47)
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 ** File not found uEnv.txt ** gpio: pin 55 (gpio 55) value is 1 Failed to mount ext2 filesystem... ** Unrecognized filesystem type **
Hi,
On 26-01-15 08:31, Frans Meulenbroeks wrote:
Apparently this did not make it to the list. Guess this is because my list membership was not approved yet then.
2015-01-25 11:30 GMT+01:00 Frans Meulenbroeks fransmeulenbroeks@gmail.com:
Hi,
I was trying to see which of the ARM boards I had lying around would boot FC21. I followed these instructions:
http://fedoraproject.org/wiki/Architectures/ARM/F21/Installation
With these I managed to boot FC21 successfully on
- orange pi (A20, similar to banana pi)
- pandaboard
- beaglebone white
However, although according to the instructions the same MLO and u-boot are to be used for beaglebone black, it does not boot there, although the very same card works with beaglebone white. I have added a serial port to the BBB and captured the boot log. See at the end of this message. Anyone an idea what is wrong?
While at it: According to http://fedoraproject.org/wiki/Architectures/ARM/F21/Installation/Hardware_St... beagleboard XM also works but there is no u-boot data in the image for XM. Suggestions for this?
And I noticed the u-boot dir also contains a u-boot for the Mele A1000. I wanted to try that one the A2000 which is identical hw, but it did not work (and I do not have serial for the A2000) Anyone a suggestion.
u-boot & the kernel in F-21 do not support hdmi out on A10 devices, however rawhide does, so give rawhide a try with the A1000 u-boot (from rawhide) that should give you video output and hopefully will tell you more.
Regards,
Hans
Hi Hans, all
Took a bit of time, but managed to do a test with Fedora-Xfce-armhfp-rawhide-20150128-sda.raw.xz https://kojipkgs.fedoraproject.org//work/tasks/6681/8756681/Fedora-Xfce-armhfp-rawhide-20150128-sda.raw.xz
I also took the u-boot from that one. Md5sum: 0829a585ac67b135e2a9f0b1a9279c0d u-boot-sunxi-with-spl.bin
I did check both VGA and HDMI but got no output on either ports.
I could ssh into the board with some effort: The information here: https://fedoraproject.org/wiki/Architectures/ARM/F21/Installation#FAQ is incomplete. I also had to disable selinux (the keys I had did not have an selinux context) http://docs.fedoraproject.org/nl-NL/Fedora/11/html/Security-Enhanced_Linux/s...
I also tried startx but it complained that no screens were found.
fpaste of dmesg: http://paste.fedoraproject.org/177436/42252728
fpaste of /proc/devices: http://paste.fedoraproject.org/177437/27367142
If there is any other info you want me to share or additional tests you want me to do, let me know (might take a day or so before I get to it though)
Best regards, Frans
2015-01-26 8:33 GMT+01:00 Hans de Goede hdegoede@redhat.com:
Hi,
On 26-01-15 08:31, Frans Meulenbroeks wrote:
Apparently this did not make it to the list. Guess this is because my list membership was not approved yet then.
2015-01-25 11:30 GMT+01:00 Frans Meulenbroeks < fransmeulenbroeks@gmail.com>:
Hi,
I was trying to see which of the ARM boards I had lying around would boot FC21. I followed these instructions:
http://fedoraproject.org/wiki/Architectures/ARM/F21/Installation
With these I managed to boot FC21 successfully on
- orange pi (A20, similar to banana pi)
- pandaboard
- beaglebone white
However, although according to the instructions the same MLO and u-boot are to be used for beaglebone black, it does not boot there, although the very same card works with beaglebone white. I have added a serial port to the BBB and captured the boot log. See at the end of this message. Anyone an idea what is wrong?
While at it: According to http://fedoraproject.org/wiki/Architectures/ARM/F21/ Installation/Hardware_Status beagleboard XM also works but there is no u-boot data in the image for XM. Suggestions for this?
And I noticed the u-boot dir also contains a u-boot for the Mele A1000. I wanted to try that one the A2000 which is identical hw, but it did not work (and I do not have serial for the A2000) Anyone a suggestion.
u-boot & the kernel in F-21 do not support hdmi out on A10 devices, however rawhide does, so give rawhide a try with the A1000 u-boot (from rawhide) that should give you video output and hopefully will tell you more.
Regards,
Hans
Hi,
On 29-01-15 11:34, Frans Meulenbroeks wrote:
Hi Hans, all
Took a bit of time, but managed to do a test with Fedora-Xfce-armhfp-rawhide-20150128-sda.raw.xz https://kojipkgs.fedoraproject.org//work/tasks/6681/8756681/Fedora-Xfce-armhfp-rawhide-20150128-sda.raw.xz
I also took the u-boot from that one. Md5sum: 0829a585ac67b135e2a9f0b1a9279c0d u-boot-sunxi-with-spl.bin
I did check both VGA and HDMI but got no output on either ports.
I could ssh into the board with some effort: The information here: https://fedoraproject.org/wiki/Architectures/ARM/F21/Installation#FAQ is incomplete. I also had to disable selinux (the keys I had did not have an selinux context) http://docs.fedoraproject.org/nl-NL/Fedora/11/html/Security-Enhanced_Linux/s...
I also tried startx but it complained that no screens were found.
fpaste of dmesg: http://paste.fedoraproject.org/177436/42252728
fpaste of /proc/devices: http://paste.fedoraproject.org/177437/27367142
If there is any other info you want me to share or additional tests you want me to do, let me know (might take a day or so before I get to it though)
To get HDMI out you need to have a hdmi cable plugged in (on both ends) before booting the device, if no cable is detected u-boot will continue without initializing hdmi. Note that the current rawhide u-boot only does 1024x768. Upstream u-boot git master does DDC + EDID and then uses the monitor / tv's native resolution.
Regards,
Hans
Hi Hans,
Thanks for your info.That helped big time. I had the hdmi connected to an alternate input of my monitor and switched monitor input after booting.... I did a quick test booting the board with the monitor input to HDMI and it worked like a charm!
Thanks again, Frans.
PS: looking forward to your talk @ Fosdem.
2015-01-29 12:24 GMT+01:00 Hans de Goede hdegoede@redhat.com:
Hi,
On 29-01-15 11:34, Frans Meulenbroeks wrote:
Hi Hans, all
Took a bit of time, but managed to do a test with Fedora-Xfce-armhfp-rawhide-20150128-sda.raw.xz https://kojipkgs.fedoraproject.org//work/tasks/6681/8756681/Fedora-Xfce- armhfp-rawhide-20150128-sda.raw.xz
I also took the u-boot from that one. Md5sum: 0829a585ac67b135e2a9f0b1a9279c0d u-boot-sunxi-with-spl.bin
I did check both VGA and HDMI but got no output on either ports.
I could ssh into the board with some effort: The information here: https://fedoraproject.org/wiki/Architectures/ARM/F21/Installation#FAQ is incomplete. I also had to disable selinux (the keys I had did not have an selinux context) http://docs.fedoraproject.org/nl-NL/Fedora/11/html/Security- Enhanced_Linux/sect-Security-Enhanced_Linux-Enabling_and_ Disabling_SELinux-Disabling_SELinux.html
I also tried startx but it complained that no screens were found.
fpaste of dmesg: http://paste.fedoraproject.org/177436/42252728
fpaste of /proc/devices: http://paste.fedoraproject.org/177437/27367142
If there is any other info you want me to share or additional tests you want me to do, let me know (might take a day or so before I get to it though)
To get HDMI out you need to have a hdmi cable plugged in (on both ends) before booting the device, if no cable is detected u-boot will continue without initializing hdmi. Note that the current rawhide u-boot only does 1024x768. Upstream u-boot git master does DDC + EDID and then uses the monitor / tv's native resolution.
Regards,
Hans
Forgot to ask: will Rawhide also give me gfx on A20 ? (banana pi)
Thanks, Frans
2015-01-29 22:54 GMT+01:00 Frans Meulenbroeks fransmeulenbroeks@gmail.com:
Hi Hans,
Thanks for your info.That helped big time. I had the hdmi connected to an alternate input of my monitor and switched monitor input after booting.... I did a quick test booting the board with the monitor input to HDMI and it worked like a charm!
Thanks again, Frans.
PS: looking forward to your talk @ Fosdem.
2015-01-29 12:24 GMT+01:00 Hans de Goede hdegoede@redhat.com:
Hi,
On 29-01-15 11:34, Frans Meulenbroeks wrote:
Hi Hans, all
Took a bit of time, but managed to do a test with Fedora-Xfce-armhfp-rawhide-20150128-sda.raw.xz https://kojipkgs.fedoraproject.org//work/tasks/ 6681/8756681/Fedora-Xfce-armhfp-rawhide-20150128-sda.raw.xz
I also took the u-boot from that one. Md5sum: 0829a585ac67b135e2a9f0b1a9279c0d u-boot-sunxi-with-spl.bin
I did check both VGA and HDMI but got no output on either ports.
I could ssh into the board with some effort: The information here: https://fedoraproject.org/wiki/Architectures/ARM/F21/Installation#FAQ is incomplete. I also had to disable selinux (the keys I had did not have an selinux context) http://docs.fedoraproject.org/nl-NL/Fedora/11/html/Security- Enhanced_Linux/sect-Security-Enhanced_Linux-Enabling_and_ Disabling_SELinux-Disabling_SELinux.html
I also tried startx but it complained that no screens were found.
fpaste of dmesg: http://paste.fedoraproject.org/177436/42252728
fpaste of /proc/devices: http://paste.fedoraproject.org/177437/27367142
If there is any other info you want me to share or additional tests you want me to do, let me know (might take a day or so before I get to it though)
To get HDMI out you need to have a hdmi cable plugged in (on both ends) before booting the device, if no cable is detected u-boot will continue without initializing hdmi. Note that the current rawhide u-boot only does 1024x768. Upstream u-boot git master does DDC + EDID and then uses the monitor / tv's native resolution.
Regards,
Hans
----- Original Message -----
Forgot to ask: will Rawhide also give me gfx on A20 ? (banana pi)
I was able to boot the Xfce image from the 29th, initial-setup is displayed on the serial console (text), but once completed I was able to log in and use the GUI on the Banana Pi.
Paul
Thanks, Frans
2015-01-29 22:54 GMT+01:00 Frans Meulenbroeks < fransmeulenbroeks@gmail.com > :
Hi Hans,
Thanks for your info.That helped big time. I had the hdmi connected to an alternate input of my monitor and switched monitor input after booting.... I did a quick test booting the board with the monitor input to HDMI and it worked like a charm!
Thanks again, Frans.
PS: looking forward to your talk @ Fosdem.
2015-01-29 12:24 GMT+01:00 Hans de Goede < hdegoede@redhat.com > :
Hi,
On 29-01-15 11:34, Frans Meulenbroeks wrote:
Hi Hans, all
Took a bit of time, but managed to do a test with Fedora-Xfce-armhfp-rawhide- 20150128-sda.raw.xz < https://kojipkgs. fedoraproject.org//work/tasks/ 6681/8756681/Fedora-Xfce- armhfp-rawhide-20150128-sda. raw.xz >
I also took the u-boot from that one. Md5sum: 0829a585ac67b135e2a9f0b1a9279c 0d u-boot-sunxi-with-spl.bin
I did check both VGA and HDMI but got no output on either ports.
I could ssh into the board with some effort: The information here: https://fedoraproject.org/ wiki/Architectures/ARM/F21/ Installation#FAQ is incomplete. I also had to disable selinux (the keys I had did not have an selinux context) http://docs.fedoraproject.org/ nl-NL/Fedora/11/html/Security- Enhanced_Linux/sect-Security- Enhanced_Linux-Enabling_and_ Disabling_SELinux-Disabling_ SELinux.html
I also tried startx but it complained that no screens were found.
fpaste of dmesg: http://paste.fedoraproject. org/177436/42252728
fpaste of /proc/devices: http://paste.fedoraproject. org/177437/27367142
If there is any other info you want me to share or additional tests you want me to do, let me know (might take a day or so before I get to it though)
To get HDMI out you need to have a hdmi cable plugged in (on both ends) before booting the device, if no cable is detected u-boot will continue without initializing hdmi. Note that the current rawhide u-boot only does 1024x768. Upstream u-boot git master does DDC + EDID and then uses the monitor / tv's native resolution.
Regards,
Hans
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On Mon, Jan 26, 2015 at 7:31 AM, Frans Meulenbroeks fransmeulenbroeks@gmail.com wrote:
Apparently this did not make it to the list. Guess this is because my list membership was not approved yet then.
It doesn't need approval, although you do need to click on the link that's emailed to you once you subscribe.
With these I managed to boot FC21 successfully on
- orange pi (A20, similar to banana pi)
We don't support that as yet.
- pandaboard
- beaglebone white
We support both of those.
However, although according to the instructions the same MLO and u-boot are to be used for beaglebone black, it does not boot there, although the very same card works with beaglebone white.
You need to use beaglebone for all of them
I have added a serial port to the BBB and captured the boot log. See at the end of this message. Anyone an idea what is wrong?
While at it: According to http://fedoraproject.org/wiki/Architectures/ARM/F21/Installation/Hardware_St... beagleboard XM also works but there is no u-boot data in the image for XM. Suggestions for this?
The uboot you need to use for the xM is called beagle although YMMV
And I noticed the u-boot dir also contains a u-boot for the Mele A1000. I wanted to try that one the A2000 which is identical hw, but it did not work (and I do not have serial for the A2000) Anyone a suggestion.
You need a serial port, as for whether they're identical is not something I know.
I also noticed beagleboard being in the uboot folder but it was not listed on the pages referred to above, Should this work?
Lastly I noticed in the image a boot.scr and a boot.cmd file (slightly different). These seem to be some generic code to boot into a number of boards, but I could not find instructions how to use/invoke this. Is that going to be useful for me? How should I use it?
We have a generic kernel, if you have the appropriate DT and a uboot that supports DT it's likely you can make them work.
Thanks, Frans
PS: subscription to the list is pending approval, please also reply directly. Thanks.
No it's not, it made it to the list.
---- boot log from beaglebone black ----
You're booting from the eMMC and it doesn't support the generic distro boot functionality. Hit the button to force it to boot from the mSD card or wipe the first few kb of the eMMC.
Peter
Peter,
Thanks for your reply.
Wrt the orange pi: I know this is not in the list of supported devices. However this one is very compatible to the banana pi so I gave it a stab and it works. (actually things like bananian also works on that board).
Wrt Beaglebone black: that one also works Indeed I had to keep the boot button pressed during poweron (and no: it does not help if you do so during reset).
Wrt mele A2000: this one is identical to A1000, will try with rawhide as suggested by Hans.
Beagle XM: will try later (probably tomorrow), would be nice to see that working too. (btw does a regular beagle also work)?
Best regards, Frans
2015-01-26 9:04 GMT+01:00 Peter Robinson pbrobinson@gmail.com:
On Mon, Jan 26, 2015 at 7:31 AM, Frans Meulenbroeks fransmeulenbroeks@gmail.com wrote:
Apparently this did not make it to the list. Guess this is because my
list
membership was not approved yet then.
It doesn't need approval, although you do need to click on the link that's emailed to you once you subscribe.
With these I managed to boot FC21 successfully on
- orange pi (A20, similar to banana pi)
We don't support that as yet.
- pandaboard
- beaglebone white
We support both of those.
However, although according to the instructions the same MLO and u-boot are to be used for beaglebone black, it does not boot there, although
the
very same card works with beaglebone white.
You need to use beaglebone for all of them
I have added a serial port to the BBB and captured the boot log. See at the end of this message. Anyone an idea what is wrong?
While at it: According to
http://fedoraproject.org/wiki/Architectures/ARM/F21/Installation/Hardware_St...
beagleboard XM also works but there is no u-boot data in the image for
XM.
Suggestions for this?
The uboot you need to use for the xM is called beagle although YMMV
And I noticed the u-boot dir also contains a u-boot for the Mele A1000.
I
wanted to try that one the A2000 which is identical hw, but it did not
work
(and I do not have serial for the A2000) Anyone a suggestion.
You need a serial port, as for whether they're identical is not something I know.
I also noticed beagleboard being in the uboot folder but it was not
listed
on the pages referred to above, Should this work?
Lastly I noticed in the image a boot.scr and a boot.cmd file (slightly different). These seem to be some generic code to boot into a number of boards, but
I
could not find instructions how to use/invoke this. Is that going to be useful for me? How should I use it?
We have a generic kernel, if you have the appropriate DT and a uboot that supports DT it's likely you can make them work.
Thanks, Frans
PS: subscription to the list is pending approval, please also reply directly. Thanks.
No it's not, it made it to the list.
---- boot log from beaglebone black ----
You're booting from the eMMC and it doesn't support the generic distro boot functionality. Hit the button to force it to boot from the mSD card or wipe the first few kb of the eMMC.
Peter
Followup; rewrote the SD card with FC21 for Mele A1000; this also works on A2000 (A2000 is a slightlt different PCB layout Sunxi says on http://linux-sunxi.org/Mele_A1000 " The Mele A1000 has a wedge-like shape whereas the slightly younger A2000 is more square" "All motherboards are essentially the same, apart from tiny revisions"
Best regards, Frans
2015-01-26 20:00 GMT+01:00 Frans Meulenbroeks fransmeulenbroeks@gmail.com:
Peter,
Thanks for your reply.
Wrt the orange pi: I know this is not in the list of supported devices. However this one is very compatible to the banana pi so I gave it a stab and it works. (actually things like bananian also works on that board).
Wrt Beaglebone black: that one also works Indeed I had to keep the boot button pressed during poweron (and no: it does not help if you do so during reset).
Wrt mele A2000: this one is identical to A1000, will try with rawhide as suggested by Hans.
Beagle XM: will try later (probably tomorrow), would be nice to see that working too. (btw does a regular beagle also work)?
Best regards, Frans
2015-01-26 9:04 GMT+01:00 Peter Robinson pbrobinson@gmail.com:
On Mon, Jan 26, 2015 at 7:31 AM, Frans Meulenbroeks fransmeulenbroeks@gmail.com wrote:
Apparently this did not make it to the list. Guess this is because my
list
membership was not approved yet then.
It doesn't need approval, although you do need to click on the link that's emailed to you once you subscribe.
With these I managed to boot FC21 successfully on
- orange pi (A20, similar to banana pi)
We don't support that as yet.
- pandaboard
- beaglebone white
We support both of those.
However, although according to the instructions the same MLO and u-boot are to be used for beaglebone black, it does not boot there, although
the
very same card works with beaglebone white.
You need to use beaglebone for all of them
I have added a serial port to the BBB and captured the boot log. See at the end of this message. Anyone an idea what is wrong?
While at it: According to
http://fedoraproject.org/wiki/Architectures/ARM/F21/Installation/Hardware_St...
beagleboard XM also works but there is no u-boot data in the image for
XM.
Suggestions for this?
The uboot you need to use for the xM is called beagle although YMMV
And I noticed the u-boot dir also contains a u-boot for the Mele
A1000. I
wanted to try that one the A2000 which is identical hw, but it did not
work
(and I do not have serial for the A2000) Anyone a suggestion.
You need a serial port, as for whether they're identical is not something I know.
I also noticed beagleboard being in the uboot folder but it was not
listed
on the pages referred to above, Should this work?
Lastly I noticed in the image a boot.scr and a boot.cmd file (slightly different). These seem to be some generic code to boot into a number of boards,
but I
could not find instructions how to use/invoke this. Is that going to be useful for me? How should I use it?
We have a generic kernel, if you have the appropriate DT and a uboot that supports DT it's likely you can make them work.
Thanks, Frans
PS: subscription to the list is pending approval, please also reply directly. Thanks.
No it's not, it made it to the list.
---- boot log from beaglebone black ----
You're booting from the eMMC and it doesn't support the generic distro boot functionality. Hit the button to force it to boot from the mSD card or wipe the first few kb of the eMMC.
Peter
Follwup: I was unable to boot on beagleboard XM. I used the same offsets to write MLO and u-boot.img as for beaglebone, but apparently this is not ok as MLO is not even loaded. I have also examined another card that does boot and there the MLO also lives at a different location (actually there it is the first file in a VFAT FS, not sure if I can dd it on that same location on the boot filesystem in the FC21 image.
If someone has done this and can provide some suggestions that would be greatly appreciated! Frans
2015-01-26 21:35 GMT+01:00 Frans Meulenbroeks fransmeulenbroeks@gmail.com:
Followup; rewrote the SD card with FC21 for Mele A1000; this also works on A2000 (A2000 is a slightlt different PCB layout Sunxi says on http://linux-sunxi.org/Mele_A1000 " The Mele A1000 has a wedge-like shape whereas the slightly younger A2000 is more square" "All motherboards are essentially the same, apart from tiny revisions"
Best regards, Frans
2015-01-26 20:00 GMT+01:00 Frans Meulenbroeks <fransmeulenbroeks@gmail.com
:
Peter,
Thanks for your reply.
Wrt the orange pi: I know this is not in the list of supported devices. However this one is very compatible to the banana pi so I gave it a stab and it works. (actually things like bananian also works on that board).
Wrt Beaglebone black: that one also works Indeed I had to keep the boot button pressed during poweron (and no: it does not help if you do so during reset).
Wrt mele A2000: this one is identical to A1000, will try with rawhide as suggested by Hans.
Beagle XM: will try later (probably tomorrow), would be nice to see that working too. (btw does a regular beagle also work)?
Best regards, Frans
2015-01-26 9:04 GMT+01:00 Peter Robinson pbrobinson@gmail.com:
On Mon, Jan 26, 2015 at 7:31 AM, Frans Meulenbroeks fransmeulenbroeks@gmail.com wrote:
Apparently this did not make it to the list. Guess this is because my
list
membership was not approved yet then.
It doesn't need approval, although you do need to click on the link that's emailed to you once you subscribe.
With these I managed to boot FC21 successfully on
- orange pi (A20, similar to banana pi)
We don't support that as yet.
- pandaboard
- beaglebone white
We support both of those.
However, although according to the instructions the same MLO and
u-boot
are to be used for beaglebone black, it does not boot there, although
the
very same card works with beaglebone white.
You need to use beaglebone for all of them
I have added a serial port to the BBB and captured the boot log. See
at
the end of this message. Anyone an idea what is wrong?
While at it: According to
http://fedoraproject.org/wiki/Architectures/ARM/F21/Installation/Hardware_St...
beagleboard XM also works but there is no u-boot data in the image
for XM.
Suggestions for this?
The uboot you need to use for the xM is called beagle although YMMV
And I noticed the u-boot dir also contains a u-boot for the Mele
A1000. I
wanted to try that one the A2000 which is identical hw, but it did
not work
(and I do not have serial for the A2000) Anyone a suggestion.
You need a serial port, as for whether they're identical is not something I know.
I also noticed beagleboard being in the uboot folder but it was not
listed
on the pages referred to above, Should this work?
Lastly I noticed in the image a boot.scr and a boot.cmd file (slightly different). These seem to be some generic code to boot into a number of boards,
but I
could not find instructions how to use/invoke this. Is that going to
be
useful for me? How should I use it?
We have a generic kernel, if you have the appropriate DT and a uboot that supports DT it's likely you can make them work.
Thanks, Frans
PS: subscription to the list is pending approval, please also reply directly. Thanks.
No it's not, it made it to the list.
---- boot log from beaglebone black ----
You're booting from the eMMC and it doesn't support the generic distro boot functionality. Hit the button to force it to boot from the mSD card or wipe the first few kb of the eMMC.
Peter
On Mon, Jan 26, 2015 at 4:14 PM, Frans Meulenbroeks fransmeulenbroeks@gmail.com wrote:
Follwup: I was unable to boot on beagleboard XM. I used the same offsets to write MLO and u-boot.img as for beaglebone, but apparently this is not ok as MLO is not even loaded. I have also examined another card that does boot and there the MLO also lives at a different location (actually there it is the first file in a VFAT FS, not sure if I can dd it on that same location on the boot filesystem in the FC21 image.
If someone has done this and can provide some suggestions that would be greatly appreciated!
The omap34xx/omap36xx/DM3730 used on the BeagleBoard classic & xM... Doesn't support RAW mode.. You need to create the vfat and copy the MLO/u-boot.img/etc..
mmc RAW mode boot was added to the bootrom around the omap4 generation timeline. (I believe the dm81xx was the first according to the TI manual, but i don't have a board to confirm that.)
Regards,
On Mon, Jan 26, 2015 at 4:40 PM, Robert Nelson robertcnelson@gmail.com wrote:
On Mon, Jan 26, 2015 at 4:14 PM, Frans Meulenbroeks fransmeulenbroeks@gmail.com wrote:
Follwup: I was unable to boot on beagleboard XM. I used the same offsets to write MLO and u-boot.img as for beaglebone, but apparently this is not ok as MLO is not even loaded. I have also examined another card that does boot and there the MLO also lives at a different location (actually there it is the first file in a VFAT FS, not sure if I can dd it on that same location on the boot filesystem in the FC21 image.
If someone has done this and can provide some suggestions that would be greatly appreciated!
The omap34xx/omap36xx/DM3730 used on the BeagleBoard classic & xM... Doesn't support RAW mode.. You need to create the vfat and copy the MLO/u-boot.img/etc..
One more, side note, u-boot does now support "extX" boot for omap targets, but you'd have to enable this for the BeagleBoard classic/xM..
Regards,
I used the following uEnv.txt to boot the Beagleboard XM rev B. I created a VFAT partition with MLO and u-boot.img on slice 1 and moved all other partitions up to the next slice by deleting/recreating with fdisk -c=dos /dev/(device).
uEnv.txt:
abcboard=omap3-beagle-xm bootpart=0:2 bootfile=boot.scr bootdir=/ uenvcmd=setenv bootargs console=${console} vram=${vram} root=LABEL=_/ ro rootwait cgroup_disable=memory fixrtc earlyprintk; ext2load mmc 0:2 0x82000000 /vmlinuz-3.17.4-301.fc21.armv7hl; ext2load mmc 0:2 0x88080000 /uInitrd-3.17.4-301.fc21.armv7hl; ext2load mmc 0:2 0x88000000 /dtb-3.17.4-301.fc21.armv7hl/omap3-beagle-xm-ab.dtb; bootz 0x82000000 0x88080000 0x88000000
fdisk (64GB SD card; resize2fs used on root):
Device Boot Start End Sectors Size Id Type /dev/mmcblk0p1 * 32 2047 2016 1008K c W95 FAT32 (LBA) /dev/mmcblk0p2 2048 1001471 999424 488M 83 Linux /dev/mmcblk0p3 1001472 2001953 1000482 488.5M 83 Linux /dev/mmcblk0p4 2001954 124735487 122733534 58.5G 83 Linux
On 1/26/15 5:14 PM, Frans Meulenbroeks wrote:
Follwup: I was unable to boot on beagleboard XM. I used the same offsets to write MLO and u-boot.img as for beaglebone, but apparently this is not ok as MLO is not even loaded. I have also examined another card that does boot and there the MLO also lives at a different location (actually there it is the first file in a VFAT FS, not sure if I can dd it on that same location on the boot filesystem in the FC21 image.
If someone has done this and can provide some suggestions that would be greatly appreciated! Frans
2015-01-26 21:35 GMT+01:00 Frans Meulenbroeks <fransmeulenbroeks@gmail.com mailto:fransmeulenbroeks@gmail.com>:
Followup; rewrote the SD card with FC21 for Mele A1000; this also works on A2000 (A2000 is a slightlt different PCB layout Sunxi says on http://linux-sunxi.org/Mele_A1000 " The Mele A1000 has a wedge-like shape whereas the slightly younger A2000 is more square" "All motherboards are essentially the same, apart from tiny revisions" Best regards, Frans 2015-01-26 20:00 GMT+01:00 Frans Meulenbroeks <fransmeulenbroeks@gmail.com <mailto:fransmeulenbroeks@gmail.com>>: Peter, Thanks for your reply. Wrt the orange pi: I know this is not in the list of supported devices. However this one is very compatible to the banana pi so I gave it a stab and it works. (actually things like bananian also works on that board). Wrt Beaglebone black: that one also works Indeed I had to keep the boot button pressed during poweron (and no: it does not help if you do so during reset). Wrt mele A2000: this one is identical to A1000, will try with rawhide as suggested by Hans. Beagle XM: will try later (probably tomorrow), would be nice to see that working too. (btw does a regular beagle also work)? Best regards, Frans 2015-01-26 9:04 GMT+01:00 Peter Robinson <pbrobinson@gmail.com <mailto:pbrobinson@gmail.com>>: On Mon, Jan 26, 2015 at 7:31 AM, Frans Meulenbroeks <fransmeulenbroeks@gmail.com <mailto:fransmeulenbroeks@gmail.com>> wrote: > Apparently this did not make it to the list. Guess this is because my list > membership was not approved yet then. It doesn't need approval, although you do need to click on the link that's emailed to you once you subscribe. >> With these I managed to boot FC21 successfully on >> - orange pi (A20, similar to banana pi) We don't support that as yet. >> - pandaboard >> - beaglebone white We support both of those. >> However, although according to the instructions the same MLO and u-boot >> are to be used for beaglebone black, it does not boot there, although the >> very same card works with beaglebone white. You need to use beaglebone for all of them >> I have added a serial port to the BBB and captured the boot log. See at >> the end of this message. >> Anyone an idea what is wrong? >> >> While at it: >> According to >> http://fedoraproject.org/wiki/Architectures/ARM/F21/Installation/Hardware_Status >> beagleboard XM also works but there is no u-boot data in the image for XM. >> Suggestions for this? The uboot you need to use for the xM is called beagle although YMMV >> And I noticed the u-boot dir also contains a u-boot for the Mele A1000. I >> wanted to try that one the A2000 which is identical hw, but it did not work >> (and I do not have serial for the A2000) >> Anyone a suggestion. You need a serial port, as for whether they're identical is not something I know. >> I also noticed beagleboard being in the uboot folder but it was not listed >> on the pages referred to above, Should this work? >> >> Lastly I noticed in the image a boot.scr and a boot.cmd file (slightly >> different). >> These seem to be some generic code to boot into a number of boards, but I >> could not find instructions how to use/invoke this. Is that going to be >> useful for me? How should I use it? We have a generic kernel, if you have the appropriate DT and a uboot that supports DT it's likely you can make them work. >> Thanks, Frans >> >> PS: subscription to the list is pending approval, please also reply >> directly. Thanks. No it's not, it made it to the list. >> ---- boot log from beaglebone black ---- You're booting from the eMMC and it doesn't support the generic distro boot functionality. Hit the button to force it to boot from the mSD card or wipe the first few kb of the eMMC. Peter
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm