Hello Petr,
Sure. Here is a link to the sources for the meta-fsl-arm layer:
https://github.com/Freescale/meta-fsl-arm
And a link to the meta-fsl-arm-extra layer:
https://github.com/Freescale/meta-fsl-arm-extra
Finally, here is a link to the Yocto Project Quick Start guide, which has instructions to get you up and running with an initial build:
http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html
Thanks,
Timesys Support
As mentioned above 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.
Board using: phycore vybrid (pcl052)
Host side command used for building:
source ./oe-init-build-env
git clone https://github.com/Freescale/meta-fsl-arm-extra.git -b dizzy
git clone https://github.com/Freescale/meta-fsl-arm.git -b dizzy
Edited local.conf with MACHINE ??= "pcl052" and bblayers.conf and that is looking like below.
-----------------------------------------------------------------------------------------------------------------------------
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "6"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/home/user/I4_Work/poky/meta \
/home/user/I4_Work/poky/meta-yocto \
/home/user/I4_Work/poky/meta-yocto-bsp \
/home/user/I4_Work/poky/meta-fsl-arm-extra \
/home/user/I4_Work/poky/meta-fsl-arm \
/home/user/I4_Work/poky/meta-fsl-demos \
"
BBLAYERS_NON_REMOVABLE ?= " \
/home/user/I4_Work/poky/meta \
/home/user/I4_Work/poky/meta-yocto \
"
------------------------------------------------------------------------------------------------------------------------------
bitbake -u goggle core-image-minimal
After building successfully got the tar ball of RFS. Copied to SD card. Extracted it. Executed "sudo ln -s sbin/init ." & "sudo chown root ."
U-Boot 2011.12 (Jul 18 2016 - 14:46:44)
CPU: Freescale VyBrid 600 family rev1.3 at 0 MHz
Reset cause:
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 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.
Helllo Anindya,
A few thoughts come to mind:
-Are you using dizzy branch for your other meta-layers? You will want to do this if you have not already, and rebuild
-I am unsure of your process for extracting the rootfs to the SD card. Can you try 'sudo tar -xvf /path/to/rootfs -C /path/to/SD/card/partition'? Can you also try DDing the SD card image produced by your Yocto build to your SD card?
Thanks,
Tony
Hi Tony,
Actually previously I was building the kernel separately using poky toolchain and rootfs taken from yocto. But now I used yocto kernel which I built using yocto build system and it is working fine. I found some modifications between yocto kernel and externel kernel source which I downloaded from "ftp://ftp.phytec.com/products/PCL-052_Cosmic-Vybrid/Linux/PD13.1.0/MCC_Demo/". Though this version of kernel is working fine with buildroot, openWRT but not working with Yocto.
Any way, thanks for giving some quick suggestions.
Thanks & regards,
Anindya
Hello Petr,
We have added Vybrid Tower support (machine name twr-vf65gs10) to the meta-fsl-arm Yocto project layer, and the Phytec phyCORE Vybrid (pcm052), Phytec Cosmic+ Vybrid (pcl052), and Device Solutions Quartz Vybrid (quartz) to the meta-fsl-arm-extra layer. Let me know if you have any questions.
Thanks,
Timesys Support
Hi Timesys Support,
Thank you for your reply. Can you please point me to some related sources and/or documentation?
Thanks,
Petr
Hello Petr,
Sure. Here is a link to the sources for the meta-fsl-arm layer:
https://github.com/Freescale/meta-fsl-arm
And a link to the meta-fsl-arm-extra layer:
https://github.com/Freescale/meta-fsl-arm-extra
Finally, here is a link to the Yocto Project Quick Start guide, which has instructions to get you up and running with an initial build:
http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html
Thanks,
Timesys Support
I just gave this a try on my pcm052. Worked pretty much out of the box. Great work!
The only think I had to change was:
meta-fsl-arm/conf/machine/include/imx-base.inc line 121:
KERNEL_IMAGETYPE = "zImage"
to
KERNEL_IMAGETYPE ?= "zImage"
With this change I could specify KERNEL_IMAGETYPE = "uImage" in my local.conf. The pcm052 u-boot is not configured to support bootz, so I have to use uImage.
Perfect, thank you!
We have partnered with timesyssupport for Linux support on Vybrid and they will be more than happy to help you out. We have no plans to support a community BSP for Vybrid in Yocto.
Best Regards,
Ragan