topic Re: Seiko WVGA Panel with iMX53 Start Board in i.MX Processors

Seiko WVGA Panel with iMX53 Start Board

Roshni — Sat, 19 Mar 2011 17:02:56 GMT

Hi All,

I am working with the Quick Start Board evaluation board with a Seiko 4.3" WVGA Touch Panel LCD connected to the Expansion Port (J13). It doesn't show any startup image nor does the boot up process detect the LCD...

Following are the boot params used:

setenv bootargs_base ‘set bootargs console=ttymxc0,115200 video=mxcdi0fb:RGB24,SEIKO-WVGA

Is there anything else specific I need to do to enable the LCD Panel? Please let me know if you need any further information to better understand the problem (eg: Kernel Boot log, Uboot params etc)

Any help will be greatly appreciated.

Thanks,
Roshni

Re: Seiko WVGA Panel with iMX53 Start Board

VladanJovanovic — Mon, 21 Mar 2011 13:27:50 GMT

Hi,

what is the revision of the Quick Start Board you have?

Vladan

Re: Seiko WVGA Panel with iMX53 Start Board

Roshni — Mon, 21 Mar 2011 22:56:49 GMT

Hi Vladan, Thanks for your quick response. I have Rev B of the board with following information on the board: SCH -26565 Rev B 700-26565 Rev B TDA 3737 Please let me know if you need any more information. Thanks for your help Roshni

Re: Seiko WVGA Panel with iMX53 Start Board

VladanJovanovic — Wed, 23 Mar 2011 07:15:25 GMT

Hi Roshni,

it looks like you've got earlier release of the board. Small modification is required on the LCD board to get it working. See attached. On Rev C boards this is not needed.

br,

Vladan

Re: Seiko WVGA Panel with iMX53 Start Board

Roshni — Wed, 23 Mar 2011 10:57:43 GMT

Thanks for your prompt reply Vladan. I greatly appreciate it. I will try the mod tonight will let you know.

Thanks a bunch again.

Roshni

Vladan Jovanovic said:

Hi Roshni,

it looks like you've got earlier release of the board. Small modification is required on the LCD board to get it working. See attached. On Rev C boards this is not needed.

br,
Vladan

Re: Seiko WVGA Panel with iMX53 Start Board

Roshni — Thu, 24 Mar 2011 01:36:01 GMT

Hi Vladan, It worked great. Thanks a lot for your prompt help. Best Regards, Roshni

Re: Seiko WVGA Panel with iMX53 Start Board

Roshni — Sun, 27 Mar 2011 22:08:34 GMT

Hi,

I was successfully able to play a 1080P / 720P Video working with following options (single Video mode):

setenv bootargs_base setenv bootargs console=ttymxc0,115200 video=mxcdi1fb:YUV444,TV-1080P30 di1_primary tve

Now I am trying to get dual display and touch screen working with the following options:

setenv bootargs_base setenv bootargs console=ttymxc0,115200 video=mxcdi0fb:RGB24,SEIKO-WVGA video=mxcdi1fb:YUV444,TV-1080P30 di1_primary tve

Every time I un-blank the LCD display, my primary display (a 1080P TV in my case) says un-supported mode, following which I can never get anything to display on my Primary display. I referred to the imx53-start-linux.pdf document and it tells that "D4 needs to be populated for Seiko LCD Panel" Pg 11-1.

1. Do I have to populate D4 also for Dual Display to work?

2. Where would I find the Schematics of MCIMX28LCD?

3. Touch screen also doesn't work, do I have to do anything special to get that to work?

Any help will be greatly appreciated. Thanks a lot for your time. Please let me know if you need any other information.

Best Regards,
Roshni

Re: Seiko WVGA Panel with iMX53 Start Board

VladanJovanovic — Thu, 31 Mar 2011 02:28:43 GMT

Hi Roshni,

I'm not sure on exact syntax for enabling dual displays right now, may be you'll have to do it from command line. Schematic for MCIMX28LCD is attached.

Does touch screen work in single-display configuration? Can you see the driver is loaded and is any kind of event generated on /dev/input/eventX ?

br,

Vladan

Re: Seiko WVGA Panel with iMX53 Start Board

Roshni — Thu, 31 Mar 2011 10:23:52 GMT

Hi Vladan,

I narrowed down the issue of dual display to a memory corruption in the driver - ipu-disp.c (ipu_init_sync_panel). I am not sure of the procedure, but I can send you a patch / explanation for it. After I made the appropriate change, dual display is working now.

Regarding touchscreen it doesn't work in single-display configuration too. I see the driver is loaded and I see some event debugging messages coming from /dev/input3/eventX in dmesg too. But nothing on touch screen comes up. Is there a way I can enable touch screen calibration? Maybe that's the reason why its not working. I tried giving a command line argument of calibration, but I did not get a /etc/pointercal. Any thoughts will be greatly appreciated.

Thanks a lot for the schematics and your prompt reply.

Best regards,
Roshni

Vladan Jovanovic said:

Hi Roshni,

I'm not sure on exact syntax for enabling dual displays right now, may be you'll have to do it from command line. Schematic for MCIMX28LCD is attached.

Does touch screen work in single-display configuration? Can you see the driver is loaded and is any kind of event generated on /dev/input/eventX ?

br,
Vladan

Re: Seiko WVGA Panel with iMX53 Start Board

VladanJovanovic — Fri, 01 Apr 2011 01:19:52 GMT

Did you install tslib from ltib? what happens when you run ts_calibrate or ts_print_raw? You need to export TSLIB_TSDEVICE env. variable to correct touchscreen device as well...

br,

Vladan

Roshni said:

Regarding touchscreen it doesn't work in single-display configuration too. I see the driver is loaded and I see some event debugging messages coming from /dev/input3/eventX in dmesg too. But nothing on touch screen comes up. Is there a way I can enable touch screen calibration? Maybe that's the reason why its not working. I tried giving a command line argument of calibration, but I did not get a /etc/pointercal. Any thoughts will be greatly appreciated.

Re: Seiko WVGA Panel with iMX53 Start Board

shlomok — Wed, 25 May 2011 06:25:23 GMT

Hi,

We also had problems identifying key presses with the MCIMX28LD Sieko LCD supplied with the imx53 Quick Start Board.

We could not identify key presses and were unable to calibrate the LCD using tslib ts_calibrate.

We found using tslib ts_print_raw test that the x and y coordinates were fine but we were getting no indication of pressure from the kernel.

We found that da9052_tsi.c touch screen driver never sends any indication of pressure to user space.

I attach a patch to the kernel that fixed this problem.

Regards,

Shlomo Kut

Re: Seiko WVGA Panel with iMX53 Start Board

AdrianWalker — Thu, 29 Dec 2011 22:33:06 GMT

I haven't ordered my iMX53 Quick Start Kit with touch screen LCD display yet, but I'm keen to look at the interface pcb logic before it arrives. I have down loaded the i.MX28 LCD Design Files:Hardware Schematics but there doesn't appear to be any logic on PCB. Can you please post/sent me a full photo of the PCB that is attached to the Seiko 4.3" WVGA Touch Panel LCD. Thanks and Happy New Year.

Adrian

Vladan Jovanovic said:

Hi Roshni,

it looks like you've got earlier release of the board. Small modification is required on the LCD board to get it working. See attached. On Rev C boards this is not needed.

br,
Vladan

Re: Seiko WVGA Panel with iMX53 Start Board

Vinay_123 — Thu, 12 Jan 2012 12:11:12 GMT

Hi,

I am using the MCIMX53QSB. In following you can find the LOG Details. Also Please view the attached Schematic of LCD. Let me know whether the patch is updated or not. I am using the latest BSP.11.09.

Please Find the attachments :

1.) env variables.

2.) log.text

3.) schematics of LCD

CPU: Freescale i.MX53 family 2.1V at 800 MHz
mx53 pll1: 800MHz
mx53 pll2: 400MHz
mx53 pll3: 432MHz
mx53 pll4: 455MHz
ipg clock : 66666666Hz
ipg per clock : 33333333Hz
uart clock : 66666666Hz
cspi clock : 108000000Hz
ahb clock : 133333333Hz
axi_a clock : 400000000Hz
axi_b clock : 200000000Hz
emi_slow clock: 133333333Hz
ddr clock : 400000000Hz
esdhc1 clock : 80000000Hz
esdhc2 clock : 80000000Hz
esdhc3 clock : 80000000Hz
esdhc4 clock : 80000000Hz
nfc clock : 26666666Hz
Board: MX53-LOCO 1.0 Rev. A
Boot Reason: [POR]
Boot Device: SD
I2C: ready
DRAM: 1 GB
MMC: FSL_ESDHC: 0,FSL_ESDHC: 1
In: serial
Out: serial
Err: serial
da9052_i2c_is_connected - i2c write success....
Serial reinitilized!
Net: got MAC address from IIM: 00:04:9f:01:df:e7
FEC0 [PRIME]
Hit any key to stop autoboot: 0
MX53-LOCO U-Boot > printenv
baudrate=115200
loadaddr=0x70800000
netdev=eth0
ethprime=FEC0
uboot=u-boot.bin
kernel=uImage
nfsroot=/opt/eldk/arm
ethact=FEC0
bootdelay=5
lvds=video=mxcdi0fb:RGB666,XGA ldb
vga=video=mxcdi1fb:GBR24,XGA di1_primary tve
hdmi=video=mxcdi0fb:RGB24,1024x768@60
bootcmd=run bootcmd_mmc
bootcmd_net=run bootargs_base bootargs_nfs; tftpboot ${loadaddr} ${kernel}; bootm
bootargs_nfs=setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp
lcd=video=mxcdi0fb:RGB24,SEIKO-WVGA
bootargs=console=ttymxc0,115200 video=mxcdi0fb:RGB24,SEIKO-WVGA root=/dev/mmcblk0p1 rw rootwait
bootcmd_mmc=run bootargs_base bootargs_mmc; mmc dev 0; mmc read ${loadaddr} 0x800 0x1800; bootm
bootargs_mmc=set bootargs ${bootargs} root=/dev/mmcblk0p1 rw rootwait
bootargs_base=set bootargs console=ttymxc0,115200 ${lcd}
stdin=serial
stdout=serial
stderr=serial

Environment size: 860/8188 bytes
MX53-LOCO U-Boot > boot
mmc0 is current device

MMC read: dev # 0, block # 2048, count 6144 ... 6144 blocks read: OK
## Booting kernel from Legacy Image at 70800000 ...
Image Name: Linux-2.6.35.3-1129-g691c08a
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3008108 Bytes = 2.9 MB
Load Address: 70008000
Entry Point: 70008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Linux version 2.6.35.3-1129-g691c08a (r80115@bluebell) (gcc version 4.4.4 (4.4.4_09.06.2010) ) #1 PREEMPT Sat Sep 24 21:21:12 CDT 2011
CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Freescale MX53 LOCO Board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 250880
Kernel command line: console=ttymxc0,115200 video=mxcdi0fb:RGB24,SEIKO-WVGA root=/dev/mmcblk0p1 rw rootwait
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: 480MB 512MB = 992MB total
Memory: 998220k/998220k available, 17588k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xf9e00000 - 0xffe00000 ( 96 MB)
vmalloc : 0xe0800000 - 0xf4000000 ( 312 MB)
lowmem : 0x80000000 - 0xe0000000 (1536 MB)
pkmap : 0x7fe00000 - 0x80000000 ( 2 MB)
modules : 0x7f000000 - 0x7fe00000 ( 14 MB)
.init : 0x80008000 - 0x80033000 ( 172 kB)
.text : 0x80033000 - 0x807fa000 (7964 kB)
.data : 0x80818000 - 0x80870120 ( 353 kB)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
RCU-based detection of stalled CPUs is disabled.
Verbose stalled-CPUs detection is disabled.
NR_IRQS:368
MXC GPIO hardware
MXC IRQ initialized
MXC_Early serial console at MMIO 0x53fbc000 (options '115200')
bootconsole [ttymxc0] enabled
Console: colour dummy device 80x30
Calibrating delay loop... 999.42 BogoMIPS (lpj=4997120)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
i.MX IRAM pool: 128 KB@0xe0840000
IRAM READY
CPU is i.MX53 Revision 2.1
Using SDMA I.API
MXC DMA API initialized
IMX usb wakeup probe
IMX usb wakeup probe
bio: create slab <bio-0> at 0
SCSI subsystem initialized
Freescale USB OTG Driver loaded, $Revision: 1.55 $

****************************** NOTICE *****************************
You have seen this notice as you have enabled OTG driver for mx53 LOCO board
For mx53 loco board, the OTG function is unavailable due to hardware limitation
So, Only one usb function (device or host) can be available for certain image
Please config your kernel to disable OTG and the usb function you don't want to use
And remain the other usb function you would like to use

Below OTG configs should be removed:
CONFIG_MXC_OTG, CONFIG_USB_OTG

Choose one of below configs for host or device function
But DO NOT choose them together

OTG host config
CONFIG_USB_EHCI_ARC_OTG

OTG device config
CONFIG_USB_GADGET

usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
da9052_i2c_is_connected - i2c read success....
regulator: DA9052_LDO1: 600 <--> 1800 mV at 1300 mV normal
regulator: DA9052_LDO2: 600 <--> 1800 mV at 1300 mV normal
regulator: DA9052_LDO3: 1725 <--> 3300 mV at 3300 mV normal
regulator: DA9052_LDO4: 1725 <--> 3300 mV at 2775 mV normal
regulator: DA9052_LDO5: 1200 <--> 3600 mV at 1300 mV normal
regulator: DA9052_LDO6: 1200 <--> 3600 mV at 1300 mV normal
regulator: DA9052_LDO7: 1200 <--> 3600 mV at 2750 mV normal
regulator: DA9052_LDO8: 1200 <--> 3600 mV at 1800 mV normal
regulator: DA9052_LDO9: 1250 <--> 3650 mV at 1500 mV normal
regulator: DA9052_LDO10: 1200 <--> 3600 mV at 1300 mV normal
regulator: DA9052_BUCK_CORE: 500 <--> 2075 mV at 1250 mV normal
regulator: DA9052_BUCK_PRO: 500 <--> 2075 mV at 1300 mV normal
regulator: DA9052_BUCK_MEM: 925 <--> 2500 mV at 1500 mV normal
regulator: DA9052_BUCK_PERI: 1800 <--> 3600 mV at 3600 mV normal
DA9053 chip ID reg read=0xa3
BB version probed
IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
Advanced Linux Sound Architecture Driver Version 1.0.23.
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Switching to clocksource mxc_timer1
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: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
UDP hash table entries: 512 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 512 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
LPMode driver module loaded
Static Power Management for Freescale i.MX5
PM driver module loaded
sdram autogating driver module loaded
Bus freq driver module loaded
DI1 is primary
mxc_dvfs_core_probe
DVFS driver module loaded
i.MXC CPU frequency driver
DVFS PER driver module loaded
JFFS2 version 2.2. (NAND) ï¿½Â© 2001-2006 Red Hat, Inc.
msgmni has been set to 1949
alg: No test for stdrng (krng)
cryptodev: driver loaded.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
regulator: get() with no identifier
By setting, SII driver will not be enabled
By setting, LDB driver will not be enabled
mxc_ipu mxc_ipu: Channel already disabled 9
mxc_ipu mxc_ipu: Channel already uninitialized 9
IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
Console: switching to colour frame buffer device 128x48
mxc_ipu mxc_ipu: Channel already disabled 7
mxc_ipu mxc_ipu: Channel already uninitialized 7
mxc_ipu mxc_ipu: Channel already disabled 10
mxc_ipu mxc_ipu: Channel already uninitialized 10
Serial: MXC Internal UART driver
mxcintuart.0: ttymxc0 at MMIO 0x53fbc000 (irq = 31) is a Freescale i.MX
console [ttymxc0] enabled, bootconsole disabled
console [ttymxc0] enabled, bootconsole disabled
mxcintuart.1: ttymxc1 at MMIO 0x53fc0000 (irq = 32) is a Freescale i.MX
mxcintuart.2: ttymxc2 at MMIO 0x5000c000 (irq = 33) is a Freescale i.MX
mxcintuart.3: ttymxc3 at MMIO 0x53ff0000 (irq = 13) is a Freescale i.MX
mxcintuart.4: ttymxc4 at MMIO 0x63f90000 (irq = 86) is a Freescale i.MX
loop: module loaded
MXC MTD nand Driver 3.0
i.MX GPMI NFC
vcan: Virtual CAN interface driver
Freescale FlexCAN Driver
FEC Ethernet Driver
fec_enet_mii_bus: probed
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.0: irq 18, io base 0x53f80000
fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
fsl-ehci fsl-ehci.1: irq 14, io base 0x53f80200
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
ARC USBOTG Device Controller driver (1 August 2005)
mice: PS/2 mouse device common for all mice
input: gpio-keys as /devices/platform/gpio-keys/input/input0
MXC keypad loaded
egalax_ts 2-0004: egalax_ts: failed to read firmware version
egalax_ts: probe of 2-0004 failed with error -5
p1003_fwv33 2-0041: couldn't read panel infomation.
p1003_fwv33: probe of 2-0041 failed with error -5
DA9052 TSI Device Driver, v1.0
input: da9052-tsi as /devices/virtual/input/input1
TSI Drv Successfully Inserted da9052-tsi
input: da9052-onkey as /devices/platform/imx-i2c.0/i2c-0/0-0048/da9052-onkey/input/input2
mxc_rtc mxc_rtc.0: rtc core: registered mxc_rtc as rtc0
i2c /dev entries driver
IR NEC protocol handler initialized
IR RC5(x) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
Linux video capture interface: v2.00
mxc_v4l2_output mxc_v4l2_output.0: Registered device video0
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
APM Battery Driver
check mma8450 chip ID
mma8450 0-001c: build time Sep 24 2011 21:16:52
input: mma8450 as /devices/virtual/input/input3
add mma8450 i2c driver
MXC WatchDog Driver 2.0
MXC Watchdog # 0 Timer: initial timeout 60 sec
Bluetooth: Virtual HCI driver ver 1.3
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCIATH3K protocol initialized
Bluetooth: Generic Bluetooth USB driver ver 0.6
usbcore: registered new interface driver btusb
VPU initialized
mxc_asrc registered
gpu mmu enabled
mxsdhci: MXC Secure Digital Host Controller Interface driver
mxsdhci: MXC SDHCI Controller Driver.
mmc0: SDHCI detect irq 0 irq 1 INTERNAL DMA
mxsdhci: MXC SDHCI Controller Driver.
mmc1: SDHCI detect irq 203 irq 3 INTERNAL DMA
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
Cirrus Logic CS42888 ALSA SoC Codec Driver
sgtl5000-i2c 1-000a: SGTL5000 revision 17
mxc_spdif mxc_spdif.0: MXC SPDIF Audio Transmitter
No device for codec mxc spdif
No device for DAI mxc spdif
No device for DAI imx-ssi-1-0
No device for DAI imx-ssi-1-1
No device for DAI imx-ssi-2-0
No device for DAI imx-ssi-2-1
No device for DAI imx-spdif-dai
usb 1-1: new low speed USB device using fsl-ehci and address 2
DMA Sound Buffer Allocated: Playback UseIram=1 ext_ram=0 buf->addr=f8016000 buf->area=e0856000 size=24576
DMA Sound Buffer Allocated: Capture UseIram=1 ext_ram=1 buf->addr=cf348000 buf->area=fa8ad000 size=24576
asoc: SGTL5000 <-> imx-ssi-2-0 mapping ok
mmc0: new high speed SDHC card at address b368
mmcblk0: mmc0:b368 00000 7.51 GiB
mmcblk0: p1
DMA Sound Buffer Allocated: Playback UseIram=1 ext_ram=1 buf->addr=cf438000 buf->area=fa8b3000 size=24576
asoc: mxc spdif <-> imx-spdif-dai mapping ok
ALSA device list:
#0: imx-3stack (SGTL5000)
#1: imx-3stack-spdif (mxc spdif)
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Bluetooth: L2CAP ver 2.14
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2
usb 1-1: device v413c p3200 is not supported
regulator_init_complete: incomplete constraints, leaving DA9052_BUCK_PERI on
regulator_init_complete: incomplete constraints, leaving DA9052_BUCK_MEM on
regulator_init_complete: incomplete constraints, leaving DA9052_BUCK_PRO on
regulator_init_complete: incomplete constraints, leaving DA9052_BUCK_CORE on
regulator_init_complete: incomplete constraints, leaving DA9052_LDO10 on
regulator_init_complete: incomplete constraints, leaving DA9052_LDO8 on
regulator_init_complete: incomplete constraints, leaving DA9052_LDO6 on
regulator_init_complete: incomplete constraints, leaving DA9052_LDO5 on
regulator_init_complete: incomplete constraints, leaving DA9052_LDO4 on
regulator_init_complete: incomplete constraints, leaving DA9052_LDO3 on
regulator_init_complete: incomplete constraints, leaving DA9052_LDO2 on
regulator_init_complete: incomplete constraints, leaving DA9052_LDO1 on
mxc_rtc mxc_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0)
input: Dell Dell USB Mouse as /devices/platform/fsl-ehci.0/usb1/1-1/1-1:1.0/input/input4
generic-usb 0003:413C:3200.0001: input: USB HID v1.10 Mouse [Dell Dell USB Mouse] on usb-fsl-ehci.0-1/input0
EXT2-fs (mmcblk0p1): warning: mounting unchecked fs, running e2fsck is recommended
usb 2-1: new high speed USB device using fsl-ehci and address 2
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 4 ports detected
VFS: Mounted root (ext2 filesystem) on device 179:1.
Freeing init memory: 172K
starting pid 1191, tty '': '/etc/rc.d/rcS'
Mounting /proc and /sys
usb 2-1.2: new low speed USB device using fsl-ehci and address 3
Starting the hotplug events dispatcher udevd
Synthesizing initial hotplug events
input: DELL Dell QuietKey Keyboard as /devices/platform/fsl-ehci.1/usb2/2-1/2-1.2/2-1.2:1.0/input/input5
generic-usb 0003:413C:2106.0002: input: USB HID v1.10 Keyboard [DELL Dell QuietKey Keyboard] on usb-fsl-ehci.1-1.2/input0
Setting the hostname to freescale
Mounting filesystems
mount: mounting usbfs on /proc/bus/usb failed: No such file or directory
Starting the dropbear ssh server:
D-Bus per-session daemon address is: unix:abstract=/tmp/dbus-Zn9qOfV0R8,guid=9f337f250a8db0eea07d604c0000000a
gtk: creating gdk-pixbuf.loaders
pango: creating module list
starting pid 2285, tty '': '/sbin/getty -L ttymxc0 115200 vt100'
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/freescale:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
(EE) XKB: Couldn't open rules file /usr/share/X11/xkb/rules/base
(EE) XKB: No components provided for device Virtual core keyboard
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)

arm-none-linux-gnueabi-gcc (4.4.4_09.06.2010) 4.4.4
root filesystem built on Thu, 29 Sep 2011 15:54:39 +0800
Freescale Semiconductor, Inc.

freescale login: matchbox: keyboard does not appear to have a <alt> key.
matchbox: ignoring key shortcut <Alt>n=next

matchbox: keyboard does not appear to have a <alt> key.
matchbox: ignoring key shortcut <Alt>p=prev

matchbox: keyboard does not appear to have a <alt> key.
matchbox: ignoring key shortcut <Alt>c=close

matchbox: keyboard does not appear to have a <alt> key.
matchbox: ignoring key shortcut <Alt>d=desktop

matchbox: keyboard does not appear to have a <alt> key.
matchbox: ignoring key shortcut <Alt>m=!matchbox-remote -mbmenu

matchbox: keyboard does not appear to have a <alt> key.
matchbox: ignoring key shortcut <ctrl><alt>x=!xterm

matchbox: keyboard does not appear to have a <alt> key.
matchbox: ignoring key shortcut <ctrl><alt>r=!rxvt

matchbox: keyboard does not appear to have a <alt> key.
matchbox: ignoring key shortcut <ctrl><alt>e=!!gpe-calender

matchbox: keyboard does not appear to have a <alt> key.
matchbox: ignoring key shortcut <alt>Tab=next

matchbox: keyboard does not appear to have a <alt> key.
matchbox: ignoring key shortcut <alt><shift>Tab=prev

matchbox: keyboard does not appear to have a <alt> key.
matchbox: ignoring key shortcut <alt>space=taskmenu

matchbox: keyboard does not appear to have a <alt> key.
matchbox: ignoring key shortcut <alt>escape=!matchbox-remote -mbmenu

matchbox: keyboard does not appear to have a <alt> key.
matchbox: ignoring key shortcut <alt>f4=close

matchbox: Cant find a keycode for keysym 65480
matchbox: ignoring key shortcut f11=fullscreen

Failed to get root pixmap id
matchbox-desktop: loading /usr/lib/matchbox/desktop/tasks.so with args ( None )
matchbox-desktop: loading /usr/lib/matchbox/desktop/dotdesktop.so with args ( None )
user_overides is (nil)
mb-desktop-dotdesktop: failed to open /usr/local/share/applications
mb-desktop-dotdesktop: failed to open //.applications
mb-applet-menu-launcher: bonobo-browser.desktop has no icon, png or name
mb-applet-menu-launcher: failed to open /usr/local/share/applications
mb-applet-menu-launcher: failed to open //.applications
mb-applet-menu-launcher: bonobo-browser.desktop has no icon, png or name
mb-applet-menu-launcher: failed to open /usr/local/share/applications
mb-applet-menu-launcher: failed to open //.applications

arm-none-linux-gnueabi-gcc (4.4.4_09.06.2010) 4.4.4
root filesystem built on Thu, 29 Sep 2011 15:54:39 +0800
Freescale Semiconductor, Inc.

freescale login: root
login[2285]: root login on 'ttymxc0'

BusyBox v1.18.5 () built-in shell (ash)
Enter 'help' for a list of built-in commands.

root@freescale ~$ cd /
root@freescale /$ ls -l
drwxr-xr-x 2 root root 4096 Sep 29 2011 bin
drwxr-xr-x 9 root root 13100 Jan 1 00:00 dev
drwxr-xr-x 9 root root 4096 Jan 1 00:00 etc
drwxr-xr-x 3 root root 4096 Sep 29 2011 home
drwxr-xr-x 5 root root 4096 Sep 29 2011 lib
drwx------ 2 root root 16384 Sep 29 2011 lost+found
drwxr-xr-x 7 root root 4096 Sep 29 2011 mnt
drwxr-xr-x 2 root root 4096 Sep 29 2011 opt
dr-xr-xr-x 60 root root 0 Jan 1 00:00 proc
drwxr-xr-x 2 root root 4096 Jan 1 00:02 root
drwxr-xr-x 2 root root 4096 Sep 29 2011 sbin
drwxr-xr-x 12 root root 0 Jan 1 00:00 sys
drwxrwxrwt 4 root root 4096 Jan 1 00:00 tmp
drwxr-xr-x 2 root root 4096 Sep 29 2011 unit_tests
drwxr-xr-x 12 root root 4096 Sep 29 2011 usr
drwxr-xr-x 11 root root 4096 Sep 29 2011 var

Please let me know what to do. As I want to use touch screen and view the TOUCH Screen Calibration.

Vinay Kumar

vinay@ammostech.com