All of lore.kernel.org
 help / color / mirror / Atom feed
* SabreLite can not boot from SD card
@ 2014-02-20  0:36 Baodong Chen
  2014-02-20  0:44 ` Baodong Chen
  2014-02-20  0:58 ` SabreLite can not boot from SD card Eric Nelson
  0 siblings, 2 replies; 10+ messages in thread
From: Baodong Chen @ 2014-02-20  0:36 UTC (permalink / raw)
  To: meta-freescale@yoctoproject.org

[-- Attachment #1: Type: text/plain, Size: 681 bytes --]

Hi guys:
I am using dora branch and MACHINE = "nitrogen6x" for my my SabreLite
board, the build is ok. after that, i follow this link:
https://wiki.linaro.org/Boards/MX6QSabreLite
to write the SD loader to NOR flash.

and i "dd if=fsl-image-gui-nitrogen6x.sdcard of=/dev/sdb" to write the
image to sdcard and insert the sdcard to SD Slot(not micro SD slot), but
can not boot.
nothing output from debug serial.

if i "dd if=u-boot.imx of=/dev/sdb bs=512 seek=2" and i can see the u-boot
message from debug serial, but the kernel can not loaded.


does fsl-image-gui-nitrogen6x.sdcard contains u-boot.imx in it?

please guide me how to get through this!

thanks!

[-- Attachment #2: Type: text/html, Size: 960 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: SabreLite can not boot from SD card
  2014-02-20  0:36 SabreLite can not boot from SD card Baodong Chen
@ 2014-02-20  0:44 ` Baodong Chen
  2014-02-20  1:13   ` Baodong Chen
  2014-02-20  0:58 ` SabreLite can not boot from SD card Eric Nelson
  1 sibling, 1 reply; 10+ messages in thread
From: Baodong Chen @ 2014-02-20  0:44 UTC (permalink / raw)
  To: meta-freescale@yoctoproject.org

[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]

before i "dd if=u-boot.imx of=/dev/sdb bs=512 seek=2", i write the
something else to the first 2 blocks(1K size) to the sdcard,
so the partition table is missing.
after i dd if=fsl-image-gui-nitrogen6x.sdcard of=/dev/sdb bs=512 count=2 to
write back the first 2 blocks, it did boot now!

thanks.


On Thu, Feb 20, 2014 at 8:36 AM, Baodong Chen <chenbdchenbd@gmail.com>wrote:

> Hi guys:
> I am using dora branch and MACHINE = "nitrogen6x" for my my SabreLite
> board, the build is ok. after that, i follow this link:
> https://wiki.linaro.org/Boards/MX6QSabreLite
> to write the SD loader to NOR flash.
>
> and i "dd if=fsl-image-gui-nitrogen6x.sdcard of=/dev/sdb" to write the
> image to sdcard and insert the sdcard to SD Slot(not micro SD slot), but
> can not boot.
> nothing output from debug serial.
>
> if i "dd if=u-boot.imx of=/dev/sdb bs=512 seek=2" and i can see the u-boot
> message from debug serial, but the kernel can not loaded.
>
>
> does fsl-image-gui-nitrogen6x.sdcard contains u-boot.imx in it?
>
> please guide me how to get through this!
>
> thanks!
>

[-- Attachment #2: Type: text/html, Size: 1722 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: SabreLite can not boot from SD card
  2014-02-20  0:36 SabreLite can not boot from SD card Baodong Chen
  2014-02-20  0:44 ` Baodong Chen
@ 2014-02-20  0:58 ` Eric Nelson
  2014-02-20  4:41   ` Baodong Chen
  1 sibling, 1 reply; 10+ messages in thread
From: Eric Nelson @ 2014-02-20  0:58 UTC (permalink / raw)
  To: Baodong Chen, meta-freescale@yoctoproject.org

Hi Baodong,

On 02/19/2014 05:36 PM, Baodong Chen wrote:
> Hi guys:
> I am using dora branch and MACHINE = "nitrogen6x" for my my SabreLite
> board, the build is ok. after that, i follow this link:
> https://wiki.linaro.org/Boards/MX6QSabreLite
> to write the SD loader to NOR flash.
>
> and i "dd if=fsl-image-gui-nitrogen6x.sdcard of=/dev/sdb" to write the
> image to sdcard and insert the sdcard to SD Slot(not micro SD slot), but
> can not boot.
> nothing output from debug serial.
>
> if i "dd if=u-boot.imx of=/dev/sdb bs=512 seek=2" and i can see the
> u-boot message from debug serial, but the kernel can not loaded.
>
> does fsl-image-gui-nitrogen6x.sdcard contains u-boot.imx in it?
>

Since SABRE Lite and Nitrogen6x boot to SPI-NOR, you don't need
to do anything weird here.

You can just dd the fsl-image-gui-nitrogen6x.sdcard image to
the entire SD card.

It should absolutely come up with a partition table, although
the size of partition 2 may be a bit small (it's very conservative).

You can double-check using fdisk immediately after running the dd
command if you use "partprobe" to force a re-read of the
partition table:

	~/$ sudo dd if=fsl-image-gui-nitrogen6x.sdcard ...
	~/$ sync && sudo partprobe
	~/$ sudo fdisk /dev/sdx

The u-boot.imx file is installed as a part of the build
process, but it's placed into a FAT filesystem in partition 1,
along with an upgrade script named 6x_upgrade that you can
use to copy it to SPI-NOR if you feel the need.

In general, we suggest that customers only upgrade U-Boot
when there's some new feature (like upcoming USB OTG support).

Regards,


Eric


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: SabreLite can not boot from SD card
  2014-02-20  0:44 ` Baodong Chen
@ 2014-02-20  1:13   ` Baodong Chen
  2014-02-20  1:30     ` Errors booting SABRE Lite (was SabreLite can not boot from SD card) Eric Nelson
  0 siblings, 1 reply; 10+ messages in thread
From: Baodong Chen @ 2014-02-20  1:13 UTC (permalink / raw)
  To: meta-freescale@yoctoproject.org

[-- Attachment #1: Type: text/plain, Size: 17450 bytes --]

i found some message in the serial log, are these message means something
wrong?


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
------ no HDMI monitor
Setting bus to 2
Valid chip addresses:
------ no Freescale display
Valid chip addresses:
------ no 1024x600 display
Valid chip addresses:
------ no 800x480 display
reading /imx6q-sabrelite.dtb
*** 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 ...

Uncompressing Linux... done, booting the kernel.
Linux version 3.0.35-4.1.0+yocto+g5809938 (chenbd@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
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
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xf4600000 - 0xffe00000   ( 184 MB)
    vmalloc : 0xc0800000 - 0xf2000000   ( 792 MB)
    lowmem  : 0x80000000 - 0xc0000000   (1024 MB)
    pkmap   : 0x7fe00000 - 0x80000000   (   2 MB)
    modules : 0x7f000000 - 0x7fe00000   (  14 MB)
      .init : 0x80008000 - 0x8003a000   ( 200 kB)
      .text : 0x8003a000 - 0x806d20b0   (6753 kB)
      .data : 0x806d4000 - 0x8072b5c0   ( 350 kB)
       .bss : 0x8072b5e4 - 0x8076f924   ( 273 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Preemptible hierarchical RCU implementation.
NR_IRQS:624
MXC GPIO hardware
sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms
arm_max_freq=1GHz
MXC_Early serial console at MMIO 0x21e8000 (options '115200')
bootconsole [ttymxc1] enabled
Console: colour dummy device 80x30
Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
CPU1: Booted secondary processor
CPU2: Booted secondary processor
CPU3: Booted secondary processor
Brought up 4 CPUs
SMP: Total of 4 processors activated (6324.22 BogoMIPS).
devtmpfs: initialized
print_constraints: dummy:
NET: Registered protocol family 16
print_constraints: vddpu: 725 <--> 1300 mV at 1150 mV fast normal
print_constraints: vddcore: 725 <--> 1300 mV at 1150 mV fast normal
print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal
print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal
print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal
print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal
------------ Board type Sabre Lite
imx_add_mxc_pwm:pdata=  (null)
imx_add_mxc_pwm:pdata=  (null)
imx_add_mxc_pwm:pdata=806f71d8
imx_add_mxc_pwm:pdata=  (null)
Flexcan NXP tja1040
hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.
hw-breakpoint: maximum watchpoint size is 4 bytes.
L310 cache controller enabled
l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x02070000, Cache size:
1048576 B
bio: create slab <bio-0> at 0
print_constraints: VDDA: 2500 mV
print_constraints: VDDIO: 3300 mV
machine_constraints_voltage: VDDD: unsupportable voltage constraints
reg-fixed-voltage reg-fixed-voltage.2: Failed to register regulator: -22
reg-fixed-voltage: probe of reg-fixed-voltage.2 failed with error -22
print_constraints: vmmc: 3300 mV
vgaarb: loaded
SCSI subsystem initialized
spi_imx imx6q-ecspi.0: probed
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Freescale USB OTG Driver loaded, $Revision: 1.55 $
imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
imx-ipuv3 imx-ipuv3.1: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 driver probed
mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 dphy version is 0x3130302a
MIPI CSI2 driver module loaded
Advanced Linux Sound Architecture Driver Version 1.0.24.
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource mxc_timer1
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Static Power Management for Freescale i.MX6
wait mode is disabled for i.MX6
cpaddr = c0880000 suspend_iram_base=c0918000
PM driver module loaded
iMX6 PCIe PCIe RC mode imx_pcie_pltfm_probe entering.
PCIE: imx_pcie_pltfm_probe start link up.
link up failed, DB_R0:0x00bc6600, DB_R1:0x08200000!
IMX PCIe port: link down!
IMX usb wakeup probe
add wake up source irq 75
IMX usb wakeup probe
cpu regulator mode:ldo_enable
i.MXC CPU frequency driver
squashfs: version 4.0 (2009/01/31) Phillip Lougher
msgmni has been set to 1759
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
pwm_config: pwm freq = 32786, clk_select=2 clock_rate=22000000
pwm_config: pwm freq = 20000, clk_select=2 clock_rate=22000000
MIPI DSI driver module loaded
mxc_sdc_fb mxc_sdc_fb.0: mxcfb0 is turned off!
mxc_sdc_fb mxc_sdc_fb.1: mxcfb1 is turned off!
mxc_sdc_fb mxc_sdc_fb.2: mxcfb2 is turned off!
mxc_sdc_fb mxc_sdc_fb.3: mxcfb3 is turned off!
imx-sdma imx-sdma: loaded firmware 1.1
imx-sdma imx-sdma: initialized
Serial: IMX driver
imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
imx-uart.1: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX
old_ufcr=a81 new_ufcr=b01, old_ucr2=4027 new_ucr2=4027, old_ubir=f num=1f7,
old_ubmr=15b denom=c34
clk=80000000 div=7 num=504 denom=3125 baud=115200
console [ttymxc1] enabled, bootconsole disabled
console [ttymxc1] enabled, bootconsole disabled
loop: module loaded
No sata disk.
m25p80 spi0.0: sst25vf016b (2048 Kbytes)
Creating 3 MTD partitions on "m25p80":
0x000000000000-0x0000000c0000 : "bootloader"
0x0000000c0000-0x0000000c2000 : "ubparams"
0x0000000c2000-0x000000200000 : "unused"
vcan: Virtual CAN interface driver
CAN device driver interface
flexcan netdevice driver
flexcan imx6q-flexcan.0: device registered (reg_base=c09a8000, irq=142)
FEC Ethernet Driver
fec_enet_mii_bus: probed
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000
fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
add wake up source irq 72
fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
fsl-ehci fsl-ehci.1: irq 72, io base 0x02184200
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems
USB Serial support registered for Qualcomm USB modem
usbcore: registered new interface driver qcserial
ARC USBOTG Device Controller driver (1 August 2005)
mousedev: PS/2 mouse device common for all mice
input: gpio-keys as /devices/platform/gpio-keys/input/input0
tsc2004_prepare_for_reading: write_cmd -5
tsc2004: probe of 2-0048 failed with error -5
egalax_ts 2-0004: egalax_ts: failed to read firmware version
egalax_ts: probe of 2-0004 failed with error -5
ft5x06-ts 2-0038: ft5x06: Could not detect touch screen.
ft5x06: Feb 17 2014
check_alarm_past: alarm in the past
snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0
i2c /dev entries driver
Linux video capture interface: v2.00
i2c-core: driver [mma8450] using legacy suspend method
i2c-core: driver [mma8450] using legacy resume method
add mma8450 i2c driver
imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)
device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised:
dm-devel@redhat.com
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCILL protocol initialized
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA
sdhci sdhci-esdhc-imx.3: no write-protect pin available!
mmc1: SDHCI controller on platform [sdhci-esdhc-imx.3] using DMA
mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
VPU initialized
mxc_asrc registered
Galcore version 4.6.9.6622
Thermal calibration data is 0x55c4b47d
Thermal sensor with ratio = 176
Anatop Thermal registered as thermal_zone0
anatop_thermal_probe: default cooling device is cpufreq!
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio
imx-hdmi-soc-dai imx-hdmi-soc-dai.0: Failed: Load HDMI-video first.
sgtl5000 0-000a: Failed to get supply 'VDDD': -19
print_constraints: 0-000a: 850 <--> 1600 mV at 1200 mV normal
sgtl5000 0-000a: sgtl5000 revision 17
mmc0: new SDHC card at address e624
mmcblk0: mmc0:e624 SD04G 3.69 GiB
 mmcblk0: p1 p2
usb 2-1: new high speed USB device number 2 using fsl-ehci
asoc: sgtl5000 <-> imx-ssi.1 mapping ok
Initialize HDMI-audio failed. Load HDMI-video first!
ALSA device list:
  #0: sgtl5000-audio
NET: Registered protocol family 26
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
Bus freq driver module loaded
Bus freq driver Enabled
mxc_dvfs_core_probe
DVFS driver module loaded
snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0)
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 3 ports detected
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
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
*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)
udhcpc (v1.21.1) started
Sending discover...
Sending discover...
Sending discover...


*No lease, failingStarting rpcbind daemon...rpcbind: cannot create socket
for udp6rpcbind: cannot create socket for tcp6*
done.
Mon Feb 17 06:24:00 UTC 2014
Running postinst /etc/rpm-postinsts/100-debianutils...
update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing)
 Removing any system startup links for run-postinsts ...
  /etc/rcS.d/S99run-postinsts
INIT: Entering runlevel: 5
Starting Xserver
*open /dev/fb0: No such file or directory*
Starting system message bus: dbus.
Starting Connection Manager
Starting Dropbear SSH server: Will output 1024 bit rsa secret key to
'/etc/dropbear/dropbear_rsa_host_key'
Generating key, this may take a while...
Public key portion is:
ssh-rsa
AAAAB3NzaC1yc2EAAAADAQABAAAAgnuuabHxqECm6rB6ZK4b+ETQYRINakuWDb93SS1AasT5n7dxIjxYh7BNAWQkTd8azrJwF7UdqBD9AlbEdZB6xP80lh5++hxCeoqAJVEaiInx
Fingerprint: md5 41:0e:c6:85:03:82:19:d6:5c:a2:31:f8:57:46:e7:2f
dropbear.
Starting advanced power management daemon: apmd.
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

* * 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


On Thu, Feb 20, 2014 at 8:44 AM, Baodong Chen <chenbdchenbd@gmail.com>wrote:

> before i "dd if=u-boot.imx of=/dev/sdb bs=512 seek=2", i write the
> something else to the first 2 blocks(1K size) to the sdcard,
> so the partition table is missing.
> after i dd if=fsl-image-gui-nitrogen6x.sdcard of=/dev/sdb bs=512 count=2
> to write back the first 2 blocks, it did boot now!
>
> thanks.
>
>
> On Thu, Feb 20, 2014 at 8:36 AM, Baodong Chen <chenbdchenbd@gmail.com>wrote:
>
>> Hi guys:
>> I am using dora branch and MACHINE = "nitrogen6x" for my my SabreLite
>> board, the build is ok. after that, i follow this link:
>> https://wiki.linaro.org/Boards/MX6QSabreLite
>> to write the SD loader to NOR flash.
>>
>> and i "dd if=fsl-image-gui-nitrogen6x.sdcard of=/dev/sdb" to write the
>> image to sdcard and insert the sdcard to SD Slot(not micro SD slot), but
>> can not boot.
>> nothing output from debug serial.
>>
>> if i "dd if=u-boot.imx of=/dev/sdb bs=512 seek=2" and i can see the
>> u-boot message from debug serial, but the kernel can not loaded.
>>
>>
>> does fsl-image-gui-nitrogen6x.sdcard contains u-boot.imx in it?
>>
>> please guide me how to get through this!
>>
>> thanks!
>>
>
>

[-- Attachment #2: Type: text/html, Size: 19616 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Errors booting SABRE Lite (was SabreLite can not boot from SD card)
  2014-02-20  1:13   ` Baodong Chen
@ 2014-02-20  1:30     ` Eric Nelson
  2014-02-20  5:30       ` Baodong Chen
  0 siblings, 1 reply; 10+ messages in thread
From: Eric Nelson @ 2014-02-20  1:30 UTC (permalink / raw)
  To: Baodong Chen, meta-freescale@yoctoproject.org

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.

>
> 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/

> ------ no HDMI monitor
> Setting bus to 2
> Valid chip addresses:
> ------ no Freescale display
> Valid chip addresses:
> ------ no 1024x600 display
> Valid chip addresses:
> ------ no 800x480 display
> reading /imx6q-sabrelite.dtb

The following is normal unless you're running a kernel
that supports device-tree (3.5.7+):

> *** 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@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":

> 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
> Virtual kernel memory layout:
>      vector  : 0xffff0000 - 0xffff1000   (   4 kB)
>      fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
>      DMA     : 0xf4600000 - 0xffe00000   ( 184 MB)
>      vmalloc : 0xc0800000 - 0xf2000000   ( 792 MB)
>      lowmem  : 0x80000000 - 0xc0000000   (1024 MB)
>      pkmap   : 0x7fe00000 - 0x80000000   (   2 MB)
>      modules : 0x7f000000 - 0x7fe00000   (  14 MB)
>        .init : 0x80008000 - 0x8003a000   ( 200 kB)
>        .text : 0x8003a000 - 0x806d20b0   (6753 kB)
>        .data : 0x806d4000 - 0x8072b5c0   ( 350 kB)
>         .bss : 0x8072b5e4 - 0x8076f924   ( 273 kB)
> SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
> Preemptible hierarchical RCU implementation.
> NR_IRQS:624
> MXC GPIO hardware
> sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms
> arm_max_freq=1GHz
> MXC_Early serial console at MMIO 0x21e8000 (options '115200')
> bootconsole [ttymxc1] enabled
> Console: colour dummy device 80x30
> Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)
> pid_max: default: 32768 minimum: 301
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
> CPU1: Booted secondary processor
> CPU2: Booted secondary processor
> CPU3: Booted secondary processor
> Brought up 4 CPUs
> SMP: Total of 4 processors activated (6324.22 BogoMIPS).
> devtmpfs: initialized
> print_constraints: dummy:
> NET: Registered protocol family 16
> print_constraints: vddpu: 725 <--> 1300 mV at 1150 mV fast normal
> print_constraints: vddcore: 725 <--> 1300 mV at 1150 mV fast normal
> print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal
> print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal
> print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal
> print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal
> ------------ Board type Sabre Lite
> imx_add_mxc_pwm:pdata=  (null)
> imx_add_mxc_pwm:pdata=  (null)
> imx_add_mxc_pwm:pdata=806f71d8
> imx_add_mxc_pwm:pdata=  (null)
> Flexcan NXP tja1040
> hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
> hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.
> hw-breakpoint: maximum watchpoint size is 4 bytes.
> L310 cache controller enabled
> l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x02070000, Cache size:
> 1048576 B
> bio: create slab <bio-0> at 0
> print_constraints: VDDA: 2500 mV
> print_constraints: VDDIO: 3300 mV
> machine_constraints_voltage: VDDD: unsupportable voltage constraints
> reg-fixed-voltage reg-fixed-voltage.2: Failed to register regulator: -22
> reg-fixed-voltage: probe of reg-fixed-voltage.2 failed with error -22
> print_constraints: vmmc: 3300 mV
> vgaarb: loaded
> SCSI subsystem initialized
> spi_imx imx6q-ecspi.0: probed
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> Freescale USB OTG Driver loaded, $Revision: 1.55 $
> imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
> imx-ipuv3 imx-ipuv3.1: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
> mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 driver probed
> mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 dphy version is 0x3130302a
> MIPI CSI2 driver module loaded
> Advanced Linux Sound Architecture Driver Version 1.0.24.
> Bluetooth: Core ver 2.16
> NET: Registered protocol family 31
> Bluetooth: HCI device and connection manager initialized
> Bluetooth: HCI socket layer initialized
> Bluetooth: L2CAP socket layer initialized
> Bluetooth: SCO socket layer initialized
> cfg80211: Calling CRDA to update world regulatory domain
> Switching to clocksource mxc_timer1
> NET: Registered protocol family 2
> IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
> TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
> TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
> TCP: Hash tables configured (established 131072 bind 65536)
> TCP reno registered
> UDP hash table entries: 512 (order: 2, 16384 bytes)
> UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
> NET: Registered protocol family 1
> RPC: Registered named UNIX socket transport module.
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> RPC: Registered tcp NFSv4.1 backchannel transport module.
> Static Power Management for Freescale i.MX6
> wait mode is disabled for i.MX6
> cpaddr = c0880000 suspend_iram_base=c0918000
> PM driver module loaded
> iMX6 PCIe PCIe RC mode imx_pcie_pltfm_probe entering.
> PCIE: imx_pcie_pltfm_probe start link up.
> link up failed, DB_R0:0x00bc6600, DB_R1:0x08200000!
> IMX PCIe port: link down!
> IMX usb wakeup probe
> add wake up source irq 75
> IMX usb wakeup probe
> cpu regulator mode:ldo_enable
> i.MXC CPU frequency driver
> squashfs: version 4.0 (2009/01/31) Phillip Lougher
> msgmni has been set to 1759
> alg: No test for stdrng (krng)
> io scheduler noop registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> pwm_config: pwm freq = 32786, clk_select=2 clock_rate=22000000
> pwm_config: pwm freq = 20000, clk_select=2 clock_rate=22000000
> MIPI DSI driver module loaded
> mxc_sdc_fb mxc_sdc_fb.0: mxcfb0 is turned off!
> mxc_sdc_fb mxc_sdc_fb.1: mxcfb1 is turned off!
> mxc_sdc_fb mxc_sdc_fb.2: mxcfb2 is turned off!
> mxc_sdc_fb mxc_sdc_fb.3: mxcfb3 is turned off!
> imx-sdma imx-sdma: loaded firmware 1.1
> imx-sdma imx-sdma: initialized
> Serial: IMX driver
> imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
> imx-uart.1: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX
> old_ufcr=a81 new_ufcr=b01, old_ucr2=4027 new_ucr2=4027, old_ubir=f
> num=1f7, old_ubmr=15b denom=c34
> clk=80000000 div=7 num=504 denom=3125 baud=115200
> console [ttymxc1] enabled, bootconsole disabled
> console [ttymxc1] enabled, bootconsole disabled
> loop: module loaded
> No sata disk.
> m25p80 spi0.0: sst25vf016b (2048 Kbytes)
> Creating 3 MTD partitions on "m25p80":
> 0x000000000000-0x0000000c0000 : "bootloader"
> 0x0000000c0000-0x0000000c2000 : "ubparams"
> 0x0000000c2000-0x000000200000 : "unused"
> vcan: Virtual CAN interface driver
> CAN device driver interface
> flexcan netdevice driver
> flexcan imx6q-flexcan.0: device registered (reg_base=c09a8000, irq=142)
> FEC Ethernet Driver
> fec_enet_mii_bus: probed
> tun: Universal TUN/TAP device driver, 1.6
> tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com
> <mailto:maxk@qualcomm.com>>
> ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
> fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
> fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000
> fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 1 port detected
> add wake up source irq 72
> fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
> fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
> fsl-ehci fsl-ehci.1: irq 72, io base 0x02184200
> fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
> hub 2-0:1.0: USB hub found
> hub 2-0:1.0: 1 port detected
> usbcore: registered new interface driver cdc_acm
> cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
> Initializing USB Mass Storage driver...
> usbcore: registered new interface driver usb-storage
> USB Mass Storage support registered.
> usbcore: registered new interface driver usbserial
> usbserial: USB Serial Driver core
> USB Serial support registered for GSM modem (1-port)
> usbcore: registered new interface driver option
> option: v0.7.2:USB Driver for GSM modems
> USB Serial support registered for Qualcomm USB modem
> usbcore: registered new interface driver qcserial
> ARC USBOTG Device Controller driver (1 August 2005)
> mousedev: PS/2 mouse device common for all mice
> input: gpio-keys as /devices/platform/gpio-keys/input/input0
> tsc2004_prepare_for_reading: write_cmd -5
> tsc2004: probe of 2-0048 failed with error -5
> egalax_ts 2-0004: egalax_ts: failed to read firmware version
> egalax_ts: probe of 2-0004 failed with error -5
> ft5x06-ts 2-0038: ft5x06: Could not detect touch screen.
> ft5x06: Feb 17 2014
> check_alarm_past: alarm in the past
> snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0
> i2c /dev entries driver
> Linux video capture interface: v2.00
> i2c-core: driver [mma8450] using legacy suspend method
> i2c-core: driver [mma8450] using legacy resume method
> add mma8450 i2c driver
> imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)
> device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised:
> dm-devel@redhat.com <mailto:dm-devel@redhat.com>
> Bluetooth: HCI UART driver ver 2.2
> Bluetooth: HCILL protocol initialized
> sdhci: Secure Digital Host Controller Interface driver
> sdhci: Copyright(c) Pierre Ossman
> mmc0: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA
> sdhci sdhci-esdhc-imx.3: no write-protect pin available!
> mmc1: SDHCI controller on platform [sdhci-esdhc-imx.3] using DMA
> mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
> VPU initialized
> mxc_asrc registered
> Galcore version 4.6.9.6622
> Thermal calibration data is 0x55c4b47d
> Thermal sensor with ratio = 176
> Anatop Thermal registered as thermal_zone0
> anatop_thermal_probe: default cooling device is cpufreq!
> usbcore: registered new interface driver usbhid
> usbhid: USB HID core driver
> usbcore: registered new interface driver snd-usb-audio
> mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio
> imx-hdmi-soc-dai imx-hdmi-soc-dai.0: Failed: Load HDMI-video first.
> sgtl5000 0-000a: Failed to get supply 'VDDD': -19
> print_constraints: 0-000a: 850 <--> 1600 mV at 1200 mV normal
> sgtl5000 0-000a: sgtl5000 revision 17
> mmc0: new SDHC card at address e624
> mmcblk0: mmc0:e624 SD04G 3.69 GiB
>   mmcblk0: p1 p2
> usb 2-1: new high speed USB device number 2 using fsl-ehci
> asoc: sgtl5000 <-> imx-ssi.1 mapping ok
> Initialize HDMI-audio failed. Load HDMI-video first!
> ALSA device list:
>    #0: sgtl5000-audio
> NET: Registered protocol family 26
> TCP cubic registered
> NET: Registered protocol family 17
> can: controller area network core (rev 20090105 abi 8)
> NET: Registered protocol family 29
> can: raw protocol (rev 20090105)
> can: broadcast manager protocol (rev 20090105 t)
> Bluetooth: RFCOMM TTY layer initialized
> Bluetooth: RFCOMM socket layer initialized
> Bluetooth: RFCOMM ver 1.11
> Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> Bluetooth: BNEP filters: protocol multicast
> Bluetooth: HIDP (Human Interface Emulation) ver 1.2
> lib80211: common routines for IEEE802.11 drivers
> VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
> Bus freq driver module loaded
> Bus freq driver Enabled
> mxc_dvfs_core_probe
> DVFS driver module loaded
> snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0)
> hub 2-1:1.0: USB hub found
> hub 2-1:1.0: 3 ports detected
> EXT3-fs: barriers not enabled
> kjournald starting.  Commit interval 5 seconds
> 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:

> *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.

> udhcpc (v1.21.1) started
> Sending discover...
> Sending discover...
> Sending discover...
> *No lease, failing
> Starting rpcbind daemon...rpcbind: cannot create socket for udp6
> rpcbind: cannot create socket for tcp6*
> done.
> Mon Feb 17 06:24:00 UTC 2014
> Running postinst /etc/rpm-postinsts/100-debianutils...
> update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing)
>   Removing any system startup links for run-postinsts ...
>    /etc/rcS.d/S99run-postinsts
> INIT: Entering runlevel: 5
> Starting Xserver
> *open /dev/fb0: No such file or directory*
> Starting system message bus: dbus.
> Starting Connection Manager
> Starting Dropbear SSH server: Will output 1024 bit rsa secret key to
> '/etc/dropbear/dropbear_rsa_host_key'
> Generating key, this may take a while...
> Public key portion is:
> ssh-rsa
> AAAAB3NzaC1yc2EAAAADAQABAAAAgnuuabHxqECm6rB6ZK4b+ETQYRINakuWDb93SS1AasT5n7dxIjxYh7BNAWQkTd8azrJwF7UdqBD9AlbEdZB6xP80lh5++hxCeoqAJVEaiInx
> Fingerprint: md5 41:0e:c6:85:03:82:19:d6:5c:a2:31:f8:57:46:e7:2f
> dropbear.
> Starting advanced power management daemon: apmd.
> 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.

> * * 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.

Did you get a login prompt?

Regards,


Eric



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: SabreLite can not boot from SD card
  2014-02-20  0:58 ` SabreLite can not boot from SD card Eric Nelson
@ 2014-02-20  4:41   ` Baodong Chen
  2014-02-20 14:22     ` Eric Nelson
  0 siblings, 1 reply; 10+ messages in thread
From: Baodong Chen @ 2014-02-20  4:41 UTC (permalink / raw)
  To: Eric Nelson; +Cc: meta-freescale@yoctoproject.org

[-- Attachment #1: Type: text/plain, Size: 2333 bytes --]

Hi Eric:
Thanks for your reply.
All i want is to have a sdcard image which contains u-boot, kernel and
rootfs all in it.
I have written SD loader to NOR flash already.
So after bitbake, using the following two commands seems work for me, the
u-boot is loaded by SD loader from NOR flash and kernel is loaded by u-boot.

dd if=fsl-image-gui-nitrogen6x.sdcard of=/dev/sdb
dd if=u-boot.imx of=/dev/sdb bs=512 seek=2

Am i right? or am i misunderstaning something?


On Thu, Feb 20, 2014 at 8:58 AM, Eric Nelson <
eric.nelson@boundarydevices.com> wrote:

> Hi Baodong,
>
>
> On 02/19/2014 05:36 PM, Baodong Chen wrote:
>
>> Hi guys:
>> I am using dora branch and MACHINE = "nitrogen6x" for my my SabreLite
>> board, the build is ok. after that, i follow this link:
>> https://wiki.linaro.org/Boards/MX6QSabreLite
>> to write the SD loader to NOR flash.
>>
>> and i "dd if=fsl-image-gui-nitrogen6x.sdcard of=/dev/sdb" to write the
>> image to sdcard and insert the sdcard to SD Slot(not micro SD slot), but
>> can not boot.
>> nothing output from debug serial.
>>
>> if i "dd if=u-boot.imx of=/dev/sdb bs=512 seek=2" and i can see the
>> u-boot message from debug serial, but the kernel can not loaded.
>>
>> does fsl-image-gui-nitrogen6x.sdcard contains u-boot.imx in it?
>>
>>
> Since SABRE Lite and Nitrogen6x boot to SPI-NOR, you don't need
> to do anything weird here.
>
> You can just dd the fsl-image-gui-nitrogen6x.sdcard image to
> the entire SD card.
>
> It should absolutely come up with a partition table, although
> the size of partition 2 may be a bit small (it's very conservative).
>
> You can double-check using fdisk immediately after running the dd
> command if you use "partprobe" to force a re-read of the
> partition table:
>
>         ~/$ sudo dd if=fsl-image-gui-nitrogen6x.sdcard ...
>         ~/$ sync && sudo partprobe
>         ~/$ sudo fdisk /dev/sdx
>
> The u-boot.imx file is installed as a part of the build
> process, but it's placed into a FAT filesystem in partition 1,
> along with an upgrade script named 6x_upgrade that you can
> use to copy it to SPI-NOR if you feel the need.
>
> In general, we suggest that customers only upgrade U-Boot
> when there's some new feature (like upcoming USB OTG support).
>
> Regards,
>
>
> Eric
>

[-- Attachment #2: Type: text/html, Size: 3804 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Errors booting SABRE Lite (was SabreLite can not boot from SD card)
  2014-02-20  1:30     ` Errors booting SABRE Lite (was SabreLite can not boot from SD card) Eric Nelson
@ 2014-02-20  5:30       ` Baodong Chen
  2014-02-20 14:35         ` Eric Nelson
  0 siblings, 1 reply; 10+ messages in thread
From: Baodong Chen @ 2014-02-20  5:30 UTC (permalink / raw)
  To: Eric Nelson; +Cc: meta-freescale@yoctoproject.org

[-- Attachment #1: Type: text/plain, Size: 19170 bytes --]

On Thu, Feb 20, 2014 at 9:30 AM, Eric Nelson <
eric.nelson@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

>


>
>> 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/

 done by script file? if so, where is the script file by which i can change
to disable this behaver

>
>
>  ------ no HDMI monitor
>> Setting bus to 2
>> Valid chip addresses:
>> ------ no Freescale display
>> Valid chip addresses:
>> ------ no 1024x600 display
>> Valid chip addresses:
>> ------ no 800x480 display
>> reading /imx6q-sabrelite.dtb
>>
>
> 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@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?

>
>  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
>> Virtual kernel memory layout:
>>      vector  : 0xffff0000 - 0xffff1000   (   4 kB)
>>      fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
>>      DMA     : 0xf4600000 - 0xffe00000   ( 184 MB)
>>      vmalloc : 0xc0800000 - 0xf2000000   ( 792 MB)
>>      lowmem  : 0x80000000 - 0xc0000000   (1024 MB)
>>      pkmap   : 0x7fe00000 - 0x80000000   (   2 MB)
>>      modules : 0x7f000000 - 0x7fe00000   (  14 MB)
>>        .init : 0x80008000 - 0x8003a000   ( 200 kB)
>>        .text : 0x8003a000 - 0x806d20b0   (6753 kB)
>>        .data : 0x806d4000 - 0x8072b5c0   ( 350 kB)
>>         .bss : 0x8072b5e4 - 0x8076f924   ( 273 kB)
>> SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
>> Preemptible hierarchical RCU implementation.
>> NR_IRQS:624
>> MXC GPIO hardware
>> sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms
>> arm_max_freq=1GHz
>> MXC_Early serial console at MMIO 0x21e8000 (options '115200')
>> bootconsole [ttymxc1] enabled
>> Console: colour dummy device 80x30
>> Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)
>> pid_max: default: 32768 minimum: 301
>> Mount-cache hash table entries: 512
>> CPU: Testing write buffer coherency: ok
>> hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters
>> available
>> CPU1: Booted secondary processor
>> CPU2: Booted secondary processor
>> CPU3: Booted secondary processor
>> Brought up 4 CPUs
>> SMP: Total of 4 processors activated (6324.22 BogoMIPS).
>> devtmpfs: initialized
>> print_constraints: dummy:
>> NET: Registered protocol family 16
>> print_constraints: vddpu: 725 <--> 1300 mV at 1150 mV fast normal
>> print_constraints: vddcore: 725 <--> 1300 mV at 1150 mV fast normal
>> print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal
>> print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal
>> print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal
>> print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal
>> ------------ Board type Sabre Lite
>> imx_add_mxc_pwm:pdata=  (null)
>> imx_add_mxc_pwm:pdata=  (null)
>> imx_add_mxc_pwm:pdata=806f71d8
>> imx_add_mxc_pwm:pdata=  (null)
>> Flexcan NXP tja1040
>> hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
>> hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.
>> hw-breakpoint: maximum watchpoint size is 4 bytes.
>> L310 cache controller enabled
>> l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x02070000, Cache size:
>> 1048576 B
>> bio: create slab <bio-0> at 0
>> print_constraints: VDDA: 2500 mV
>> print_constraints: VDDIO: 3300 mV
>> machine_constraints_voltage: VDDD: unsupportable voltage constraints
>> reg-fixed-voltage reg-fixed-voltage.2: Failed to register regulator: -22
>> reg-fixed-voltage: probe of reg-fixed-voltage.2 failed with error -22
>> print_constraints: vmmc: 3300 mV
>> vgaarb: loaded
>> SCSI subsystem initialized
>> spi_imx imx6q-ecspi.0: probed
>> usbcore: registered new interface driver usbfs
>> usbcore: registered new interface driver hub
>> usbcore: registered new device driver usb
>> Freescale USB OTG Driver loaded, $Revision: 1.55 $
>> imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
>> imx-ipuv3 imx-ipuv3.1: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
>> mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 driver probed
>> mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 dphy version is 0x3130302a
>> MIPI CSI2 driver module loaded
>> Advanced Linux Sound Architecture Driver Version 1.0.24.
>> Bluetooth: Core ver 2.16
>> NET: Registered protocol family 31
>> Bluetooth: HCI device and connection manager initialized
>> Bluetooth: HCI socket layer initialized
>> Bluetooth: L2CAP socket layer initialized
>> Bluetooth: SCO socket layer initialized
>> cfg80211: Calling CRDA to update world regulatory domain
>> Switching to clocksource mxc_timer1
>> NET: Registered protocol family 2
>> IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
>> TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
>> TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
>> TCP: Hash tables configured (established 131072 bind 65536)
>> TCP reno registered
>> UDP hash table entries: 512 (order: 2, 16384 bytes)
>> UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
>> NET: Registered protocol family 1
>> RPC: Registered named UNIX socket transport module.
>> RPC: Registered udp transport module.
>> RPC: Registered tcp transport module.
>> RPC: Registered tcp NFSv4.1 backchannel transport module.
>> Static Power Management for Freescale i.MX6
>> wait mode is disabled for i.MX6
>> cpaddr = c0880000 suspend_iram_base=c0918000
>> PM driver module loaded
>> iMX6 PCIe PCIe RC mode imx_pcie_pltfm_probe entering.
>> PCIE: imx_pcie_pltfm_probe start link up.
>> link up failed, DB_R0:0x00bc6600, DB_R1:0x08200000!
>> IMX PCIe port: link down!
>> IMX usb wakeup probe
>> add wake up source irq 75
>> IMX usb wakeup probe
>> cpu regulator mode:ldo_enable
>> i.MXC CPU frequency driver
>> squashfs: version 4.0 (2009/01/31) Phillip Lougher
>> msgmni has been set to 1759
>> alg: No test for stdrng (krng)
>> io scheduler noop registered
>> io scheduler deadline registered
>> io scheduler cfq registered (default)
>> pwm_config: pwm freq = 32786, clk_select=2 clock_rate=22000000
>> pwm_config: pwm freq = 20000, clk_select=2 clock_rate=22000000
>> MIPI DSI driver module loaded
>> mxc_sdc_fb mxc_sdc_fb.0: mxcfb0 is turned off!
>> mxc_sdc_fb mxc_sdc_fb.1: mxcfb1 is turned off!
>> mxc_sdc_fb mxc_sdc_fb.2: mxcfb2 is turned off!
>> mxc_sdc_fb mxc_sdc_fb.3: mxcfb3 is turned off!
>> imx-sdma imx-sdma: loaded firmware 1.1
>> imx-sdma imx-sdma: initialized
>> Serial: IMX driver
>> imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
>> imx-uart.1: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX
>> old_ufcr=a81 new_ufcr=b01, old_ucr2=4027 new_ucr2=4027, old_ubir=f
>> num=1f7, old_ubmr=15b denom=c34
>> clk=80000000 div=7 num=504 denom=3125 baud=115200
>> console [ttymxc1] enabled, bootconsole disabled
>> console [ttymxc1] enabled, bootconsole disabled
>> loop: module loaded
>> No sata disk.
>> m25p80 spi0.0: sst25vf016b (2048 Kbytes)
>> Creating 3 MTD partitions on "m25p80":
>> 0x000000000000-0x0000000c0000 : "bootloader"
>> 0x0000000c0000-0x0000000c2000 : "ubparams"
>> 0x0000000c2000-0x000000200000 : "unused"
>> vcan: Virtual CAN interface driver
>> CAN device driver interface
>> flexcan netdevice driver
>> flexcan imx6q-flexcan.0: device registered (reg_base=c09a8000, irq=142)
>> FEC Ethernet Driver
>> fec_enet_mii_bus: probed
>> tun: Universal TUN/TAP device driver, 1.6
>> tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com
>> <mailto:maxk@qualcomm.com>>
>> ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
>> fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
>> fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
>> fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000
>> fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
>> hub 1-0:1.0: USB hub found
>> hub 1-0:1.0: 1 port detected
>> add wake up source irq 72
>> fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
>> fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
>> fsl-ehci fsl-ehci.1: irq 72, io base 0x02184200
>> fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
>> hub 2-0:1.0: USB hub found
>> hub 2-0:1.0: 1 port detected
>> usbcore: registered new interface driver cdc_acm
>> cdc_acm: USB Abstract Control Model driver for USB modems and ISDN
>> adapters
>> Initializing USB Mass Storage driver...
>> usbcore: registered new interface driver usb-storage
>> USB Mass Storage support registered.
>> usbcore: registered new interface driver usbserial
>> usbserial: USB Serial Driver core
>> USB Serial support registered for GSM modem (1-port)
>> usbcore: registered new interface driver option
>> option: v0.7.2:USB Driver for GSM modems
>> USB Serial support registered for Qualcomm USB modem
>> usbcore: registered new interface driver qcserial
>> ARC USBOTG Device Controller driver (1 August 2005)
>> mousedev: PS/2 mouse device common for all mice
>> input: gpio-keys as /devices/platform/gpio-keys/input/input0
>> tsc2004_prepare_for_reading: write_cmd -5
>> tsc2004: probe of 2-0048 failed with error -5
>> egalax_ts 2-0004: egalax_ts: failed to read firmware version
>> egalax_ts: probe of 2-0004 failed with error -5
>> ft5x06-ts 2-0038: ft5x06: Could not detect touch screen.
>> ft5x06: Feb 17 2014
>> check_alarm_past: alarm in the past
>> snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0
>> i2c /dev entries driver
>> Linux video capture interface: v2.00
>> i2c-core: driver [mma8450] using legacy suspend method
>> i2c-core: driver [mma8450] using legacy resume method
>> add mma8450 i2c driver
>> imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s
>> (nowayout=1)
>> device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised:
>> dm-devel@redhat.com <mailto:dm-devel@redhat.com>
>> Bluetooth: HCI UART driver ver 2.2
>> Bluetooth: HCILL protocol initialized
>> sdhci: Secure Digital Host Controller Interface driver
>> sdhci: Copyright(c) Pierre Ossman
>> mmc0: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA
>> sdhci sdhci-esdhc-imx.3: no write-protect pin available!
>> mmc1: SDHCI controller on platform [sdhci-esdhc-imx.3] using DMA
>> mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
>> VPU initialized
>> mxc_asrc registered
>> Galcore version 4.6.9.6622
>> Thermal calibration data is 0x55c4b47d
>> Thermal sensor with ratio = 176
>> Anatop Thermal registered as thermal_zone0
>> anatop_thermal_probe: default cooling device is cpufreq!
>> usbcore: registered new interface driver usbhid
>> usbhid: USB HID core driver
>> usbcore: registered new interface driver snd-usb-audio
>> mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio
>> imx-hdmi-soc-dai imx-hdmi-soc-dai.0: Failed: Load HDMI-video first.
>> sgtl5000 0-000a: Failed to get supply 'VDDD': -19
>> print_constraints: 0-000a: 850 <--> 1600 mV at 1200 mV normal
>> sgtl5000 0-000a: sgtl5000 revision 17
>> mmc0: new SDHC card at address e624
>> mmcblk0: mmc0:e624 SD04G 3.69 GiB
>>   mmcblk0: p1 p2
>> usb 2-1: new high speed USB device number 2 using fsl-ehci
>> asoc: sgtl5000 <-> imx-ssi.1 mapping ok
>> Initialize HDMI-audio failed. Load HDMI-video first!
>> ALSA device list:
>>    #0: sgtl5000-audio
>> NET: Registered protocol family 26
>> TCP cubic registered
>> NET: Registered protocol family 17
>> can: controller area network core (rev 20090105 abi 8)
>> NET: Registered protocol family 29
>> can: raw protocol (rev 20090105)
>> can: broadcast manager protocol (rev 20090105 t)
>> Bluetooth: RFCOMM TTY layer initialized
>> Bluetooth: RFCOMM socket layer initialized
>> Bluetooth: RFCOMM ver 1.11
>> Bluetooth: BNEP (Ethernet Emulation) ver 1.3
>> Bluetooth: BNEP filters: protocol multicast
>> Bluetooth: HIDP (Human Interface Emulation) ver 1.2
>> lib80211: common routines for IEEE802.11 drivers
>> VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
>> Bus freq driver module loaded
>> Bus freq driver Enabled
>> mxc_dvfs_core_probe
>> DVFS driver module loaded
>> snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0)
>> hub 2-1:1.0: USB hub found
>> hub 2-1:1.0: 3 ports detected
>> EXT3-fs: barriers not enabled
>> kjournald starting.  Commit interval 5 seconds
>> 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 .

>
>  *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.

>
>  udhcpc (v1.21.1) started
>> Sending discover...
>> Sending discover...
>> Sending discover...
>> *No lease, failing
>> Starting rpcbind daemon...rpcbind: cannot create socket for udp6
>> rpcbind: cannot create socket for tcp6*
>> done.
>> Mon Feb 17 06:24:00 UTC 2014
>> Running postinst /etc/rpm-postinsts/100-debianutils...
>> update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge
>> (continuing)
>>   Removing any system startup links for run-postinsts ...
>>    /etc/rcS.d/S99run-postinsts
>> INIT: Entering runlevel: 5
>> Starting Xserver
>> *open /dev/fb0: No such file or directory*
>> Starting system message bus: dbus.
>> Starting Connection Manager
>> Starting Dropbear SSH server: Will output 1024 bit rsa secret key to
>> '/etc/dropbear/dropbear_rsa_host_key'
>> Generating key, this may take a while...
>> Public key portion is:
>> ssh-rsa
>> AAAAB3NzaC1yc2EAAAADAQABAAAAgnuuabHxqECm6rB6ZK4b+
>> ETQYRINakuWDb93SS1AasT5n7dxIjxYh7BNAWQkTd8azrJwF7UdqBD9AlbEd
>> ZB6xP80lh5++hxCeoqAJVEaiInx
>> Fingerprint: md5 41:0e:c6:85:03:82:19:d6:5c:a2:31:f8:57:46:e7:2f
>> dropbear.
>> Starting advanced power management daemon: apmd.
>> 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.

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

[-- Attachment #2: Type: text/html, Size: 22961 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: SabreLite can not boot from SD card
  2014-02-20  4:41   ` Baodong Chen
@ 2014-02-20 14:22     ` Eric Nelson
  2014-02-21  1:50       ` Baodong Chen
  0 siblings, 1 reply; 10+ messages in thread
From: Eric Nelson @ 2014-02-20 14:22 UTC (permalink / raw)
  To: Baodong Chen; +Cc: meta-freescale@yoctoproject.org

Hi Baodong,

On 02/19/2014 09:41 PM, Baodong Chen wrote:
> Hi Eric:
> Thanks for your reply.

Please don't top-post!

> All i want is to have a sdcard image which contains u-boot, kernel and
> rootfs all in it.

And you get that with the stock image produced by Dora.

> I have written SD loader to NOR flash already.
 >
> So after bitbake, using the following two commands seems work for me,
> the u-boot is loaded by SD loader from NOR flash and kernel is loaded by
> u-boot.
> dd if=fsl-image-gui-nitrogen6x.sdcard of=/dev/sdb
> dd if=u-boot.imx of=/dev/sdb bs=512 seek=2
>
> Am i right? or am i misunderstaning something?
>

Okay, here's where I drop out.

The SABRE Lite and all Boundary Devices boards boot to SPI-NOR.

If you're re-programming them with the SPI-to-SD-Loader, you're
explicitly stating that you know what you're doing.

If you're over-riding that, you're probably either testing or
preparing for a custom design, and you **will** need to understand
how the image creation step in Yocto works.

All of the Freescale boards are already configured to do this,
so I'd recommend that you look at how that's done.

Perhaps others on this list can offer guidance.

If you get lost in the details, you can also just write a
post-installation script to create your SD card using the
parts provided in tmp/deploy/images/ instead of simply
using dd.

Regards,


Eric


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Errors booting SABRE Lite (was SabreLite can not boot from SD card)
  2014-02-20  5:30       ` Baodong Chen
@ 2014-02-20 14:35         ` Eric Nelson
  0 siblings, 0 replies; 10+ messages in thread
From: Eric Nelson @ 2014-02-20 14:35 UTC (permalink / raw)
  To: Baodong Chen; +Cc: meta-freescale@yoctoproject.org

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@boundarydevices.com
> <mailto:eric.nelson@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@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@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!



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: SabreLite can not boot from SD card
  2014-02-20 14:22     ` Eric Nelson
@ 2014-02-21  1:50       ` Baodong Chen
  0 siblings, 0 replies; 10+ messages in thread
From: Baodong Chen @ 2014-02-21  1:50 UTC (permalink / raw)
  To: Eric Nelson; +Cc: meta-freescale@yoctoproject.org

[-- Attachment #1: Type: text/plain, Size: 2018 bytes --]

On Thu, Feb 20, 2014 at 10:22 PM, Eric Nelson <
eric.nelson@boundarydevices.com> wrote:

> Hi Baodong,
>
>
> On 02/19/2014 09:41 PM, Baodong Chen wrote:
>
>> Hi Eric:
>> Thanks for your reply.
>>
>
> Please don't top-post!
>
>
>  All i want is to have a sdcard image which contains u-boot, kernel and
>> rootfs all in it.
>>
>
> And you get that with the stock image produced by Dora.

Yes, the u-boot.imx located in build/tmp/deploy/images/nitrogen6x

>
>
>  I have written SD loader to NOR flash already.
>>
> >
>
>> So after bitbake, using the following two commands seems work for me,
>> the u-boot is loaded by SD loader from NOR flash and kernel is loaded by
>> u-boot.
>> dd if=fsl-image-gui-nitrogen6x.sdcard of=/dev/sdb
>> dd if=u-boot.imx of=/dev/sdb bs=512 seek=2
>>
>> Am i right? or am i misunderstaning something?
>>
>>
> Okay, here's where I drop out.
>
> The SABRE Lite and all Boundary Devices boards boot to SPI-NOR.
>
> If you're re-programming them with the SPI-to-SD-Loader, you're
> explicitly stating that you know what you're doing.
>
> If you're over-riding that, you're probably either testing or
> preparing for a custom design, and you **will** need to understand
> how the image creation step in Yocto works.
>
I will hack
https://github.com/Freescale/meta-fsl-arm/blob/dora/classes/image_types_fsl.bbclass

>
> All of the Freescale boards are already configured to do this,
> so I'd recommend that you look at how that's done.
>
> Perhaps others on this list can offer guidance.
>
> If you get lost in the details, you can also just write a
> post-installation script to create your SD card using the
> parts provided in tmp/deploy/images/ instead of simply
> using dd.
>
The u-boot.imx located in build/tmp/deploy/images/nitrogen6x,  but the
fsl-image-gui-nitrogen6x.sdcard file
do not contain the u-boot.imx in it, as you said, uboot.imx default should
in SPI NOR flash. so this is ok

>
> Regards,
>
>
> Eric
>

[-- Attachment #2: Type: text/html, Size: 3619 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2014-02-21  1:50 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-02-20  0:36 SabreLite can not boot from SD card Baodong Chen
2014-02-20  0:44 ` Baodong Chen
2014-02-20  1:13   ` Baodong Chen
2014-02-20  1:30     ` Errors booting SABRE Lite (was SabreLite can not boot from SD card) Eric Nelson
2014-02-20  5:30       ` Baodong Chen
2014-02-20 14:35         ` Eric Nelson
2014-02-20  0:58 ` SabreLite can not boot from SD card Eric Nelson
2014-02-20  4:41   ` Baodong Chen
2014-02-20 14:22     ` Eric Nelson
2014-02-21  1:50       ` Baodong Chen

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.