On 03/01/2013 01:06 AM, Andrei Gherzan wrote:
On Thu, Feb 28, 2013 at 8:37 PM, Eric Nelson
<[email protected]
<mailto:[email protected]>> wrote:
On 02/28/2013 11:16 AM, Eric Nelson wrote:
On 02/28/2013 08:34 AM, Andrei Gherzan wrote:
On Thu, Feb 28, 2013 at 5:30 PM, Eric Nelson
<eric.nelson@boundarydevices.__com
<mailto:[email protected]>
<mailto:eric.nelson@__boundarydevices.com
<mailto:[email protected]>>> wrote:
Hi Otavio and Andrei,
On 02/28/2013 08:01 AM, Otavio Salvador wrote:
On Thu, Feb 28, 2013 at 11:42 AM, Andrei Gherzan
<[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>> wrote:
While using imx6, I faced 2 issues after
updating the kernel
to ver. / rel.
1.1.0:
1. If i boot the board with hdmi monitor
connected the boot
process hangs
with:
---
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
fbcvt: 1920x1080@60: CVT Name - 2.073M9
imx-ipuv3 imx-ipuv3.0: IPU DMFC DP HIGH
RESOLUTION: 1(0,1),
5B(2~5), 5F(6,7)
Console: switching to colour frame buffer
device 240x67
mxc_sdc_fb mxc_sdc_fb.1: register mxc display
driver lcd
mxc_sdc_fb mxc_sdc_fb.2: register mxc display
driver ldb
_regulator_get: get() with no identifier
mxc_hdmi mxc_hdmi:
mxc_hdmi_edid_rebuild_____modelist: Added
mode 0(VIC 0):
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 0):
mxc_hdmi mxc_hdmi:
mxc_hdmi_edid_rebuild_____modelist: Added
mode 3(VIC 1):
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):
fbcvt: 1920x1080@60: CVT Name - 2.073M9
mxc_sdc_fb mxc_sdc_fb.3: register mxc display
driver ldb
>
This all looks valid, though things shouldn't hang here.
---
Additional infos:
$ cat
/sys/devices/platform/mxc_sdc_____fb.0/graphics/fb0/modes
V:640x480p-60
U:640x480p-60
Was this from a boot without the HDMI monitor
connected? The mxc_hdmi
driver should list all of the display resolutions
supported by the
monitor as reported by EDID.
Nope. This is from a boot with HDMI monitor connected.
Kernel command line: console=ttymxc1,115200
console=ttymxc1,115200
root=/dev/sda2 rootwait
video=mxcfb0:dev=hdmi,____1920x1080M@60,if=RGB24
When trying to reproduce things, I noted a
-- You have two 'console=ttymxc1,115200' clauses here
-- You appear to be using SATA (/dev/sda2). For SD card boot,
this should be /dev/mmcblk0p2 with a Yocto-standard image
-- There's some extraneous stuff (__) in your video= clause
I just booted with a slightly modified kernel command-line to try
and match yours:
Kernel command line: console=ttymxc1,115200
video=mxcfb0:dev=hdmi,__1920x1080M@60,if=RGB24 fbmem=48M vmalloc=400
root=/dev/mmcblk0p1 rootwait
What I found is that things booted, and I got a login prompt on the
serial console, but my display isn't functioning properly.
Hi Andrei,
A couple of other things I noticed:
- The serial port clock appears to get screwed up at around
the point at which you say things hang. This is due to
a recurring issue related to re-parenting of some of the
clocks and will need to be addressed.
For me, this causes a bunch of garbage, but my serial
port and terminal emulator recover after ~1k of garbage.
You might want to try restarting the terminal emulator
you're using.
- I don't trust my Yocto image. I tried to pull in the
1.1.0 patch set unsuccessfully and even the stock
720P resolution isn't working for me. I get the Yocto
splash screen, but my X Server is dying.
I'll re-build, but it will take hours. Meanwhile, can
you try using the stock 6x_bootscript, which should
come up at 720P?
Where can I find this stock script? I would kindly test it.
Hi Andre,
This should be installed as a part of the Yocto SD card image.
I built using "nitrogen6x" machine type and found that there's
a copy of the script in:
build/tmp/deploy/images/6x_bootscript-nitrogen6x
How are you currently setting your bootargs in U-Boot?
The stock script uses HDMI detection and sets up 720P along
with other arguments:
https://github.com/boundarydevices/u-boot-imx6/blob/production/board/boundary/nitrogen6x/6x_bootscript.txt
Ahh. Never mind. I just found out how you're doing this, and oddly,
it has my name as the author!
https://github.com/Freescale/meta-fsl-arm-extra/commit/ebcb70c68a30bd0d07220d61a378488a512aa6c1
So you're setting and saving 'bootargs' with your video settings
directly. If you add this bit, things should work for you.
'video=mxcfb1:off video=mxcfb2:off'
Note that you might also need 'enable_wait_mode=off'. We saw
some issues during early startup that still haven't been addressed
as discussed here:
http://boundarydevices.com/wait-a-second-hopefully-less/
Regards,
Eric
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale
