* i.MX6q Boot failure using MACHINE=nitrogen6x
@ 2013-12-02 16:51 Tarek El-Sherbiny
2013-12-02 17:07 ` Eric Nelson
0 siblings, 1 reply; 9+ messages in thread
From: Tarek El-Sherbiny @ 2013-12-02 16:51 UTC (permalink / raw)
To: meta-freescale@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 23930 bytes --]
Hello,
I'm building the latest Yocto branch (*dora*) for the Nitrogen6 board as
given by this post:
http://boundarydevices.com/yocto-dora-release-mx6/
The image is based on core-image-basic + packagegroup-fsl-gstreamer .
When I boot the nitrogen board I get the following kernel messages then
system hangs:
3739488 bytes read in 263 ms (13.6 MiB/s)
## Booting kernel from Legacy Image at 12000000 ...
Image Name: Linux-3.0.35-4.1.0+yocto+g580993
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3739424 Bytes = 3.6 MiB
Load Address: 10008000
Entry Point: 10008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Linux version 3.0.35-4.1.0+yocto+g5809938 (telsherbiny@HP-Elite7500) (gcc
version 4.8.1 (GCC) ) #1 SMP PREEMPT Fri Nov 29 16:29:21 GMT 2013
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: console=ttymxc1,115200
video=mxcfb0:dev=hdmi,1920x1080@60 fbmem=24M,10M root=/dev/mmcblk0p1
rootfs=ext2 rw rootwait enable_wait_mode=off consoleblank=0 dmfc=3 bpp=32
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 Nitrogen6X/W
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
print_constraints: VDD_1.8V: 1800 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 ONLY-DP HIGH RESOLUTION: 5B(0~3), 5F(4~7)
imx-ipuv3 imx-ipuv3.1: IPU DMFC ONLY-DP HIGH RESOLUTION: 5B(0~3), 5F(4~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:0x00b97500, 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: register mxc display driver hdmi
mxc_hdmi mxc_hdmi: Detected HDMI controller 0x13:0xa:0xa0:0xc1
ipu_init_sync_panel: disp=1, pixel_clk=148500000 148500000
pwm_config: pwm freq = 32786, clk_select=2 clock_rate=22000000
pwm_config: pwm freq = 20000, clk_select=2 clock_rate=22000000
ipu_init_sync_panel: disp=1, pixel_clk=148500000 148500000
Console: switching to colour frame buffer device 240x67
mxc_sdc_fb mxc_sdc_fb.1: register mxc display driver lcd
ipu_init_sync_panel: disp=0, pixel_clk=27000000 27000000
pwm_config: pwm freq = 32786, clk_select=2 clock_rate=22000000
pwm_config: pwm freq = 20000, clk_select=2 clock_rate=22000000
mxc_sdc_fb mxc_sdc_fb.2: register mxc display driver ldb
_regulator_get: get() with no identifier
ldb_disp_init: ret=3, 1280x800
ldb_disp_init:r=59, x=1280, y=800, p=14065, l=40, r=40, upper=10, lower=3,
h=80, v=10
ldb_disp_init: 1024x768
ipu_init_sync_panel: disp=0, pixel_clk=71098000 71458646
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 0(VIC 16):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 1(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 2(VIC 1):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 3(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 4(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 5(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 6(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 7(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 8(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 9(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 10(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 11(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 12(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 13(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 14(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 15(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 16(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 17(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 18(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 19(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 20(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 21(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 22(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 23(VIC 0):
pwm_config: pwm freq = 32786, clk_select=2 clock_rate=22000000
pwm_config: pwm freq = 20000, clk_select=2 clock_rate=22000000
ipu_init_sync_panel: disp=1, pixel_clk=25175000 25142857
mxc_sdc_fb mxc_sdc_fb.3: register mxc display driver ldb
ldb_disp_init: ret=3, 1280x800
ldb_disp_init:r=59, x=1280, y=800, p=14065, l=40, r=40, upper=10, lower=3,
h=80, v=10
ldb_disp_init: 1024x768
imx-ipuv3 imx-ipuv3.0: WARNING: adapt panel end blank lines
ipu_init_sync_panel: disp=1, pixel_clk=172920000 172920000
imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00080000
imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_5 = 0x10000000
imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_5 = 0x00800000
imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00100000
mxc_sdc_fb mxc_sdc_fb.0: timeout when waiting for flip irq
mxc_sdc_fb mxc_sdc_fb.0: timeout when waiting for flip irq
mxc_sdc_fb mxc_sdc_fb.0: timeout when waiting for flip irq
ipu_init_sync_panel: disp=1, pixel_clk=71098000 71458646
pwm_config: pwm freq = 32786, clk_select=2 clock_rate=22000000
pwm_config: pwm freq = 20000, clk_select=2 clock_rate=22000000
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
imx-uart.2: ttymxc2 at MMIO 0x21ec000 (irq = 60) is a IMX
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: Nov 29 2013
rtc-isl1208 0-006f: chip found, driver version 0.3
add wake up source irq 108
rtc-isl1208 0-006f: rtc core: registered rtc-isl1208 as rtc0
check_alarm_past: alarm in the past
snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc1
i2c /dev entries driver
Linux video capture interface: v2.00
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video18
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video19
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video20
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video21
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
sdhci sdhci-esdhc-imx.2: no write-protect pin available!
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
mmc2: SDHCI controller on platform [sdhci-esdhc-imx.1] using DMA
mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
VPU initialized
mxc_asrc registered
usb 2-1: new high speed USB device number 2 using fsl-ehci
Galcore version 4.6.9.6622
Thermal calibration data is 0x57e4e67d
Thermal sensor with ratio = 182
Anatop Thermal registered as thermal_zone0
anatop_thermal_probe: default cooling device is cpufreq!
usbcore: registered new interface driver usbhid
mmc0: host does not support reading read-only switch. assuming write-enable.
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
mmc0: new high speed SDHC card at address e624
mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio
mmcblk0: mmc0:e624 SU16G 14.8 GiB
sgtl5000 0-000a: Failed to get supply 'VDDD': -19
print_constraints: 0-000a: 850 <--> 1600 mV at 1200 mV normal
mmcblk0: p1
sgtl5000 0-000a: sgtl5000 revision 17
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 3 ports detected
asoc: sgtl5000 <-> imx-ssi.1 mapping ok
asoc: mxc-hdmi-soc <-> imx-hdmi-soc-dai.0 mapping ok
ALSA device list:
#0: sgtl5000-audio
#1: imx-hdmi-soc
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
rtc-isl1208 0-006f: setting system clock to 2013-12-02 11:01:25 UTC
(1385982085)
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p1): using internal journal
EXT3-fs (mmcblk0p1): recovery complete
EXT3-fs (mmcblk0p1): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:1.
devtmpfs: mounted
Freeing init memory: 200K
usb 2-1.1: new full speed USB device number 3 using fsl-ehci
INIT: version 2.88 booting
generic-usb: probe of 0003:D0D9:0002.0001 failed with error -22
usb 2-1.2: new low speed USB device number 4 using fsl-ehci
Starting udev
Starting Bootlog daemon: input: USB Optical Mouse as
/devices/platform/fsl-ehci.1/usb2/2-1/2-1.2/2-1.2:1.0/input/input1
generic-usb 0003:0461:4D0F.0002: input,hidraw0: USB HID v1.11 Mouse [USB
Optical Mouse] on usb-fsl-ehci.1-1.2/input0
udevd[1433]: 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
mxc_sdc_fb mxc_sdc_fb.0: timeout when waiting for flip irq
bootlogd.
ALSA: Restoring mixer settings...
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...
mxc_hdmi mxc_hdmi: same edid
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 0(VIC 16):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 1(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 2(VIC 1):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 3(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 4(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 5(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 6(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 7(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 8(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 9(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 10(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 11(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 12(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 13(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 14(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 15(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 16(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 17(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 18(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 19(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 20(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 21(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 22(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 23(VIC 0):
mxc_hdmi mxc_hdmi: same edid
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 0(VIC 16):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 1(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 2(VIC 1):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 3(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 4(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 5(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 6(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 7(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 8(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 9(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 10(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 11(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 12(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 13(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 14(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 15(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 16(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 17(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 18(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 19(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 20(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 21(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 22(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 23(VIC
0):Sending discover...
Sending discover...
mxc_hdmi mxc_hdmi: same edid
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 0(VIC 16):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 1(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 2(VIC 1):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 3(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 4(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 5(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 6(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 7(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 8(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 9(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 10(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 11(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 12(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 13(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 14(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 15(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 16(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 17(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 18(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 19(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 20(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 21(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 22(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 23(VIC 0):
What exactly is missing?
Thanks
--
*Tarek*
[-- Attachment #2: Type: text/html, Size: 29119 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: i.MX6q Boot failure using MACHINE=nitrogen6x
2013-12-02 16:51 i.MX6q Boot failure using MACHINE=nitrogen6x Tarek El-Sherbiny
@ 2013-12-02 17:07 ` Eric Nelson
2013-12-03 12:43 ` Tarek El-Sherbiny
0 siblings, 1 reply; 9+ messages in thread
From: Eric Nelson @ 2013-12-02 17:07 UTC (permalink / raw)
To: Tarek El-Sherbiny, meta-freescale@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 2368 bytes --]
Hi Tarek,
On 12/02/2013 09:51 AM, Tarek El-Sherbiny wrote:
> Hello,
>
> I'm building the latest Yocto branch (/dora/) for the Nitrogen6 board as
> given by this post:
> http://boundarydevices.com/yocto-dora-release-mx6/
>
> The image is based on core-image-basic + packagegroup-fsl-gstreamer .
>
> When I boot the nitrogen board I get the following kernel messages then
> system hangs:
>
>
> <snip>
>
> INIT: version 2.88 booting
>
> generic-usb: probe of 0003:D0D9:0002.0001 failed with error -22
> usb 2-1.2: new low speed USB device number 4 using fsl-ehci
> Starting udev
> Starting Bootlog daemon: input: USB Optical Mouse as
> /devices/platform/fsl-ehci.1/usb2/2-1/2-1.2/2-1.2:1.0/input/input1
> generic-usb 0003:0461:4D0F.0002: input,hidraw0: USB HID v1.11 Mouse [USB
> Optical Mouse] on usb-fsl-ehci.1-1.2/input0
> udevd[1433]: 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
> mxc_sdc_fb mxc_sdc_fb.0: timeout when waiting for flip irq
> bootlogd.
>
> ALSA: Restoring mixer settings...
>
> 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...
>
> mxc_hdmi mxc_hdmi: same edid
> mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 0(VIC 16):
> mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 1(VIC 0):
> mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 23(VIC 0):
>
> What exactly is missing?
>
It doesn't appear that your machine is hanging, but rather bouncing
on HDMI connect/disconnect. Jose reported this a while back:
https://lists.yoctoproject.org/pipermail/meta-freescale/2013-October/005113.html
Can you try applying this patch into sources/meta-fsl-arm-extra?
~/yocto/sources/meta-fsl-arm-extra$ patch -p1 < 0001-*.patch
We've seen some issues with particular monitors (especially DVI) where
the DVI/HDMI detection pins seem to "bounce" when X starts up.
This kernel version includes a patch which bypasses the HDMI/DVI
disconnect code:
https://github.com/boundarydevices/linux-imx6/commit/d9cd79d11ff9f7a7f89cbc94b68757b67cdfe5fc
Please advise,
Eric
[-- Attachment #2: 0001-linux-boundary-bump-version-to-include-SATA-HDMI-upd.patch --]
[-- Type: text/x-diff, Size: 1060 bytes --]
From ec2e6d82a16974aa652d38f955d7303b037a1112 Mon Sep 17 00:00:00 2001
From: Eric Nelson <eric.nelson@boundarydevices.com>
Date: Mon, 2 Dec 2013 09:57:49 -0700
Subject: [PATCH] linux-boundary: bump version to include SATA/HDMI updates
Signed-off-by: Eric Nelson <eric.nelson@boundarydevices.com>
---
recipes-kernel/linux/linux-boundary_3.0.35.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes-kernel/linux/linux-boundary_3.0.35.bb b/recipes-kernel/linux/linux-boundary_3.0.35.bb
index 7875f93..6ed31bc 100644
--- a/recipes-kernel/linux/linux-boundary_3.0.35.bb
+++ b/recipes-kernel/linux/linux-boundary_3.0.35.bb
@@ -8,8 +8,8 @@ DESCRIPTION = "Linux kernel for Boundary Devices boards"
SRC_URI = "git://github.com/boundarydevices/linux-imx6.git \
file://defconfig"
-LOCALVERSION = "-4.1.0+yocto"
-SRCREV = "58099389255add7c17ce6babf37a50ce5d11d6b8"
+LOCALVERSION = "-4.1.0+yocto-20131202"
+SRCREV = "ee999dcf7b8e8e2854d4f5cf0243c42e7c39ac48"
# GPU support patches
--
1.8.1.2
^ permalink raw reply related [flat|nested] 9+ messages in thread
* Re: i.MX6q Boot failure using MACHINE=nitrogen6x
2013-12-02 17:07 ` Eric Nelson
@ 2013-12-03 12:43 ` Tarek El-Sherbiny
2013-12-03 14:48 ` Eric Nelson
0 siblings, 1 reply; 9+ messages in thread
From: Tarek El-Sherbiny @ 2013-12-03 12:43 UTC (permalink / raw)
To: Eric Nelson; +Cc: meta-freescale@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 3102 bytes --]
Hi Eric,
Thank you very much for the patch. With the new kernel I don't see the
bouncing on HDMI problem.
I am using HDMI to DVI cable to test 1080 as I don't have 1080 HDMI monitor.
With the new kernel Linux does not drive the DVI monitor at all. I switched
to 720 HDMI monitor and now there is output signal but I get horizontal
scrolling lines across the screen!
I don't see this problem with u-boot or Freescale kernel.
Have you seen this problem before?
Thanks,
Tarek
On Mon, Dec 2, 2013 at 5:07 PM, Eric Nelson <eric.nelson@boundarydevices.com
> wrote:
> Hi Tarek,
>
>
> On 12/02/2013 09:51 AM, Tarek El-Sherbiny wrote:
>
>> Hello,
>>
>> I'm building the latest Yocto branch (/dora/) for the Nitrogen6 board as
>>
>> given by this post:
>> http://boundarydevices.com/yocto-dora-release-mx6/
>>
>> The image is based on core-image-basic + packagegroup-fsl-gstreamer .
>>
>> When I boot the nitrogen board I get the following kernel messages then
>> system hangs:
>>
>>
>> <snip>
>>
>>
>> INIT: version 2.88 booting
>>
>> generic-usb: probe of 0003:D0D9:0002.0001 failed with error -22
>> usb 2-1.2: new low speed USB device number 4 using fsl-ehci
>> Starting udev
>> Starting Bootlog daemon: input: USB Optical Mouse as
>> /devices/platform/fsl-ehci.1/usb2/2-1/2-1.2/2-1.2:1.0/input/input1
>> generic-usb 0003:0461:4D0F.0002: input,hidraw0: USB HID v1.11 Mouse [USB
>> Optical Mouse] on usb-fsl-ehci.1-1.2/input0
>> udevd[1433]: 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
>> mxc_sdc_fb mxc_sdc_fb.0: timeout when waiting for flip irq
>> bootlogd.
>>
>> ALSA: Restoring mixer settings...
>>
>> 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...
>>
>> mxc_hdmi mxc_hdmi: same edid
>> mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 0(VIC 16):
>> mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 1(VIC 0):
>> mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 23(VIC 0):
>>
>> What exactly is missing?
>>
>>
> It doesn't appear that your machine is hanging, but rather bouncing
> on HDMI connect/disconnect. Jose reported this a while back:
>
> https://lists.yoctoproject.org/pipermail/meta-freescale/
> 2013-October/005113.html
>
> Can you try applying this patch into sources/meta-fsl-arm-extra?
>
> ~/yocto/sources/meta-fsl-arm-extra$ patch -p1 < 0001-*.patch
>
> We've seen some issues with particular monitors (especially DVI) where
> the DVI/HDMI detection pins seem to "bounce" when X starts up.
>
> This kernel version includes a patch which bypasses the HDMI/DVI
> disconnect code:
> https://github.com/boundarydevices/linux-imx6/commit/
> d9cd79d11ff9f7a7f89cbc94b68757b67cdfe5fc
>
>
> Please advise,
>
>
> Eric
>
--
*Tarek*
[-- Attachment #2: Type: text/html, Size: 4367 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: i.MX6q Boot failure using MACHINE=nitrogen6x
2013-12-03 12:43 ` Tarek El-Sherbiny
@ 2013-12-03 14:48 ` Eric Nelson
2013-12-03 15:12 ` Tarek El-Sherbiny
0 siblings, 1 reply; 9+ messages in thread
From: Eric Nelson @ 2013-12-03 14:48 UTC (permalink / raw)
To: Tarek El-Sherbiny; +Cc: meta-freescale@yoctoproject.org
Hi Tarek,
On 12/03/2013 05:43 AM, Tarek El-Sherbiny wrote:
> Hi Eric,
>
> Thank you very much for the patch. With the new kernel I don't see the
> bouncing on HDMI problem.
> I am using HDMI to DVI cable to test 1080 as I don't have 1080 HDMI monitor.
> With the new kernel Linux does not drive the DVI monitor at all. I
> switched to 720 HDMI monitor and now there is output signal but I get
> horizontal scrolling lines across the screen!
> I don't see this problem with u-boot or Freescale kernel.
> Have you seen this problem before?
>
Can you forward the output from /sys/class/graphics/fb0/modes and
/sys/class/graphics/fb0/mode from each of these displays?
It's possible that we're blocking some of the modes because they
don't support audio:
https://github.com/boundarydevices/linux-imx6/commit/104d4ebfcad4021ed982ec0f436d56c3d0f44068
We added a driver parameter to the mxc_hdmi driver to force
the use of CEA modes. You can override it with this kernel
command-line parameter.
mxc_hdmi.only_cea=0
If you're running a recent U-Boot, you can also get a list
of supported modes from your monitor using these two
commands:
U-Boot > i2c dev 1
U-Boot > i2c edid
Please advise,
Eric
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: i.MX6q Boot failure using MACHINE=nitrogen6x
2013-12-03 14:48 ` Eric Nelson
@ 2013-12-03 15:12 ` Tarek El-Sherbiny
2013-12-03 16:40 ` Eric Nelson
0 siblings, 1 reply; 9+ messages in thread
From: Tarek El-Sherbiny @ 2013-12-03 15:12 UTC (permalink / raw)
To: Eric Nelson; +Cc: meta-freescale@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 1927 bytes --]
Hi Eric,
root@nitrogen6x:~# cat /sys/class/graphics/fb0/modes
S:720x480p-60
S:720x576p-50
S:1280x720p-50
S:1280x720p-60
S:1280x1024p-60
V:1024x768p-75
V:1024x768p-70
V:1024x768p-60
V:800x600p-75
V:800x600p-72
V:800x600p-60
V:640x480p-75
V:640x480p-72
V:640x480p-60
U:720x400p-70
D:1360x768p-60
D:1280x720p-60
V:640x480p-60
root@nitrogen6x:~# cat /sys/class/graphics/fb0/mode
S:1280x1024p-60
I'm not running the latest U-boot!
Thanks,
Tarek
On Tue, Dec 3, 2013 at 2:48 PM, Eric Nelson <eric.nelson@boundarydevices.com
> wrote:
> Hi Tarek,
>
>
> On 12/03/2013 05:43 AM, Tarek El-Sherbiny wrote:
>
>> Hi Eric,
>>
>> Thank you very much for the patch. With the new kernel I don't see the
>> bouncing on HDMI problem.
>> I am using HDMI to DVI cable to test 1080 as I don't have 1080 HDMI
>> monitor.
>> With the new kernel Linux does not drive the DVI monitor at all. I
>> switched to 720 HDMI monitor and now there is output signal but I get
>> horizontal scrolling lines across the screen!
>> I don't see this problem with u-boot or Freescale kernel.
>> Have you seen this problem before?
>>
>>
> Can you forward the output from /sys/class/graphics/fb0/modes and
> /sys/class/graphics/fb0/mode from each of these displays?
>
> It's possible that we're blocking some of the modes because they
> don't support audio:
> https://github.com/boundarydevices/linux-imx6/commit/
> 104d4ebfcad4021ed982ec0f436d56c3d0f44068
>
> We added a driver parameter to the mxc_hdmi driver to force
> the use of CEA modes. You can override it with this kernel
> command-line parameter.
> mxc_hdmi.only_cea=0
>
> If you're running a recent U-Boot, you can also get a list
> of supported modes from your monitor using these two
> commands:
> U-Boot > i2c dev 1
> U-Boot > i2c edid
>
> Please advise,
>
>
> Eric
>
--
*Tarek*
[-- Attachment #2: Type: text/html, Size: 3048 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: i.MX6q Boot failure using MACHINE=nitrogen6x
2013-12-03 15:12 ` Tarek El-Sherbiny
@ 2013-12-03 16:40 ` Eric Nelson
2013-12-03 17:33 ` Tarek El-Sherbiny
0 siblings, 1 reply; 9+ messages in thread
From: Eric Nelson @ 2013-12-03 16:40 UTC (permalink / raw)
To: Tarek El-Sherbiny; +Cc: meta-freescale@yoctoproject.org
Hi Tarek,
On 12/03/2013 08:12 AM, Tarek El-Sherbiny wrote:
> Hi Eric,
>
> root@nitrogen6x:~# cat /sys/class/graphics/fb0/modes
> S:720x480p-60
> S:720x576p-50
> S:1280x720p-50
> S:1280x720p-60
> S:1280x1024p-60
> V:1024x768p-75
> V:1024x768p-70
> V:1024x768p-60
> V:800x600p-75
> V:800x600p-72
> V:800x600p-60
> V:640x480p-75
> V:640x480p-72
> V:640x480p-60
> U:720x400p-70
> D:1360x768p-60
> D:1280x720p-60
> V:640x480p-60
This looks like a pretty standard set of modes for a
4:3 aspect ratio monitor.
> root@nitrogen6x:~# cat /sys/class/graphics/fb0/mode
> S:1280x1024p-60
This doesn't match one of the CEA modes:
https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.0.35_4.1.0/drivers/video/mxc/mxc_edid.c#L41
Can you boot with this command-line argument?
mxc_hdmi.only_cea=0
I think you'll either need that or you'll need to choose a
display resolution from the list. It appears that your monitor
and CEA both like 1280x720@60, though you'll likely get
letter-boxing.
Regards,
Eric
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: i.MX6q Boot failure using MACHINE=nitrogen6x
2013-12-03 16:40 ` Eric Nelson
@ 2013-12-03 17:33 ` Tarek El-Sherbiny
2013-12-03 18:31 ` Eric Nelson
0 siblings, 1 reply; 9+ messages in thread
From: Tarek El-Sherbiny @ 2013-12-03 17:33 UTC (permalink / raw)
To: Eric Nelson; +Cc: meta-freescale@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 2319 bytes --]
Hi Eric,
On the command line arguments I had dmfc=3. That was set to improve the IPU
performance as I need to play up to 16 streams simultaneously.
When I removed this option the boundary kernel is booting without the
horizontal lines problem. HDMI to DVI is still not working.
cat /proc/cmdline
console=ttymxc1,115200 video=mxcfb0:dev=hdmi,1920x1080@60 fbmem=24M,10M
root=/dev/mmcblk0p1 rootfs=ext2 rw rootwait enable_wait_mode=off
consoleblank=0 bpp=32
This is fine for know but it would be nice to understand why dmfc is
conflict with boundary kernel.
Also I'm not sure how is this going to affect the IPU performance!
Hope you have an answer to this question so I can fully test the
application.
https://lists.yoctoproject.org/pipermail/meta-freescale/2013-December/005854.html
Thanks,
Tarek
The command line argument doesn't help:
console=ttymxc1,115200 video=mxcfb0:dev=hdmi,1920x1080@60 fbmem=24M,10M
root=/dev/mmcblk0p1 rootfs=ext2 rw rootwait enable_wait_mode=off
consoleblank=0 dmfc=3 bpp=32
Also
On Tue, Dec 3, 2013 at 4:40 PM, Eric Nelson <eric.nelson@boundarydevices.com
> wrote:
> Hi Tarek,
>
>
> On 12/03/2013 08:12 AM, Tarek El-Sherbiny wrote:
>
>> Hi Eric,
>>
>> root@nitrogen6x:~# cat /sys/class/graphics/fb0/modes
>> S:720x480p-60
>> S:720x576p-50
>> S:1280x720p-50
>> S:1280x720p-60
>> S:1280x1024p-60
>> V:1024x768p-75
>> V:1024x768p-70
>> V:1024x768p-60
>> V:800x600p-75
>> V:800x600p-72
>> V:800x600p-60
>> V:640x480p-75
>> V:640x480p-72
>> V:640x480p-60
>> U:720x400p-70
>> D:1360x768p-60
>> D:1280x720p-60
>> V:640x480p-60
>>
>
> This looks like a pretty standard set of modes for a
> 4:3 aspect ratio monitor.
>
>
> root@nitrogen6x:~# cat /sys/class/graphics/fb0/mode
>> S:1280x1024p-60
>>
>
> This doesn't match one of the CEA modes:
> https://github.com/boundarydevices/linux-imx6/
> blob/boundary-imx_3.0.35_4.1.0/drivers/video/mxc/mxc_edid.c#L41
>
> Can you boot with this command-line argument?
> mxc_hdmi.only_cea=0
>
> I think you'll either need that or you'll need to choose a
> display resolution from the list. It appears that your monitor
> and CEA both like 1280x720@60, though you'll likely get
> letter-boxing.
>
> Regards,
>
>
> Eric
>
--
*Tarek*
[-- Attachment #2: Type: text/html, Size: 3672 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: i.MX6q Boot failure using MACHINE=nitrogen6x
2013-12-03 17:33 ` Tarek El-Sherbiny
@ 2013-12-03 18:31 ` Eric Nelson
2013-12-04 12:55 ` Tarek El-Sherbiny
0 siblings, 1 reply; 9+ messages in thread
From: Eric Nelson @ 2013-12-03 18:31 UTC (permalink / raw)
To: Tarek El-Sherbiny; +Cc: meta-freescale@yoctoproject.org
Hi Tarek,
Are you using multiple displays?
If not, you're going to want these
video=mxcfb1:off video=mxcfb2:off video=mxcfb2:off
Otherwise you'll get a default LDB display. You can check this
in /sys/class/graphics/fb2/.
Did you try running the DVI monitor with "mxc_hdmi.only_cea=0" in your
kernel command-line?
I'm not sure what dmfc=3 is doing to the display, but I suspect
that you're exceeding the bandwidth requirements with multiple
displays configured.
I'm also not certain what you're running into with the
gstreamer build.
Regards,
Eric
On 12/03/2013 10:33 AM, Tarek El-Sherbiny wrote:
> Hi Eric,
>
> On the command line arguments I had dmfc=3. That was set to improve the
> IPU performance as I need to play up to 16 streams simultaneously.
> When I removed this option the boundary kernel is booting without the
> horizontal lines problem. HDMI to DVI is still not working.
>
> cat /proc/cmdline
> console=ttymxc1,115200 video=mxcfb0:dev=hdmi,1920x1080@60 fbmem=24M,10M
> root=/dev/mmcblk0p1 rootfs=ext2 rw rootwait enable_wait_mode=off
> consoleblank=0 bpp=32
>
>
> This is fine for know but it would be nice to understand why dmfc is
> conflict with boundary kernel.
> Also I'm not sure how is this going to affect the IPU performance!
> Hope you have an answer to this question so I can fully test the
> application.
> https://lists.yoctoproject.org/pipermail/meta-freescale/2013-December/005854.html
>
> Thanks,
> Tarek
>
>
>
> The command line argument doesn't help:
>
> console=ttymxc1,115200 video=mxcfb0:dev=hdmi,1920x1080@60 fbmem=24M,10M
> root=/dev/mmcblk0p1 rootfs=ext2 rw rootwait enable_wait_mode=off
> consoleblank=0 dmfc=3 bpp=32
>
> Also
>
>
>
> On Tue, Dec 3, 2013 at 4:40 PM, Eric Nelson
> <eric.nelson@boundarydevices.com
> <mailto:eric.nelson@boundarydevices.com>> wrote:
>
> Hi Tarek,
>
>
> On 12/03/2013 08:12 AM, Tarek El-Sherbiny wrote:
>
> Hi Eric,
>
> root@nitrogen6x:~# cat /sys/class/graphics/fb0/modes
> S:720x480p-60
> S:720x576p-50
> S:1280x720p-50
> S:1280x720p-60
> S:1280x1024p-60
> V:1024x768p-75
> V:1024x768p-70
> V:1024x768p-60
> V:800x600p-75
> V:800x600p-72
> V:800x600p-60
> V:640x480p-75
> V:640x480p-72
> V:640x480p-60
> U:720x400p-70
> D:1360x768p-60
> D:1280x720p-60
> V:640x480p-60
>
>
> This looks like a pretty standard set of modes for a
> 4:3 aspect ratio monitor.
>
>
> root@nitrogen6x:~# cat /sys/class/graphics/fb0/mode
> S:1280x1024p-60
>
>
> This doesn't match one of the CEA modes:
> https://github.com/__boundarydevices/linux-imx6/__blob/boundary-imx_3.0.35_4.1.__0/drivers/video/mxc/mxc_edid.__c#L41
> <https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.0.35_4.1.0/drivers/video/mxc/mxc_edid.c#L41>
>
> Can you boot with this command-line argument?
> mxc_hdmi.only_cea=0
>
> I think you'll either need that or you'll need to choose a
> display resolution from the list. It appears that your monitor
> and CEA both like 1280x720@60, though you'll likely get
> letter-boxing.
>
> Regards,
>
>
> Eric
>
>
>
>
> --
> /Tarek/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: i.MX6q Boot failure using MACHINE=nitrogen6x
2013-12-03 18:31 ` Eric Nelson
@ 2013-12-04 12:55 ` Tarek El-Sherbiny
0 siblings, 0 replies; 9+ messages in thread
From: Tarek El-Sherbiny @ 2013-12-04 12:55 UTC (permalink / raw)
To: Eric Nelson; +Cc: meta-freescale@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 3800 bytes --]
On Tue, Dec 3, 2013 at 6:31 PM, Eric Nelson <eric.nelson@boundarydevices.com
> wrote:
> Hi Tarek,
>
> Are you using multiple displays?
>
No just one display
> If not, you're going to want these
> video=mxcfb1:off video=mxcfb2:off video=mxcfb2:off
>
I will give this a try. Thanks
> Otherwise you'll get a default LDB display. You can check this
> in /sys/class/graphics/fb2/.
>
> Did you try running the DVI monitor with "mxc_hdmi.only_cea=0" in your
> kernel command-line?
>
Yes, it doesn't help.
> I'm not sure what dmfc=3 is doing to the display, but I suspect
> that you're exceeding the bandwidth requirements with multiple
> displays configured.
>
> I'm also not certain what you're running into with the
> gstreamer build.
>
No problem I found it :-)
> Regards,
>
>
> Eric
>
>
> On 12/03/2013 10:33 AM, Tarek El-Sherbiny wrote:
>
>> Hi Eric,
>>
>> On the command line arguments I had dmfc=3. That was set to improve the
>> IPU performance as I need to play up to 16 streams simultaneously.
>> When I removed this option the boundary kernel is booting without the
>> horizontal lines problem. HDMI to DVI is still not working.
>>
>> cat /proc/cmdline
>> console=ttymxc1,115200 video=mxcfb0:dev=hdmi,1920x1080@60 fbmem=24M,10M
>> root=/dev/mmcblk0p1 rootfs=ext2 rw rootwait enable_wait_mode=off
>> consoleblank=0 bpp=32
>>
>>
>> This is fine for know but it would be nice to understand why dmfc is
>> conflict with boundary kernel.
>> Also I'm not sure how is this going to affect the IPU performance!
>> Hope you have an answer to this question so I can fully test the
>> application.
>> https://lists.yoctoproject.org/pipermail/meta-freescale/
>> 2013-December/005854.html
>>
>> Thanks,
>> Tarek
>>
>>
>>
>> The command line argument doesn't help:
>>
>> console=ttymxc1,115200 video=mxcfb0:dev=hdmi,1920x1080@60 fbmem=24M,10M
>> root=/dev/mmcblk0p1 rootfs=ext2 rw rootwait enable_wait_mode=off
>> consoleblank=0 dmfc=3 bpp=32
>>
>> Also
>>
>>
>>
>> On Tue, Dec 3, 2013 at 4:40 PM, Eric Nelson
>> <eric.nelson@boundarydevices.com
>> <mailto:eric.nelson@boundarydevices.com>> wrote:
>>
>> Hi Tarek,
>>
>>
>> On 12/03/2013 08:12 AM, Tarek El-Sherbiny wrote:
>>
>> Hi Eric,
>>
>> root@nitrogen6x:~# cat /sys/class/graphics/fb0/modes
>> S:720x480p-60
>> S:720x576p-50
>> S:1280x720p-50
>> S:1280x720p-60
>> S:1280x1024p-60
>> V:1024x768p-75
>> V:1024x768p-70
>> V:1024x768p-60
>> V:800x600p-75
>> V:800x600p-72
>> V:800x600p-60
>> V:640x480p-75
>> V:640x480p-72
>> V:640x480p-60
>> U:720x400p-70
>> D:1360x768p-60
>> D:1280x720p-60
>> V:640x480p-60
>>
>>
>> This looks like a pretty standard set of modes for a
>> 4:3 aspect ratio monitor.
>>
>>
>> root@nitrogen6x:~# cat /sys/class/graphics/fb0/mode
>> S:1280x1024p-60
>>
>>
>> This doesn't match one of the CEA modes:
>> https://github.com/__boundarydevices/linux-imx6/__
>> blob/boundary-imx_3.0.35_4.1.__0/drivers/video/mxc/mxc_edid.__c#L41
>>
>> <https://github.com/boundarydevices/linux-imx6/
>> blob/boundary-imx_3.0.35_4.1.0/drivers/video/mxc/mxc_edid.c#L41>
>>
>> Can you boot with this command-line argument?
>> mxc_hdmi.only_cea=0
>>
>> I think you'll either need that or you'll need to choose a
>> display resolution from the list. It appears that your monitor
>> and CEA both like 1280x720@60, though you'll likely get
>> letter-boxing.
>>
>> Regards,
>>
>>
>> Eric
>>
>>
>>
>>
>> --
>> /Tarek/
>>
>
>
--
*Tarek*
[-- Attachment #2: Type: text/html, Size: 5880 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2013-12-04 12:55 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-02 16:51 i.MX6q Boot failure using MACHINE=nitrogen6x Tarek El-Sherbiny
2013-12-02 17:07 ` Eric Nelson
2013-12-03 12:43 ` Tarek El-Sherbiny
2013-12-03 14:48 ` Eric Nelson
2013-12-03 15:12 ` Tarek El-Sherbiny
2013-12-03 16:40 ` Eric Nelson
2013-12-03 17:33 ` Tarek El-Sherbiny
2013-12-03 18:31 ` Eric Nelson
2013-12-04 12:55 ` Tarek El-Sherbiny
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.