Bug 9990

Summary:	Yocto 1.7 for phycore-vybrid is unable to boot.
Product:	[Build System, Metadata & Runtime] BSPs	Reporter:	Anindya Gayen <anindyasundar.gayen>
Component:	bsps-meta-fsl-arm	Assignee:	Atul Bansal <atul.bansal>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	critical
Priority:	Medium+	CC:	anindyasundar.gayen, richard.purdie, sgw
Version:	1.7.4
Target Milestone:	1.7.4
Hardware:	Other
OS:	arm
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know

Description Anindya Gayen 2016-07-20 15:50:08 UTC

I followed the documentation mentioned at https://community.nxp.com/thread/333571. As mentioned there I inserted two layers as meta-fsl-arm & meta-fsl-arm-extra. There yocto building is done successfully but at booting time it is giving System Halted massage after kernel boot. Please get the total kernel logs below.




U-Boot 2011.12 (Jul 18 2016 - 14:46:44)

CPU:   Freescale VyBrid 600 family rev1.3 at 0 MHz
Reset cause: <NULL>
Board: Cosmic for phyCORE-Vybrid
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  512 MiB
MMC:   FSL_SDHC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   Link UP timeout
FEC1
Hit any key to stop autoboot:  0 
reading uImage-3.0-ts-armv7l

2521804 bytes read
## Booting kernel from Legacy Image at 80010000 ...
   Image Name:   Linux-3.0.15
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2521740 Bytes = 2.4 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Linux version 3.0.15 (ganindya@Ani) (gcc version 4.9.3 20150529 (release) [ARM/embedded-4_9-branch revision 227977] (GNU Tools for ARM Embedded Processors) ) #1 Mon Jul 18 14:53:58 IST 2016
CPU: ARMv7 Processor [410fc051] revision 1 (ARMv7), cr=10c53c7d
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: PHYTEC Cosmic Board for phyCORE-Vybrid
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: rw mem=256M console=ttymxc1,115200n8 init=/sbin/init root=/dev/mmcblk0p3 rootwait rootfstype=ext2 mtdparts=NAND:256k(spare),256k(bootloader),128k(env),4m(kernel),-(rootfs)
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 256MB = 256MB total
Memory: 254648k/254648k available, 7496k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xf4600000 - 0xffe00000   ( 184 MB)
    vmalloc : 0x90800000 - 0xf2000000   (1560 MB)
    lowmem  : 0x80000000 - 0x90000000   ( 256 MB)
    modules : 0x7f000000 - 0x80000000   (  16 MB)
      .init : 0x80008000 - 0x8002f000   ( 156 kB)
      .text : 0x8002f000 - 0x804a2bc4   (4559 kB)
      .data : 0x804a4000 - 0x804d4e40   ( 196 kB)
       .bss : 0x804d4e64 - 0x805159a0   ( 259 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:456
MVF GPIO hardware
sched_clock: 32 bits at 66MHz, resolution 15ns, wraps every 65075ms
Console: colour dummy device 80x30
Calibrating delay loop... 262.96 BogoMIPS (lpj=1314816)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
hw perfevents: enabled with ARMv7 Cortex-A5 PMU driver, 3 counters available
NET: Registered protocol family 16
mcf_edma: Initialized successfully
hw-breakpoint: Debug register access (0xee003e17) caused undefined instruction on CPU 0
hw-breakpoint: Debug register access (0xee004e52) caused undefined instruction on CPU 0
IMX usb wakeup probe. id=1
IMX usb wakeup probe. id=0
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.24.
Switching to clocksource pit
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 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 Vybrid
PM driver module loaded
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 497
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Console: switching to colour frame buffer device 80x30
fb0: Layer0 fb device registered successfully.
fb1:  fb device registered successfully.
fb2:  fb device registered successfully.
fb3:  fb device registered successfully.
Serial: MVF driver
imx-uart.1: ttymxc1 at MMIO 0x40028000 (irq = 94) is a IMX
console [ttymxc1] enabled
brd: module loaded
FSL NFC MTD nand Driver 1.0
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xcc (Micron NAND 512MiB 3,3V 16-bit)
5 cmdlinepart partitions found on MTD device NAND
Creating 5 MTD partitions on "NAND":
0x000000000000-0x000000040000 : "spare"
0x000000040000-0x000000080000 : "bootloader"
0x000000080000-0x0000000a0000 : "env"
0x0000000a0000-0x0000004a0000 : "kernel"
0x0000004a0000-0x000020000000 : "rootfs"
FEC Ethernet Driver
fec_enet_mii_bus: probed
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.1: irq 108, io base 0x400b4000
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
ARC USBOTG Device Controller driver (1 August 2005)
g_ether gadget: using random self ethernet address
g_ether gadget: using random host ethernet address
usb0: MAC ca:22:97:6f:20:5f
usb0: HOST MAC de:0e:4d:7b:3c:e9
g_ether gadget: controller 'fsl-usb2-udc' not recognized; trying CDC Ethernet (ECM)
g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
g_ether gadget: g_ether ready
fsl-usb2-udc: bind to driver g_ether 
mousedev: PS/2 mouse device common for all mice
input: gpio-keys as /devices/platform/gpio-keys/input/input0
snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0
i2c /dev entries driver
imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0)
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci sdhci-esdhc-imx.1: no write-protect pin available!
mmc0: SDHCI controller on platform [sdhci-esdhc-imx.1] using ADMA
ALSA device list:
  No soundcards found.
TCP cubic registered
NET: Registered protocol family 17
VFP support v0.3: implementor 41 architecture 2 part 30 variant 5 rev 1
snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0)
Waiting for root device /dev/mmcblk0p3...
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new SDHC card at address aaaa
mmcblk0: mmc0:aaaa SS08G 7.40 GiB 
 mmcblk0: p1 p2 p3
EXT2-fs (mmcblk0p3): warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem) on device 179:3.
Freeing init memory: 156K
System halted.   <------------------------------ IT IS STUCKING HERE...

Comment 1 Otavio Salvador 2016-07-21 16:19:54 UTC

Phytec board is maintained by Timesys so I am assigning it for them.

Comment 2 Richard Purdie 2016-10-06 15:29:46 UTC

Timesys don't track issues in the Yocto Project bugzilla as far as I know and haven't responded so I am closing this issue here as I don't think it will go anywhere. Please take it directly up with the BSP maintainers if there is still an issue.