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 ... 16 17 [18] 19 20 ... 60
256
Hello,

You are already in contact with our technical support team on this matter.

Please feel free to post any resolution here to help other community users.

There may also be other FTDI Community users who will be able to help you.

Best Regards,
FTDI Community

257
Discussion - Hardware / Re: FT260 GPIO initial output state
« on: August 20, 2021, 01:07:08 PM »
hi,

have a look at https://ftdichip.com/wp-content/uploads/2020/08/AN_184-FTDI-Device-Input-Output-Pin-States.pdf. This application note goes over the I/O pin states of our devices, section 22 is for the FT260.

we also have a couple of software examples for the FT260 that may be able to help you. The folder for the code examples can be found here: https://ftdichip.com/products/ft260q/ under the downloads tab, you should have a look at the GPIO and GPIO_OpenDrain examples.

Please let me know if you have any more questions

Thanks

Kieran 

 

258
Hi,

One thing to check is that you have set timeouts to a finite value (e.g. 5000ms) which will avoid the read and writes hanging if they are unable to complete. You should check the status value once a call returns as well as comparing the sizeTransferred, which is provided by the read and write functions, to what you had requested, to see if all data was written/read.

Best Regards, FTDI Community

259
Hi,

Thanks for your update,

Yes it sounds like another device may be holding the clock low and so it depends if this other device can release the clock or if it has locked up and may need reset. You could try disconnecting the I2C lines for each device on the bus to check if the other device has got the line held low,

Best Regards, FTDI Community

260
Discussion - Software / Re: LibFT4222H spi slave buffer question
« on: August 16, 2021, 02:14:46 PM »
Hello,

You are correct, the driver retrieves the data from the chip automatically and stores it in the driver buffer within the PC and so you are reading the data from this local buffer. You can check the RxStatus to see how many bytes are available in this buffer.

Best Regards, FTDI Community

261
FTDI News / Re: New Power Delivery High Speed USB Devices
« on: August 04, 2021, 10:39:31 AM »
Hello,

Unfortunately we do not have an application note which covers the differences between the FTx232H and the FTx232HP/FTx233HP ICs.

However to answer your question yes the availability of Power Delivery and Type C support are the only differences between the old and new ICs.

Best Regards,
FTDI Community

262
Discussion - Software / Re: FT260 - Pauses in I2C comunication.
« on: August 04, 2021, 10:29:57 AM »
Hi,

We can try this out to see if we can see the same thing,

What timebase was your scope on and so what kind of pause duration were you seeing in each case?

One thing to note is that the FT260 uses interrupt transfers which support 64Kbytes/sec (for each IN or out pipe) and so the throughput will be limited by this, this may be one factor in the delay you see. 

Best Regards, FTDI Community

263
Discussion - Software / Re: FT4232H I2C Library recommendations
« on: August 02, 2021, 03:41:20 PM »
Hello,

The LibMPPSE library is essentially a wrapper library for standard D2XX API calls, the source is available is required, and it appears you already have access to this.
Please fell free to modify the LibMPSSE source code as required for your given application and produce a custom DLL.

Best Regards,
FTDI Community

264
Discussion - Software / Re: FT4232H I2C Library recommendations
« on: August 02, 2021, 11:47:16 AM »
Hello,

The FTCI2C.dll is no longer supported so we would recommend using the LibMPSSE.dll for new projects. however unfortunately the LibMPSSE helper library only supports GPIO functionality on the GPIOH pins.

There are two options for programming the MPSSE on the device to act as a SPI/I2C bridge, the first being to utilise LibMPSSE
The second option is to use raw D2XX commands to issue opcodes and data to the device, please see the following for a list of MPSSE opcodes:
https://www.ftdichip.com/Support/Documents/AppNotes/AN_108_Command_Processor_for_MPSSE_and_MCU_Host_Bus_Emulation_Modes.pdf

You will need to utilise a D2XX approach if you wish to utilise the GPIOL pins in your application.

Please see the following for an example of using raw D2XX commands in an I2C MPSSE application:
https://ftdichip.com/wp-content/uploads/2020/08/AN_113_FTDI_Hi_Speed_USB_To_I2C_Example.pdf

The MPSSE Basics application note may also be useful to you:
https://www.ftdichip.com/Support/Documents/AppNotes/AN_135_MPSSE_Basics.pdf

Best Regards,
FTDI Community

265
General Discussion / Re: FT813_Riverdi display 7 inch
« on: July 29, 2021, 02:43:54 PM »
Hello,

Thank you for the update.

I have had a quick look at the pinout for the module you are using and the pin out on the LCD connector on the click board, it appears that these do not match. For example the CS# signal is pin 3 on the LCD, but it is pin 6 on the Click board. Riverdi should be able to confirm this for you, but I suspect a mismatch in signal assignments is the root cause of the issue currently.

As for your second question, no toggling the PD pin is optional during the boot sequence, however we would recommend implementing this functionality via a GPIO pin if possible.

Best Regards,
BRT Community

266
General Discussion / Re: FT813_Riverdi display 7 inch
« on: July 26, 2021, 03:49:07 PM »
Hello,

Thank you for your question.

Unfortunately we do not have any specific examples for the NXPS32K148, but if you intend on implementing your solution with a low power MCU I would suggest looking at the following application notes which concern building an EVE library. The first application note covers how the low level transfers are structured between and MCU (in this example a PIC) and the EVE IC. The second covers how to create an EVE Library to interface to the MCU. And finally the last one covers some EVE examples for PIC MCUs, :
FT81X Simple PIC Example
FT81X Creating a Simple Library For PIC MCU
FT81X Simple PIC Library Examples

These application notes cover how to configure a display, but please take note of the specific display settings your module utilises.

The principals described in these Applications Notes can be used to implement solutions for a wide variety of MCUs, and give a better understating of how EVE functions on a low level.

We are currently finalising another application note based upon BRT_AN_014 above which expands this to a variety of other MCU platforms, I would advise utilising this library for porting to the NXPS32K148. I have uploaded the draft versions of this application note to WeTansfer (we are currently migrating our FTP site), please see the following link:
https://we.tl/t-75ILJqCMMc

As for HMI creation with these libraries you can use the EVE Screen Editor (ESE) to lay out static screens and create Display Lists but this does not create code for the logic of moving between screens. EVE Asset Builder (EAB) is also available to convert any graphics assets (fonts, images, etc) your require into an EVE readable format. These can be found at the following:
https://brtchip.com/eve-toolchains/

Best Regards,
FTDI Community

267
Discussion - Software / Re: Delay Between CLK and MOSI Operation
« on: July 23, 2021, 04:39:24 PM »
Hello,

SPI Mode 1 is not supported with the MPSSE engine.

Please consider FT4222H which supports all SPI modes.

Best Regards,
FTDI Community

268
Discussion - Software / Re: Delay Between CLK and MOSI Operation
« on: July 23, 2021, 11:05:30 AM »
Hello,

This is not possible. Is there a reason why you need it?
You should use the instructions (e.g. clock data on x edge) so that you change data on the edge which is not the valid one and in this case would normally not be an issue.   

Which SPI mode does your SPI peripheral use? Note that MPSSE only supports mode 0 and 2.
Mode 1 or 3 is not supported.

You can also try enabling 3-phase clocking.
This will give 3 phases so data is valid on both edges.

See AN_108 Command Processor For MPSSE and MCU Host Bus Emulation Modes for more details.

AN_411_FTx232H MPSSE I2C Master Example in Csharp shows an illustration of 3-phase in section 6.2.2.

Best Regards,
FTDI Community

269
Hello,

We have a recovery procedure in this application note below (see section 3.2). Could you advise if this procedure helps to recover from the error?
AN_412_FT600_FT601 USB Bridge chips Integration
https://ftdichip.com/wp-content/uploads/2020/08/AN_412_FT600_FT601-USB-Bridge-chips-Integration.pdf

Best Regards, FTDI Community


270
Discussion - Drivers / Re: FT4222H linux driver's bug
« on: July 06, 2021, 03:05:51 PM »
Hello,

Thank you for your question, I will look into reproducing this behaviour.

Could you just clarify what hardware configuration for the FT4222 you are using? is it the UMFT4222EV-D?


Best Regards,
FTDI Community

Pages: 1 ... 16 17 [18] 19 20 ... 60