BD Nitrogen6x Trusty: nothing on lvds

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

BD Nitrogen6x Trusty: nothing on lvds

Jump to solution
1,151 Views
laza
Contributor III

Nitrogen6x2g Ubuntu kernel 3-14-52 : black screen

Hi,

I'm using Nitrogen6x 2Gb with Ubuntu image fromhttps://boundarydevices.com/mx-linux-kernel-3-14-52 and U-Boot 2015.07-15001-g440d481 (Oct 07 2015 - 12:32:09 -0700).

Also, I set 
allow_noncea=1
bootargs=video=mxcfb0:dev=ldb,1024x600M@60,if=RGB666

but display remains black!

What am I doing wrong?

Console:

non-CEA modes allowed on HDMI, audio may be affected

----------- trying to load /initrd.img
2317536 bytes read in 312 ms (7.1 MiB/s)
5499904 bytes read in 564 ms (9.3 MiB/s)
Kernel image @ 0x10800000 [ 0x000000 - 0x53ec00 ]
## Flattened Device Tree blob at 13000000
   Booting using the fdt blob at 0x13000000
   reserving fdt memory region: addr=13000000 size=c000
   Using Device Tree in place at 13000000, end 1300efff

Starting kernel ...

snvs_rtc 20cc034.snvs-rtc-lp: can't get snvs-rtc clock
imx6q-pcie 1ffc000.pcie: phy link never came up
imx6q-pcie 1ffc000.pcie: Failed to bring link up!
imx6q-pcie 1ffc000.pcie: failed to initialize host
ov5640_read_reg:write reg error:reg=300a
tc358743_read_reg:reg=0 ret=-5
tc358743_probe:cannot find camera
egalax_ts 2-0004: Failed to read firmware version
tsc2004_reset: write_cmd -5
tsc2004 2-0048: Failed to reset TSC -5
tc358743_probe: failed, error=-19
adv7180 2-0020: adv7180_read:read reg error: reg=11 ret=-5
ili210x_i2c 2-0041: i2c transfer failed
ili210x_i2c 2-0041: Failed to get firmware version, err: -5
Goodix-TS 2-0014: i2c test failed attempt 1: -5
Goodix-TS 2-0014: i2c test failed attempt 2: -5
Goodix-TS 2-0014: I2C communication failure: -5
Goodix-TS 2-005d: i2c test failed attempt 1: -5
Goodix-TS 2-005d: i2c test failed attempt 2: -5
update_device_addr: ov5642 ret=-5
mxc_v4l_open: Mxc Camera no sensor ipu1/csi1
mxc_v4l_open: Mxc Camera no sensor ipu0/csi0
mxc_v4l_open: Mxc Camera no sensor ipu1/csi0
mxc_v4l_open: Mxc Camera no sensor ipu0/csi0
Goodix-TS 2-005d: I2C communication failure: -5
ov5642_read_reg:write reg error:reg=300a
ft5x06-ts 2-0038: ft5x06: Could not detect touch screen -19.
update_device_addr: ov5640_mipi ret=-5
ov5640_read_reg(mipi):reg=300a ret=-5
                                                                         [ OK ]
saned disabled; edit /etc/default/saned

Ubuntu 14.04.4 LTS nitrogen ttymxc1
Labels (2)
1 Solution
668 Views
gary_bisson
Senior Contributor III

Hi,

As the blog post says:

This release uses the same mechanism as the 3.14.28 which means that U-Boot is in charge of setting the display parameters in the device tree. So it requires to use U-Boot v2015.07 or higher. Please make sure to read our blog post about this release:

What LVDS display are you using? Once you know its name, please find its match using:

=> fbpanel lvds

Once found, you can setup the display settings accordingly (here is an example for the hannstar LVDS display):

=> setenv fb_lvds hannstar

=> setenv fb_lcd off

=> setenv fb_hdmi off

=> savee && reset

Hope this helps.

Regards,

Gary

View solution in original post

2 Replies
669 Views
gary_bisson
Senior Contributor III

Hi,

As the blog post says:

This release uses the same mechanism as the 3.14.28 which means that U-Boot is in charge of setting the display parameters in the device tree. So it requires to use U-Boot v2015.07 or higher. Please make sure to read our blog post about this release:

What LVDS display are you using? Once you know its name, please find its match using:

=> fbpanel lvds

Once found, you can setup the display settings accordingly (here is an example for the hannstar LVDS display):

=> setenv fb_lvds hannstar

=> setenv fb_lcd off

=> setenv fb_hdmi off

=> savee && reset

Hope this helps.

Regards,

Gary

668 Views
laza
Contributor III

And that is what I was searching for!

I love you gary_bisson :smileyhappy:

Thank you for both answers!

Regards,
Laza

0 Kudos