hi all and FrankL.
I'm working with H8sx1668 interfacing TFT directly, The project phase was in Coding. The PCB was done with 4layer. The matter is since its very short time for us, i requested renesas to give me a basic working set of code without using RTOS, but they don't.
If anyone working with the Drect TFT driving. Simply i need a suggestion of either its possible to interface the TFT, SDRAM, Parallel flash or not.
It's possible, why not? But I think SRAM would be a better choice than SDRAM.
I guess you are using 1668R and your TFT-resolution is 320 x 240?
If you've got problems to meet reliable DMA-timing you could lower standard DCLK frequency (~6MHz) to 4-5 MHz without visible flicker.
Thanks for u r response...
Actually the PCB was finalised with SDRAM. And i'm using 10.4" (640x480) SIZE TFT. i'm strugling with all the sample codes downloaded from the renasas site. but no use at all. The parallel flash can able to write using E10A, and the SDRAM can also working fine. But i can't drive TFT. Once I connected the LCD Connector (31-pin) the backlight becomes dull. There is not a single pixle enabled in the panel. ( the CLK signal was fine upto the 2nd pin of the LCD, The HSYNC and VSYNC signals are also fine). Is there any basic level of coding simply to fill the screen?,. That much is enough for me... Please do a help..
I'm sorry, but I don't know your
software, your hardware or what any pin of
your LCD-connector is doing.
I think you can interface to the LCD by using a non-os approach - but you won't have a wealth of information to draw on. The standard Renesas Demo's are all built around the FreeRTOS code. I had never worked with an OS before digging into the Direct Drive GAPI demo to polish up some existing labs. Turns out the OS really doesn't get in the way and was largely invisible to me (I basically just wrote embedded C as normal). I just had to pay attention to setting up my functions intitially. There is a 1668 demo board that you might want to see if you can get your hands on (contact your local Renesas FAE). If you can get a board - and look at the existing Demo - chances are you will have a much better time getting your board doing what you want.
As it was explained to me - as long as you have your pixel clock running - and have the Vsync / Hsync doing the correct thing - and have your enable line going the right direction - you will get pixels out on the screen... maybe in the wrong spots and not stable - but yoiu will get something. That is IF you are shifting out data on your I/O.
So look at your rough timing on the dot clock and vsync/hsync & make sure your enable is going the correct direction. Make sure your backlight is working. The most painful part is getting a stable hello world on screen. After that it gets fun. Make sure and check for opens or bridges in your connector as well. If you can get hold of the 1668 demo board - you can sit with a scope and check all timings of the Demo - then double check them on your board.
Note that if you "go it alone" and bypass the GAPI / RTOS that you will be faced with re-writing 6-12 months worth of code. That is some nasty stuff to tackle if you don't have too.
I would start by going to the www.america.renesas.com/h8lcd page then click on the 2378 kit owner button on the upper right corner - and looking at what is up there for the 2378. (the 1668 version is a work in progress). Note that the demo code can be customized to run on the 1668 pretty easily... I have been playing with the 1668 for several months. The Demo code that comes with the 1668 demo board can be easily set up to run from the SDRAM (I think it is actually configured this way).
The 1668 demo board from Renesas is configured to boot up - then copy contents of the Serial Flash that is on the board to SDRAM (this contains all the Graphics images).
Note you might want to look below the obolete 2378 annotated schematics at the link thta says Annotated Schematics for the H8SX/1668... they might point you in the right direction. Be sure and read over all the notes on the .pdf. You might find a smoking gun in hardware. I have tried to attach the annotated schematic to this post.
By the way - the first pixel lighting took me almost a week on my last project (that is at least 50 hours worth of work). Debugging the hardware on an LCD project can be VERY frustrating... no matter what the hardware / software environment.
Thanks for sharing your experience blake....
Me too have our H8sx1668 board( only controller board) given by Renesas. But we ourself finished the PCB for the schematic (ROKH8Sx1668 from renesas). First i have to confirm that our hardware is working well, so i tried with "Directlcd_Demo" from renesas site. But when i changed the header file from Kyocera_QV.h to Kyocera_VG.h the error occurs " cannot achive DESIRED_FRAME_RATE" where i kept the frame rate as 60. I think the demo codes are work with the 320x240 lcd only. Have u achieved 640x480 lcd interface?
I can't atach my schematic here, but its the site in follwing link http://america.renesas.com/redirect.do?action=redirect&sessionId=5XFPAX7N0F9C9L7&downloadId=D1015548&user=ssureshtronics&status=EXPIRED
VGA panels should use 30 FPS.
Calvin is right - you have to do a math model on the speed of the dot clock and the amount of time it takes to shift out 640 x 480 pixels. I think 60 FPS is unreachable. Just to get something on the screen to make sure you are on the right path - I would take it to 15 or 20 FPS just to make sure you are getting out data - then crank up the FPS until you run out of bandwidth.
The AE lab has reached 640 x 480 on a former project (I'm almost certain) so it is possible with the 1668.
Thanks blake and calvin..
Let me try out with less than 30 FPS. And share u later..
hi blake..
I tried by varying the FPS but no use, our renesas support team also struggling to suggest us. Have u working on 640x480 TFT driving with H8sx1668?, if yes please share me the schematic that you are using , i just want to compare with that. Shall i get the below details from you?.
What is the DOT clock rate you acheived.( for 640x480 VGA panels min. dot clock was 22MHz)
Are u using SDRAM or SRAM for frame buffer, if u r using SDRAM, then which mode u r transfering(cluster mode?)
You are using EDACK or BS for dot clock generation..
Please help me know the answers for above queries. Try to share woth me the Schematic... just want to confirm that even Renesas was done with VGA tft or not.![]()
Yes, the 1668R will run a VGA TFT display. We usually use the Cluster mode (see the Design Guide) to get the clocking fast enough for the big displays.
Thanks ckgrier,
Have you got the display output?... if yes please share me your idea... I tried on cluster mode, but the LCD dot clock was 8 MHz. shall i know the panel details that u r using..
Hope u'll share...
The approach used for VGA is described in detail here:
There's a HEW project and app note that can generate the correct configuration for you. You should not see low values like 8Mhz on the pixel clock.
This has been shown to work on a Kyocera panel, but it will work on any of them.
Are you using 1668 or 1668R?
Thanks ckgrier
I'm using H8sx1668R, There are many app notes and design guide datas but practically i tried even in the cluster mode also. All the app notes were given for 320x240 panels. The HSYNC, VSYNC, BACK PORCH and FRONT PORCH values given in the code were not matching with the spec sheet values. I need something technical details will you please?.. have you got the output sure....
here's setup files for a WVGA panel from Kyocera (800x480). I've seen pictures from a customer showing it in operation.
The CNF files goes in your "\Platform\H8SX1668_RTA_SDRAM_CLUSTER" directory. The CNF(Kyocera_WV) file goes in "\Commonsource\Drivers" directory.
Make sure you select the build configuration from the drop-down menu for Cluster mode. It may be hard to see if the build configuration name gets cut off, but the drop-down order should match the order in the "Build Configurations" setup menu.
You should note that on some panels the timing we use isn't exactly what the panel data sheet says.
Thanks ckgrier
yes i tried with the "DirectLCD_CNF(Kyocera_VG).h" , The build configuratoin is alsoSDRAM_CLUSTER_MODE. Now i'm geting 32 MHz od LCD DOT Clock, the panel still shows blank. The backlight was ok. I think the output will get soon.
©2003–2010 Renesas Technology Corp. All rights reserved. Using Our Website | Privacy
Contact us