On Sat, 26 Apr 2014 10:39:20 +0200 Alexander Graf <[email protected]> wrote:
> > > > Am 26.04.2014 um 10:13 schrieb lists <[email protected]>: > > > > 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: [email protected] > > To contact the owner, e-mail: [email protected] > > Actually it didn't work last time I tried. My email should still be around, not that it matters. That is why I looked for other distributions. My recollection is at the time I didn't know I needed the USB to serial cable. I ordered it, then probably two weeks later reprted the distribution didn't work. [Incidentally the Angstrom distribution works on the serial port. The board is set up for 115200 8N1.] This boot loader stuff is all greek to me since I am the end user and not the kernel guru. However, I am willing to try any new build. While we're at it, is it certain that the BeagleBone Black can use the same image as the regular BeagleBone? -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
