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 2 [3] 4 5 ... 22
31
Discussion - Software / Re: cannot enter MPSSE mode
« on: September 10, 2019, 12:49:15 PM »
Hello,

We are dealing with your issue via email.

Please put the resolution here for other community user's benefit.

Best Regards,
FTDI Community

32
Hello,

Can you please test with known good hardware like our Development Modules?

You could also send your schematics to your local support team for review. See Contact Us.

Best Regards,
FTDI Community

33
Discussion - Software / Re: FT813 (or BT815) few fonts at the same time.
« on: September 06, 2019, 01:56:03 PM »
Hi,

Although in theory you can scale individual characters of text like an image, it is normally more feasible to load the font several times converted to different sizes. If you don't need all characters (e.g. maybe just numbers and maths symbols) you can save some space there too. Or in many cases you can try L2 or L4 format or even L1 which won't take up as much space. You can experiment a bit to see what looks good on the screen.

If you want just a few sizes, then loading each to a different bitmap handle should work well.

For BT81x, we have a beta sample app below which you can refer to for BT81x. See SampleApp folder in this file and in particular within sampleapp go to src -> Application -> Set_10.c -> ExtendedFormatFont() for an example.

BT81x Sample Apps

Note that the file is around 200MBytes.

Best Regards, FTDI Community

34
Discussion - Software / Re: EVE Screen Designer - color problem
« on: September 04, 2019, 09:47:47 AM »
Hello,

The alpha colour channel does not take effect for theses widgets.
But I've ran a test and the colours seems to be working fine on our end.

Can you provide your project files?

Best Regards,
FTDI Community

35
Test and Review Area / LibFT260 v1.1.2 Beta
« on: September 04, 2019, 09:39:01 AM »
Hi,

We have a new beta version of LibFT260 here. It adds a 64-bit DLL as well as some updates to the example code.

LibFT260_v1.1.2

Please let us know if you have any feedback on this beta by either posting here or emailing us at support1@ftdichip.com

Best Regards, FTDI Community

36
Hi,

One thing to check is how large your images are when de-compressed by LoadImage. The resulting image data in RAM_G will be larger than the JPG itself as it will be de-compressed.

You can add a check using the CMD_GETPROPS (see 7.3 of this appnote below). As a quick test, you can also try converting to RGB565 with our asset builder to see how large the raw data output file is to give an idea of the decompressed size.
https://brtchip.com/wp-content/uploads/Support/Documentation/Application_Notes/ICs/EVE/BRT_AN_014_FT81X_Simple_PIC_Library_Examples.pdf

Best Regards, FTDI Community

37
Discussion - Hardware / Re: FT4222H reset and Configuration
« on: September 03, 2019, 04:37:25 PM »
Hello,

You have contacted our support team via email with these questions.

The answer can be posted here once it's resolved to help other FTDI Community users.

Best Regards,
FTDI Community

38
Hi,

EVE displays the image in real time from RAM_G and so any change to memory used for a bitmap will be immediately shown on the screen if the bitmap is visible.

As you said, double buffering is the best solution, as you can load the second image whilst still displaying the first and change over immediately. Note that compressed images such as PNG (via Loadimage) and bin files from the asset converter (via Inflate) still take the same amount of RAM_G once decompressed by the Loadimage or Inflate command. However, depending on the image you may be able to experiment with the image quality by converting via our asset converter. The table in the BITMAP_LAYOUT section of the Programmers Guide shows how many bits per pixel. e.g. RGB565 uses 2 bytes per pixel whereas RGB332 uses only one byte per pixel.

Another option if two images won't fit is to load a version of the image in lower quality and change to this whilst the other is being updated. (either by loading a separate low quality image or by inflating to a different area of RAM_G as L8 greyscale. A slightly less complex way might be to dim the image or blank it completely by setting COLOR_RGB before the Vertex command to a low value or to (0,0,0). Then put back to (255,255,255) once the image has been loaded.

Best Regards, FTDI Community



39
Discussion - Hardware / Re: FT602 - No video stream to computer
« on: September 03, 2019, 10:54:50 AM »
Hello,

Great thanks for letting me know that after trying a USB 3.0 cable you were able to get your test program partially working.

To continue support please contact support at the following email address:- support1@ftdichip.com.

Regards,
FTDI Community

40
Discussion - Hardware / Re: FT602 - No video stream to computer
« on: September 02, 2019, 02:32:06 PM »
Hello,

Are you connecting to a USB 3.0 Host port on your host PC? If so do you notice any difference if you use a USB 3.0 cable rather than a USB 2.0 cable?

Also, you mention that you encounter some error messages, can you provide some details on these error messages please?

Regards,
FTDI Community

41
Discussion - Software / Re: EVE Screen Designer - color problem
« on: September 02, 2019, 10:55:19 AM »
Hello,

Sorry can you just clarify if it doesn't work on real hardware or that it just doesn't work in the ESD simulation?

Best Regards,
FTDI Community

42
Hello,

This is confirmed as a bug in FT4222_I2CMaster_Write().
It will be fixed with the next LibFT422 patch.
However the actual transaction is OK and the extra count of 4 can be discarded as a workaround.

Best Regards,
FTDI Community

43
Hello,

In general with USB full speed 64 bytes transfer package is made up of 2 status bytes and 62 user bytes.
Note this is 512 maximum transfer package size for USB high speed like the FT4222H.
The two bytes 02 60 are the status bytes required by the D2XX driver.
The status bytes are for the driver and should be invisible to the user application and is handled by the driver.

Which version of LibFT4222 are you using? Which version of the D2XX driver are you using?
The latest are v1.4.2 and 2.12.28 respectively (for Windows).

Which FT4222H IC revision are you using?

Have you tested out the I2C examples provided with LibFT4222?

Best Regards,
FTDI Community

44
Hello Liam,

Which driver version and IC are you using?

Has BytesWritten been initialised correctly first? This would be good practise.

You could also try FT_Purge.

What are your timeouts set to in FT_SetTimeouts? Could it be that it's timing out before there is enough time to send the data?
Remember USB is non-deterministic. There can be lots happening on a USB bus or with the OS which can cause delays.

See the D2XX Programmer's Guide for more information.

Also AN232B-04 Data Throughput, Latency & Handshaking provides some useful information and applies to all FTDI devices.

Best Regards,
FTDI Community

45
Hi,

We will have a look through your details provided but here is a link to the latest beta and source code:
LibMPSSE

Best Regards, FTDI Community

Pages: 1 2 [3] 4 5 ... 22