[meta-freescale] Errors booting SABRE Lite (was SabreLite can not boot from SD card)

[Eric Nelson]

Hello Baodong,

On 02/19/2014 10:30 PM, Baodong Chen wrote:
> On Thu, Feb 20, 2014 at 9:30 AM, Eric Nelson
> <eric.nelson at boundarydevices.com
> <mailto:eric.nelson at boundarydevices.com>> wrote:
>
>     Hello Baodong,
>
>     On 02/19/2014 06:13 PM, Baodong Chen wrote:
>
>         i found some message in the serial log, are these message means
>         something wrong?
>
>
>     Please start a new thread when you change topics.
>
>     Also, please try not to top-post and full-post on the ML.
>
>   got it,trying to

Better, but you might consider a different e-mail client!

>
>         U-Boot 2013.07 (Feb 17 2014 - 02:01:32)
>
>         CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
>         Reset cause: POR
>         Board: SABRE Lite
>         DRAM:  1 GiB
>         MMC:   FSL_SDHC: 0, FSL_SDHC: 1
>         SF: Detected SST25VF016B with page size 4 KiB, total 2 MiB
>         *** Warning - bad CRC, using default environment
>
>         No panel detected: default to HDMI
>         enable_hdmi: setup HDMI monitor
>         Display: HDMI (1024x768)
>         In:    serial
>         Out:   serial
>         Err:   serial
>         Net:   using phy at 6
>         FEC [PRIME]
>         Warning: failed to set MAC address
>
>         Hit any key to stop autoboot:  0
>         AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
>         flags: ncq stag pm led clo only pmp pio slum part
>         No port device detected!
>         ** Bad device size - sata 0 **
>         ** Bad device size - sata 0 **
>
>         SATA device 1: unknown device
>         ** Bad device sata 1 **
>         ** Bad device sata 1 **
>         mmc0 is current device
>         reading /6x_bootscript
>         2340 bytes read in 16 ms (142.6 KiB/s)
>         ## Executing script at 10008000
>
>
>     The following says that no displays were auto-detected.
>     See this post for details:
>     http://boundarydevices.com/__auto-configuration-of-__displays-for-i-mx6-using-a-u-__boot-script/
>     <http://boundarydevices.com/auto-configuration-of-displays-for-i-mx6-using-a-u-boot-script/>
>
>   done by script file? if so, where is the script file by which i can
> change to disable this behaver

board/boundary/nitrogen6x/6x_bootscript-yocto.txt:
	https://github.com/boundarydevices/u-boot-imx6/blob/production/board/boundary/nitrogen6x/6x_bootscript-yocto.txt

The i2c probe commands are used to identify the various touch 
controllers, or the EDID channel for HDMI (i2c dev 1, address 50).

If you know your display, you can just replace them with something that
sets bootargs to include it and set fbmem For example if you have a 
1280x800 LVDS panel, you might set it like so:

setenv bootargs $bootargs video=mxcfb0:dev=ldb,1280x800MR at 60,if=RGB666
setenv fbmem "fbmem=10M";
setenv nextcon 1

You can also use the on-line boot-script compiler to test:
	http://git.boundarydevices.com/bootscript.php

>
 > <snip>
>
>     The following is normal unless you're running a kernel
>     that supports device-tree (3.5.7+):
>
>   using 3.0.35
>
>
>         *** Unable to read file /imx6q-sabrelite.dtb ***
>         only CEA modes allowed on HDMI port
>         reading /uImage
>         3739464 bytes read in 333 ms (10.7 MiB/s)
>         ## Booting kernel from Legacy Image at 10800000 ...
>              Image Name:   Linux-3.0.35-4.1.0+yocto+__g580993
>              Image Type:   ARM Linux Kernel Image (uncompressed)
>              Data Size:    3739400 Bytes = 3.6 MiB
>              Load Address: 10008000
>              Entry Point:  10008000
>              Verifying Checksum ... OK
>              Loading Kernel Image ... OK
>
>         Starting kernel ...
>
>
>     Cool! It looks like you're booting now.
>
>         Uncompressing Linux... done, booting the kernel.
>
>
>     Linux-3.0.35:
>
>         Linux version 3.0.35-4.1.0+yocto+g5809938 (chenbd at chenbd-laptop)
>         (gcc
>         version 4.8.1 (GCC) ) #1 SMP PREEMPT Mon Feb 17 03:25:36 CST 2014
>         CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
>         CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
>         Machine: Boundary Devices Nitrogen6X/SABRE Lite Board
>         Memory policy: ECC disabled, Data cache writealloc
>         CPU identified as i.MX6Q, silicon rev 1.2
>         PERCPU: Embedded 7 pages/cpu @8c008000 s5440 r8192 d15040 u32768
>         Built 1 zonelists in Zone order, mobility grouping on.  Total
>         pages: 227328
>
>
>     Also note here that all of the 'video=' clauses say "off":
>
>   why all of them are off? by u-boot? how to enable that?
>

Because they weren't detected by the boot script.

>
>         Kernel command line: enable_wait_mode=off video=mxcfb0:off
>         video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off
>         console=ttymxc1,115200 vmalloc=401
>         PID hash table entries: 4096 (order: 2, 16384 bytes)
>         Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
>         Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
>         Memory: 640MB 256MB = 896MB total
>         Memory: 900748k/900748k available, 147828k reserved, 0K highmem
>
 > ...
 >
>         EXT3-fs (mmcblk0p2): using internal journal
>         EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
>         VFS: Mounted root (ext3 filesystem) on device 179:2.
>         devtmpfs: mounted
>         Freeing init memory: 200K
>         INIT: version 2.88 booting
>
>     This error is because no displays were detected:
>
>   the board had no display connected .
>
That explains it.

>
>         *Error opening /dev/fb0: No such file or directory*
>         Starting udev
>         udevd[1393]: starting version 182
>         camera_reset: power_gp=0x6, reset_gp=0x8 reset_gp2=0xab
>         ov5642_powerdown: powerdown=0, power_gp=0x6
>         ov5642_read_reg:write reg error:reg=300a
>         camera ov5642 is not found
>         Starting Bootlog daemon: bootlogd.
>         Populating dev cache
>         ALSA: Restoring mixer settings...
>         No state is present for card sgtl5000audio
>         Found hardware: "sgtl5000-audio" "" "" "" ""
>         Hardware is initialized using a generic method
>         No state is present for card sgtl5000audio
>         Configuring network interfaces... eth0: Freescale FEC PHY driver
>         [Micrel
>         KSZ9021 Gigabit PHY] (mii_bus:phy_addr=1:06, irq=284)
>
>
>     Do you have an ethernet cable connected?
>     Does the network have a DHCP server?
>
>     If the answer to both questions is yes, this is probably a
>     timing issue. The Gb ethernet port on SABRE Lite is pretty
>     slow to link, and sometimes the DHCP will time out before
>     that occurs.
>
>   the board had no eth connected.
>
Ok.

>
>         udhcpc (v1.21.1) started
>         Sending discover...
>         Sending discover...
>         Sending discover...
>         *No lease, failing
>
 > ...
 >
>         apmd[2273]: apmd 3.2.1 interfacing with apm driver 1.13 and APM
>         BIOS 1.2
>         creating NFS state directory: done
>         NFS daemon support not enabled in kernel
>         Starting syslogd/klogd: done
>
>
>     I have no idea what may be happening with the avahi-daemon.
>
>   so...
>
>         * * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon
>              ...fail!*
>         Starting Telephony daemon
>         Starting Linux NFC daemon
>         Starting OProfileUI server
>         Running local boot scripts (/etc/rc.local).
>         *
>         ** (oprofile-server:2308): WARNING **: Failed to create avahi
>         client:
>         Daemon not running*
>         Stopping Bootlog daemon: bootlogd.
>
>         Poky (Yocto Project Reference Distro) 1.5.1 nitrogen6x /dev/ttymxc1
>
>     At this point, it appears that Yocto is fully booted.
>
>   yes
>
>     Did you get a login prompt?
>
>   login ok as root without passwd.
>

Cool. So you're up and running.

>
>     Regards,
>
>
>     Eric
>
> Thanks!