Hello,

Yes, the append technique in AN_340 is one of the best ways to do this,

Which EVE device do you use? The BT817/8 also have a more advanced version of this where you can store sections of command list (as well as section of display list) and this can make it even easier

However, the Append can be used on all EVE devices in any case if you use other models apart from BT817/8.

We also have an example of the same technique as AN_340 where we draw the chart line and the numerical values here using append whilst the other static items are stored:
https://brtchip.com/wp-content/uploads/Support/Documentation/Application_Notes/Modules/EVE/AN_356-FT800-Interfacing-I2C-Sensor-to-VM800P.pdf

Best Regards, BRT Community

Hello!

I'm trying to find a way how to update part of displayed screen (i.e. change only some values on displayed screen or status of displayed button). I don't want each time send whole display list. I found a document "APPLICATION NOTE AN_340 FT800_Optimising screen updates with Macro and Append" given by Bridgtech.
In my example I want change only values for displayed labels. Could you advise me if gives other possibility how to update choose parts of the showed screen ?

void showScreen ()
{
uint32_t coordinates = Gpu_Hal_Rd32(phost, REG_TOUCH_SCREEN_XY);
uint8_t Read_tag = Gpu_Hal_Rd8(phost, REG_TOUCH_TAG);
uint16_t x_coordinate, y_coordinate;

x_coordinate = (coordinates >> 16);
y_coordinate = coordinates;

Gpu_CoCmd_Dlstart(phost); //Start the display list

App_WrCoCmd_Buffer(phost, CLEAR(1, 1, 1)); //Command CLEAR is recommended to be used before any other drawing operation,
//in order to put the graphics engine in a known state.
//The end of the display list is always flagged with the command DISPLAY


Gpu_CoCmd_Gradient(phost,0, 0, 0x636363UL, 0, DispHeight, 0x222222UL);

Gpu_CoCmd_Number(phost, 20, 20, 28 , 0, coordinates);
Gpu_CoCmd_Number(phost, 20, 40, 28 , 0, x_coordinate);
Gpu_CoCmd_Number(phost, 20, 60, 28 , 0, y_coordinate);
Gpu_CoCmd_Number(phost, 20, 80, 28 , 0, Read_tag);

App_WrCoCmd_Buffer(phost, DISPLAY()); //instruct the graphics processor to show the list
Gpu_CoCmd_Swap(phost); //make this list active
App_Flush_Co_Buffer(phost);
Gpu_Hal_WaitCmdfifo_empty(phost);
}

Thank you in advance!

Hi, did you get any new information about that compatibility topic?

Elevators, the unsung heroes of vertical transport, are all getting an upgrade.
Say goodbye to traditional interfaces and hello to the future of lift controls!
 
🔍 Curious about how this transformation is happening?
Click the link below to discover more! 👇
Learn more here: https://bit.ly/Elevate-your-Lift-Controls-with-EVE

#Bridgetek #EVE #DisplayController #ElevatorDisplay #ElevatorUI #Innovation #HMI

I have to drive, for a 5" 800x480 TFT IPS 1000nits RGB 40pin, the backlight which requires Vf=30V, If=40mA (array of 2x10 white LEDs).

Can you help me find the right led driver?

Chip used: BT817Q

Hi!

I have Riverdy's EVE4 IPS 10.1" LCD TFT (type RVT101HVBNWC00-B), which is run by BT817Q.

I noticed that my application can not take full advantage of DL memory in BT817Q.

To further investigate the problem I wrote simple test program:

   printf("\r\n ------------------------------------------------ \r\n");
uint32_t c = 1091;
//uint32_t c = 2038;


Gpu_Copro_SendCmd(phost, CMD_COLDSTART);
Gpu_Copro_SendCmd(phost, CMD_DLSTART);
Gpu_Copro_SendCmd(phost, CLEAR_COLOR_RGB(0, 0, 0));
Gpu_Copro_SendCmd(phost, CLEAR(1, 1, 1));

for(uint32_t i = 0; i < c; i++)
{
Gpu_Copro_SendCmd(phost, NOP());
//Gpu_Copro_SendCmd(phost, TAG(1));
}

Gpu_Copro_SendCmd(phost, COLOR_RGB(255, 0, 0));
Gpu_Copro_SendCmd(phost, VERTEX_FORMAT(3));
Gpu_Copro_SendCmd(phost, BEGIN(LINE_STRIP));
Gpu_Copro_SendCmd(phost, LINE_WIDTH(5 * 16));
Gpu_Copro_SendCmd(phost, VERTEX2F(10 * 8, 10 * 8));
Gpu_Copro_SendCmd(phost, VERTEX2F(500 * 8, 500 * 8));
Gpu_Copro_SendCmd(phost, END());

Gpu_Copro_SendCmd(phost, DISPLAY());
Gpu_Copro_SendCmd(phost, CMD_SWAP);

uint32_t reg_REG_CMD_DL = Gpu_Hal_Rd32 (phost, REG_CMD_DL);

printf("reg_REG_CMD_DL = %d        c = %d \r\n", reg_REG_CMD_DL, c);

If I run this program I can go with variable “c”, which is filling up DL memory with dummy NOP command up to value 1091. If “c” becomes 1092, red line on screen starts having artifacts.

Printf command for last stable c = 1091 returns:

reg_REG_CMD_DL = 4404        c = 1091

So here we have magical upper limit of DL’s memory at 4404 bytes. 

This is strange because DL's size should be 8191, according to manual.

Further tinkering revealed that if I fill DL’s memory with another dummy command like TAG(1) behaviour changes.

For instance if I remove lines of code (comment them):

uint32_t c = 1091;
…and
Gpu_Copro_SendCmd(phost, NOP());

…and uncomment lines:
//uint32_t c = 2038;
…and
//Gpu_Copro_SendCmd(phost, TAG(1));

…my test application behaves as expected. I can go with variable “c” up to 2038.

In this case printf returns:

reg_REG_CMD_DL = 8191        c = 2038

…for last stable “c”. For c = 2039 and above, screen turns black, i.e. DL’s memory overflows.

Can somebody explain this?

I my actual application I am not filling DL’s memory with dummy code like in above example, instead I am filling it up with graphics primitives (lines, dots, circles etc), however when DL’s fullness reaches 4404, display starts displaying gibberish.

The Embedded Video Engine (EVE) by Bridgetek revolutionises graphics control, offering full-color Graphics, Touch, and Audio in one IC.
It's like a Graphics card with Touch Screen and Sound for any MCU.

Connect via SPI for easy integration into your design, ideal for updating older designs or creating new user-friendly interfaces.

Key Features:

• Graphics: Enhance UI with color displays
• Touch: Intuitive control with touch screen
• Audio: Play various tones with minimal MCU effort

Start with our development modules: https://brtchip.com/search-products/?product_cate=21&keyword_search=&interface=&packages=&usb_speed=&usb_class=&io_connector=&action=get_system_ajax

For comprehensive understanding and support, visit our revamped page covering EVE's capabilities, including comparison tables and guidance on display, touch, and audio functionalities: https://brtchip.com/getting-started/

Learn more about our EVEs through this comparison table: *https://brtchip.com/getting-started/#module
*Copy and paste this link if you face trouble navigating to it.

Hi,
Yes, unlike the compressed png/jpg formats, the compressed file for an inflate could have different types of content and so there will not be standard image data in all cases. As Rudolph mentioned, since you will create the file in most cases, you can include our own header containing the details before compressing, and then when using it in EVE, you can parse that after inflating it (and then exclude that header data when you display the resulting raw image in EVE).

Best Regards, BRT Community

CMD_INFLATE "only" unpacks data so the only information you can get additionally is the end address using CMD_GETPTR and therefore you could calculate the size of the uncompressed file.
So what you could do is to add extra information in front or after the data before compressing it.

Hello,

Regarding the issue with your text, your matrix will be getting applied to the following items too and so one suggestion is to revert the matrix to the identity matrix again via
CMD_LOADIDENTITY
CMD_SETMATRIX
before you proceed to draw the other items such as text which you do not want to be rotated,

Best Regards, BRT Community