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 ... 23
1
Discussion - Software / Re: FT260 and LibFT260, using Interrupts
« on: November 13, 2019, 11:02:07 AM »
Hello,

Thanks for your post.

I believe that you have also contacted email support where we will continue to deal with your issue and post any resolution here.

Regards,
FTDI Community

2
Discussion - Hardware / Re: FT932X I2C High speed Mode not working
« on: November 12, 2019, 04:45:41 PM »
Hello,

You have sent us an email on this matter. Feel free to post any resolution here to help other forum users.

Best Regards,
FTDI Community

3
Discussion - Hardware / Re: Is FT260 the correct solution?
« on: November 11, 2019, 04:44:14 PM »
Hello,

The FT260 can't be made to appear as a keyboard.

The source code for the keyboard example for the FT9xx MCU is available. It's included as part of the FT9xx Toolchain:

C:\Users\Username\Documents\Bridgetek\FT9xx\2.5.0\Examples

Best Regards,
FTDI Community

4
Discussion - Hardware / Re: Is FT260 the correct solution?
« on: November 06, 2019, 04:04:01 PM »
Hello,

The FT260 would appear as a HID class device but not exactly like a keyboard.
It doesn’t use FTDI drivers but uses standard HID class drivers.
Feel free to evaluate using the UMFT260EV1A.

The other real keyboard solution we have is FT90x / FT93x. This has a programmable USB device controller. We have already produced a keyboard example in AN_360 FT9xx Example Applications. See USBD Example HID . This is a bigger MCU though.

Best Regards,
FTDI Community

5
Hello,

Unfortunately FTDI do not offer that services, but hopefully one of the other forum members can help you out!

Best Regards,
FTDI Community

6
Discussion - Hardware / Re: FT813 non const text display?
« on: November 01, 2019, 11:51:03 AM »
Hi,

Glad it helped and thanks for letting us know,

Just to add, if you were originally trying to update variables on the screen without re-sending the command list, it is generally necessary to re-send the commands to create each screen update rather than have a change reflected on the screen in real time.

There are a couple of techniques that can help minimise the amount of the display which you re-send in AN_340 below and we also use the technique in several other examples such as section 9 of BRT_AN_014 and our sample apps too.

https://brtchip.com/wp-content/uploads/Support/Documentation/Application_Notes/ICs/EVE/AN_340_FT800_Optimising-screen-updates-with-Macro-and-Append.pdf

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


7
Hello,

It is not possible to shorten this time unfortunately as the end of the transfer is sent over a separate USB frame after the end of the data and so there is always a gap of more than one USB frame interval.

Best Regards,
FTDI Community

8
Discussion - Hardware / Re: FT813 non const text display?
« on: October 28, 2019, 12:05:21 PM »
Hi,

You can use string commands (such as sprintf) to write a string into the string variable x. This will allow you to create the string and then display it rather than have the hard-coded text string.

Best Regards,
FTDI Community

9
Discussion - Software / Re: Unable to read or write
« on: October 25, 2019, 10:08:23 AM »
Hello,

Since this is not one of our products, although it utilises our device, I am unable to support it.
Product Manufacturers are responsible for supporting end-users of their products, so you will need to contact μFR.
FTDI cannot control how the USB ICs are used and often has no knowledge of the entire product.
Please see the following document for reference:

http://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_102_OEM_Technical_Support_Requirements_for_FTDI_Products.pdf

It does sound though like the FTDI IC being used in this product is working correctly, as you are able to access and issue D2XX commands to the IC and they return without error.

Best Regards,
FTDI Community

10
Discussion - Hardware / Re: FT90x USB Connection Error
« on: October 22, 2019, 04:30:59 PM »
Hello,

It sounds like a problem with your custom hardware.

Also, VID_0000&PID_0002 doesn't match to what the FT905 is associated with.

What firmware is the FT905 running? Have you tried restoring the bootloader using the FT9xx Programming Utility found on your desktop as part of the FT9xx Toolchain?
Which silicon revision are you using? Rev B or the latest Rev C?

Please email your schematics to your local support team for review:

https://www.ftdichip.com/FTContact.htm

Best Regards,
FTDI Community

11
Hello,

Perhaps due to unaligned read/write.

An aligned write is a write on the FIFO interface with all byte enables selected, i.e. on a 16-bit interface, an aligned write is 16-bits wide and on a 32-bit interface, an aligned write is 32-bits wide.
 
An unaligned write is a write on the FIFO interface that is not as wide as the interface, i.e. on a 16-bit interface, an unaligned write is a single byte write and on a 32-bit interface, an unaligned write is 1, 2, or 3 bytes.
 
An aligned read is a read from the FIFO interface when the slave asserts all byte enables. On a 16-bit interface, an aligned read is 16-bits wide and on a 32-bit interface, an aligned read is 32-bits wide
 
An unaligned read is a read from the FIFO interface that is not as wide as the interface, i.e. on a 16-bit interface, an unaligned read is a single byte read and on a 32-bit interface, an unaligned read is 1, 2, or 3 bytes. An unaligned read from the slave always signals that it is a short packet

Further details can be found in AN_421 - https://www.ftdichip.com/Support/Documents/AppNotes/AN_412_FT600_FT601%20USB%20Bridge%20chips%20Integration.pdf

Regards,
FTDI Community

12
Discussion - Hardware / Re: FT232RQ revive
« on: October 15, 2019, 11:01:44 AM »
Hello,

Unfortunately it is not possible to access the EERPOM from the UART side of the IC.

Best Regards,
FTDI Community

13
Hello,

In 245 Synchronous FIFO mode the TXE_N is an output signal, Transmit FIFO Empty. It is active low and when active it indicates the Transmit FIFO has space and it is ready to receive data from the FIFO master. It indicates there is a minimum, or at least 1 byte of space available.

By the way if you contact support1@ftdichip.com we have a new driver I can provide to you.

Thanks,
FTDI Community

14
Test and Review Area / Re: LibFT260 v1.1.2 Beta
« on: October 11, 2019, 11:33:14 AM »
Hi,

We also have a new example which uses LibFT260 in C#. It includes imports for the I2C functions to allow them to be used in managed code. You can also add the UART ones in a similar way if you require these. Here is a draft version of the document and a beta version of the code below.

AN_438 Draft

AN_438 Beta Code

Note that these are subject to change and provided as a draft version only until fully released to our website,

The example may help if you're looking to create your own C# GUI applications using the FT260 etc.

Remember our Shared Projects section on the forum if you would like to show any of your projects which you make with the FT260.

Best Regards, FTDI Community

15
Discussion - Software / Re: FT260 LibFT260 I2C Flags
« on: October 07, 2019, 04:35:14 PM »
Hello,

Please refer to AN_395 User Guide for LibFT260.

There are also software examples provided with LibFT260 download.

Best Regards,
FTDI Community

Pages: [1] 2 3 ... 23