Hello,
some weeks ago we bought a F&S armStoneA9 starter kit with graphics lcd (looks like ET070080 , 800x480 18bit color).
The last weeks I brought up the build system on an Ubuntu 13.10 with crosstool-ng and glibc 2.16 instead of the prebuild binaries from f+s for fedora. After some problems it works now so that i can load the own compiled kernel and rootfs via tftp/nfs.
But what i can't get to work (neither with the original nand SW nor the self compiled SW) is the LCD and the touchscreen.
After/during boot sequence four penguins with f+s logo are displayed in the left corner and that's it.
I tried e.g. adding something like mxcfb0:dev=lcd,LCD-ET070080,if=RGB666 on the kernel command line (found the infos in mxc_lcdif.c) but it didn't work obviously.
The only mysterious thing I see in dmesg is:
atmel_mxt_ts 2-004a: __mxt_read_reg: i2c transfer failed (-5)
atmel_mxt_ts: probe of 2-004a failed with error -5
It seems that the touchscreen controller isn't found/probed? Is that maybe a problem?
Moreover I see differences between the manual and reality:
Manual says :
Configure input for: default-event0 sx8655 Touchscreen
When starting Linux for the first time you need to calibrate your touch with:
mount -o remount,rw /
ts_calibrate
after that you can test with:
ts_test
To use the touch with Xserver you need to reboot after the calibration or restart with:
/etc/init.d/S35x11 stop
/etc/init.d/S35x11 start
The SW in the delivered device (which is V1.2) is already mounted rw. So the missing/nonworking shutdown always forces a ubifs recovery. Moreover no output for default-event0 or touchscreen is seen.
The script S35x11 also doesn't exist, neither in the nand SW nor in the buildroot sources for V1.2 under board/f+s/common as you can see in the build output:
>>> Executing post-build script /opt/f+s/buildroot-f+s/board/f+s/QBlissA9/final_script_std
>>> Doing final F+S QBlissA9 setup for standard configuration
>>> Doing final F+S (common) setup for standard configuration
/bin/cp: der Aufruf von stat für »board/f+s/common/inittab“ ist nicht möglich: Datei oder Verzeichnis nicht gefunden
/bin/cp: der Aufruf von stat für »board/f+s/common/mdev.conf“ ist nicht möglich: Datei oder Verzeichnis nicht gefunden
/bin/cp: der Aufruf von stat für »board/f+s/common/S35x11“ ist nicht möglich: Datei oder Verzeichnis nicht gefunden
The framebuffer examples mentioned in first steps manual '8.8 DirectFB' also doesn't exist in the delivered SW.
I had to enable them in buildroot config to try them. The output is always on the HDMI video output.
So what should be the default behavior when the LCD is connected and if it should turn on automatically what is wrong here?