[opensuse-arm] Beaglebone black 13.1 JEOS
Is the JEOS for the Beaglebone suitable for the Beaglebone Black? Specifically as found on this page.
http://download.opensuse.org/ports/armv7hl/distribution/13.1/appliances/
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
I think this image is for beaglebone black. Not sure if it suitable for beaglebone. Guillaume Le 28/02/2014 09:23, lists a écrit :
Is the JEOS for the Beaglebone suitable for the Beaglebone Black? Specifically as found on this page.
http://download.opensuse.org/ports/armv7hl/distribution/13.1/appliances/
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 28.02.2014 14:40, Guillaume Gardet wrote:
I think this image is for beaglebone black. Not sure if it suitable for beaglebone.
They are supposed to be suitable both for beaglebone and beaglebone black. They are utilizing the same TI platform: http://beagleboard.org/products/beaglebone http://beagleboard.org/Products/BeagleBone%20Black The images are known to be not working on beaglebone black, because my patches have not been accepted for 13.1 tree yet. If you want to run JeOS on beaglebone black, please use this one: https://build.opensuse.org/package/show/home:matwey:beaglebone/JeOS-beaglebo... -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Le 28/02/2014 14:41, Matwey V. Kornilov a écrit :
On 28.02.2014 14:40, Guillaume Gardet wrote:
I think this image is for beaglebone black. Not sure if it suitable for beaglebone.
They are supposed to be suitable both for beaglebone and beaglebone black. They are utilizing the same TI platform:
http://beagleboard.org/products/beaglebone http://beagleboard.org/Products/BeagleBone%20Black
The images are known to be not working on beaglebone black, because my patches have not been accepted for 13.1 tree yet.
Which patches are needed? u-boot, kernel, others? Did you create submit requests? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 28.02.2014 17:47, Guillaume Gardet wrote:
Which patches are needed? u-boot, kernel, others?
Did you create submit requests?
Patches to the kernel-source, http://lists.opensuse.org/opensuse-kernel/2014-01/msg00031.html maybe I did something wrong... -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
28.02.2014 18:08, Matwey V. Kornilov пишет:
On 28.02.2014 17:47, Guillaume Gardet wrote:
Which patches are needed? u-boot, kernel, others?
Did you create submit requests?
Patches to the kernel-source,
http://lists.opensuse.org/opensuse-kernel/2014-01/msg00031.html
maybe I did something wrong...
Forget this, they seem to be applied. I will go to test the image. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Fri, 28 Feb 2014 20:01:11 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
28.02.2014 18:08, Matwey V. Kornilov пишет:
On 28.02.2014 17:47, Guillaume Gardet wrote:
Which patches are needed? u-boot, kernel, others?
Did you create submit requests?
Patches to the kernel-source,
http://lists.opensuse.org/opensuse-kernel/2014-01/msg00031.html
maybe I did something wrong...
Forget this, they seem to be applied. I will go to test the image.
I can't seem to get it to work. I assume you have to SSH into it. Nothing on the HDMI display. It doesn't show up in a nmap. As a sanity check, I loaded an Ubuntu image image on a SDHC and it does work in the BeagleBone Black. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
01.03.2014 12:07, lists пишет:
I can't seem to get it to work. I assume you have to SSH into it. Nothing on the HDMI display. It doesn't show up in a nmap.
As any other JeOSes from Ports the image has interactive yast2-firstboot, you have to have serial console connection at the first boot, to set the root password, create the users, and configure the network. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sat, 01 Mar 2014 14:15:23 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
01.03.2014 12:07, lists пишет:
I can't seem to get it to work. I assume you have to SSH into it. Nothing on the HDMI display. It doesn't show up in a nmap.
As any other JeOSes from Ports the image has interactive yast2-firstboot, you have to have serial console connection at the first boot, to set the root password, create the users, and configure the network.
The Beaglebone Black doesn't have a real serial port. It requires a special usb cable/chip. I'm trying not to be negative here, but I think this won't be accepted well by the beaglebone users. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sat, 1 Mar 2014 02:48:41 -0800 lists <lists@lazygranch.com> wrote:
On Sat, 01 Mar 2014 14:15:23 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
01.03.2014 12:07, lists пишет:
I can't seem to get it to work. I assume you have to SSH into it. Nothing on the HDMI display. It doesn't show up in a nmap.
As any other JeOSes from Ports the image has interactive yast2-firstboot, you have to have serial console connection at the first boot, to set the root password, create the users, and configure the network.
The Beaglebone Black doesn't have a real serial port. It requires a special usb cable/chip. I'm trying not to be negative here, but I think this won't be accepted well by the beaglebone users.
I got the FTDI cable today. This is the text from the serial port when attempting to use opensuse JEOS: --------------------------------------------------------------------------------- \0x00 U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53) 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 (Jul 10 2013 - 14:02:53) 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: 1 \0x08\0x08\0x08 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 ** File not found /boot/uImage ** U-Boot# --------------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sat, 1 Mar 2014 02:48:41 -0800 lists <lists@lazygranch.com> wrote:
On Sat, 01 Mar 2014 14:15:23 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
01.03.2014 12:07, lists пишет:
I can't seem to get it to work. I assume you have to SSH into it. Nothing on the HDMI display. It doesn't show up in a nmap.
As any other JeOSes from Ports the image has interactive yast2-firstboot, you have to have serial console connection at the first boot, to set the root password, create the users, and configure the network.
The Beaglebone Black doesn't have a real serial port. It requires a special usb cable/chip. I'm trying not to be negative here, but I think this won't be accepted well by the beaglebone users. I got the FTDI cable today. This is the text from the serial port when attempting to use opensuse JEOS:
\0x00 U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53) 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 (Jul 10 2013 - 14:02:53)
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: 1 \0x08\0x08\0x08 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 ** File not found /boot/uImage ** U-Boot# --------------------------------------------------------------- I have seen that error on my bone. I always have to hold the boot button (or whatever its called), before plugging in the power and hold it till
Am 09.03.2014 07:07, schrieb lists: the kernel is loaded. Then it finds the uEnv.txt properly. What I think is happening: the bone (or uboot) doesn't find the sdcard and is looking just at the internal emmc. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sun, 09 Mar 2014 12:38:02 +0100 Josua Mayer <josua.mayer97@gmail.com> wrote:
On Sat, 1 Mar 2014 02:48:41 -0800 lists <lists@lazygranch.com> wrote:
On Sat, 01 Mar 2014 14:15:23 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
01.03.2014 12:07, lists пишет:
I can't seem to get it to work. I assume you have to SSH into it. Nothing on the HDMI display. It doesn't show up in a nmap.
As any other JeOSes from Ports the image has interactive yast2-firstboot, you have to have serial console connection at the first boot, to set the root password, create the users, and configure the network.
The Beaglebone Black doesn't have a real serial port. It requires a special usb cable/chip. I'm trying not to be negative here, but I think this won't be accepted well by the beaglebone users. I got the FTDI cable today. This is the text from the serial port when attempting to use opensuse JEOS:
\0x00 U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53) 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 (Jul 10 2013 - 14:02:53)
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: 1 \0x08\0x08\0x08 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 ** File not found /boot/uImage ** U-Boot# --------------------------------------------------------------- I have seen that error on my bone. I always have to hold the boot button (or whatever its called), before plugging in the power and hold it till the kernel is loaded. Then it finds the uEnv.txt
Am 09.03.2014 07:07, schrieb lists: properly. What I think is happening: the bone (or uboot) doesn't find the sdcard and is looking just at the internal emmc.
You have to hold that boot button once to get the Beaglebone Black into a mode where it looks for the SDHC. Once you do it, you shouldn't have to do it again. Well that is the plan. Check out
http://shrkey.com/setting-up-beaglebone-black-to-boot-off-the-microsd-card/
I have some other distributions on SDHC and they boot just fine. Minix is another disty that doesn't come up with networking, i.e. you have to use the serial port. I have run that in the board as well as Ubuntu. I overwrote the ubuntu for the JEOS, but here is the serial output for the minix booting. I am not holding the boot button down. --------------------------------------------------------------------- ---------------------------------------------------------------------- \0x00\0x07\0x00 U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53) 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 (Jul 10 2013 - 14:02:53) 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: 1 \0x08\0x08\0x08 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 1336 bytes read in 3 ms (434.6 KiB/s) Loaded environment from uEnv.txt Importing environment from mmc ... Running uenvcmd ... starting from MMC mmc - MMC sub system Usage: mmc read addr blk# cnt mmc write addr blk# cnt mmc erase blk# cnt mmc rescan mmc part - lists available partition on current mmc device mmc dev [dev] [part] - show or set current mmc device [partition] mmc list - lists available devices mmc rstn - enable hardware reset of emmc reading kernel.bin 256932 bytes read in 33 ms (7.4 MiB/s) reading ds.elf 60436 bytes read in 10 ms (5.8 MiB/s) reading rs.elf 80476 bytes read in 13 ms (5.9 MiB/s) reading pm.elf 57192 bytes read in 10 ms (5.5 MiB/s) reading sched.elf 30500 bytes read in 8 ms (3.6 MiB/s) reading vfs.elf 138284 bytes read in 19 ms (6.9 MiB/s) reading memory.elf 2496380 bytes read in 287 ms (8.3 MiB/s) reading log.elf 38736 bytes read in 9 ms (4.1 MiB/s) reading tty.elf 46940 bytes read in 9 ms (5 MiB/s) reading mfs.elf 84036 bytes read in 13 ms (6.2 MiB/s) reading vm.elf 149008 bytes read in 21 ms (6.8 MiB/s) reading pfs.elf 238796 bytes read in 31 ms (7.3 MiB/s) reading init.elf 171636 bytes read in 23 ms (7.1 MiB/s) Unknown command 'dcache' - try 'help' Unknown command 'icache' - try 'help' console=tty00 rootdevname=c0d0p1 verbose=3 hz=1000 filemap=0 board_name=A335BNLT ## Starting application at 0x80200000 ... MINIX booting cstart intr_init(0) main() initializing asyncm... done initializing idle... done initializing clock... done initializing system... done initializing kernel... done initializing ds... done initializing rs... done initializing pm... done initializing sched... done initializing vfs... done initializing memory... done initializing log... done initializing tty... done initializing mfs... done initializing vm... done initializing pfs... done initializing init... done system_init()... done MINIX 3.2.1. Copyright 2012, Vrije Universiteit, Amsterdam, The Netherlands MINIX is open source software, see http://www.minix3.org cycles_accounting_init()... done IRQ 72 handler registered by tty / 5 Started VFS: 8 worker thread(s) Starting the mmc driver mmc_block(info)Initializing the MMC block device mmc_host_mmchs(info)Using instance number 0 IRQ 64 handler registered by mmc / 73129 mmc_block(info)System event framework fresh start Root device name is /dev/c0d0p1 mmc_host_mmchs(info)Enabling high speed mode /dev/c0d0p1: clean mmc_host_mmchs(info)Enabling high speed mode mmc_host_mmchs(info)Enabling high speed mode /dev/c0d0p1 is mounted on / none is mounted on /proc /dev/c0d0p2: clean /dev/c0d0p3: clean size on /dev/imgrd set to 0kB Multiuser startup in progress ... Starting services: randomIRQ 41 handler registered by lan8710a / 73138 IRQ 42 handler registered by lan8710a / 73138 lan8710a inet ipc. Starting daemons: update cron syslogd. Starting i2c subsystem: IRQ 70 handler registered by i2c / 73141 i2cIRQ 71 handler registered by i2c / 73142 i2cIRQ 30 handler registered by i2c / 73143 i2c. Running on a BeagleBone Black Starting i2c device drivers: cat24c256IRQ 7 handler registered by tps65217 / 73145 tps65217 tda19988. Starting networking: dhcpd nonamed shell telnet ftp finger. Local packages (start): done. Minix Release 3 Version 2.1 (console) beaglebone login: ---------------------------------------------------------------------------- ------------------------------------------------------------------------------ Yeah, I know, I should use pastebin for this. Anyway, it find Minix on the Beaglebone Black just fine. If you had to put that button all the time to get it to read the SDHC, then the SBC would certainly not be very stand alone. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
09.03.2014 10:07, lists пишет:
U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53)
You are booting from wrong media -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Mon, 10 Mar 2014 13:32:04 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
09.03.2014 10:07, lists пишет:
U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53)
You are booting from wrong media
Can you elaborate? For instance, are you saying I downloaded the wrong image file? If so, where can the correct image file be found. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 11.03.2014 07:19, lists wrote:
On Mon, 10 Mar 2014 13:32:04 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
09.03.2014 10:07, lists пишет:
U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53)
You are booting from wrong media
Can you elaborate? For instance, are you saying I downloaded the wrong image file? If so, where can the correct image file be found.
Beaglebone is equipped with internal eMMC memory and external SD card reader. My instance of beaglebone's internal MMC was flashed with Angstrom linux. Proprietary low-level bootloader is able to read second level boot-loader from any of them (but eMMC is by default). u-boot version in your log is definitely not from the opensuse image. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Tue, 11 Mar 2014 17:01:21 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
On 11.03.2014 07:19, lists wrote:
On Mon, 10 Mar 2014 13:32:04 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
09.03.2014 10:07, lists пишет:
U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53)
You are booting from wrong media
Can you elaborate? For instance, are you saying I downloaded the wrong image file? If so, where can the correct image file be found.
Beaglebone is equipped with internal eMMC memory and external SD card reader. My instance of beaglebone's internal MMC was flashed with Angstrom linux. Proprietary low-level bootloader is able to read second level boot-loader from any of them (but eMMC is by default).
u-boot version in your log is definitely not from the opensuse image.
How do you explain the Beaglebone Black booting from Minix and Ubuntu but not the JEOS image. Remember, it is the same SBC. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
01.03.2014 14:48, lists пишет:
The Beaglebone Black doesn't have a real serial port. It requires a special usb cable/chip. I'm trying not to be negative here, but I think this won't be accepted well by the beaglebone users.
Then you should use XFCE-beaglebone image (seeing the console on your monitor), but I've not tested graphics yet, probably this image is just not working. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sun, 09 Mar 2014 16:57:02 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
01.03.2014 14:48, lists пишет:
The Beaglebone Black doesn't have a real serial port. It requires a special usb cable/chip. I'm trying not to be negative here, but I think this won't be accepted well by the beaglebone users.
Then you should use XFCE-beaglebone image (seeing the console on your monitor), but I've not tested graphics yet, probably this image is just not working.
Actually it makes sense not to install the graphics. It would have been better if Circitco made it more evident that you needed this FTDI cable. That would save on shipping and time. It isn't like you can go to a store and buy this stuff. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
28.02.2014 17:47, Guillaume Gardet пишет:
Did you create submit requests?
Would you please handle SR 224264 to openSUSE:13.1:Ports? Thank you. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
----- Matwey V. Kornilov <matwey.kornilov@gmail.com> a écrit :
28.02.2014 17:47, Guillaume Gardet пишет:
Did you create submit requests?
Would you please handle SR 224264 to openSUSE:13.1:Ports? Thank you.
Seems ok to me. Dirk, or Alex, could you please accept this request? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sun, 9 Mar 2014 14:39:13 +0100 (CET) guillaume.gardet@free.fr wrote:
----- Matwey V. Kornilov <matwey.kornilov@gmail.com> a écrit :
28.02.2014 17:47, Guillaume Gardet пишет:
Did you create submit requests?
Would you please handle SR 224264 to openSUSE:13.1:Ports? Thank you.
Seems ok to me. Dirk, or Alex, could you please accept this request?
Guillaume
I'm not following this, but I assume another build is requested? While the minix build is lacking a lot of stuff, oh like the packages (!), I will admit they set things up so you can build the image yourself. Other than following instructions, I have little understanding of how they set up the cross compilation, but it went very fast. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (5)
-
Guillaume Gardet -
guillaume.gardet＠free.fr
-
Josua Mayer -
lists -
Matwey V. Kornilov