LCD8000-70T-EX1 touch won't work

Do you have UART8000-U Cable for the touchscreen part?

I used this uart cable to configure via u-boot: Raspberry Pi USB-Kabel Raspberry Pi im Conrad Online Shop | 409202

I configured according to this file: http://www.farnell.com/datasheets/1854297.pdf - see page 7 step "4" and page 9 step "1" and "2".

Just in case a calibration was done before, can you do these"

• root@RIoTboard_6solo:/ # rm /data/system/calibration
• root@RIoTboard_6solo:/ # sync

The default android build doesn't have touch support and a few other things. You need to flash the board with a newer build.  I will post the links to the mfg tools, the build, and the tutorial shortly.

Thank you so much! I actually thought about giving the 4.4 a try to see if it works with that one. I wish that vital information were included in some of the docs. I read through a lot of pdfs lately but never came across that.

BTW Is there a possibility to enter u-boot via the mini-usb cable instead of the uart? Because the uart driver causes my PC to crash everytime I open Putty and boot the Riotboard. Right now I have to take my board with me to uni because the PCs there don't crash but it's quite bothersome xD

And I'm looking forward to the tutorials

okay so to get the latest for the riotboard go directly to

•     RIoTboard Development Platform (http://www.embest-tech.com/shop/star/riotboard.html)

you will want to download

• RIoTboard Android Image SVN2705

Then you need the mfg tools to actually update the image

• RIoTboard Android Image Programming tools 

1. Create a new folder somewhere you will remember (on a windows machine)
2. Extract the image and the programming tools into that folder
3. Copy image\u-boot-mx6solo-RIoTboard.bin into Mfgtools-Rel-4.1.0_130816_MX6DL_UPDATER\Profiles\MX6DL Linux Update\OS Firmware\files\android
4. From image\eMMC, copy boot.img, recovery.img and system.img and place them into same folder as above (riot_update\tools\Mfgtools-Rel-4.1.0_130816_MX6DL_UPDATER\Profiles\MX6DL Linux Update\OS Firmware\files\android) replacing the existing files in that folder
5. Power off the board and set the switches from the original settings to this Serial Download Settings (1-off, 2-on, 3-on, 4-on, 5-off, 6-on, 7-on, 8-on)
   
   
6. Plug-in the USB cable to J11 (Mini-USB port near Ethernet plug on the board).
7. Power the board with the 5V power supply. (The board should now be recognized as and drivers getting installed). Once the board is recongnized as usb hid, you can continue.
8. Now start the MFG tool (tools\Mfgtools-Rel-4.1.0_130816_MX6DL_UPDATER\MfgTool2.exe) as an administrator. (If you get error 21 you need to make sure Mfgtools-Rel-4.1.0_130816_MX6DL_UPDATER\Profiles\MX6DL Linux Update\OS Firmware\ucl2.txt is renamed into ucl2.xml)
9. Press the “Start” to begin downloading the new image. Don't do anything until the mfgtool says done. (If Windows ask you to format the new drive in a dialog, DON’T DO THIS!)
10. Press ‘Stop’ and then ‘Exit’ to finish and close the dialog.
11. Unpower the board.
12. Restore the previous jumper settings again: (1-on, 2-off, 3-on, 4-on, 5-off, 6-on, 7-on, 8-on)
    

now this gives you a completely fresh install so we can to go into uboot and tell it to use the gpio for the screen and not the hdmi. you mentioned your ftdi crashes your machine. newer operating systems use a built in ftdi driver that causes a few issues.

1. Download FTDI drivers for you machine https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers/introduction
2. Download a telnet application (I use putty PuTTY Download Page)
3. Connect your ftdi cable to your computer and wait for it to enumerate a com port. On windows pay attention to what port it assigns.
4. Open putty (or how you use ttl), select serial, and type in your com port (ie COM4) and for the speed put in 115200
   OS X open your terminal, type ls /dev/cu.* that should give you a list of tty devices. Then type screen /dev/cu.usbserial 115200 (cu.usbserial should be your ttl device, 115200 is the baud rate)
5. Connect your TTL device to the riotboard, the pin with the arrow is RX, the middle pin is TX and the last pin is ground
   
6. Power up your board and press enter when the message to hit any key to stop autoboot pops up
7. now we want to set the boot variables with the setenv command
   

   setenv bootargsconsole=ttymxc1,115200 init=/init nosmp video=mxcfb0:dev=lcd,7inch_LCD,if=RGB565 video=mxcfb1:off fbmem=10M vmalloc=400M androidboot.console=ttymxc1 androidboot.hardware=freescale calibration
   saveenv
   reset
8. When the riotboard boots now you should get the calibration pop up (crosshairs) before it finishes booting

Let me know if you have any trouble or if everything works for you.

Thanks for that indepth how-to. Unfortunately it doesn't work. I did everything according to your instructions. When using the mfg tool windows asked me if I wanted to format the drive, like you said I pressed "cancel" and waited for the mfg tool to finish, then pressed stop and afterwards exit.

I tried ftdi driver but it doesn't work. I retried with the one recommended for my cable (by a user in the comments of the conrad link I posted earlier) and it works and then recognizes the USB to serial cable. However when I start putty with all the right settings and power the board on nothing happens. it should be booting and the hit any key thing should appear but nothing happens. On the upside my pc doesn't crash anymore, but yeah I can't configure anything xD

That's odd. Well as long as you can see the press any key part yhen the update part worked.

A few things on your ttl. Is it 3v3 or 5v ttl?

If you put a jumper between TX and RX and open putty, connect to your Com at 115200 and type something does it show what you type? If not there could be a issue with your ttl. If it does your fine.

Perhaps try space instead of enter? I just did the same thing but use a 3v3 ttl adapter I got from adafruit.Com.

Sounds like you are almost there we just need to figure out the ttl half, but your original post said you were able to do it before. You are doing the same thing now. does my instructions have something different from what you did the first time?

No sorry, that's a misunderstanding I don't even get to the "press enter" part. When I connect putty with the board and power the board on putty stays blank. This is what I get: Pasteboard — Uploaded Image

About the ttl, I'm not sure how to find that out. It has a fourth connector that has 5V. Unfortunately there's no real datasheet enclosed in the shop: USB RB-TTL cable for Raspberry Pi from Conrad.com

Your instructions regarding the putty connection are actually same as I did before. The only thing different now is the image on the riotboard flash memory. Could it be that the mfg tool is at fault?

EDIT:

Well I'll be damned, just for fun I tried to exchange the TX and RX connectors and it did boot right away...I'll see if it works now.

Oh no you have to send TX to RX in both cases . Think TX talks and RX listens and you get the correct picture.

Clem