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

Author Topic: Start problem on V2DIP1-32  (Read 11174 times)

dUb

  • Newbie
  • *
  • Posts: 1
    • View Profile
Start problem on V2DIP1-32
« on: January 13, 2023, 10:52:27 AM »

He,

we develop a little firmware on the V2DIP1-32 which retrieve the data from an HID device and forward to a UART bus.
We use a custom firmware because, we need to send a periodic frame on the uart bus (10ms).
As you can see in the attachment files, sometimes, the V2DIP1-32 start with a degraded performance. To track the problem, we created a "alive" thread with the high priority which toggle a gpio pin every 10ms.
When the V2DIP1-32 starts with a low performance, the "alive" thread toggle the pin every 20ms and the uart frame is sent every 120ms!

Any suggestion about this performance degradation?
Logged

FTDI Community

  • Administrator
  • Hero Member
  • *****
  • Posts: 892
    • View Profile
Re: Start problem on V2DIP1-32
« Reply #1 on: January 20, 2023, 02:49:04 PM »

Hi,

This is likely an issue with your custom firmware, you could try using one of our precompiled firmware like V2DAP, to see if you are seeing the same degradation. You could also use VNC2 tools to debug and analyse. There are some code analysis tools built in. 

you could also try applying the SP3 patch to the VNC2 toolchain, and then rebuild. If you email into support1@ftdichip.com we can give you the details on how to access the patch.

Best Regards

FTDI Community
Logged