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 4 ... 10
 11 
 on: March 19, 2019, 08:59:38 AM 
Started by Rajesh@sys - Last Post by FTDI Community
Hello,

Do you mean RXF# and TXE#?

RXF#:
When high, do not read data from the FIFO. When low, there is data available in the FIFO which can be read by driving RD# low. When in synchronous mode, data is transferred on every clock that RXF# and RD# are both low. Note that the OE# pin must be driven low at least 1 clock period before asserting RD# low.

TXE#:
When high, do not write data into the FIFO. When low, data can be written into the FIFO by driving WR# low. When in synchronous mode, data is transferred on every clock that TXE# and WR# are both low.

A write operation can be started when TXE# is low.

A read operation is started when the chip drives RXF# low.

Best Regards,
FTDI Community

 12 
 on: March 18, 2019, 04:45:42 PM 
Started by dbell - Last Post by dbell
We need receive data stream within the UVC from our FT602 to our C#/C++ app on Windows 10.

 Does FT602 have a USB 3 interface for host, or is only UVC available? 

BACKGROUND...
We are using for non-video data stream.

 13 
 on: March 18, 2019, 01:31:27 PM 
Started by techtoys - Last Post by FTDI Community
Hello,

Please have a look at the following Application Note:
https://brtchip.com/wp-content/uploads/Support/Documentation/Application_Notes/ICs/EVE/AN_340_FT800_Optimising-screen-updates-with-Macro-and-Append.pdf

The methods described in this should be helpful for you.

Best Regards,
FTDI Community

 14 
 on: March 16, 2019, 03:09:13 PM 
Started by techtoys - Last Post by techtoys
Hi

Is there any method to do a partial update to LCD screen driven by FT813?
Testing with Msvc_Emulator with a very simple feature. Code snippet is shown below:

Code: [Select]
//Display list to draw something at the top
Gpu_CoCmd_Dlstart(phost);
FuncA_display_object(); //function to display something on top of the screen
App_WrCoCmd_Buffer(phost, END());
App_WrCoCmd_Buffer(phost, DISPLAY());
Gpu_CoCmd_Swap(phost);
App_Flush_Co_Buffer(phost);
Gpu_Hal_WaitCmdfifo_empty(phost);

//2nd display list to draw some other contents a the bottom.
Gpu_CoCmd_Dlstart(phost);
App_WrCoCmd_Buffer(phost, SCISSOR_XY((DispWidth / 2) - 14, (DispHeight - 75)));
App_WrCoCmd_Buffer(phost, SCISSOR_SIZE(32, 32));
App_WrCoCmd_Buffer(phost, CLEAR_COLOR_RGB(255,255, 1));
App_WrCoCmd_Buffer(phost, CLEAR(1, 1, 1));
FuncB_display_object(); //function to display other contents at the bottom of the screen
App_WrCoCmd_Buffer(phost, END());
App_WrCoCmd_Buffer(phost, DISPLAY());
Gpu_CoCmd_Swap(phost);
App_Flush_Co_Buffer(phost);
Gpu_Hal_WaitCmdfifo_empty(phost);

The mindset to run FuncA_display_object() and FuncB_display_object() within a single display list with one swap is not allowed for my case. With code above I can see only the bottom content because the second display list is refreshing the whole screen. I did try to use scissor but this macro only restrict the area to draw in the second display list, the rest of the area including the top part has been erased completely.

Is it something related to SAVE_CONTEXT() & RESTORE_CONTEXT()? and Can somebody help in this ?

Thanks in advance.

John


 15 
 on: March 15, 2019, 01:27:33 PM 
Started by Rajesh@sys - Last Post by Rajesh@sys
hi,

RXE and TXE signals are dependent or independent ?


                can TXE and RXE go LOW at same time.

 16 
 on: March 14, 2019, 05:37:52 PM 
Started by chicoprojeto - Last Post by chicoprojeto
Good afternoon!
My VNC2 is configured as IPA and SCS. And I'm communicating via SPI.
When VNC2 reboots it only sends the prompt (0x3 and 0x0d).

As soon as I start VNC2 I read the 2 bytes that are in memory and this takes approximately 500us.

Then I open the opw file in approximately 2ms, but to read the return I take approximately 16ms, this is because the status always comes in 1 and I request the byte again until the status comes with 0 ... Can anyone here help me? Looks like some sync problem. That way, I'm taking too long to burn 8MBytes on a flash drive for about 30 minutes, I'd like to cut back on that time.

The software I recorded in vnc2 is what you have enabled on the site:
"FTDI \ Firmware \ Samples \ V2.0.2-SP2 \ VNC1L \ V2DAP"

 17 
 on: March 14, 2019, 10:43:46 AM 
Started by RafiRomero - Last Post by RafiRomero
That's great, thanks for your fast and extremely informative answers!

 18 
 on: March 12, 2019, 12:57:45 PM 
Started by RafiRomero - Last Post by Kaetemi
Generally it will be running tight loops where it waits for the co processor to finish. It'll be easiest to just put a 1ms sleep in those loops. You may also put the 1ms wait in the "Idle" function of your app instead, since that gets called during tight loops (Create an Idle slot under App.main, double click to go to user code, and put in the sleep code).

The main loop builds a new display list for each frame, which is necessary for animating widgets. Ideally the render portion of the loop will be called at the same rate as the frame rate.

An alternative could be to do a blocking wait on the main thread, instead of spinning the thread, and make use of the interrupt output pin of the EVE chip to resume the thread, but that may involve some platform specific code.

 19 
 on: March 11, 2019, 01:35:03 PM 
Started by RafiRomero - Last Post by FTDI Community
Hello,

I would suggest that if you are not using touch controls that it would be fine to add a Sleep to the main loop.
Adjusting for your desired refresh rate would be acceptable.

Best Regards,

FTDI Community

 20 
 on: March 11, 2019, 11:54:42 AM 
Started by RafiRomero - Last Post by RafiRomero
I'm running the exported code from EVE Screen Designer (4.5 Beta 2) on a BeagleBoard running Linux (I've adapted some of the HAL).
It's running fine, but using 100% of the CPU, because FT_Esd_MainLoop is running a tight loop with no yield or sleep.
I am wondering if it is OK to add a sleep in the main loop?
If so, is there some constraint as to how often I need to let the main loop run, or does it just need to be fast enough to redraw the screen at the rate I require (so, 1Hz would probably be fine for my application, but I'll probably run it rather faster)?
I'm not using touch controls.

Pages: 1 [2] 3 4 ... 10