I would like to use it with my Due, unfortunately the Due modifications I have run across only work with the 16bit models. Could anyone give me some pointers for getting it running in 8 bit mode?
Dimdim:
This should work just fine, it's just that the level converters will be redundant since the Due's logic is already 3.3V. It should be OK though.
Oh, I'm not worried about the board's electrical compatibility, its just that the current Due modifications to the UTFT Library only work with the 16 bit models of LCD. I am curious what I would need to modify in the library to get my 8 Bit LCD running properly.
I'm sorry, there seems to be a mixup.. I was replying to a post that now appears to be gone (it was regarding a shield that simplified wiring a TFT to a MEGA).
Dimdim:
I'm sorry, there seems to be a mixup.. I was replying to a post that now appears to be gone (it was regarding a shield that simplified wiring a TFT to a MEGA).
Dimdim:
I'm sorry, there seems to be a mixup.. I was replying to a post that now appears to be gone (it was regarding a shield that simplified wiring a TFT to a MEGA).
Yes that was me, my post and I killed the post in hurry klicked the wrong button.
Dimdim:
I wired it up according to UTFT's documentation, adapting it to the specific TFT. It was not difficult. I should point out that it is an ITDB32WD compatible display that I got off of ebay, and not an ITead original.
The display works natively with 3.3V logic (I had to use resistors to use it with the older Arduinos) so it is actually easier to interface to the Due than to older Arduinos.
Did someone has an benchmark from the lib between oldone on mega how fast is it?
I try to convert the UFT Clock from Henning Karlsen to work with the Due Electronics - Henning Karlsen. But my Calender is blinking the clock is working proper.
Markus_L811:
Did someone has an benchmark from the lib between oldone on mega how fast is it?
I don't use the UTFT library, but I have a sainsmart TFT shield with a mega using an SSD1289. I'm interested to see how it compares to the Due implementation.
An easy, but important test is clearing the screen. To be able to present games flicker free, the clear operation needs to be one of the fastest.
I have achieved a rate of 51fps for a clear screen operation on a mega 2560, this is in a loop clearing to a random colour.
It will be interesting to see how well the Due performs in this basic operation.
pYro_65:
I don't use the UTFT library, but I have a sainsmart TFT shield with a mega using an SSD1289.
I have achieved a rate of 51fps for a clear screen operation on a mega 2560, this is in a loop clearing to a random colour.
then what Library are you using? I also have a Mega and a TFT display, but it takes about a second to clear the screen! I would love to have it run faster!
also, I hope this gets noticed by the creator of the UTFT library, who wants to port it to the Due but can't because he doesn't yet own one. I guess this would make porting a whole lot easier.
jake1981:
Yeah, the library should be cleaned up.. It's a bit messy.. But this is a great starting point for everyone needing a display for due..
Here's one more thing, when using samples (or doing your own) - you need to change bitmap definitions a bit to make it work.. For example, tux.c in UTFT_Rotate_Bitmap example:
it should start like this..
comment out #include <avr/pgmspace.h>
and change variable definition to:
const unsigned int varname = {
[/quote]
Seems not working for me only geht an white screen
jake1981:
Yes, but you need to get itdb02_32s display and mega shield for it from iteadstudio.com, these sources are compatible with that display and propably only with that display, other than 16bit modes are removed and this library only supports arduino due as I replaced and removed code, instead of just making it compatible with due along others. But here's a library, examples work "as is" with mega pins chosen on utft init..
thatdude624:
then what Library are you using? I also have a Mega and a TFT display, but it takes about a second to clear the screen! I would love to have it run faster!
I'm having a go at building my own driver, the mainstream libraries are too slow for games and interactivity. They all suffer a similar overhead with respect to being portable between uC's and compatible with multiple devices. Whereas I've targeted my code directly to the 2560 and the display. I'll post the code on the forums eventually.
I'm having a go at building my own driver, the mainstream libraries are too slow for games and interactivity. They all suffer a similar overhead with respect to being portable between uC's and compatible with multiple devices. Whereas I've targeted my code directly to the 2560 and the display. I'll post the code on the forums eventually.
Very interesting a faster code ... Do you can post it Here???
I'm having a go at building my own driver, the mainstream libraries are too slow for games and interactivity. They all suffer a similar overhead with respect to being portable between uC's and compatible with multiple devices. Whereas I've targeted my code directly to the 2560 and the display. I'll post the code on the forums eventually.
Very interesting a faster code ... Do you can post it Here???
I'll also post any info on the library there. Remember my info was for a Mega 2560, not the Due. Although I guess its a good reference to see what we can expect at a minimum from the Due.