omap2430sdp fb and lcd - unable to see anything

omap2430sdp fb and lcd - unable to see anything

[Ram]

[-- Attachment #1: Type: text/plain, Size: 735 bytes --]

Hi,
   Have been trying to get linux-2.6.19-omap1 working with OMAP2430SDP.

   Im using the code 2.6.14-7 (with linux.omap.com) as a reference.

   I have tried to port frame buffer driver and lcd driver to linux 2.6.19

   Im able to do
         $ cat /bin/busybox > /dev/fb

  But i dont see anything on the LCD. I also notice that the LED "CPLD Done"
is not on.
  The LED, is right below the LCD panel on the SDP.

  Im not sure if the LCD panel is powered-on?.

Please Advice, do let me know if im doing something im not supposed to do.

Appending boot messages does this makes sense?.
I see the fb and lcd getting registered.

have a doubt on power and clock settings. not sure, hence the mail


Please advice



Regards,
sriram

[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 5436 bytes --]

Linux version 2.6.19-omap1 (sriram@sriram) (gcc version 3.4.4) #15 Fri Feb 9 06:15:56 IST 2007
CPU: Some Random V6 Processor [4107b366] revision 6 (ARMv6TEJ), cr=00c5387f
Machine: OMAP2430 sdp2430 board
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 8192
  DMA zone: 64 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 8128 pages, LIFO batch:0
  Normal zone: 0 pages used for memmap
OMAP24302
SRAM: Mapped pa 0x40200000 to va 0xd0000000 size: 0x100000
CPU0: D VIPT write-back cache
CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
Built 1 zonelists.  Total pages: 8128
Kernel command line: mem=32M console=ttyS0,115200n8 rw root=/dev/nfs nfsroot=192.168.13.251:/home/sriram/minrootfs ip=dhcp
Clocking rate (Crystal/DPLL/MPU): 13.0/532/266 MHz
clock.c: Enable for dpll_ck without enable code
Clock apll54_ck didn't lock
GPMC revision 3.0
IRQ: Found an INTC at 0xd80fe000 (revision 3.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP243x GPIO hardware version 2.4
PID hash table entries: 128 (order: 7, 512 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 32MB = 32MB total
Memory: 29484KB available (2320K code, 509K data, 116K init)
Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
OMAP DMA hardware revision 4.0
Initializing OMAP McBSP system
omapdsp: could not acquire dsp_fck handle.
OMAP virtual buses initialized
omap2_disp: timeout waiting for display controller reset
OMAP Display hardware version 1.0
USB: No board-specific platform config found
i2c_omap i2c_omap.2: bus 2 rev3.7 at 100 kHz
i2c_omap i2c_omap.1: bus 1 rev3.7 at 100 kHz
TWL4030: TRY attach Slave TWL4030-ID0 on Adapter OMAP I2C adapter[1][1]
TWL4030: TRY attach Slave TWL4030-ID1 on Adapter OMAP I2C adapter[1][1]
TWL4030: TRY attach Slave TWL4030-ID2 on Adapter OMAP I2C adapter[1][1]
TWL4030: TRY attach Slave TWL4030-ID3 on Adapter OMAP I2C adapter[1][1]
TWL4030: Driver registration complete.
NET: Registered protocol family 2
IP route cache hash table entries: 256 (order: -2, 1024 bytes)
TCP established hash table entries: 1024 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 1024 bind 512)
TCP reno registered
NetWinder Floating Point Emulator V0.97 (double precision)
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Registering OMAP device 'sdp2430_lcd9'. Parent at L3
omap2_disp_outLCD panel 240x320
Registering OMAP device 'omap24xxfb6'. Parent at L3
omap24xxfb: Options "<NULL>"
Console: switching to colour frame buffer device 30x40
omap24xxfb: fb0 frame buffer device 
omap24xxfb: display mode 240x320x16 hsync 19kHz vsync 57Hz
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.0: ttyS2 at MMIO 0x4806e000 (irq = 74) is a ST16654
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Registering OMAP device 'omap-twl4030rtc16'. Parent at L4CORE
omap-twl4030rtc:TWL4030-RTC Power up reset detected.
omap-twl4030rtc:Enabling TWL4030-RTC.
smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <nico@cam.org>
eth0: SMC91C94 (rev 9) at c2852300 IRQ 245 [nowait]
eth0: Ethernet addr: 08:00:28:01:0a:de
eth0: No PHY found
omapflash.0: Found 1 x16 devices at 0x0 in 16-bit bank
omapflash.0: Found 1 x16 devices at 0x2000000 in 16-bit bank
 Intel/Sharp Extended Query Table at 0x010A
 Intel/Sharp Extended Query Table at 0x010A
 Intel/Sharp Extended Query Table at 0x010A
 Intel/Sharp Extended Query Table at 0x010A
 Intel/Sharp Extended Query Table at 0x010A
 Intel/Sharp Extended Query Table at 0x010A
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
erase region 0: offset=0x0,size=0x20000,blocks=255
erase region 1: offset=0x1fe0000,size=0x8000,blocks=4
erase region 2: offset=0x2000000,size=0x20000,blocks=255
erase region 3: offset=0x3fe0000,size=0x8000,blocks=4
omapflash.0: 2 set(s) of 1 interleaved chips --> 32 partitions of 2048 KiB
Creating 4 MTD partitions on "omapflash.0":
0x00000000-0x00040000 : "bootloader"
0x00040000-0x00060000 : "params"
0x00060000-0x00260000 : "kernel"
0x00260000-0x04000000 : "filesystem"
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
eth0: link up
Sending DHCP requests ., OK
IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.13.33
IP-Config: Complete:
      device=eth0, addr=192.168.13.33, mask=255.255.255.0, gw=192.168.13.1,
     host=192.168.13.33, domain=, nis-domain=(none),
     bootserver=0.0.0.0, rootserver=192.168.13.251, rootpath=
Looking up port of RPC 100003/2 on 192.168.13.251
Looking up port of RPC 100005/1 on 192.168.13.251
VFS: Mounted root (nfs filesystem).
Freeing init memory: 116K

[-- Attachment #3: Type: text/plain, Size: 0 bytes --]

RE: omap2430sdp fb and lcd - unable to see anything

[Syed Mohammed, Khasim]

Hi Sriram,
 
Can you just list the set of files that you are trying to port from 2.6.14 to 2.6.19?
 
Yes, you have to enable power for UI board, its from T2 LDO. Please refer to power_companion.c & omap2_disp_out.c
 
Regards,
Khasim

________________________________

From: linux-omap-open-source-bounces@linux.omap.com on behalf of Ram
Sent: Fri 2/9/2007 8:43 AM
To: linux-omap-open-source@linux.omap.com
Subject: omap2430sdp fb and lcd - unable to see anything



Hi,
   Have been trying to get linux-2.6.19-omap1 working with OMAP2430SDP.

   Im using the code 2.6.14-7 (with linux.omap.com) as a reference.

   I have tried to port frame buffer driver and lcd driver to linux 2.6.19

   Im able to do
         $ cat /bin/busybox > /dev/fb

  But i dont see anything on the LCD. I also notice that the LED "CPLD Done"
is not on.
  The LED, is right below the LCD panel on the SDP.

  Im not sure if the LCD panel is powered-on?.

Please Advice, do let me know if im doing something im not supposed to do.

Appending boot messages does this makes sense?.
I see the fb and lcd getting registered.

have a doubt on power and clock settings. not sure, hence the mail


Please advice



Regards,
sriram