From: McPherson, C. A <Cha...@st...> - 2012-05-03 20:20:55
|
Hi everyone, Just today I started having a problem with my Overo Fire, Palo35 and LCD touchscreen. First let me make a point that up until today, everything has been working just fine with this system. However, starting this afternoon, the kernel is having trouble finding the touchscreen as /dev/input/touchscreen0 is non-existent, and consequently none of our UI software is working. Another interesting fact is that both the blue and red LEDs are staying on. I've tried fiddling with the touchscreen connection, and I've tried switching the screen with another one entirely. Nothing works. I get these messages when the OS starts up: 320x240x16bpp linelen 640 type 0 visual 2 colors 65536 pixtype 5 createfont: (height == 0) found builtin font System (0) Error opening touchscreen device [(null)]: No such file or directory Cannot initialise mouse and just in case it matters, I am booting off of an SD card, and my u-boot environment variables are as follows: bootcmd=if mmc init; then if run loadbootscript; then run bootscript; else if run loaduimage; then run mmcboot; else run nandboot; fi; fi; else run nandboot; fi bootdelay=5 baudrate=115200 loadaddr=0x82000000 console=ttyS2,115200n8 mpurate=500 vram=12M dvimode=1024x768MR-16@60 mmcroot=/dev/mmcblk0p2 rw mmcrootfstype=ext3 rootwait nandroot=/dev/mtdblock4 rw nandrootfstype=jffs2 mmcargs=setenv bootargs console=${console} mpurate=${mpurate} vram=${vram} omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${defaultdisplay} root=${mmcroot} rootfstype=${mmcrootfstype} nandargs=setenv bootargs console=${console} mpurate=${mpurate} vram=${vram} omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${defaultdisplay} root=${nandroot} rootfstype=${nandrootfstype} loadbootscript=fatload mmc 0 ${loadaddr} boot.scr bootscript=echo Running bootscript from mmc ...; source ${loadaddr} loaduimage=fatload mmc 0 ${loadaddr} uImage mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr} nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} 280000 400000; bootm ${loadaddr} dieid#=34240004000000000403a3810201100b defaultdisplay=lcd35 stdin=serial stdout=serial stderr=serial Environment size: 1211/131068 bytes Does anyone know what the problem could be? -Charles McPherson |