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 ... 50 51 [52] 53 54 ... 60
766
Discussion - Software / Re: FT81x Video with sound using CMD_VIDEOSTART
« on: August 22, 2018, 01:00:17 PM »
Hello

Unfortunately you cannot use sound with the CMD_VIDEOSTART / CMD_VIDEOFRAME commands.

However if you have a look at the following demo application, this covers video playback using CMD_PLAYVIDEO where the video doesn't consume the whole screen as well as having overlaid graphics:
ftp://ftp.ftdichip.com/CES/FT81xLiftDemoWithVideo/FT_App_Lift_EW2016.zip

Best Regards,

FTDI Community

767
Hello,

Please can you contact email support on support1@ftdichip.com and we will look into this, the outcome of which we will post here.

Regards,
FTDI Community

768
Hi Alexei,

I'm afraid that each individual port on the device can only be opened once / with one handle. As you mentioned any further attempts whilst already open will fail.

One thing you could consider is to have a 'routing' process open which talks to the port and then pass any data to this from any other processes and it can send to the device, and vice versa for reading. That way there is only one process opening the port.

Best Regards, FTDI Community

769
Discussion - Software / Re: Vinculum II programming interface
« on: August 13, 2018, 05:01:40 PM »
Hello,

I believe you also contacted email support with the same issue. Please continue to correspond via that support channel and we will post the resolution here.

Regards,
FTDI Community.

770
Discussion - Software / Re: Trouble appending data to an existing file
« on: August 13, 2018, 01:14:04 PM »
Hello,

Can you just clarify which product you are using?

Best Regards,
FTDI Community

771
Discussion - Software / Re: FT813 CRC calculating and adressing
« on: August 08, 2018, 11:58:18 AM »
Hi,

After adding commands or data to the co-processor RAM_CMD you must manually write the REG_CMD_WRITE to update it to point to the end of your data. In general, your application writes REG_CMD_WRITE and the co-processor writes the register REG_CMD_READ. Your MCU must keep an accurate count of the number of bytes sent and take account of the wrap around at RAM_CMD + 4095 (effectively it maintains an equivalent count to what the EVE device is doing internally)

If an error occurs, you should follow the steps shown in section 5.6 below:
http://brtchip.com/wp-content/uploads/Support/Documentation/Programming_Guides/ICs/EVE/FT81X_Series_Programmer_Guide.pdf
What cases do you see the pointers remain un-equal? The section mentioned above has some examples where it may happen such as an invalid image format, corrupted image, image de-compress where there isn't enough RAM_G space  to put the resulting data, a blocking call (such as calibrate), a command with invalid parameters (e.g. non multiple of 4 bytes) or it could be an error in the amount by which the MCU increments REG_CMD_WRITE.

For the transparent image, please ensure that the original one displays correctly in a program such as GIMP as the original image may have some non-transparent pixels (e.g. slightly different shade from the transparent colour) where you had expected transparency.

Regards,
FTDI Community

772
Discussion - Software / Re: Unable to allocate dynamic memory
« on: August 02, 2018, 09:25:29 AM »
Hello,

Please check AN_157 Vinculum II Memory Management for all available information on memory management.

The Thread Manager can also be useful. See the Help menu with in the IDE:



Have you considered our latest MCUs?
A more recent solution is to use the FT90x which allows more customisation than the Vinculum products.

There are significant benefits of FT90x:

-Eclipse based IDE
-Source code for API drivers is provided
-Significant performance improvement
-Actively in development by R&D
-Improved documentation and software examples

Best Regards,
FTDI Community

773
Discussion - Software / Re: FT4222 support in Raspberry Pi
« on: July 30, 2018, 04:44:58 PM »
Hello Carlos,

The LibFT4222 Linux Library is for i386, x86_64 and ARMv6-hf which implements the LibFT4222 API, with D2XX built-in.

Our standard Linux D2XX driver is 1.4.8 ARMv6 hard-float is suitable for Raspberry Pi.

So LibFT4222 should be suitable for RPi (ARMv6), though this has never been tested.

Best Regards,
FTDI Community

774
Discussion - Software / Re: FT813 CRC calculating and adressing
« on: July 30, 2018, 03:11:46 PM »
Hi Gokhan,

For Q1,
Yes, some commands such as CRC and GetPtr use the RAM_CMD FIFO to return the result. In these cases, you should still respect the rollover and should not try to get the result from an address beyond the end of the FIFO.

When you write the command, send the parameters replacing any result fields with dummy 0h values of the same size (in this case, all 3 parameters are 32-bit values including the result). Whilst CS is low, FT8xx will wrap the data around at (RAM_CMD+4095). Your own MCU's count of the offset should also perform a wrap-around.
void cmd_memcrc( uint32_t ptr, uint32_t num, uint32_t result );

Then update the write pointer and await the pointers being equal i.e. REG_CMD_READ == REG_CMD_WRITE.

Once equal, check the ending address WritePointer = REG_CMD_WRITE    This would be the 12th address as you mentioned in this example. (4092 plus 4 byte command plus 12 bytes of parameter)

Now you can do a 32-bit memory read of address (RAM_CMD + WritePointer - 4) & (4095) and you will be going back by 4 bytes taking account of rollover and reading the result. Therefore, you would do a read of the 8th address as you mentioned.

The REG_CMD_READ and REG_CMD_WRITE would still be pointing at the 12th address. You would use a memread32 to retrieve the 32-bit result value beginning at the 8th address.

For Q2,
You should always use the buffer as a true circular buffer. You should start your 3012 bytes of command from the current pointer position and should not write them back to 0.

Do you use burst writes? (keeping CS asserted and streaming the commands)?

If so, as you stream the data, the FT8xx will wrap around internally at 4095 back to 0 and so the commands will stay within the buffer.

Your own MCU code should also perform the rollover so that you can write the correct value to REG_CMD_WRITE at the end of the new list. e.g. MCU would track offset as ((2048+3012) & 4095)

Best Regards,
FTDI Community

775
Discussion - Software / Re: FT60X Isochronous Endpoint
« on: July 30, 2018, 11:45:58 AM »
Hello,

The FT60x supports Control, Bulk and Interrupt USB Transfer Types with up to 8 configurable endpoints, or PIPEs. This is detailed in the FT600-FT601 Datasheet:

http://www.ftdichip.com/Support/Documents/DataSheets/ICs/DS_FT600Q-FT601Q%20IC%20Datasheet.pdf

Regards,
FTDI Community

776
Discussion - Drivers / Re: FTDI devices not shown in Device Manager
« on: July 27, 2018, 11:21:08 AM »
Hi,

Please email FTDI Support on support1@ftdichip.com where we will assist you further.

Regards,
FTDI Community




777
Discussion - Drivers / Re: Mini Module FT2232H has incorrect PID code
« on: July 23, 2018, 03:10:35 PM »
Hi,

The FT2232H Mini Module allows configuration with both USB Bus-powered and USB Self-powered designs. Can I ask you to double check that you having properly configured the module for your design. Have a look at page 7 of the Datasheet for assistance:

http://www.ftdichip.com/Support/Documents/DataSheets/Modules/DS_FT2232H_Mini_Module.pdf

Regards,
FTDI Community

778
Hi,

The example may have an older version of the libFT4222H library (targeted to FT4222H rev B) inside. The FT81x modules use the revision C of the FT4222H

Please see the imports\LibFT4222H\lib folder inside this download.
http://www.ftdichip.com/Support/SoftwareExamples/LibFT4222-v1.4.1.zip
If you copy these updated DLL/lib files to your sample app folder replacing the existing ones then this should resolve the issue.

Regards,
FTDI Community



779
Hello,

Ft_Gpu_Hal_Wr8() - will immediately perform a direct SPI write to the desired register.

Ft_Gpu_CoCmd_MemWrite() - places the command into the co-processor list which the API will package into an SPI transfer.

The overheard of waiting on the API to perform the SPI write, versus manually performing the SPI write with Ft_Gpu_Hal_Wr8() is likely the cause of the issue.

Best Regards,
FTDI Community

780
Hello,

Can you try writing the REG_ROTATE register with the Ft_Gpu_Hal_Wr8() function and not via the Ft_Gpu_CoCmd_MemWrite(), and let me know how you get on?


Best Regards,
FTDI Community

Pages: 1 ... 50 51 [52] 53 54 ... 60