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: June 26, 2019, 04:38:24 PM 
Started by Rajesh@sys - Last Post by FTDI Community
Hello Rajesh,

Please see TN_153 Instructions on Including the D2XX Driver in a Visual Studio Express 2013 Project for more information.

Code: [Select]
ft_handle is used as follows:

FT_HANDLE fthandle;
FT_STATUS status;

status = FT_Open(0, &fthandle);

The status should be checked for errors. Error codes can be found in ftd2xx.h. FT_OK is 0.

This code snippet is opening the first FTDI device connected to the PC. You may want to make the code more robust by opening by serial number or description, for example:

Code: [Select]
status = FT_OpenEx("FTEE5MM", FT_OPEN_BY_SERIAL_NUMBER, &fthandle);
or

Code: [Select]
status = FT_OpenEx("FT232H", FT_OPEN_BY_DESCRIPTION, &fthandle);
All devices can be listed first using FT_CreateDeviceInfoList and FT_GetDeviceInfoList first. See the D2XX Programmer's Guide for more information.

If the device is not connected, the function status will return an error code.

TN_167 code could be improved to exit the code when there are errors:

Code: [Select]
if(status != FT_OK)
{
printf("open device status not ok %d\n", status);
return 0;
}

Sometimes brackets are not used meaning that the code will continue:

Code: [Select]
if(status != FT_OK)
printf("timeout A status not ok %d\n", status);

Best Regards,
FTDI Community

 2 
 on: June 26, 2019, 04:37:28 PM 
Started by scorpioprise - Last Post by FTDI Community
Hello,

It sounds like you have corrupted the project with the changes that you have made.
It might be worthwhile re-downloading the project and starting again and taking care with each change you make.
You could also start with a new project in Eclipse and add your own code/structure. See section 3.1 Creating a new project in AN_325 FT9xx Toolchain Installation Guide.

AN_398 was never released. Instead the information is included in section 2.34 Datalogger Feature of AN_365 FT9xx API Programmers Manual.

AN_415 Ethernet to GPIO does indeed use the datalogger feature to store information in EEPROM.

Webpage images could be stored on the SD Card to reduce space or the webpage images could be removed for test purposes.
the Ethernet stack lwip is most likely taking up a lot of space. There should be more information online about reducing this size. The alternative would be to develop your own Ethernet stack.

Note the Bridgetek Community is now open.
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

Best Regards,
FTDI Community

 3 
 on: June 26, 2019, 04:32:50 PM 
Started by Yunuce - Last Post by FTDI Community
Hello,

Please see the FT905/FT906/FT907/FT908 Datasheet for more information.

VCCIO3V3 is the supply voltage for all the I/O ports.

See the Electrical Characteristics in section 5.2:

ParameterDescriptionMinimumTypicalMaximumUnitsConditions
VCCIO3V3I/O operating supply voltage2.973.33.63VNormal Operation

Please note, the Bridgetek Community is now open.
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

Best Regards,
FTDI Community

 4 
 on: June 26, 2019, 09:21:52 AM 
Started by scorpioprise - Last Post by scorpioprise
Hi everyone,
I'm experiencing some troubles against AN415 (Ethernet to GPIO), because after some few modifications (moved some headers, removed some debug messages, changed project name), I could not compile it anymore, and I've hit a series of errors "multiple definition of" ( i.e. "_exit","_start","_exithook") that hit in crt0.S.

I don't understand why, as I've made no change neither in main nor in crt0, adding that particular defines.

Searching into the code, I have a reference to crt0 in comments

Code: [Select]
void flash_config_init() {

[..cut..]// Project settings incorrect. Require dlog support with modified
// linker script and crt0.S file.
// See AN_398 for examples.
there is a AN398 reference, which I couldn't find on FTDI or BRT sites.

Also, I need to understand how to reduce the imagesize, as i've understood that it takes the whole flash, but I need to know the real allocated space, and change it according to my needs.
Thankyou in advance

 5 
 on: June 26, 2019, 05:58:08 AM 
Started by Yunuce - Last Post by Yunuce
Hello,

I am working on i2c/spi with Ft906L and I want to use other pins as GPIO but I couldn't find GPIO pins characteristic.
I wonder that if I use those pins what is the voltage level?

Thanks.

 6 
 on: June 25, 2019, 04:30:36 PM 
Started by LOstrander - Last Post by FTDI Community
Hello Logan,

Yes the following signals are all connected to the programmer module via CN7 which are then connected to PortB of the FT4232H on the UMFTPD2A, so I can see why there would be some contention on the SPI lines:

SPIS0_CLK/GPIO36
SPIS0_SS/GPIO37
SPIS0_MOSI/GPIO38
SPIS0_MISO/GPIO39

As I have mentioned in my emails, please check out the SPI master to SPI slave example in AN_360 FT9xx Example Applications which can be used as a reference.

Best Regards,
FTDI Community

 7 
 on: June 25, 2019, 11:16:53 AM 
Started by Rajesh@sys - Last Post by Rajesh@sys
Hi,

 i am using visual studio 2017 to configure FT232H to synchronous mode.
i am able to detect ft232h as comport.(using vcp drivers)

as given pdf (building application  in visual studio) i have included .dll files from and header file  "d2xx driver".

i have used code from "TN_167 FIFO Basics (USB2.0)" fifo synchronous read code.


with these i am able  confirm FTDI IC is connected. as it showing(command prompt) code is excited with 0.

if i disconnect usb i am able to see "device status not ok".



my query is :

1) why i am not able to access ft_handle function.

2) code is everytime entering into null.


please suggest me., how access ft_handle



thanks

 8 
 on: June 21, 2019, 05:25:45 PM 
Started by LOstrander - Last Post by LOstrander
At least part of my issue was solved: It looks like you can't have the programmer attached to CN5 if you have a SPI Slave on CN2.  I assume this has something to do with how the programmer uses the same pad.  I disconnected the programmer, and my CLK and MISO lines reappeared!

I still get a crash when I try to send certain things over SPI (might be the datatype I'm trying to send, since regular old numbers seem to work fine), and if I try to make the variables static it seems to complain, but it looks like the SPI problem is pretty much solved.

 9 
 on: June 21, 2019, 04:37:06 PM 
Started by LOstrander - Last Post by FTDI Community
Hello,

We are currently discussing your issues by email. You can post any resolution here to help other users.

Also, Our new Bridgetek Community is now open.
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

Best Regards,
FTDI Community

 10 
 on: June 21, 2019, 02:20:36 PM 
Started by LOstrander - Last Post by LOstrander
I've added the ft900_registers.h file to the project, and now it at least gets through the function and loads the next screen without crashing.

However, this has pointed out a new issue: It doesn't seem to actually be setting the SPI Slave pins as such.  Specifically, the CLK line seems to be convinced it's an output, and idles high at 3.3V.  The SS and MOSI lines appear to be working.  The MISO line is hard to tell because it requires the CLK line to work for it to work.  When my SPI Master is disconnected from the MM900EV-LITE, it functions perfectly (besides the MISO for obvious reasons).

Does anyone have a pinout of the CN2 connector that explicitly shows which pin is which number?  I'm 99% sure I'm right in assuming it's left column odd, right column even, but I want to rule that out.  The next pin down (Pad 66) is my "Go" signal, and it works perfectly.

Pages: [1] 2 3 ... 10