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

Pages: [1] 2 3 ... 10
 1 
 on: Today at 02:23:28 PM 
Started by Rajesh@sys - Last Post by FTDI Community
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

 2 
 on: Today at 12:48:53 PM 
Started by Rajesh@sys - Last Post by Rajesh@sys

we are using UM232H in one of our projects.
we are using in synch FIFO mode.

After power ON
 
1) to set synchronous FIFO mode. we are sending 0x40 using FT_HANDLE/ from Visual Studio/COM port - after every power ON off board..

2) we are using Labview to read data. using NI-VISA as USB port.

here we are facing problem.   switching between labview and visual studio.

Query:

3) how to set  UM232H in synchronous FIFO mode permanently.

please suggest/share if any document is available for setting synch mode permanently.


 3 
 on: Today at 04:54:16 AM 
Started by vinays - Last Post by vinays
In one of our ongoing project we are using FT602-Q device for video streaming or data capture from Image sensor.
We're using Intel MAX 10 FPGA to capture the data from Image Sensor. FPGA is interfaced with FT602
I have few questions please clarify
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.
3)Does FT602 accepts raw data from Image sensor, if not any conversions needed to implement? please suggest.

 4 
 on: April 24, 2019, 10:25:15 PM 
Started by MauroDiamantino - Last Post by MauroDiamantino
Hello, I'm working with a device which communicates with a PC using a FTDI chip and I found an unexpected behavior when I set up timeout and then I tried to read data from the device. The device is a Aaronia spectrum analyzer which utilizes a FTDI 232R chip. The PC is a Raspberry Pi 3B+ with Raspbian which I installed the D2XX driver (version 1.4.8 ARMv6). The problem arose when I set up the timeout values and then I tried to read data from the device. I decided to set it up to 10 seconds initially and then reduce it many times up to the minimum possible value which allows a correct operation. With the initial value (10s) I tried to read data from the device and I got error messages which stated no bytes were read. After many tries to solve the problem changing the read timeout, I  managed to solve it adding a call to "usleep" function with 200000 (200ms) as argument before the reading operation, so I found the reading function was not blocking to wait the data during the timeout. I tried the same operation in my notebook HP 14-an020la with Debian 4.9.130-2 and I got the same result.
What could it be the error? Am I correctly understanding the timeout?

 5 
 on: April 23, 2019, 06:02:49 PM 
Started by LOstrander - Last Post by LOstrander
I seem to have it working now.  It looks like the emulator's C compiler doesn't like me using the ff.h header in anything besides the ESD specific functions, but when I upload the program to my FT900, it works perfectly.

 6 
 on: April 23, 2019, 10:46:10 AM 
Started by ConfusedIrishMan - Last Post by FTDI Community
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

 7 
 on: April 23, 2019, 10:20:05 AM 
Started by LOstrander - Last Post by FTDI Community
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

 8 
 on: April 23, 2019, 09:18:27 AM 
Started by esterill - Last Post by cioma
My 5p:

The latest FT_Prog messes up LG 27MD5KA-B Thunderbolt display backlight settings on Windows 10 when it scans for FTDI devices: screen backlight blinks every 0.5s during scan and ends up being very dim (one can hardly see anything on it). The workaround is to start the scan again and unplug the display from PC during it. After replugging it might end up with the original backlight settings.

 9 
 on: April 23, 2019, 09:05:03 AM 
Started by Bart - Last Post by cioma
AFAIK the USB bulk transfers (512 bytes packets in High Speed mode) are used for actual data exchange. Any amount of data may be sent to OUT endpoint as USB subsystem on the host computer handles this automatically: device sends NAK on the OUT endpoint when its buffer gets full and the host computer reschedules the data delivery. Therefore there is no need to split write data in 512 byte chunks. And the data is buffered on the host computer. Same for the IN endpoint: host computer buffers data until either its size reaches the limit you've requested (e.g. 64 kB) or a timeout occurs.

 10 
 on: April 22, 2019, 04:27:41 PM 
Started by LOstrander - Last Post by LOstrander
I have been trying to incorporate a couple of functions into my ESD program to read and write a few text files from an SD card.

First I tried using the fopen() functions native to C.  The program compiled and ran, but when I went to check the SD card's contents, the files were nowhere to be found.

Next I tired using the FatF header included in the SD card example in the Ft9XX Toolchain.  I changed the functions over to the FatF commands, and included all of the files required in my ESD project.

For some reason, however, it refuses to recognize the typedefs for the various functions within the header (specifically the DSTATUS and DRESULT types in diskio.h), and claims a few variables/enums were undeclared because of this.

So my question is kind of two-fold:  Is there an easy way to communicate with the SD card on the FT900 through ESD for non-bitmap files, and if it involves the ff.h header, what do I change to make it function?

For reference, I'm using the ME812A WH50R and MM900EV-LITE in ESD 4.5.

Pages: [1] 2 3 ... 10