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: December 01, 2022, 04:43:10 PM 
Started by xenon68 - Last Post by FTDI Community
Hello,

This is the correct example to use:

C:\Users\Username\Documents\FTDI\Firmware\Samples\V2.0.2-SP2\General\FirmwareUpdate

Also refer to AN_159 Vinculum-II Firmware Flash Programming for more information.

Please note the restriction in the example readme:

Fragmented ROM files not supported. Do "CHKDSK <filename>" from command line to check.

This has been tested by FTDI and is working.

There may be other FTDI Community users who can help you further.

Best Regards,
FTDI Community

 2 
 on: December 01, 2022, 03:43:28 PM 
Started by sanka1p - Last Post by FTDI Community
Hi,

i tested this for you and i am able to receive the full string at a Baud rate of 9600. See the attached capture. This is what my write looks like:

 // Write data
    ftStatus = FT260_UART_Write(handle, buffer, 10, 10, &dwRealAccessData);
    if (FT260_OK != ftStatus)
    {
        printf("UART Write NG : %d\n", ftStatus);
    }

Best Regards
FTDI Community


 3 
 on: December 01, 2022, 02:30:20 PM 
Started by radioman85 - Last Post by radioman85
Thx for your links. I'll go through them and see if I find something.

 4 
 on: December 01, 2022, 10:09:36 AM 
Started by Nehmonn - Last Post by FTDI Community
Hello,

You can have a look at VNC2 UART to USB Memory Bridge. This project uses V2DAP firmware and also provides sample code. You can change the Baud rate using FT_PROG. This is shown on page 7 of the pdf.

VNC2 does work differently from VNC1L. Vinculum II User Guide will be able to help you with using the command set. It provides descriptions and examples of the different commands you can use.

Best Regards
FTDI Community




 5 
 on: November 30, 2022, 03:51:52 PM 
Started by Burpee - Last Post by FTDI Community
Hi,

You can have a look at Establishing Synchronous 245 FIFO Communications using a Morph-IC-II. This gives an example utility you can try, along with some sample code. The sample code can be found here: https://ftdichip.com/wp-content/uploads/2020/12/Synchronous%20245%20Morph-IC-II%20Application.zip.

Best Regards
FTDI Community

 6 
 on: November 30, 2022, 12:48:36 PM 
Started by Nehmonn - Last Post by Nehmonn
Hi, everybody.

For VNC1L, FTDI send me "VncFwMod.exe" software and VDAPFUL_V03_69.ROM.
I had readen this ROM file with "VncFwMod" software and had modified UART rate and version number, then reprogram the VNC1L by used FT-Prog software
All was ok.

Today, FTDI don't send me a VDAPFUL for VNC2 so I must compile V2DAP project included in toolchain V2.02 SP2 under VNC1L directory.
Then I program VNC2 by sending V2DAP.ROM by FT-Prog.exe.

Problem : when I communicate with VNC2 throught the PC terminal, VDAP2.ROM don't work like préviously with VNC1L
and when I send some commands (example : RDF after OPR ), VNC2 send too many characters and don't give control.

First, is it possible to send me ROM file to communicate throught UART to read and write files on USB key like "VDAPFUL_V03_69.ROM" file but for VNC2 please (and full project) ?

Then, is there software version "VncFwMod.exe" for VNC2 chip (to change baudrate and ROM file VERSION) ?

Many thanks for your help.

 7 
 on: November 30, 2022, 01:11:00 AM 
Started by xenon68 - Last Post by xenon68
Using the project FirmwareUpdateApp as an example in my code below. Using either the function FirmwareUpdateFATFileFeedback or FirmwareUpdateFATFile the both don't accept the ROM files.  I have used ROMs from my own projects and even the ROMs from install of Vinculum II IDE install 2.

First I have flashed the reflasher using:
VinPrg.exe ReflashFATFile.rom -o 0x1f000 -d "VII Debugger Module"

Then I run my application, select a ROM file that the linker has created and immediately returns from the FirmwareUpdateFATFileFeedback call.  The status is the ROM is invalid.

The return from the updating function is always FIRMWARE_UPDATE_INVALID_FILE.
Any suggestions what could be going wrong?


       file = fopen("FWUPDATE.ROM", "r");

   if (file == NULL)
   {
      puts1USART("@File not found@");
   }
   else
   {
      puts1USART("@Calling firmware update@");
      //#define REFLASHER_OFFSET 0x1f000
      //#define FEEDBACK       FIRMWARE_UPDATE_FEEDBACK_UART | FIRMWARE_UPDATE_FEEDBACK_GPIO_A2
      //status = FirmwareUpdateFATFileFeedback(file, REFLASHER_OFFSET, FEEDBACK);
      status = FirmwareUpdateFATFile(file, REFLASHER_OFFSET);
      
      if(status == FIRMWARE_UPDATE_INVALID_FILE) {
         puts1USART("@INVALID FILE@");
      }
      puts1USART("@Returned@");

      fclose(file);
   }

 8 
 on: November 29, 2022, 08:18:02 PM 
Started by sanka1p - Last Post by sanka1p
I changed the baud rate of FT260 to 9600 and my MCU baud rate is also 9600. Now when I execute sample uart.cpp project, I am only receiving the first character i.e 'a' from that sample and not the whole string. Can you tell me why? In my MCU program , I am trying to capture whole string. .

 9 
 on: November 29, 2022, 05:00:18 PM 
Started by radioman85 - Last Post by FTDI Community
Hello,

Please see TN_181 Type-C USB Connectors with FTDI Products which should help you.

You are missing 5K1 resistors on the CC1 (A5) and CC2 (B5) lines which are required.

You may have got these mixed up with A8 and B8.

Also there should be 27ohm an 47pF on the USB data lines. I can see 22ohm in your design which is incorrect.
See AN_146 USB Hardware Design Guidelines for FTDI ICs for more details.

Best Regards,
FTDI Community

 10 
 on: November 29, 2022, 01:57:33 PM 
Started by Yvonne - Last Post by FTDI Community
Hi Yvonne,

This can happen when the HID device is toggling DATA0/DATA1 without handshakes from the host. HID devices can do that sometimes, it’s even mentioned in the USB spec. You need to do a ClearFeature endpoint halt on the interrupt endpoint before reading it again.

In the code you are using to clear the halt state, the endpoint should be the interrupt endpoint instead of epCtrl in line 2. If you change this, it should clear the halted endpoint.

Best Regards

FTDI Community

Pages: [1] 2 3 ... 10