FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  

News:

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.

Messages - FTDI Community

Pages: 1 ... 52 53 [54] 55 56 ... 60
796
General Discussion / Re: FT4332H - EEPROM
« on: June 27, 2018, 02:54:06 PM »
Hi,

Yes, you require an EEPROM to communicate in RS485 mode because, as you have discovered, adding an external EEPROM allows selecting the TXDEN for RS485 mode.

When used without an external EEPROM the FT4232H defaults to a quad USB to an asynchronous serial port device. If no EEPROM is connected (or the EEPROM is blank), the FT4232H will default to serial ports.

Adding an external EEPROM allows customization of USB VID, PID, Serial Number, Product Description Strings and Power Descriptor value of the FT4232H. Other parameters controlled by the EEPROM include Remote Wake Up, Soft Pull Down on Power-Off and I/O pin drive strength. Note that the EEPROM contents have no effect on the selected mode with the exception of selecting the TXDEN for RS485 mode when asynchronous serial interface has been selected in software.

I hope this helps.

Regards,
FTDI Community

797
Discussion - Software / Re: FT81x and available free GRAM
« on: June 27, 2018, 02:46:09 PM »
Hello,

EVE Screen Designer:
http://www.ftdichip.com/Support/Utilities.htm#ESD4

and

EVE Screen Editor:
http://www.ftdichip.com/Support/Utilities.htm#EVEScreenEditor

Will give you indications on how much RAM_DL and RAM_G is being used, this may be useful when trying to ascertain available RAM from a given screen.

Best Regards,
FTDI Community

798
Discussion - Hardware / Re: FT60X FIFO buffer size. What does double buffered mean?
« on: June 25, 2018, 03:18:42 PM »
Hi,

The FIFO buffer for the FT60x is 16kbytes in total for all channels.

The term double buffer means a buffer for for each direction.

For example, in a single IN configuration, the IC will allocate 8K + 8K (double buffer).
For 1 channel IN + OUT configuration, the IC will allocate 4K + 4K (double buffer).

Please have a look at table 2.2.2 in AN_386 http://www.ftdichip.com/Support/Documents/AppNotes/AN_386%20FTDI%20FT600%20Maximize%20Performance.pdf for details of the FIFO modes and FIFO sizes of FT245 and FT600 modes.

I hope this helps.

Regards,
FTDI Community

799
Discussion - Software / Re: FT900 RTC Interrupt - Help needed
« on: June 25, 2018, 01:41:49 PM »
Hello,

We provide some example code in AN_360 FT9xx Example Applications.
See RTC Example 2 which demonstrates RTC interrupt every 2 seconds. This example should be useful to you.

These examples are provided with the free FT9xx Toolchain which is different from the MikroE tools.

Note that the RTC functionality between FT90x and FT93x is different and this is commented in the source code since the toolchain supports both MCU variants.
The RTC in FT90x is a simple counter. It provides information as a basic “system on” timer. The RTC in FT930 provides more detailed information and is powered by an external battery source.

Best Regards,
FTDI Community

800
Discussion - Software / Re: A bug for PWM_HZ command?
« on: June 25, 2018, 11:14:40 AM »
Hello,

The REG_PWM_HZ register is to correct register to write to alter the frequency of the backlight.

Can you show me how you are writing the register within your code?

Best Regards,
FTDI Community

801
Discussion - Software / Re: Eclipse Build of Example HellWorld failed
« on: June 25, 2018, 11:01:59 AM »
Hello,

I would assume your export failed due to not having the correct resources copied into the FT9xx toolchains workspace. It is possible to export ESD projects and edit them within eclipse, however this is not the intended workflow.

ESD includes a lot of framework code to implement functionality, and as such the code output is very ESD specific. The tool is intended for use by those who have very little to no programming experience. I would suggest that it would be far more productive for you to look at the previously linked Sample Applications and programmers guide. Thus being able to eliminate the ESD code from the equation and work directly with the Display List code to drive the FT813.

Please take some time to look at the following examples in either Visual Studio or the FT9xx Toolchain:
http://www.ftdichip.com/Support/SoftwareExamples/FT800_Projects.htm

Again ESD is intended for quick prototyping or for those with little programming experience, you can absolutely use EVE without ESD. You would not be able to use the ESD widgets without importing them, but i would suggest creating your own would be more beneficial.

Best Regards,
FTDI Community

802
Discussion - Software / Re: EVE Screen Designer - Screen orientation from landscape to portrait
« on: June 25, 2018, 10:45:36 AM »
Hello,

I noticed you posed the same question in a separate topic:
http://www.ftdicommunity.com/index.php?topic=113.msg

Best Regards,
FTDI Commuity

803
Discussion - Software / Re: EVE - How to draw an Arc with a line thicknesa
« on: June 25, 2018, 10:34:57 AM »
Hello,

Please see section 2.5.4 of the programmers guide:
http://brtchip.com/wp-content/uploads/Support/Documentation/Programming_Guides/ICs/EVE/FT81X_Series_Programmer_Guide.pdf
You can use the VERTEX2F or VERTEX2II commands to draw graphics primitives including lines/arcs.

I notice you have had a lot of queries recently, it may be more productive for you to direct these to support1@ftdichip.com.

Best Regards,
FTDI Community

804
Discussion - Software / Re: FT900 RTC Interrupt - Help needed
« on: June 25, 2018, 09:23:14 AM »
Hello,

Since you are using the MikroC compiler from Mikro Electronica you will need to contact them for support.

Best Regards,
FTDI Community

805
Discussion - Software / Re: EVE Screen Designer - Adding a them for example Ft_Esd_Theme_LightGreen
« on: June 21, 2018, 03:18:02 PM »
Hello,

Please refer to the Themes section of the ESD 4.0 User Guide:
http://brtchip.com/wp-content/uploads/Support/Documentation/Programming_Guides/Modules/EVE/BRT_AN_021_EVE-Screen-Designer-4.0-User-Guide.pdf

Best Regards,
FTDI Community

806
Discussion - Software / Re: Eclipse Build of Example HellWorld failed
« on: June 21, 2018, 03:15:41 PM »
Hello,

Yes, we have a programmers guide available for the FT80x or FT81x series of ICs, below is the link for the FT81x series programmer guide:
http://brtchip.com/wp-content/uploads/Support/Documentation/Programming_Guides/ICs/EVE/FT81X_Series_Programmer_Guide.pdf

Sample applications can be found at the following like, these detail a variety of what is possible with the EVE platform.
http://www.ftdichip.com/Support/SoftwareExamples/FT800_Projects.htm

You will also find the EVE platform guide useful:
http://brtchip.com/wp-content/uploads/Support/Documentation/Application_Notes/ICs/EVE/AN_391-EVE-Platform-Guide.pdf

Best Regards,
FTDI Community

807
Discussion - Software / Re: EVE Screen Designer - Screen orientation from landscape to portrait
« on: June 21, 2018, 01:30:59 PM »
Hello,

If you take a look at the 'Simple Button' example included in ESD, this shows you how to alter a variable of a widget based upon a button press. This should be a good basis for what your are trying to do.

Best Regards,
FTDI Community

808
Discussion - Software / Re: ME813A-WH50C Display - Skipping touch screen calibration at startup
« on: June 14, 2018, 02:58:38 PM »
Hello,

It is not a bug, the calibration values just need to be set.
The calibration routine writes values into the REG_TOUCH_TRANSFORM_A - REG_TOUCH_TRANSFORM_F registers. you could run the calibration routine and once this has completed read the values in the applicable registers. You can use these values you write the REG_TOUCH_TRANSFORM_A - REG_TOUCH_TRANSFORM_F registers at the start of your program and your screen should be roughly calibrated. If it requires fine tuning after you can then call the calibration routine from your menu option.

Best Regards,
FTDI Community

809
Discussion - Software / Re: EVE Screen Designer - Screen orientation from landscape to portrait
« on: June 14, 2018, 02:18:38 PM »
Hello,

You can certainly still use ESD while working on a portrait project. You will just need to be aware of how rotating the screen will alter widget placement, etc.

It may be easier to work with raw code when utilising the ME813A-WH50C in portrait mode.

Best Regards,
FTDI Community

810
Discussion - Software / Re: ME813A-WH50C Display - Skipping touch screen calibration at startup
« on: June 14, 2018, 11:54:38 AM »
Hello,

Thanks for your question.

Screen calibration is achieved with the CMD_CALIBRATE() function. Please see section 5.52 of the FT81x programmers guide:
http://brtchip.com/wp-content/uploads/Support/Documentation/Programming_Guides/ICs/EVE/FT81X_Series_Programmer_Guide.pdf

Normally this function is call during the main initialization loop of a EVE program.

From the 'SampleLayout' project in EVE Screen Designer (as you have previously mentioned that you are using ESD in another forum topic), within the 'Ft_Esd_App.c' file. The 'Ft_Gpu_CoCmd_Calibrate()' function sends the CMD_CALIBRATE command to the FIFO:
Code: [Select]
/* API to demonstrate calibrate widget/functionality */
ft_void_t App_CoPro_Widget_Calibrate()
{
ft_uint32_t NumBytesGen = 0, TransMatrix[6];
ft_uint16_t CurrWriteOffset = 0;
Ft_Gpu_CoCmd_Dlstart(&s_Host);
Ft_Gpu_Hal_WrCmd32(&s_Host, CLEAR_COLOR_RGB(64, 64, 64));
Ft_Gpu_Hal_WrCmd32(&s_Host, CLEAR(1, 1, 1));
Ft_Gpu_Hal_WrCmd32(&s_Host, COLOR_RGB(0xff, 0xff, 0xff));
/* Draw number at 0,0 location */
//Ft_App_WrCoCmd_Buffer(&s_Host, COLOR_A(30));
Ft_Gpu_CoCmd_Text(&s_Host, (FT_DispWidth / 2), (FT_DispHeight / 2), 27, OPT_CENTER, "Please Tap on the dot");
#if defined(FT_801_ENABLE) || defined(FT_811_ENABLE) || defined(FT_813_ENABLE)
Ft_Gpu_Hal_Wr8(&s_Host, REG_CTOUCH_EXTENDED, CTOUCH_MODE_COMPATIBILITY);
#endif
Ft_Gpu_CoCmd_Calibrate(&s_Host, 0);
/* Wait till coprocessor completes the operation */
Ft_Gpu_Hal_WaitCmdfifo_empty(&s_Host);
/* Print the configured values */
Ft_Gpu_Hal_RdMem(&s_Host, REG_TOUCH_TRANSFORM_A, (ft_uint8_t *)TransMatrix, 4 * 6); //read all the 6 coefficients
#ifdef MSVC_PLATFORM
ESD_print("Touch screen transform values are A 0x%x,B 0x%x,C 0x%x,D 0x%x,E 0x%x, F 0x%x",
TransMatrix[0], TransMatrix[1], TransMatrix[2], TransMatrix[3], TransMatrix[4], TransMatrix[5]);
#endif
}

If you export the ESD code to the FT9XX tool chain you can make the appropriate edits and recompile to upload to you FT9XX.

Best Regards,
FTDI Community

Pages: 1 ... 52 53 [54] 55 56 ... 60