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] 4 5 ... 10
 21 
 on: March 11, 2019, 10:49:50 AM 
Started by bogus - Last Post by FTDI Community
Hello,

This is a 3rd party product.  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

Regards,
FTDI Community

 22 
 on: March 09, 2019, 03:43:06 PM 
Started by bogus - Last Post by bogus
I did that but without success. My modules look like this: https://robokitshop.in/products/ft232rl-ftdi-5v-3-3v-usb-to-ttl-converter-adapter-module-for-arduino

 23 
 on: March 07, 2019, 02:12:48 PM 
Started by TheDarkMax2 - Last Post by FTDI Community
Hello,

The ftd2xx.lib is COFF.

I believe COFF2OMF.exe is part of RAD Studios so you may want to contact them about this, or perhaps someone on the forum has some experience with using the tool.

Regards,
FTDI Community

 24 
 on: March 06, 2019, 04:46:36 PM 
Started by bogus - Last Post by FTDI Community
Hello,

After programming in FT_Prog did you hit the Cycle Port button?

If you are still having problems can you confirm which of our devices that you are using please? i.e a cable or a development module?

Regards,
FTDI Community


 25 
 on: March 05, 2019, 05:53:23 PM 
Started by bogus - Last Post by bogus
Hi everybody,
I bought some modules with FT232RL chips and I want to flash internal EEPROM memory in these modules, but I can't. At face value all looks good, while programming I have no error but when I read out memory I see that any value did not changed. Do anyone have idea why it happends? Are these modules fake? RS232 communication works fine.

 26 
 on: March 05, 2019, 10:38:45 AM 
Started by TheDarkMax2 - Last Post by TheDarkMax2
Is ftd2xx.lib COFF or OMF? I can't convert it :( The RAD Studio says that it's COFF, but COFF2OMF says that it's OMF. And I need a version for the RAD Studio (Builder).

 27 
 on: February 22, 2019, 12:53:16 PM 
Started by Pereubu123 - Last Post by Pereubu123
Maybe I tried to explain the problem in rather confusing way. I will try again:

Let assume that memory device work in mode 0 or mode 3. let us decide to use mode 0.
Where CPOL = 0, CPHA = 0, mode 0.
For this mode, input data is latched in on the rising edge of serial clock (C), and
output data is available from the falling edge of C.
So when we let say  my program is used to read one word data from a random address:
one write command plus address is used  and then on the side mpsse we should use on the
raising edge sampling in to get the data from from spi flash componenet?

That is why the sample in "Interfacing FT2232H Hi-Speed Devices To SPI Bus Application Note AN_114" (page 13) looks very odd:

//send WRITE command  O
utputBuffer[dwNumBytesToSend++] = MSB_FALLING_EDGE_CLOCK_BIT_OUT; 
OutputBuffer[dwNumBytesToSend++] = 2; 
OutputBuffer[dwNumBytesToSend++] = READ; 
//send address 
OutputBuffer[dwNumBytesToSend++] = MSB_FALLING_EDGE_CLOCK_BIT_OUT; 
OutputBuffer[dwNumBytesToSend++] = 7; 
OutputBuffer[dwNumBytesToSend++] = (BYTE)(address); 
//read data   

OutputBuffer[dwNumBytesToSend++] = MSB_FALLING_EDGE_CLOCK_BYTE_IN;     
OutputBuffer[dwNumBytesToSend++] = '\x01';   
OutputBuffer[dwNumBytesToSend++] = '\x00'


The question is why we are using MSB_FALLING_EDGE_CLOCK_BYTE_IN?

Why FALLING_EDGE instead of RAISING_EDGE?

 28 
 on: February 21, 2019, 10:48:01 AM 
Started by Pereubu123 - Last Post by Pereubu123
Data is typically clocked in and out on clock edges. 
Either the rising or falling edge can be used on transmit or receive.
In the 93C46D example, the EEPROM clocks data in and out on the rising edge.
I have my own selected SPI flash component, with clocking in (sampling) data on rising clock edge,
and clocking out data for that particular SPI memory chip on falling edge. Actually, input data is latched in on the rising edge of serial clock (C), and
output data is available from the falling edge of C.

What is confusing is:

(taken form AN_135 FTDI MPSSE Basics Version 1.1)
"In the 93C46D example noted above, the EEPROM clocks data in and out on the rising edge. 
In this case, the MPSSE should be configured for data transfer on falling edges for both transmit and receive. 
This allows the data out from both the MPSSE and the target device to stabilize before being clocked in on the next edge."
Now, I expect that I have to use opposite: MPSSE should be configured clocking in data on falling edge while clocking out data
on rising edge. But what is the meaning "This allows the data out from both the MPSSE and the target device to stabilize before
being clocked in on the next edge"?

So, is that Ok to follow the logic above to configure MPSSE to  latch input data on the rising edge of serial clock (C), and
output data to be  available from the falling edge of C.

 29 
 on: February 20, 2019, 05:32:41 PM 
Started by scorpioprise - Last Post by scorpioprise
Thank you, Kaetemi, I'll give a try to your solution, when I can move again with ESD project.

Can You explain a little the structure?

ESD_Project (top folder)
|-- Project( where exporting ) (subfolder level 1)
|-- EclipseProjectSrc (subfolder level 1)

Is your idea?

 30 
 on: February 20, 2019, 02:18:32 PM 
Started by bernie - Last Post by FTDI Community
Hello,

You could try changing the latency timer (FT_SetLatencyTimer) to 1 or enabling flow control in your application program (FT_SetFlowControl). Have a look at the D2XX Programmer Guide for further details:

https://www.ftdichip.com/Support/Documents/ProgramGuides/D2XX_Programmer's_Guide(FT_000071).pdf

Regards,
FTDI Community.

Pages: 1 2 [3] 4 5 ... 10