Am 26.04.2014 um 10:13 schrieb lists :

I had some trouble with the USB to serial converter. It used to work on Cutecom. Now the program can't open /dev/ttyUSB0. Anyway, I figured out minicom. Kind of crude but it does the job. [Besides, the 1989's were good times.]

Here is the output from minicom:

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: 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#

Hrm. I'm not sure what the person who did the beaglebone image implemented a booting process, but the "usual openSUSE way" to booting is that there is an ext2 /boot partition which contains a boot.scr which then contains all commands necessary to load the image, device tree etc. The uboot output here indicates that nothing even looks for boot.scr. So maybe the u-boot package didn't get patched properly or JeOS creation ended up picking a wrong u-boot package? This all probably used to work, so key is to find out what changed. Alex

Looks to me like it found the SD card but doesn't boot. This is using openSUSE-13.1-ARM-JeOS-beaglebone.armv7l-1.12.1-Build33.3.raw.xz -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Sat, 26 Apr 2014 10:39:20 +0200 Alexander Graf wrote:

...

Am 26.04.2014 um 10:13 schrieb lists :

I had some trouble with the USB to serial converter. It used to work on Cutecom. Now the program can't open /dev/ttyUSB0. Anyway, I figured out minicom. Kind of crude but it does the job. [Besides, the 1989's were good times.]

Here is the output from minicom:

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: 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#

Hrm. I'm not sure what the person who did the beaglebone image implemented a booting process, but the "usual openSUSE way" to booting is that there is an ext2 /boot partition which contains a boot.scr which then contains all commands necessary to load the image, device tree etc.

The uboot output here indicates that nothing even looks for boot.scr. So maybe the u-boot package didn't get patched properly or JeOS creation ended up picking a wrong u-boot package?

This all probably used to work, so key is to find out what changed.

Alex

...

Looks to me like it found the SD card but doesn't boot. This is using openSUSE-13.1-ARM-JeOS-beaglebone.armv7l-1.12.1-Build33.3.raw.xz --

Just for completeness, here is the contents of JEOS from the SD card: Top level called BOOT contents: boot boot.scr dtb lost+found MLO u-boot.bin Contents of boot: 0x947d08bb boot.script initrd.uboot linux.vmx mbrid contents of dtb: am335x-base0033.dtb am335x-boneblack.dtb am335x-bone.dtb am335x-evm.dtb am335x-evmsk.dtb am335x-nano.dtb -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Sat, 26 Apr 2014 01:13:18 -0700 lists wrote:

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 ** File not found /boot/uImage ** U-Boot#

Looks to me like it found the SD card but doesn't boot. This is using openSUSE-13.1-ARM-JeOS-beaglebone.armv7l-1.12.1-Build33.3.raw.xz

Don't you have to press and hold S2 switch on beaglebone black, while turning on power, if you want to boot from SD card? Maybe in your case, it is trying to boot from something else? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Twenty odd years ago I discovered gtkterm. You have to build it on openSUSE as they dropped it years ago but a package is available in Ubuntu. Since I discovered gtkterm I have never bothered with any of the others and I have used it as a terminal to Mainframes, SPARC Enterprise systems, ARM, etc. It's a clone of Windows hyperterminal, Configuration --> Port -- set /dev/ttyUSB0, 8-N-1, 115200, save the configuration as default so you don't have to do it again and off you go. It also allows you to save everything to a file should you need to look over it later. https://fedorahosted.org/gtkterm/ Minicom should have been pensioned off decades ago. Regards Sid. On 26/04/14 09:13, lists wrote:

I had some trouble with the USB to serial converter. It used to work on Cutecom. Now the program can't open /dev/ttyUSB0. Anyway, I figured out minicom. Kind of crude but it does the job. [Besides, the 1989's were good times.]

Here is the output from minicom:

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: 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#

Looks to me like it found the SD card but doesn't boot. This is using openSUSE-13.1-ARM-JeOS-beaglebone.armv7l-1.12.1-Build33.3.raw.xz

-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks

On 26/04/14 20:06, lists wrote:

On Sat, 26 Apr 2014 14:43:01 +0100 Sid Boyce wrote:

...

Twenty odd years ago I discovered gtkterm. You have to build it on openSUSE as they dropped it years ago but a package is available in Ubuntu.

Since I discovered gtkterm I have never bothered with any of the others and I have used it as a terminal to Mainframes, SPARC Enterprise systems, ARM, etc. It's a clone of Windows hyperterminal, Configuration --> Port -- set /dev/ttyUSB0, 8-N-1, 115200, save the configuration as default so you don't have to do it again and off you go.

It also allows you to save everything to a file should you need to look over it later. https://fedorahosted.org/gtkterm/

Minicom should have been pensioned off decades ago. Regards Sid.

I did the git and it isn't finding gkt3, which I do have installed. But I'm sure I can work around this. At least the program has been touched in the last century. Minicom looks like the old Z modem from the win95 days.

You can kind of see why a terminal emulator doesn't get much love these days, given the death of serial ports.

I just built the git version. slipstream:/home/lancelot/ftp/APR14/gtkterm # ldd src/gtkterm linux-vdso.so.1 (0x00007fff1fc00000) libgtk-3.so.0 => /usr/lib64/libgtk-3.so.0 (0x00007ffc11ae0000) libgdk-3.so.0 => /usr/lib64/libgdk-3.so.0 (0x00007ffc11828000) # rpm -qf /usr/lib64/libgtk-3.so.0.1000.7 libgtk-3-0-3.10.7-1.2.x86_64 have both gtk-2 and gtk-3 installed but it's using gtk-3. It's up and running on 2 boxes. Before gtkterm I used seyon, kermit and minicom but none have measured up. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Sat, 26 Apr 2014 01:17:16 -0700 lists wrote:

I think you are best off running Angstrom. It is small enough to fit in the onboard memory. The board boots fast with Angstrom. Ubuntu was OK. The advantage to Angstrom and Ubuntu is you won't have to buy the FTDI cable, which is about half the cost of the board.

That all said, I'd like to run Opensuse JEOS if I could. I have no need for the HDMI output. I am working on a signal processing black box. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

OK thanks. I've got a serial cable already, but I'll have a look at ubuntu and others. Cheers. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org