About the I2C-clock-stretching-bug: I've analyzed it in detail, documented it and looked for workarounds.
See:

• http://www.raspberrypi.org/phpBB3/viewt ... 1&p=405024
• http://www.advamation.com/knowhow/raspb ... c-bug.html

I've analyzed the I2C clock-stretching-problem in more detail and tried to document it. See http://www.advamation.com/knowhow/raspberrypi/rpi-i2c-bug.html From what I've seen, what Gert said is unfortunately only partly correct: Clock-stretching only works directly after I2C-Read-acknowledge-phases ...

have you managed to measure the fps with your CPLD and this screen? Yes: It currently runs here (without any optimizations) with my own framebuffer-driver with up to 16 fps. In an optimized test I've already reached the theoretical maximum of nearly 50 fps. :D But I have not measured the framerate ...

P3T3 wrote:Which circuit are you using for parallel inreface? First one with 7404 or second one without 7404?

I used something like the 16-bit bus version shown on https://github.com/notro/fbtft/wiki/SPI ... ce-circuit, implemented in a CPLD.

That's a new "wrong" behaviour for me :-) It's working now. I guess that the problem was a timing issue. [1] Thanks again! ([1] The "wrong" behaviour was, that the display only recognized every 2nd pixel-data (probably because of a problematic WR/CS-timing), and this lead to the screenshot I posted...

sudo modprobe fbtft_device name=sainsmart32spifb #show default gpios dmesg sudo modprobe sainsmart32fb FRAMEBUFFER=/dev/fb1 startx Thanks! After correcting a small bug (I missed the 74HC04 in your diagram) in my CPLD and using the above commands, the 3.2" TFT displays an image. :D Unfortunately, so...

Do you think the RPI is ready to be installed into a final product to be launched for sale immediately? Yes. But you should have some computer skills, know Linux quite well etc., so you can analyze and solve the problems, which may occur, by yourself. And I'm currently developing some professional ...

Hi, I'm currently trying to test fbtft with a SainSmart 3.2" TFT; it's not yet working, but maybe there's a bug in my electronics (since I use a CPLD instead of the shift-registers and the counter, which is the better/faster/more flexible way in my opinion [1]). But: Should it work with the sainsmar...