Hello,

Thank you for the clarification, let me just double check with the developers the best way to achieve this.

Best Regards,
BRT Community

Hello,

Thank you for your questions.
I will look into why the export feature is causing errors when a CMD_PLAYVIDEO command is included.

For your first question, the export code feature can be very useful, however it would help to know what your target MCU is to be able to advise further.

Eve Screen Designer uses our Video converter utility (now incorporated into EVE Asset Builder) to convert the .AVI file into an EVE compatible format. A general use case is to convert the video and store this converted asset in flash/RAM_G, you can then use the CMD_PLAYVIDEO to play the video using either the OPT_MEDIAFIFO or OPT_FLASH option to tell the co-processor where the video data is stored and where to stream it in from.

I will need to contact the development team to query how Eve Screen Designer simulates using a video from flash memory as i do not believe that it currently supports uploading flash images to the development board.

When using flash as the source for your video file you require  '#define ADDR_VIDEO 4096'. This does denote the location in flash where the video file is stored and is used in the subsequent command:
   
      Gpu_CoCmd_FlashSource(phost, ADDR_VIDEO);

Unfortunately when streaming the video from flash you cannot set ADDR_VIDEO to be a filename.

I have attached a set of examples which covers various ways of streaming video with EVE.

Best Regards,
BRT Community

Hello,

All the rendering and touch handling activities are processed in a periodically running thread.

To handle the interrupt from MPU/MCU, users shall introduce the interrupt handler and update
a global variable to capture the changes. When the GUI thread is scheduled, the UI will be rendered
according to the updated value in the global variable. 


Best Regards,
BRT Community

Hi,

Yes, it is recommended to keep your own graphics states in a structure for example and you can then update and read the values there throughout the rest of your application. Your calls to set FG colour etc can then use the values from your structure. This will make the code easier to maintain too and also means you can check the value without a SPI access. I'm afraid you are not able to read the values back but we find the structure to be a good way.

Best Regards, BRT Community

Hi Rudolph, Everyone,

Good News - we've got the new page live now and you can find the datasheet and programmers guide on this page below:

https://brtchip.com/bt81x/

The programmers guide includes both BT815/6 and BT817/8 but has notes on features which are BT817/8 only,

Best Regards, BRT Community

Hello,

Thank you for your comments and suggestions, I will pass these onto the development team.

As for point 5, yes it is possible to display bitmaps on the BT81x without a connected NOR Flash IC. You can store the bitmap data on your MCUs flash and load these into RAM_G as desired (we normally recommend loading any graphics assists into RAM_G during your initialization sequence), please see the following:
AN 314 FT800 Advanced-Techniques Working-with-Bitmaps

Section 7 of the following application note also has some image examples where the image is loaded into RAM_G from the MCU:
BRT AN 014 - FT81X Simple PIC Library Examples

Best Regards,
BRT Community

Hello,

Yes this is the correct approach.
We have a porting guide for the previous version of ESD which you can reference:
https://brtchip.com/wp-content/uploads/Support/Documentation/Application_Notes/Modules/EVE/BRT_AN_001-ESD-3.0-Exported-Project-Porting-Guide.pdf

Customers shall look into the function “Esd_Loop” in file “Ft_Esd_Core.c” to see which slots to be called periodically.

You can find the main function which is the entry to the application in the Ft_Esd_Support.c file.

In FreeRTOS, this main function shall be renamed and invoked by a RTOS thread, this should be scheduled to be higher priority to get fast response.

For App structure initialization, please see the attached picture. It is allocated statically in heap while the application is initialized.


Best Regards,
BRT Community

Hello,

It looks like the SPI master init is failing, which is causing the subsequent calls to return a FT4222_IS_NOT_SPI_MODE error.
Replacing the FT4222 Lib/DLL files in the project normally resolves this issue.

Are you by any chance using a USB 3.0 port on a windows 7 machine?

Best Regards,
BRT Community