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] 2 3 ... 16
1
Hello,

I’m not familiar with the product that you are using.  Since this is not one of our products, although it may utilise our device, It is difficult to offer any support on it as FTDI cannot control how the USB ICs are used and has no knowledge of the entire product.

Product Manufacturers are responsible for supporting end-users of their products, so you will need to contact the manufacturer directly.  Please see the following document for reference:
http://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_102_OEM_Technical_Support_Requirements_for_FTDI_Products.pdf.

With that said however, if they are using our default driver then you may want to try using our latest driver v2.12.28, which is available on our website here:

http://www.ftdichip.com/Drivers/D2XX.htm

You can download the setup executable by clicking on this link. Once installed you should be able to plug in your device and the driver will install. Have a look at our Installation guides here http://www.ftdichip.com/Support/Documents/InstallGuides.htm for further information.

I’m sorry I could not be of further assistance.

Regards,
FTDI Community

2
Hello,

The issue sounds most likely with LabVIEW.

Note Microsoft stopped all support for Windows XP from April 2014 however LibFT260 has been tested with XP.

We do have some basic LabVIEW examples, but they are very old. Unfortunately we don’t have access to LabVIEW so it’s no longer supported.

Are the results the same on Windows 7 or Windows 10?

Is the correct HID interface being opened?

This was tested on our test PC in the lab. The FT260 was successfully listed and opened using LibFT260:



Note: FT260 is configured as dual channel mode and are listed as interfaces 0 and 1. The successful line of code opens this interface number:

ftStatus = FT260_Open(0, &ft260Handle);

Other HID interfaces may exist on the PC such as mouse, keyboard, etc.

Can you take LabVIEW out of the question for testing purposes, and run the examples provided with LibFT260?

.\LibFT260-v1.1.1\samples

Best Regards,
FTDI Community

3
Hello,

Thank you for your post, I have passed this on to the development team to see if they wish to add any comments.

Best Regards,
FTDI Community

4
Discussion - Drivers / Re: Need FTDI (FT602) information
« on: May 07, 2019, 03:41:58 PM »
Hello,

Please can you contact email support on support1@ftdichip.com with a screenshot of your Configurator settings and we will investigate further.

Regards,
FTDI Community

5
Hello,

What exactly is happening on the screen when you add these two lines.

Also FYI, there is no inbuilt font '14' (in your CMD_BUTTON call), the RAM and ROM fonts can be found in the datasheet, these range from 16-34.

Best Regards,
FTDI Community

6
Hello,

Can you give me an example of what you change in the display list for the screen to not display?

Also unfortunately we do not have any examples which cover loading data from an SD for PIC MCUs, but one this has been achieved the same EVE procedure can be used to display the image as detailed in BRT_AN_014.

Best Regards,
FTDI Community.

7
Hello,

If you open your .png file in a hex editor, this will give you the required data which can be copied into your code.

Section 7.3 in the following covers this briefly:
https://brtchip.com/wp-content/uploads/Support/Documentation/Application_Notes/ICs/EVE/BRT_AN_014_FT81X_Simple_PIC_Library_Examples.pdf

Best Regards,
FTDI Community

8
Discussion - Drivers / Re: Unexpected behavior of timeout
« on: April 26, 2019, 03:29:50 PM »
Hello,

Have a look at our Data Throughput, Latency & Handshaking Application Note where you will find some information:

https://www.ftdichip.com/Support/Documents/AppNotes/AN232B-04_DataLatencyFlow.pdf

Our USB Data Transfer Efficiency Technical Note may also be of use as it looks at the factors influencing the efficiency of data transfer for FTDI devices:
 
https://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_103_FTDI_USB_Data_Transfer_Efficiency(FT_000097).pdf

In addition have a look at this Application Note on Optimizing D2XX Data Throughput:
 
https://www.ftdichip.com/Support/Documents/AppNotes/AN232B-03_D2XXDataThroughput.pdf

Regards,
FTDI Community

9
Discussion - Drivers / Re: Need FTDI (FT602) information
« on: April 26, 2019, 03:21:34 PM »
Hello,

1) In our project data from image sensor is stored in a FIFO using FPGA and this FIFO output(12-bit data) is sent to FT602 by the FPGA. Is it possible to send 12-bit data on 32-bit data lines of FT602 ? What is the data format
used in FT602  data transmission.


This is not possible. The FT602 is based around a 32-bit data bus and it looks for 32-bit control words.

3)Does FT602 accepts raw data from Image sensor, if not any conversions needed to implement? please suggest.

The FT602 is a UVC bridge it is not a sensor adapter and does not handle raw pixel data. It is not designed for direct attachment to a camera sensor or digital video source. The FIFO interface requires an FPGA to interface to FT602. 

For further information have a look at section 2.3 of AN_434 - https://www.ftdichip.com/Support/Documents/AppNotes/AN_434_FT602_UVC_Bus_Master_Sample.pdf

Regards,
FTDI Community.

10
Discussion - Hardware / Re: 232h in synchronous mode
« on: April 26, 2019, 02:23:28 PM »
Hello Rajesh,

There is no way to permanently set Sync FIFO mode. Your application will need to do it each time you open the port by calling FT_SetBitMode.

You can make the SetBitMode call from whichever application you use at the time (via FT_SetBitMode in Visual Studio, or via the similar VI in Labview)

Best Regards, FTDI Community

11
Hello,

The function takes a data buffer, in this case declared as 'SAMAPP_Tomato_DXT1_C0_Data_Raw'.

Code: [Select]
void Gpu_Hal_WrMemFromFlash(Gpu_Hal_Context_t *host,uint32_t addr,const prog_uchar8_t *buffer, uint32_t length)
{
    uint32_t SizeTransfered = 0;     

    Gpu_Hal_StartTransfer(host, GPU_WRITE, addr);
    while (length--) {
        Gpu_Hal_Transfer8(host,pgm_read_byte_near(buffer));
        buffer++;
    }
    Gpu_Hal_EndTransfer(host);
}

In the previous example this is defined in the 'SampleApp_RawData.cpp' file.

You can have a look at the updated Arduino source code in the main SampleApp:
https://brtchip.com/wp-content/uploads/EVE_Projects/SampleApp.zip


Best Regards,
FTDI Community

12
Discussion - Software / Re: Manipulating SD Files with ESD
« on: April 23, 2019, 10:20:05 AM »
Hello,

The main EVE Sample Application does include a section where it interfaces the SD card, although this only completes a read of data from the card:
Code: [Select]
#ifdef SAMAPP_ENABLE_APIS_SET13
#if defined (ARDUINO_PLATFORM) || defined (FT900_PLATFORM) || defined (FT93X_PLATFORM)
void set13_fontBufferToRAMG(uint8_t *filePath, uint32_t address) {
int chunk_size = 1024;
uint8_t buff[1024];
FIL pFile;
long int curPos = 0;
long int filesz = 0;
UINT bytesread = 0;
FRESULT fResult;

fResult = f_open(&pFile, filePath, FA_READ | FA_OPEN_EXISTING);
if (fResult != FR_OK) {
printf("Cannot open %s, please check SD card, error: %d \n", filePath, fResult);
return;
}
filesz = f_size(&pFile);
printf("Opened %s, file size: %ld\n", filePath, filesz);

while (curPos < filesz) {
bytesread = (filesz - curPos)>chunk_size?chunk_size:(filesz - curPos);

fResult = f_read(&pFile, buff, chunk_size, &bytesread);
if (fResult != FR_OK) {
printf("Error on f_read\n");
return;
}
Gpu_Hal_WrMem(phost, address + curPos, buff, bytesread);
curPos += bytesread;
}
}
#endif

The SD card example from the FT9XX toolchain (section 3.17) is the best SD card interfacing example for the FT9XX:
https://brtchip.com/wp-content/uploads/Support/Documentation/Application_Notes/ICs/MCU/AN-360-FT9xx-Example-Applications.pdf

What exact errors are being thrown?

ESD 4.5 will look for an SD card to be mounted to your development board, however we don't have any examples of writing non bitmap/font data to this.

Best Regards,
FTDI Community

13
Discussion - Software / Re: FT813 Touch screen response
« on: April 16, 2019, 04:57:43 PM »
Hi John,

We're very pleased that it helped and that it's working well now,

Best Regards, FTDI Community

14
Discussion - Software / Re: My Gui keeps crashing
« on: April 16, 2019, 04:27:37 PM »
Hello,

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

Please clarify what you mean by “the toy crashes  :-\: the application freezes”

Is FT9xx Eclipse IDE or ESD freezing or your custom application?

The UART debug interface can be good enough to debug.

You may want to consider moving pictures and icons to the SD card.

Also, ESD includes a lot of framework code to implement functionality, thus increasing the code size, 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 our 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 FT81x.

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

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

Best Regards,
FTDI Community

15
Hello,

The example included in AN_303 uses old source code form out main 'SampleApp', this has been updated to use the 'Gpu_Hal_WrMemFromFlash' function in place of the 'Ft_App_LoadRawFromFile'. This should be defined in the GPU_HAL.cpp file in your project:

Code: [Select]
void SAMAPP_GPU_DXT1() {
//load each .raw file into graphics RAM from directory ‘test’
//RAM_G is starting address in graphics RAM, for example 00 0000h
uint16_t imgWidth = 128, imgHeight = 128, c0_c1_width = 32, c0_c1_height = 32, c0_c1_stride = c0_c1_width * 2, b0_b1_width = imgWidth, b0_b1_height = imgHeight, b0_b1_stride = b0_b1_width/ 8, szPerFile = 2048;

#if defined(ARDUINO_PLATFORM) || defined(FT900_PLATFORM) || defined(FT93X_PLATFORM)
Gpu_Hal_WrMemFromFlash(phost, RAM_G, SAMAPP_Tomato_DXT1_C0_Data_Raw, szPerFile);
Gpu_Hal_WrMemFromFlash(phost, RAM_G + szPerFile, SAMAPP_Tomato_DXT1_C1_Data_Raw, szPerFile);
Gpu_Hal_WrMemFromFlash(phost, RAM_G + szPerFile * 2, SAMAPP_Tomato_DXT1_B0_Data_Raw, szPerFile);
Gpu_Hal_WrMemFromFlash(phost, RAM_G + szPerFile * 3, SAMAPP_Tomato_DXT1_B1_Data_Raw, szPerFile);
#endif

Gpu_CoCmd_Dlstart(phost);
App_WrCoCmd_Buffer(phost, CLEAR(1, 1, 1));
App_WrCoCmd_Buffer(phost, COLOR_RGB(255, 255, 255));

#if defined(MSVC_PLATFORM) || defined(MSVC_FT800EMU)
Gpu_Hal_WrMemFromFlash(phost, RAM_G, SAMAPP_Tomato_DXT1_C0_Data_Raw, szPerFile);
Gpu_Hal_WrMemFromFlash(phost, RAM_G + szPerFile, SAMAPP_Tomato_DXT1_C1_Data_Raw, szPerFile);
Gpu_Hal_WrMemFromFlash(phost, RAM_G + szPerFile * 2, SAMAPP_Tomato_DXT1_B0_Data_Raw, szPerFile);
Gpu_Hal_WrMemFromFlash(phost, RAM_G + szPerFile * 3, SAMAPP_Tomato_DXT1_B1_Data_Raw, szPerFile);
#endif

Gpu_CoCmd_LoadIdentity(phost);
Gpu_CoCmd_SetMatrix(phost);

App_WrCoCmd_Buffer(phost, SAVE_CONTEXT());
//B0&B1 handle
App_WrCoCmd_Buffer(phost, BITMAP_HANDLE(1));
App_WrCoCmd_Buffer(phost, BITMAP_SOURCE(RAM_G + szPerFile*2));
App_WrCoCmd_Buffer(phost, BITMAP_LAYOUT(L1, b0_b1_stride, b0_b1_height)); //L1 format stride is 1 bit per pixel
App_WrCoCmd_Buffer(phost,
BITMAP_SIZE(NEAREST, BORDER, BORDER, imgWidth, imgHeight)); //draw in full size
//C0&C1 handle
App_WrCoCmd_Buffer(phost, BITMAP_HANDLE(2));
App_WrCoCmd_Buffer(phost, BITMAP_SOURCE(RAM_G));
App_WrCoCmd_Buffer(phost, BITMAP_LAYOUT(RGB565, c0_c1_stride, c0_c1_height)); //RGB565 format stride is 2 bytes per pixel
App_WrCoCmd_Buffer(phost,
BITMAP_SIZE(NEAREST, BORDER, BORDER, imgWidth, imgHeight)); //draw in full size
// start drawing bitmaps
App_WrCoCmd_Buffer(phost, BEGIN(BITMAPS));
App_WrCoCmd_Buffer(phost, BLEND_FUNC(ONE, ZERO));
App_WrCoCmd_Buffer(phost, COLOR_A(0x55));
App_WrCoCmd_Buffer(phost, VERTEX2II(DispWidth / 2 - b0_b1_width / 2, DispHeight / 2 - b0_b1_height / 2, 1, 0));
App_WrCoCmd_Buffer(phost, BLEND_FUNC(ONE, ONE));
App_WrCoCmd_Buffer(phost, COLOR_A(0xAA));
App_WrCoCmd_Buffer(phost, VERTEX2II(DispWidth / 2 - b0_b1_width / 2, DispHeight / 2 - b0_b1_height / 2, 1, 1));
App_WrCoCmd_Buffer(phost, COLOR_MASK(1, 1, 1, 0));
Gpu_CoCmd_Scale(phost, 4 * 65536, 4 * 65536);
Gpu_CoCmd_SetMatrix(phost);
App_WrCoCmd_Buffer(phost, BLEND_FUNC(DST_ALPHA, ZERO));
App_WrCoCmd_Buffer(phost, VERTEX2II(DispWidth / 2 - b0_b1_width / 2, DispHeight / 2 - b0_b1_height / 2, 2, 1));
App_WrCoCmd_Buffer(phost, BLEND_FUNC(ONE_MINUS_DST_ALPHA, ONE));
App_WrCoCmd_Buffer(phost, VERTEX2II(DispWidth / 2 - b0_b1_width / 2, DispHeight / 2 - b0_b1_height / 2, 2, 0));
App_WrCoCmd_Buffer(phost, END());
App_WrCoCmd_Buffer(phost, RESTORE_CONTEXT());

//reset the transformation matrix because its not part of the context, RESTORE_CONTEXT() command will not revert the command.
Gpu_CoCmd_LoadIdentity(phost);
Gpu_CoCmd_SetMatrix(phost);

App_WrCoCmd_Buffer(phost, COLOR_RGB(255, 0, 0));
Gpu_CoCmd_Text(phost, (DispWidth / 2), 50, 31, OPT_CENTER, "DXT1: 8KB.");
Gpu_CoCmd_Text(phost, (DispWidth / 2), 80, 31, OPT_CENTER,
"Original: 32KB.");

App_WrCoCmd_Buffer(phost, DISPLAY());
//swap the current display list with the new display list
Gpu_CoCmd_Swap(phost);
//write to the FT800 FIFO command buffer - bitmap will appear after this command
App_Flush_Co_Buffer(phost);
Gpu_Hal_WaitCmdfifo_empty(phost);
Gpu_Hal_Sleep(3000);
}

Best Regards,
FTDI Community

Pages: [1] 2 3 ... 16