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 ... 4 5 [6] 7 8 ... 10
 51 
 on: January 01, 2024, 03:11:36 PM 
Started by Slava - Last Post by Slava
I need to use port A of the FT4232H in all I2C/SPI/JTAG/UART modes and switch between them in software. I don't see any problem in switching between I2C/SPI/JTAG, but I don't understand how to switch it from I2C to UART. Please help!

Regards,
Slava

 52 
 on: December 29, 2023, 07:56:22 AM 
Started by EmmeCi - Last Post by EmmeCi
I haVe aN electronic board with a FTDI Chip.

Using FT_Prog I can change the Manufacturer/Description/Serial string without change VID/PID. Is it legal with USB Org directive?

I checked everywhere but I didn't find no mention regarding the change about the topic.

Colud someone clarify this question?

Marco

 53 
 on: December 22, 2023, 03:55:46 PM 
Started by Zoltan - Last Post by FTDI Community
Hello,

Please provide the USBView details and screenshot for analysis.

Please send this via email to your local support team:

https://ftdichip.com/technical-support/

Best Regards,
FTDI Community

 54 
 on: December 22, 2023, 03:53:32 PM 
Started by DRN - Last Post by DRN
Great, Thanks!

 55 
 on: December 22, 2023, 03:45:30 PM 
Started by DRN - Last Post by FTDI Community
Hello,

We are aware of the feedback and will continue to support you via email.

Best Regards,
FTDI Community

 56 
 on: December 22, 2023, 01:59:04 PM 
Started by DRN - Last Post by DRN
Details of how I fixed the infinite looping problem in LibMPSSE version 1.0.4 (not 1.0.3)

 57 
 on: December 22, 2023, 09:41:18 AM 
Started by wzongya - Last Post by FTDI Community
Hi,
We don't have any experience with "Linux Docker" although i note that they have a community page also.
https://www.docker.com/community/

Our D2xx driver as well as the libFT4222 files are available from our website   
https://ftdichip.com/drivers/
https://ftdichip.com/wp-content/uploads/2022/06/libft4222-linux-1.4.4.170.tgz

Regards
FTDI Community

 58 
 on: December 22, 2023, 03:16:38 AM 
Started by wzongya - Last Post by wzongya
Hi,
    I want to get the device info for FT4222 with libft4222.so in linux docker image, and  with the source code in the pciture (getdeviceinfo.png).
    I chown the 0777 mode for the directory /dev/bus/usb, and have root privileges in linux docker image,but we get the unknown dev type. We get the correct dev type FT4222 with the same code in host not in docker.
   Could you tell me where is a problem? Do you have any idea how to fix it ?
Thank you.

   

 59 
 on: December 21, 2023, 07:51:18 PM 
Started by Zoltan - Last Post by Zoltan
Hello!

Yes, it is visible in the device manager, but its name has an exclamation point.
VID, PID have not changed! As I can see, the other parameters have not changed either!
Only the text fields (and the length and type fields) were incorrectly overwritten.

I see error code 10 in the driver information tab. STATUS_DEVICE_DATA_ERROR
With the explanation "The device cannot be started"...

I think that because the device cannot be started for some reason, it is not available for the Configuration program either.
The question is, why doesn't the device driver start when it finds incorrect "Manufacturer, Description, Serial" fields?!
And is there any way to start the IC with basic config data, without reconfiguring the IC?!

Thanks,
Zoltan

 60 
 on: December 21, 2023, 04:12:15 PM 
Started by Zoltan - Last Post by FTDI Community
Hello,

I wonder if you also changed the VID and PID?

Please check the device details with USBView Utility:

https://ftdichip.com/utilities/#microsoft-usbview

Does the device appear in Device Manager if you are using Windows?

If the VID/PID is changed then it might explain if the device can't been seen.

If that's the case then you can try editing the D3xx Driver files to include changed VID/PID numbers.
Note that this breaks driver signing so you may need to install via disabling driver signature enforcement or using test mode. Both are detailed in this external link:
https://maxedtech.com/about-testmode/

Then hopefully you can use the configuration tool to change back to defaults:

https://ftdichip.com/utilities/#ft60x-configuration

Best Regards,
FTDI Community

Pages: 1 ... 4 5 [6] 7 8 ... 10