ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Ltib] ARM9DIMM-LPC3250 DirectFB problems


From: Kevin Wells
Subject: RE: [Ltib] ARM9DIMM-LPC3250 DirectFB problems
Date: Wed, 27 Oct 2010 10:15:56 +0200

Hi Marco,

It sounds like you have your display up and running, but I'm
not sure why that dfb app doesn't work. It seems to need
panning, which the AMBA FB driver doesn't support. Can you
run gtk now?

Kevin


> -----Original Message-----
> From: address@hidden [mailto:ltib-
> address@hidden On Behalf Of address@hidden
> Sent: Tuesday, October 26, 2010 6:59 AM
> To: address@hidden
> Subject: [Ltib] ARM9DIMM-LPC3250 DirectFB problems
> 
> Hi Kevin,
> I solved the problems related to the kernel startup: now i can see the
> Penguin. I'm using QVGA display.
> 
> I tried the directfd commands but something goes wrong.
> 
> Here follow an example:
> I tried dfbg command. The response on the serial console was the following.
> address@hidden user]# dfbg lg-alten.
> png
> 
> 
>      =======================|  DirectFB 1.1.0
> |=======================
>           (c) 2001-2007  The DirectFB Organization (directfb.
> org)
>           (c) 2000-2004  Convergence (integrated media)
> GmbH
> 
> ------------------------------------------------------------
> 
> 
> (*) DirectFB/Core: Single Application Core. (2010-10-26 10:
> 41)
> (*) Direct/Thread: Running 'VT Switcher' (CRITICAL,
> 731)...
> (*) Direct/Thread: Running 'Keyboard Input' (INPUT,
> 732)...
> (*) DirectFB/Input: Keyboard 0.9 (directfb.
> org)
> (!) Direct/Modules: Could not open module directory `/usr/lib/directfb-
> 1.1-
> 0/gf!
>     --> No such file or
> directory
> (*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (directfb.
> org)
> (*) DirectFB/Core/WM: Default 0.3 (directfb.
> org)
> (*) FBDev/Mode: Testing 320x240
> RGB16
> (*) FBDev/Mode: Preparing switch to 320x240
> RGB16
> (*) FBDev/Mode: Testing 320x240
> RGB16
> (*) FBDev/Mode: Preparing switch to 320x240
> RGB16
> (*) FBDev/Mode: Testing 320x240
> RGB16
> (*) FBDev/Mode: Preparing switch to 320x240
> RGB16
> (*) FBDev/Mode: Testing 320x240
> RGB16
> (*) FBDev/Mode: Preparing switch to 320x240
> RGB16
> (*) FBDev/Mode: Testing 320x240
> RGB16
> (*) FBDev/Mode: Preparing switch to 320x240
> RGB16
> (*) FBDev/Mode: Switched to 320x240 (320x240) at 16 bit RGB16 (wanted
> RGB16).
> (!) DirectFB/FBDev: Panning display failed (x=0 y=0 ywrap=0
> vbl=0)!
>     --> Invalid
> argument
> (*) FBDev/Surface: Allocated 320x240 16bit RGB16 buffer at offset 0 and
> pitch
> 6.
> (*) FBDev/Mode: (Post)Setting 320x240
> RGB16
> (*) FBDev/Mode: Testing 320x240
> RGB16
> (*) FBDev/Mode: Preparing switch to 320x240
> RGB16
> (*) FBDev/Mode: (Post)Setting 320x240
> RGB16
> (*) Direct/Interface: Loaded 'PNG' implementation of
> 'IDirectFBImageProvider'.
> address@hidden user]#
> 
> The displays showed for few milliseconds the image and than went to blank
> screen (black background).
> 
> Do you have any idea?
> 
> Thanks,
>                     Marco
> 
> 
> --------------------------------------------------------------------------
> --------------------------------
> RE: [Ltib] GTK+ cannot open display - ARM9DIMM-LPC3250
> From:         Kevin Wells
> Subject:      RE: [Ltib] GTK+ cannot open display - ARM9DIMM-LPC3250
> Date:         Thu, 23 Sep 2010 18:20:12 +0200
> 
> Hi Marco,
> 
> > During Sibl-uboot-kernel startup i can't see a Penguin on the display.
> You should see the penguin once the kernel starts up. Are you using the
> QVGA or VGA display? From what I understand, older versions of SIBL
> do not turn on the VGA display backlight.
> 
> > CLCD: Phytec LCD hardware, QVGA portrait display
> It looks like you are using an older port. You should do a CVS update
> and get the latest FDI changes. If your using the latest updates, this
> should indicate an FDI display name.
> 
> > console: GTK+ cannot open display.
> You can always try building the directfb examples and running them
> first to verify the display works (once you get the display turned on).
> 
> I hope this helps,
> Kevin
> 
> > -----Original Message-----
> > From: address@hidden [mailto:ltib-
> > address@hidden On Behalf Of address@hidden
> > Sent: Tuesday, September 21, 2010 7:14 AM
> > To: address@hidden
> > Subject: [Ltib] GTK+ cannot open display - ARM9DIMM-LPC3250
> >
> > Hi,
> >
> > i'm trying to use LCD with ARM9DIMM-LPC3250 board.
> >
> > I used ltib to generate Kernel and rootfs with gtk+ (and all libraries
> > needed)
> > support.
> >
> > I loaded the new uboot and kernel on Flash. I'm running the rootfs from
> > NFS
> > server on development machine.
> >
> > During Sibl-uboot-kernel startup i can't see a Penguin on the display.
> >
> > When i execute the GTK_Init function the following message appear on
> > serial
> > console: GTK+ cannot open display.
> >
> > Maybe i forgot to include or set in my kernel or image configuration?
> >
> > This is the output on the console:
> >
> > SIBL 1.01 (06/12/2009) - 266000000 Hz
> > Copyright 2009, Future Designs, Inc.
> > -------------------------------------------------------------------
> > DDR:   SDRAMCLK_CTRL = 0003CAA2
> > DDR:   DDR_LAP_NOM   = 0000002A (42)
> > DDR:   DDR_LAP_COUNT = 0000002A (42)
> > DDR:   DDR_CAL_DELAY = 00000008 (8)
> >
> > LCD:   Turning on ... Done
> > NAND:  Initializing MLC ... OK
> > LCD:   Drawing splash screen ...  OK
> > NAND:  Initializing MLC ... OK
> > UBOOT: Loading to address 0x81FC0000 ...  OK
> > UBOOT: Running at 0x81FC0000...
> >
> >
> > U-Boot 1.3.3 (Aug  3 2010 - 10:40:20)
> >
> > DRAM:  32 MB
> > NAND:  256 MiB
> > In:    serial
> > Out:   serial
> > Err:   serial
> > Hit any key to stop autoboot:  0
> >
> > NAND read: device 0 offset 0x80000, size 0x200000
> >
> > Reading data from 0x27f800 -- 100% complete.
> > 2097152 bytes read: OK
> > Unknown command 'mmcinit' - try 'help'
> > ## Booting kernel from Legacy Image at 80100000 ...
> >    Image Name:   Linux-2.6.27.8
> >    Image Type:   ARM Linux Kernel Image (uncompressed)
> >    Data Size:    1605308 Bytes =  1.5 MB
> >    Load Address: 80008000
> >    Entry Point:  80008000
> >    Verifying Checksum ... OK
> >    Loading Kernel Image ... OK
> > OK
> >
> > Starting kernel ...
> >
> > Uncompressing
> >
> Linux.....................................................................
> > ..................................
> > done, booting the kernel.
> > Linux version 2.6.27.8 (address@hidden) (gcc version 3.4.5) #19 PREEMPT
> > Mon
> > Sep 20 21:28:18 CEST 2010
> > CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177
> > Machine: FDI ARM-TS-KIT 3250 board with the LPC3250 Microcontroller
> > Memory policy: ECC disabled, Data cache writeback
> > CPU0: D VIVT 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 in Zone order, mobility grouping on.  Total pages:
> 32512
> > Kernel command line: console=ttyTX0,115200n81 noinitrd ip=192.168.10.20:
> > 192.168.10.1:255.255.255.0 root=/dev/nfs rw nfsroot=192.168.10.10:
> > /home/luca/ltib-10M
> > PID hash table entries: 512 (order: 9, 2048 bytes)
> > Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
> > Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
> > Memory: 128MB = 128MB total
> > Memory: 126448KB available (3004K code, 190K data, 100K init)
> > Calibrating delay loop... 133.12 BogoMIPS (lpj=266240)
> > Mount-cache hash table entries: 512
> > CPU: Testing write buffer coherency: ok
> > net_namespace: 288 bytes
> > NET: Registered protocol family 16
> > Hardware descriptor info:
> > DRAM config word: 0x00000001
> > syscfg word:      0x00000002
> > fieldval word:    0x000a3250
> > MAC address:      <6>00:11:22:33:44:55
> > LPC32XX DMA driver
> > LPC32XX unique ID: 00000000000000000000000000000000
> > SCSI subsystem initialized
> > usbcore: registered new interface driver usbfs
> > usbcore: registered new interface driver hub
> > usbcore: registered new device driver usb
> > NET: Registered protocol family 2
> > IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> > TCP established hash table entries: 4096 (order: 3, 32768 bytes)
> > TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
> > TCP: Hash tables configured (established 4096 bind 4096)
> > TCP reno registered
> > NET: Registered protocol family 1
> > NetWinder Floating Point Emulator V0.97 (double precision)
> > fuse init (API version 7.9)
> > msgmni has been set to 247
> > io scheduler noop registered
> > io scheduler anticipatory registered
> > io scheduler deadline registered
> > io scheduler cfq registered (default)
> > CLCD: Phytec LCD hardware, QVGA portrait display
> > ipmi message handler version 39.2
> > Serial: 8250/16550 driver4 ports, IRQ sharing disabled
> > serial8250.0: ttyS0 at MMIO 0x40090000 (irq = 9) is a 16550A
> > lpc32xx_hsuart.0: ttyTX0 at MMIO 0x40014000 (irq = 26) is a
> lpc32xx_hsuart
> > console [ttyTX0] enabled
> > LPC32XX_mii_bus: probed
> > eth0: LPC32XX mac at 0x31060000 irq 29
> > eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:00, irq=-1)
> > usbmon: debugfs is not available
> > I2C device at address 0x2d<6>ISP1301 Vendor ID  : 0x04cc
> > ISP1301 Product ID : 0x1301
> > ISP1301 Version ID : 0x0210
> > usb-ohci usb-ohci: at 0xf3120000, irq 0
> > usb-ohci usb-ohci: pnx4008 OHCI
> > usb-ohci usb-ohci: new USB bus registered, assigned bus number 1
> > usb-ohci usb-ohci: irq 59, io mem 0xf3120000
> > usb usb1: configuration #1 chosen from 1 choice
> > hub 1-0:1.0: USB hub found
> > hub 1-0:1.0: 2 ports detected
> > usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
> > usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> > usb usb1: Product: pnx4008 OHCI
> > usb usb1: Manufacturer: Linux 2.6.27.8 ohci_hcd
> > usb usb1: SerialNumber: usb-ohci
> > Initializing USB Mass Storage driver...
> > usbcore: registered new interface driver usb-storage
> > USB Mass Storage support registered.
> > rtc-test rtc-test.0: rtc core: registered test as rtc0
> > rtc-test rtc-test.1: rtc core: registered test as rtc1
> > i2c /dev entries driver
> > PNX4008-WDT: PNX4008 Watchdog Timer: heartbeat 19 sec
> > TCP cubic registered
> > NET: Registered protocol family 17
> > RPC: Registered udp transport module.
> > RPC: Registered tcp transport module.
> > ieee80211: 802.11 data/management/control stack, git-1.1.13
> > ieee80211: Copyright (C) 2004-2005 Intel Corporation <address@hidden
> > com>
> > VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 1
> > rtc-test rtc-test.0: setting system clock to 1970-01-01 00:00:01 UTC (1)
> > IP-Config: Guessing netmask 255.255.255.0
> > IP-Config: Gateway not on directly connected network.
> > Looking up port of RPC 100003/2 on 192.168.10.10
> > Looking up port of RPC 100005/1 on 192.168.10.10
> > VFS: Mounted root (nfs filesystem).
> > Freeing init memory: 100K
> > Warning: unable to open an initial console.
> >
> >
> >         Welcome to Future Designs, Inc. LPC3250 Linux
> >
> > The default password for the root account is: root
> > please change this password using the 'passwd' command
> > and then edit this message (/etc/issue) to remove this message
> >
> > nxp login:
> >
> > Best regards,
> >
> > Marco
> >
> > _______________________________________________
> > LTIB home page: http://ltib.org
> >
> > Ltib mailing list
> > address@hidden
> > http://lists.nongnu.org/mailman/listinfo/ltib
> 
> 
> 
> _______________________________________________
> LTIB home page: http://ltib.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib

reply via email to

[Prev in Thread] Current Thread [Next in Thread]