UEFI support for Crown Bay
Yocto=1.2
BSB = Crown Bay (Intel Atom Processor E660 with Intel Platform Controller Hub EG20T Development Kit)
Target System= Inforce Computing, Inc. - SYS9400 Reference Platform - VGA output only.
UEFI only no BIOS
Base Image: core-image-minimal
Hob used to build the image
The target platform only has UEFI and doesn't have traditional BIOS. I am able to re-configure the UEFI firmware using the BLDK application if needed. The Crown Bay BSP doesn't include an efi loader (bootia32.efi) like Cedar Trail BSP in the live image (hddimg). If I add the EFI boot files from Cedar Trail live image, the USB flash disk presents the menu for boot or install. Upon selecting boot, I can see output on the serial console, but it eventually stops no output on the VGA monitor. I have attached the output from the serial port.
1. Is UEFI supported with Crown Bay BSP? Is there a flag that needs to be set like EFI = "1"?
There seems to be discussions about this back in 2011:
https://lists.yoctoproject.org/pipermail/yocto/2011-November/005806.html
http://lists.linuxtogo.org/pipermail/openembedded-core/2011-November/012972.
html
2. Is it possible to setup serial console for Crown Bay? I tried the following flags from the n450 information:
SYSLINUX_OPTS_atom-pc = "serial 0 115200"
SERIAL_CONSOLE_atom-pc = "115200 ttyS0"
APPEND_atom-pc = "console=ttyS0,115200 console=tty0"
3. There was some discussion about EMGD and X Windows issues and a possible fix. Where can I download the latest BSP to try out?
Regards,
Sean Liming
Annabooks
Tel: 714-970-7523 / Cell: 858-774-3176
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 3.2.18-yocto-standard (sean@sean76Pro) (gcc version 4.6.4 20120303 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Sep 21 21:06:20 PDT 2012 BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
BIOS-e820: 0000000000100000 - 000000001f2df000 (usable)
BIOS-e820: 000000001f2df000 - 000000001f39f000 (reserved)
BIOS-e820: 000000001f39f000 - 000000001f3df000 (ACPI data)
BIOS-e820: 000000001f3df000 - 000000001f4c2000 (ACPI NVS)
BIOS-e820: 000000001f4c2000 - 000000001f4ca000 (reserved)
BIOS-e820: 000000001f4ca000 - 000000001f6da000 (ACPI NVS)
BIOS-e820: 000000001f6da000 - 000000001f6dc000 (usable)
BIOS-e820: 000000001f6dc000 - 000000001f6df000 (ACPI NVS)
BIOS-e820: 000000001f6df000 - 000000001f6ef000 (reserved)
BIOS-e820: 000000001f6ef000 - 000000001f6f0000 (usable)
BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved)
BIOS-e820: 00000000fffc0000 - 00000000fffca000 (reserved)
Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
DMI not present or invalid.last_pfn = 0x1f6f0 max_arch_pfn = 0x100000
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106init_memory_mapping: 0000000000000000-000000001f6f0000
RAMDISK: 1dd2f000 - 1e29b000
ACPI Error: A valid RSDP was not found (20110623/tbxfroot-219)
0MB HIGHMEM available.
502MB LOWMEM available.
mapped low ram: 0 - 1f6f0000
low ram: 0 - 1f6f0000
Zone PFN ranges:
DMA 0x00000010 -> 0x00001000
Normal 0x00001000 -> 0x0001f6f0
HighMem empty
Movable zone start PFN for each node
early_node_map[4] active PFN ranges
0: 0x00000010 -> 0x0000009f
0: 0x00000100 -> 0x0001f2df
0: 0x0001f6da -> 0x0001f6dc
0: 0x0001f6ef -> 0x0001f6f0Using APIC driver default
SMP: Allowing 1 CPUs, 0 hotplug CPUs
Found and enabled local APIC!
Allocating PCI resources starting at 1f6f0000 (gap: 1f6f0000:df62c000)setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1
PERCPU: Embedded 13 pages/cpu @deee0000 s28992 r0 d24256 u53248
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 126595
Kernel command line: BOOT_IMAGE=/vmlinuz LABEL=boot root=/dev/ram0 console=ttyS0,115200 console=tty0 PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Initializing CPU#0
allocated 2059776 bytes of page_cgroup
please try 'cgroup_disable=memory' option if you don't want memory cgroups
Initializing HighMem for node 0 (00000000:00000000)
Memory: 489912k/515008k available (5079k kernel code, 20492k reserved, 2307k data, 488k init, 0k highmem) virtual kernel memory layout:
fixmap : 0xfff17000 - 0xfffff000 ( 928 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xdfef0000 - 0xff7fe000 ( 505 MB)
lowmem : 0xc0000000 - 0xdf6f0000 ( 502 MB)
.init : 0xc1737000 - 0xc17b1000 ( 488 kB)
.data : 0xc14f5f09 - 0xc1736bc0 (2307 kB)
.text : 0xc1000000 - 0xc14f5f09 (5079 kB)Checking if this processor honours the WP bit even in supervisor mode...Ok.
SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptible hierarchical RCU implementation.
NR_IRQS:2304 nr_irqs:256 16
Console: colour dummy device 80x25
console [tty0] enabled
console [ttyS0] enabled
Fast TSC calibration using PIT
Detected 1300.190 MHz processor.
Calibrating delay loop (skipped), value calculated using timer frequency.. 2600.38 BogoMIPS (lpj=5200760)pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
Initializing cgroup subsys debug
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys blkio
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
using mwait in idle threads.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 20k freed
ftrace: allocating 21515 entries in 43 pages
weird, boot CPU (#0) not listed by the BIOS.
SMP motherboard not detected.
Enabling APIC mode: Flat. Using 0 I/O APICs
SMP disabled
Performance Events: PEBS fmt0+, generic architected perfmon, Intel PMU driver.
... version: 3 ... bit width: 40 ... generic registers: 2 ... value mask: 000000ffffffffff ... max period: 000000007fffffff ... fixed-purpose events: 3 ... event mask: 0000000700000003
Brought up 1 CPUs
Total of 1 processors activated (2600.38 BogoMIPS).
devtmpfs: initialized
NET: Registered protocol family 16
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: Interpreter disabled.
vgaarb: loaded
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.
PCI: Probing PCI hardware
pci 0000:00:17.0: PCI bridge to [bus 01-02]
pci 0000:01:00.0: PCI bridge to [bus 02-02]
vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
pnp: PnP ACPI: disabled
pci 0000:01:00.0: no compatible bridge window for [mem 0xffff0000-0xffffffff pref] pci 0000:02:00.0: no compatible bridge window for [mem 0xfffe0000-0xffffffff pref] pci 0000:02:06.0: no compatible bridge window for [mem 0xfffe0000-0xffffffff pref] pci 0000:00:17.0: BAR 9: assigned [mem 0x20000000-0x201fffff pref] pci 0000:01:00.0: BAR 9: assigned [mem 0x20000000-0x200fffff pref] pci 0000:01:00.0: BAR 6: assigned [mem 0x20100000-0x2010ffff pref] pci 0000:02:00.0: BAR 6: assigned [mem 0x20000000-0x2001ffff pref] pci 0000:02:06.0: BAR 6: assigned [mem 0x20020000-0x2003ffff pref] pci 0000:01:00.0: PCI bridge to [bus 02-02]
pci 0000:01:00.0: bridge window [io 0x2000-0x2fff] pci 0000:01:00.0: bridge window [mem 0xa0000000-0xa00fffff] pci 0000:01:00.0: bridge window [mem 0x20000000-0x200fffff pref] pci 0000:00:17.0: PCI bridge to [bus 01-02] pci 0000:00:17.0: bridge window [io 0x2000-0x2fff] pci 0000:00:17.0: bridge window [mem 0xa0000000-0xa00fffff] pci 0000:00:17.0: bridge window [mem 0x20000000-0x201fffff pref]
pci 0000:00:17.0: can't find IRQ for PCI INT A; please try using pci=biosirq pci 0000:01:00.0: can't find IRQ for PCI INT A; please try using pci=biosirq
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes) TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 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.
pci 0000:02:02.0: can't find IRQ for PCI INT B; please try using pci=biosirq pci 0000:02:02.1: can't find IRQ for PCI INT B; please try using pci=biosirq pci 0000:02:02.2: can't find IRQ for PCI INT B; please try using pci=biosirq pci 0000:02:02.3: can't find IRQ for PCI INT B; please try using pci=biosirq pci 0000:02:08.0: can't find IRQ for PCI INT A; please try using pci=biosirq pci 0000:02:08.1: can't find IRQ for PCI INT A; please try using pci=biosirq pci 0000:02:08.2: can't find IRQ for PCI INT A; please try using pci=biosirq pci 0000:02:08.3: can't find IRQ for PCI INT A; please try using pci=biosirq Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 5552k freed
platform rtc_cmos: registered platform RTC device (no PNP device found)
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Registering unionfs 2.5.10 (for 3.1.0-rc4)
msgmni has been set to 967
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254) io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)pch_gpio 0000:02:00.2: can't find IRQ for PCI INT A; please try using pci=biosirq pch_gpio 0000:02:00.2: pch_gpio_probe request_irq failedpch_gpio 0000:02:00.2: pch_gpio_probe Failed returns 0
pcieport 0000:00:17.0: device [8086:8184] has invalid IRQ; check vendor BIOS Marking TSC unstable due to TSC halts in idle states deeper than C2 pch-dma 0000:02:0a.0: enabling device (0000 -> 0002)
pch-dma 0000:02:0a.0: can't find IRQ for PCI INT B; please try using pci=biosirq pch-dma 0000:02:0a.0: Failed to request IRQ
pch-dma: probe of 0000:02:0a.0 failed with error -16
pch-dma 0000:02:0c.0: enabling device (0000 -> 0002)
pch-dma 0000:02:0c.0: can't find IRQ for PCI INT C; please try using pci=biosirq pch-dma 0000:02:0c.0: Failed to request IRQ
pch-dma: probe of 0000:02:0c.0 failed with error -16
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
serial 0000:02:0a.1: enabling device (0000 -> 0003)
serial 0000:02:0a.1: can't find IRQ for PCI INT B; please try using pci=biosirq 0000:02:0a.1: ttyS2 at I/O 0x2058 (irq = 0) is a 16550A
serial 0000:02:0a.2: enabling device (0000 -> 0003)
serial 0000:02:0a.2: can't find IRQ for PCI INT B; please try using pci=biosirq 0000:02:0a.2: ttyS3 at I/O 0x2050 (irq = 0) is a 16550A
serial 0000:02:0a.3: enabling device (0000 -> 0003)
serial 0000:02:0a.3: can't find IRQ for PCI INT B; please try using pci=biosirq Couldn't register serial port 0000:02:0a.3: -28
serial 0000:02:0a.4: enabling device (0000 -> 0003)
serial 0000:02:0a.4: can't find IRQ for PCI INT B; please try using pci=biosirq Couldn't register serial port 0000:02:0a.4: -28
Linux agpgart interface v0.103
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
ahci 0000:02:06.0: can't find IRQ for PCI INT D; please try using pci=biosirq ahci 0000:02:06.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA mode ahci 0000:02:06.0: flags: ncq sntf pm led clo only pmp pio slum part ccc
------------[ cut here ]------------ WARNING: at /home/sean/Yocto/hobbuilds/tmp/work/crownbay-poky-linux/linux-yocto-3.2.18+git8+5b4c9dc78b5ae607173cc3ddab9bce1b5f78129b_1+48101e609711fc) Modules linked in: Pid: 1, comm: swapper/0 Not tainted 3.2.18-yocto-standard #1 Call Trace: [<c14e8696>] ? printk+0x1e/0x20 [<c103bfc3>] warn_slowpath_common+0x73/0xa0 [<c12e476c>] ? ata_host_activate+0xec/0x100 [<c12e476c>] ? ata_host_activate+0xec/0x100 [<c103c013>] warn_slowpath_null+0x23/0x30 [<c12e476c>] ata_host_activate+0xec/0x100 [<c12f7c20>] ? ahci_pmp_qc_defer+0x40/0x40 [<c12f5d84>] ahci_init_one+0x5c4/0x8d0 [<c14eea56>] ? _raw_spin_unlock_irqrestore+0x16/0x40 [<c12223dd>] pci_device_probe+0x8d/0x120 [<c114b8b8>] ? sysfs_create_link+0x18/0x20 [<c12b4e99>] driver_probe_device+0x69/0x170 [<c1221f72>] ? pci_match_device+0xb2/0xc0 [<c12b5031>] __driver_attach+0x91/0xa0 [<c12b4fa0>] ? driver_probe_device+0x170/0x170 [<c12b40e9>] bus_for_each_dev+0x49/0x80 [<c12b4bb2>] driver_attach+0x22/0x30 [<c12b4fa0>] ? driver_probe_device+0x170/0x170 [<c12b488f>] bus_add_driver+0x17f/0x260 [<c1222240>] ? pci_dev_put+0x20/0x20 [<c12b54eb>] driver_register+0x6b/0x120 [<c1222e03>] __pci_register_driver+0x43/0xc0 [<c175bb4f>] ahci_init+0x14/0x16 [<c1001126>] do_one_initcall+0x36/0x170 [<c1209b2a>] ? radix_tree_lookup+0xa/0x10 [<c1083824>] ? irq_to_desc+0x14/0x20 [<c175bb3b>] ? ata_sff_init+0x39/0x39 [<c17377de>] kernel_init+0xaf/0x16e [<c1031685>] ? schedule_tail+0x25/0xa0 [<c14f4c46>] ? ret_from_fork+0x6/0x1c [<c173772f>] ? start_kernel+0x2fb/0x2fb [<c173772f>] ? start_kernel+0x2fb/0x2fb [<c14f51f6>] kernel_thread_helper+0x6/0x10 ---[ end trace 8ac8d7ad169d2d66 ]---
scsi0 : ahci
scsi1 : ahci
ata1: SATA max UDMA/133 abar m1024@0xa0003000 port 0xa0003100
ata2: SATA max UDMA/133 abar m1024@0xa0003000 port 0xa0003180pch_spi 0000:02:0c.1: enabling device (0000 -> 0002)pch_spi 0000:02:0c.1: can't find IRQ for PCI INT C; please try using pci=biosirq pch-spi pch-spi.0: pch_spi_pd_probe request_irq failed
pch-spi: probe of pch-spi.0 failed with error -16
CAN device driver interfacepch_can 0000:02:0c.3: enabling device (0000 -> 0002)pch_can 0000:02:0c.3: can't find IRQ for PCI INT C; please try using pci=biosirq pch_can 0000:02:0c.3: (unregistered net_device): PCH CAN opened without MSI
e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
e1000: Copyright (c) 1999-2006 Intel Corporation.
e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-k
e1000e: Copyright(c) 1999 - 2011 Intel Corporation.pch_gbe 0000:02:00.1: enabling device (0000 -> 0003)pch_gbe 0000:02:00.1: can't find IRQ for PCI INT A; please try using pci=biosirq pch_gbe 0000:02:00.1: Invalid MAC address, interface disabled.pch_gbe 0000:02:00.1: MAC address : 00:00:00:00:00:00ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driverehci_hcd 0000:02:02.3: can't find IRQ for PCI INT B; please try using pci=biosirq ehci_hcd 0000:02:02.3: Found HC with no IRQ. Check BIOS/PCI 0000:02:02.3 setup! ehci_hcd 0000:02:02.3: init 0000:02:02.3 fail, -19ehci_hcd 0000:02:08.3: can't find IRQ for PCI INT A; please try using pci=biosirq ehci_hcd 0000:02:08.3: Found HC with no IRQ. Check BIOS/PCI 0000:02:08.3 setup! ehci_hcd 0000:02:08.3: init 0000:02:08.3 fail, -19ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driverohci_hcd 0000:02:02.0: can't find IRQ for PCI INT B; please try using pci=biosirq ohci_hcd 0000:02:02.0: Found HC with no IRQ. Check BIOS/PCI 0000:02:02.0 setup! ohci_hcd 0000:02:02.0: init 0000:02:02.0 fail, -19ohci_hcd 0000:02:02.1: can't find IRQ for PCI INT B; please try using pci=biosirq ohci_hcd 0000:02:02.1: Found HC with no IRQ. Check BIOS/PCI 0000:02:02.1 setup! ohci_hcd 0000:02:02.1: init 0000:02:02.1 fail, -19ohci_hcd 0000:02:02.2: can't find IRQ for PCI INT B; please try using pci=biosirq ohci_hcd 0000:02:02.2: Found HC with no IRQ. Check BIOS/PCI 0000:02:02.2 setup! ohci_hcd 0000:02:02.2: init 0000:02:02.2 fail, -19ohci_hcd 0000:02:08.0: can't find IRQ for PCI INT A; please try using pci=biosirq ohci_hcd 0000:02:08.0: Found HC with no IRQ. Check BIOS/PCI 0000:02:08.0 setup! ohci_hcd 0000:02:08.0: init 0000:02:08.0 fail, -19ohci_hcd 0000:02:08.1: can't find IRQ for PCI INT A; please try using pci=biosirq ohci_hcd 0000:02:08.1: Found HC with no IRQ. Check BIOS/PCI 0000:02:08.1 setup! ohci_hcd 0000:02:08.1: init 0000:02:08.1 fail, -19ohci_hcd 0000:02:08.2: can't find IRQ for PCI INT A; please try using pci=biosirq ohci_hcd 0000:02:08.2: Found HC with no IRQ. Check BIOS/PCI 0000:02:08.2 setup! ohci_hcd 0000:02:08.2: init 0000:02:08.2 fail, -19
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.pch_udc 0000:02:02.4: enabling device (0000 -> 0002)pch_udc 0000:02:02.4: can't find IRQ for PCI INT B; please try using pci=biosirq pch_udc 0000:02:02.4: pch_udc_probe: irq not set
(NULL device *): gadget not registered.
i8042: PNP: No PS/2 controller found. Probing ports directly.
i8042: No controller found
mousedev: PS/2 mouse device common for all micei2c_eg20t 0000:02:0c.2: enabling device (0000 -> 0002)i2c_eg20t 0000:02:0c.2: can't find IRQ for PCI INT C; please try using pci=biosirq i2c_eg20t 0000:02:0c.2: pch_i2c_probe :request_irq FAILEDi2c_eg20t: probe of 0000:02:0c.2 failed with error -16
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: multipath personality registered for level -4
md: faulty personality registered for level -5
device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: [email protected]
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pci 0000:02:04.0: SDHCI controller found [8086:8809] (rev 1) sdhci-pci 0000:02:04.0: can't find IRQ for PCI INT C; please try using pci=biosirq sdhci-pci 0000:02:04.0: Invalid iomem size. You may experience problems.
sdhci-pci: probe of 0000:02:04.0 failed with error -16
sdhci-pci 0000:02:04.1: SDHCI controller found [8086:880a] (rev 1) sdhci-pci 0000:02:04.1: can't find IRQ for PCI INT C; please try using pci=biosirq sdhci-pci 0000:02:04.1: Invalid iomem size. You may experience problems.
sdhci-pci: probe of 0000:02:04.1 failed with error -16
usbcore: registered new interface driver usbhid
usbhid: USB HID core driversnd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
ata1: SATA link down (SStatus 0 SControl 300)snd_hda_intel 0000:00:1b.0: can't find IRQ for PCI INT A; please try using pci=biosirq
ata2: SATA link down (SStatus 0 SControl 300)
hda-intel: unable to grab IRQ 0, disabling devicesnd_hda_intel: probe of 0000:00:1b.0 failed with error -16
ALSA device list:
No soundcards found.
oprofile: using NMI interrupt.
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
Registering the dns_resolver key type
Using IPI No-Shortcut mode
registered taskstats version 1
console [netcon0] enabled
netconsole: network logging started
Freeing unused kernel memory: 488k freed
udev[41]: starting version 164
Quoted 33 lines · Sean Liming
Yocto=1.2
BSB = Crown Bay (Intel Atom Processor E660 with Intel Platform Controller Hub EG20T Development Kit)
Target System= Inforce Computing, Inc. - SYS9400 Reference Platform - VGA output only.
UEFI only no BIOS
Base Image: core-image-minimal
Hob used to build the image
The target platform only has UEFI and doesn’t have traditional BIOS. I am able to re-configure the UEFI firmware using the BLDK application if needed. The Crown Bay BSP doesn’t include an efi loader (bootia32.efi) like Cedar Trail BSP in the live image (hddimg). If I add the EFI boot files from Cedar Trail live image, the USB flash disk presents the menu for boot or install. Upon selecting boot, I can see output on the serial console, but it eventually stops no output on the VGA monitor. I have attached the output from the serial port.
Quoted 3 lines
1. Is UEFI supported with Crown Bay BSP? Is there a flag that needs to be set like EFI = “1”?
Hi,
The Crown Bay BSP doesn't yet have EFI support - I added it earlier this year but had some problems getting it to work. I just now updated it and tried again but though I see the grub menu, selecting 'boot' also gets me a blank screen, and I don't even get serial output.
If you want to try it out for yourself and see if you get better results, here's the branch (the top 6 commits add efi support and some related cleanup):
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-contrib/log/?h=tzanussi/crownbay-efi-v2
The current BSP can be found in the meta-intel repo in the meta-crownbay directory (the README has some build instructions):
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-crownbay
Since you're using the Inforce Sys9400, though, I'm thinking that it might make more sense to use the meta-sys940x BSP:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-sys940x
I see it already has efi support and so I think that's already been tested and probably works (cc'ing Darren, the author of the sys940x and EFI expert who actually added the EFI support recipes, etc).
As for EMGD and X, the current BSPs should all be good to go - there was some unrelated problems with X in the core which has been fixed, and at least as far as the crownbay goes, I know it works as I tested it just yesterday...
Hope that helps,
Tom
Quoted 47 lines
There seems to be discussions about this back in 2011:
https://lists.yoctoproject.org/pipermail/yocto/2011-November/005806.html
http://lists.linuxtogo.org/pipermail/openembedded-core/2011-November/012972.html
2. Is it possible to setup serial console for Crown Bay? I tried the following flags from the n450 information:
SYSLINUX_OPTS_atom-pc = "serial 0 115200"
SERIAL_CONSOLE_atom-pc = "115200 ttyS0"
APPEND_atom-pc = "console=ttyS0,115200 console=tty0"
3. There was some discussion about EMGD and X Windows issues and a possible fix. Where can I download the latest BSP to try out?
Regards,
Sean Liming
Annabooks
Tel: 714-970-7523 / Cell: 858-774-3176
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Quoted 75 lines
-----Original Message-----
From: Tom Zanussi [mailto:[email protected]]
Sent: Saturday, September 22, 2012 9:40 PM
To: Sean Liming
Cc: [email protected]
Subject: Re: [yocto] UEFI support for Crown BayQuoted 33 lines · Sean Liming
Yocto=1.2
BSB = Crown Bay (Intel Atom Processor E660 with Intel Platform Controller Hub EG20T Development Kit)
Target System= Inforce Computing, Inc. - SYS9400 Reference Platform - VGA output only.
UEFI only no BIOS
Base Image: core-image-minimal
Hob used to build the image
The target platform only has UEFI and doesn’t have traditional BIOS. I am able to re-configure the UEFI firmware using the BLDK application if needed. The Crown Bay BSP doesn’t include an efi loader (bootia32.efi) like Cedar Trail BSP in the live image (hddimg). If I add the EFI boot files from Cedar Trail live image, the USB flash disk presents the menu for boot or install. Upon selecting boot, I can see output on the serial console, but it eventually stops no output on the VGA monitor. I have attached the output from the serial port.
Quoted 3 lines
1. Is UEFI supported with Crown Bay BSP? Is there a flag that needs to be set like EFI = “1”?
Hi,
The Crown Bay BSP doesn't yet have EFI support - I added it earlier this year but had some problems getting it to work. I just now updated it and tried again but though I see the grub menu, selecting 'boot' also gets me a blank screen, and I don't even get serial output.
If you want to try it out for yourself and see if you get better results, here's the branch (the top 6 commits add efi support and some related cleanup):
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-
contrib/log/?h=tzanussi/crownbay-efi-v2The current BSP can be found in the meta-intel repo in the meta-crownbay directory (the README has some build instructions):
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-crownbay
Since you're using the Inforce Sys9400, though, I'm thinking that it might make more sense to use the meta-sys940x BSP:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-sys940x
I see it already has efi support and so I think that's already been tested and probably works (cc'ing Darren, the author of the sys940x and EFI expert who actually added the EFI support recipes, etc).
Quoted 10 lines
As for EMGD and X, the current BSPs should all be good to go - there was some unrelated problems with X in the core which has been fixed, and at least as far as the crownbay goes, I know it works as I tested it just yesterday...
Hope that helps,
Tom
Tom,
Thank you. I will get started trying them out.
Regards,
Sean Liming
Annabooks
Tel: 714-970-7523 / Cell: 858-774-3176
Quoted 50 lines
Quoted 8 lines
There seems to be discussions about this back in 2011:
https://lists.yoctoproject.org/pipermail/yocto/2011-November/005806.ht
mlhttp://lists.linuxtogo.org/pipermail/openembedded-core/2011-
November/0
Quoted 41 lines
12972.html
2. Is it possible to setup serial console for Crown Bay? I tried the following flags from the n450 information:
SYSLINUX_OPTS_atom-pc = "serial 0 115200"
SERIAL_CONSOLE_atom-pc = "115200 ttyS0"
APPEND_atom-pc = "console=ttyS0,115200 console=tty0"
3. There was some discussion about EMGD and X Windows issues and a possible fix. Where can I download the latest BSP to try out?
Regards,
Sean Liming
Annabooks
Tel: 714-970-7523 / Cell: 858-774-3176
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto