[yocto] yocto 1.6 - beaglebone black - cape manager

[Maciej Borzecki]

On Thursday 25 of September 2014 09:18:07 Diego Sueiro wrote:
> Takk,
> 
> On Wed, Sep 24, 2014 at 5:20 PM, TakkTakk <tomek82221 at gazeta.pl> wrote:
> > ok, i changed "bootz" to "bootm" and i kept S2 swith pressed.
> > Yocto not booting, two leds D2, D3 is shining.
> > 
> > Serial console output:
> > 
> > U-Boot SPL 2013.04-dirty (Sep 09 2014 - 21:38:22)
> > 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
> > reading u-boot.img
> > reading u-boot.img
> > 
> > 
> > U-Boot 2013.04-dirty (Sep 09 2014 - 21:38:22)
> > 
> > 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
> > reading uEnv.txt
> > 527 bytes read in 4 ms (127.9 KiB/s)
> > Loaded environment from uEnv.txt
> > Importing environment from mmc ...
> > Running uenvcmd ...
> > reading uImage
> > 4368264 bytes read in 499 ms (8.3 MiB/s)
> > reading /dtbs/am335x-boneblack.dtb
> > 29192 bytes read in 10 ms (2.8 MiB/s)
> > ## Booting kernel from Legacy Image at 80200000 ...
> > 
> >    Image Name:   Linux-3.8.13
> >    Image Type:   ARM Linux Kernel Image (uncompressed)
> >    Data Size:    4368200 Bytes = 4.2 MiB
> >    Load Address: 80008000
> >    Entry Point:  80008000
> >    Verifying Checksum ... OK
> > 
> > ## Flattened Device Tree blob at 80f80000
> > 
> >    Booting using the fdt blob at 0x80f80000
> >    Loading Kernel Image ... OK
> > 
> > OK
> > 
> >    Using Device Tree in place at 80f80000, end 80f8a207
> > 
> > Starting kernel ...
> > 
> > Uncompressing Linux... done, booting the kernel.
> 
> Hummm. That's strange.
> I don't know if kernel 3.8.13 populate the serial debug interface as ttyO0
> or ttyS0.

You could try console=ttyS0 or console=ttyO0 in kernel command line.
 
> 
> I think you can remove your uEnv.txt file from FAT partition and powerup
> the board by pressing the boot switch,
> The u-boot from meta-beagleboard doesn't need any extra configuration.


> 
> 
> Regards,
> 
> --
> *dS
> Diego Sueiro
> 
> Administrador do Embarcados
> www.embarcados.com.br
> <http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail
> &utm_campaign=Assinatura%20Email%20Diego>
> 
> /*long live rock 'n roll*/

-- 

Maciej Borzęcki 
Senior Software Engineer Open-RnD Sp. z o.o. 
www.open-rnd.pl, Facebook, Twitter 
mobile: +48 telefon, fax: +48 42 657 9079 

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub 
poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do 
których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo 
zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku 
uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie 
nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy. 

This message, including any attachments hereto, may contain privileged or 
confidential information and is sent solely for the attention and use of the 
intended addressee(s). If you are not an intended addressee, you may neither 
use this message nor copy or deliver it to anyone. In such case, you should 
immediately destroy this message and kindly notify the sender by reply email. 
Thank you.