BRT Community

Quote
Writing Blob file ".\unified.blob" to BT81X Flash Storage
Error, Flash is not able to get into full mode
Fail to write Blob file ".\unified.blob" to BT81X Flash Storage
Existing ...
----

Oh yes, that "Existing" is a typo in the flashtool. :-)

That typo is not seen on my version EAB 1.0.  You might be using old version.

Quote from: exatech on August 05, 2019, 04:15:51 PM
Thanks,
but as I mentioned: the asset builder cannot connect to my board. So, I need my host processor to install the blob. How can I do that?
best regards,
Henk

Asset Builder requires the FT4222 or MPSSE enabled module to be connected with EVE module.    If you need install the blob,  you may just download the "unified.blob" file which is located at installation path of EAB to RAMG_G,  and call the cmd_flashupdate to program it to flash, assuming the cmd_flashattach has been issued successfully and the flash is in Basic mode.

I think the best way to achieve your desired effect is to send different display list to EVE, other than utilizing the cmd_screensaver command,  providing the MCU is still active during screensaver phase.


uint16_t cmd_buff_write = Gpu_Hal_Rd16(g_phost, REG_CMD_WRITE); //Get the write pointer of command buffer
Gpu_CoCmd_GetProps(g_phost, 0, 0,0); //Send the command cmd_getprops
App_Flush_Co_Buffer(g_phost);     
Gpu_Hal_WaitCmdfifo_empty(g_phost);  //wait till the command is executed (cmd_read==cmd_write)

printf("write point of cmd is %d\n", cmd_buff_write);
printf("coCmd_GetProps = 0x%x\n", Gpu_Hal_Rd32(g_phost,   RAM_CMD + cmd_buff_write));
printf("coCmd_GetProps+4 = 0x%x\n", Gpu_Hal_Rd32(g_phost, RAM_CMD + cmd_buff_write+4));
printf("coCmd_GetProps+8 = 0x%x\n", Gpu_Hal_Rd32(g_phost, RAM_CMD + cmd_buff_write + 8));
printf("coCmd_GetProps+12 = 0x%x\n", Gpu_Hal_Rd32(g_phost,RAM_CMD + cmd_buff_write + 12));


Here is my code immediately following the cmd_loadimage. It works well and get the expected result.
Hope it is helpful.

"cmd_loadimage" decodes PNG into various image formats based on the PNG image properties.  It might be in
Paletted4444, or L8 or RGB565.   So user may need use cmd_getprops to retrieve the decoded size to calculate the next available address.

To use cmd_getprops, please see the example in "cmd_regread". It is common practice to read the output parameter from EVE coprocessor buffer.

Hi Rudolph,

    I searched the website and found Riverdi provides that 7inch display panel ,which might be what you want.  see:
https://riverdi.com/product-category/eve/?filter_graphics-controller=bt81x-eve-3&filter_size-inch=7&query_type_size-inch=or

It is open source and works perfectly on latest BT81X, check it out:

https://github.com/kaetemi/nuklear_eve

Hi Rudolph,
     For EVE bitmap format,  the alpha channel is kept in the following formats, ARGB1555, PALETTED, ARGB4, ARGB2 and ASTC(BT81X).   If you want to keep the alpha channel, you may try EAB to convert it into the formats above.   ASTC4x4 shall be good enough for you.

     Best Regards
      Paul J

It may be caused by bitmap limitation of ASTC format in flash. ASTC bitmaps in flash must be 64-bytes aligned. In particular , fonts in flash must use a multiple of four ASTC blocks per character.   So the suggestion is to load the glyph into RAM_G and change the offset 32(start_of_graphics_data) of xfont to the glyph address of RAM_G. The glyph in RAM_G has no such limitation and it shall work.

QuoteBut that does not happen when I do build and update to hardware in eve screen designer 4.5 beta 2.

do you mean upload the .exe file into the ME813AU board? 
If you want to work with FT90X platform, beside building in ESD,  you need a SD card to store all the EVE assets, such as the converted image data.  All the assets shall be at root directory of SD card.

Quote
There are 21 reserved bits in VERTEX_FORMAT.
Bit 3 could have been used to change the format of VERTEX2F:
Bit 0...13 = Y
Bit 16...29 = X

With 1 bit less in resolution as a trade-off the frac-value of 0 would be -8192 to 8191, same as 1 and so the maximum pixel precision would be 1/8 pixel.

I think your idea shall be Bit 2 (starting from Bit 0) ,i.e. the THIRD bit, other than bit 3 is used in VERTEX_FORMAT.
But I do not know what benefit it may bring to you.

please try to put the image data into the SAME folder with the project binary ,for example "myProject.exe".