FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  


Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support

New Bridgetek Community is now open

Please note that we have created the Bridgetek Community to discuss all Bridgetek products e.g. EVE, MCU.

Please follow this link and create a new user account to get started.

Bridgetek Community

Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.

Topics - Rudolph

Pages: [1]
Shared Projects / EVE code library
« on: May 19, 2020, 07:32:48 AM »
I have no idea why this forum is still up and why there is so much posted here.
I am more active over at:  http://www.brtcommunity.com/

That said, I have a code library for FT8xx/BT8xx that could answer a couple of questions that are posted here:

I have examples projects for Arduino, ATSAMC21 and ATSAME51.
My goal is to support all the EVE displays out there, at least these that I can actually get and that are documented.

And I went multi-plattform right from the start, I have support for a whole bunch of micros including AVR, ATSAM, STM32 and RISC-V.

Discussion - Software / Timing parameters for EVE modules?
« on: July 05, 2018, 12:56:21 PM »
With the discussions here around the ME813A-WH50C module I just thought it would be a nice touch to add timing parameters for a few of the newer modules to my library.

But there are no timing parameters to be found, not even the ones from the panel datasheets.

BRT_AN_018_FT90x_Camera_to_EVE\eve\EVE_config.h has these:

#define EVE_DISP_WIDTH 800 // Active width of LCD display
#define EVE_DISP_HEIGHT 480 // Active height of LCD display
#define EVE_DISP_HCYCLE 928 // Total number of clocks per line
#define EVE_DISP_HOFFSET 88 // Start of active line
#define EVE_DISP_HSYNC0 0 // Start of horizontal sync pulse
#define EVE_DISP_HSYNC1 48 // End of horizontal sync pulse
#define EVE_DISP_VCYCLE 525 // Total number of lines per screen
#define EVE_DISP_VOFFSET 32 // Start of active screen
#define EVE_DISP_VSYNC0 0 // Start of vertical sync pulse
#define EVE_DISP_VSYNC1 3 // End of vertical sync pulse
#define EVE_DISP_PCLK 2 // Pixel Clock
#define EVE_DISP_SWIZZLE 0 // Define RGB output pins
#define EVE_DISP_PCLKPOL 1 // Define active edge of PCLK
#endif // FT81X_WQVGA

But with no reference whatsoever for what module these parameters are supposed to be used.
Are these good for the three 5" modules with 800x480?

What parameters should be used with the ME810A-HV35R then?

Well, if FTDI/BRT would send me a sample ME813A-WH50C and ME810A-HV35R I would gladly tests these for use with my library and put these into my extensive collection of EVE modules. :-)

Discussion - Hardware / Updated Design Support?
« on: June 30, 2018, 06:25:09 PM »
What about updated hardware-support?
Specifically I would like to see updated Altium Designer Libraries for FT8xx series.
What Altium has on their website as official FTDI support package really is old.
It mentions FT8xx but it really only has FT80x footprints and the FT800 schematic symbol, maybe the FT801.

A "reference" design with a FT813/FT812 would be nice, maybe on of the released modules like the ME810A-HV35R.

Or one for the upcoming BT815/BT16.
Regarding the BT81x - the website http://brtchip.com/bt81x/ still says "Available June 2018" and still only has that draft datasheet from february and still links to that buggy "FT81x Series Programmers Guide" in version 1.1 from 2016-09-19.
But we are almost past June now.

New Member Introductions / Hello
« on: May 21, 2018, 02:34:11 PM »

my name is Rudolph Riedel, I am from Germany and I am playing with a whole bunch of different EVE FT8xx display for over 2 1/2 years now which resulted in a free driver on Github: https://github.com/RudolphRiedel/FT800-FT813

And while I know that technically Bridgetek took over the EVE activties they do not have a forum so far.
Plus their EMEA support has the same address as FTDI, only with a different mail-address.

Pages: [1]