Nothing is visible in LVDS display when connected to nitrogen 6x

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Nothing is visible in LVDS display when connected to nitrogen 6x

4,230件の閲覧回数
ashwathhebbar
Contributor II

Hi,

I am trying to interface LVDS display(Nit6x_1024x600) from boundary devices to Nitrogen6x board.

This is my kernel boot-up logs...

U-Boot 2013.07-00047-gaf468ad (Aug 26 2013 - 09:35:41)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz

Reset cause: POR

Board: Nitrogen6X

DRAM:  1 GiB

MMC:   FSL_SDHC: 0, FSL_SDHC: 1

SF: Detected SST25VF016B with page size 4 KiB, total 2 MiB

auto-detected panel wsvga-lvds

Display: wsvga-lvds (1024x600)

In:    serial

Out:   serial

Err:   serial

Net:   using phy at 6

FEC [PRIME]

Hit any key to stop autoboot:  0

## Error: "bootcmd_base" not defined

mmc0 is current device

** Unrecognized filesystem type **

406 bytes read in 144 ms (2 KiB/s)

## Executing script at 10008000

Unknown command 'bootargs' - try 'help'

1782524 bytes read in 159 ms (10.7 MiB/s)

## Booting kernel from Legacy Image at 10800000 ...

   Image Name:   Linux-3.0.15-1033-g1e54cdcd

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    1782460 Bytes = 1.7 MiB

   Load Address: 10008000

   Entry Point:  10008000

   Verifying Checksum ... OK

   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux...

done, booting the kernel.

Linux version 3.0.15-1033-g1e54cdcd (ubuntu@ubuntu-WSG52B55W7-0248) (gcc version 4.4.4 (4.4.4_09.06.20103

CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d

CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache

Machine: Freescale i.MX 6Quad Sabre-Lite Board

vmalloc area too small, limiting to 16MB

Memory policy: ECC disabled, Data cache writealloc

PERCPU: Embedded 7 pages/cpu @8c008000 s4512 r8192 d15968 u32768

Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 227328

Kernel command line: console=ttymxc1,115200 video=mxcfb0:dev=ldb,1024x600M,if=RGB666 vmalloc=400 video=mM

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: 904764k/904764k available, 143812k 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 - 0x8002a000   ( 136 kB)

      .text : 0x8002a000 - 0x8032fb00   (3095 kB)

      .data : 0x80330000 - 0x8035d380   ( 181 kB)

       .bss : 0x8035d3a4 - 0x80383884   ( 154 kB)

SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=4, Nodes=1

Preemptible hierarchical RCU implementation.

        Verbose stalled-CPUs detection is disabled.

NR_IRQS:496

MXC GPIO hardware

sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms

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

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).

print_constraints: dummy:

NET: Registered protocol family 16

cpaddr = c0840000 wait_iram_base=c0812000

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: 2800 <--> 3150 mV at 3000 mV fast normal

L310 cache controller enabled

l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x02070000, Cache size: 1048576 B

IMX usb wakeup probe

IMX usb wakeup probe

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

SCSI subsystem initialized

imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)

imx-ipuv3 imx-ipuv3.1: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)

Advanced Linux Sound Architecture Driver Version 1.0.24.

Switching to clocksource mxc_timer1

Clockevents: could not switch to one-shot mode:

Clockevents: could not switch to one-shot mode:

Clockevents: could not switch to one-shot mode:

Clockevents: could not switch to one-shot mode: dummy_timer is not functional.

dummy_timer is not functional.

dummy_timer is not functional.

Could not switch to high resolution mode on CPU 2

Could not switch to high resolution mode on CPU 0

Could not switch to high resolution mode on CPU 1

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

Bus freq driver module loaded

Static Power Management for Freescale i.MX6

cpaddr = c0841000 suspend_iram_base=c08b8000

PM driver module loaded

i.MXC CPU frequency driver

msgmni has been set to 1767

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

dummy_timer is not functional.

Could not switch to high resolution mode on CPU 3

mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver ldb

mxc_sdc_fb mxc_sdc_fb.0: NO mxc display driver found!

mxc_sdc_fb mxc_sdc_fb.1: register mxc display driver lcd

imx-ipuv3 imx-ipuv3.0: Channel already disabled 9

imx-ipuv3 imx-ipuv3.0: Channel already uninitialized 9

Console: switching to colour frame buffer device 100x30

imx-ipuv3 imx-ipuv3.0: Channel already disabled 10

imx-ipuv3 imx-ipuv3.0: Channel already uninitialized 10

mxc_sdc_fb mxc_sdc_fb.2: register mxc display driver ldb

mxc_sdc_fb mxc_sdc_fb.2: NO mxc display driver found!

mxc_sdc_fb mxc_sdc_fb.3: register mxc display driver ldb

mxc_sdc_fb mxc_sdc_fb.3: NO mxc display driver found!

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

console [ttymxc1] enabled, bootconsole disabled

console [ttymxc1] enabled, bootconsole disabled

loop: module loaded

mousedev: PS/2 mouse device common for all mice

snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0

i2c /dev entries driver

sdhci: Secure Digital Host Controller Interface driver

sdhci: Copyright(c) Pierre Ossman

mmc0: Unknown controller version (3). You may experience problems.

mmc0: SDHCI controller on platform [sdhci-esdhc-imx.3] using DMA

mmc1: Unknown controller version (3). You may experience problems.

mmc1: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA

sgtl5000 0-000a: Failed to get supply 'VDDD': -19

print_constraints: 0-000a: 850 <--> 1600 mV at 1200 mV normal

sgtl5000 0-000a: sgtl5000 revision 17

asoc: sgtl5000 <-> imx-ssi.1 mapping ok

ALSA device list:

  #0: sgtl5000-audio

TCP cubic registered

NET: Registered protocol family 37

VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4

snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0)

VFS: Cannot open root device "(null)" or unknown-block(0,0)

Please append a correct "root=" boot option; here are the available partitions:

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

CPU2: stopping

Function entered at [<80034544>] from [<8002a2c4>]

Function entered at [<8002a2c4>] from [<8002f60c>]

Exception stack(0xbffb3f90 to 0xbffb3fd8)

3f80:                                     8035d83c a0000093 bffb3fd8 00000000

3fa0: bffb2000 80344ac4 8035d464 80341a44 1000406a 412fc09a 00000000 00000000

3fc0: 00000000 bffb3fd8 8003040c 80030410 60000013 ffffffff

Function entered at [<8002f60c>] from [<80030410>]

Function entered at [<80030410>] from [<800309a0>]

Function entered at [<800309a0>] from [<1001f9b4>]

CPU0: stopping

Function entered at [<80034544>] from [<8002a2c4>]

Function entered at [<8002a2c4>] from [<8002f60c>]

Exception stack(0x80331f68 to 0x80331fb0)

1f60:                   8035d83c a0000093 80331fb0 00000000 80330000 80344ac4

1f80: 8035d464 80341a44 1000406a 412fc09a 00000000 00000000 00000000 80331fb0

1fa0: 8003040c 80030410 60000013 ffffffff

Function entered at [<8002f60c>] from [<80030410>]

Function entered at [<80030410>] from [<800309a0>]

Function entered at [<800309a0>] from [<80008874>]

Function entered at [<80008874>] from [<1000803c>]

CPU1: stopping

Function entered at [<80034544>] from [<8002a2c4>]

Function entered at [<8002a2c4>] from [<8002f60c>]

Exception stack(0xbffabf90 to 0xbffabfd8)

bf80:                                     8035d83c a0000093 bffabfd8 00000000

bfa0: bffaa000 80344ac4 8035d464 80341a44 1000406a 412fc09a 00000000 00000000

bfc0: 00000000 bffabfd8 8003040c 80030410 60000013 ffffffff

Function entered at [<8002f60c>] from [<80030410>]

Function entered at [<80030410>] from [<800309a0>]

Function entered at [<800309a0>] from [<1001f9b4>]

and here my booting stopped. And 6q_bootscript that I am using is given below.

bootargs $bootargs console=ttymxc1,115200 vmalloc=400M root=/dev/mmcblk0p1 rootwait fixrtc consoleblank=0 ;

setenv bootargs $bootargs video=mxcfb0:dev=ldb,LDB-SVGA,if=RGB666 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=10M;

ext2load mmc ${disk}:1 10800000 /boot/uImage && bootm 10800000 ; echo "Error loading kernel image"

Can anybody tell me any syntax problem is there in the above uboot script.  I wanted to have LVDS display working with nitrogen6x board. Any help would be appreciated.

Regards,

Ashwath

ラベル(3)
タグ(3)
0 件の賞賛
返信
2 返答(返信)

1,341件の閲覧回数
SergioSolis
NXP Employee
NXP Employee

Hello Ashwan,

I'm not 100% sure that the problem is with the LVDS arguments. Are you able to see the ubuntu prompt in your terminal even if you get no video from LVDS?

I think the booting arguments for that LVDS are: video=mxcfb0:dev=ldb,1024x600M@60,if=RGB666

Perhaps you can have more luck by contacting boundary devices, but I found the following link with bootargs examples:

https://linuxlink.timesys.com/docs/gsg/NITROGEN6X

0 件の賞賛
返信

1,341件の閲覧回数
ashwathhebbar
Contributor II

Hi ,

Thanks for the reply. Now I have got some input from boundary devices.  Let me go through that.

I will get back in case issue is not resolved.

Regards,

Ashwath

0 件の賞賛
返信