Hello Aneesh,

Note that this is the community forum for Bridgetek, not FTDI.
The FTDI community forum can be found here:

https://www.ftdicommunity.com/

Anyway the reset pin is usually controlled by hardware.
It's active low so pulling it low will put the device into reset and pulling it high will bring it out of reset.

What is the AN pin?

If you are looking for APIs see below.

Virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC.  Application software can access the USB device in the same way as it would access a standard COM port.
D2XX drivers allow direct access to the USB device through a DLL.  Application software can access the USB device through a series of DLL function calls.  The functions available are listed in the D2XX Programmer's Guide document which is available from the Documents section of this site.

However, please note that FTDI have not produced a programmer's guide for VCP drivers due to the large amount of documentation available from Microsoft on serial communication.  Please refer to our Related Links page for more information.

Best Regards,
BRT Community

Hello,

Thanks for the feedback. I will pass to our R&D team for consideration.

Best Regards,
BRT Community

Hello,

The developers are struggling to recreate this issue.

I believe it may be related to multiple iterative installations of ESD on the same PC.

Can I get you to try uninstalling ESD and deleting the 'EVE Screen Designer' folder from Documents, then re-installing ESD 4.12 onto your machine?

Please let me know if this helps.

Best Regards,
BRT Community

Hello,

These are known limitations.

ESD label is not providing the support to all the parameters from hardware commands.

We will work on this in future.

Best Regards,
BRT Community

Hello,

EVE Screen Designer 4.12 has been released and can be downloaded at the following:
https://brtchip.com/esd/

Best Regards,
BRT Community

Hello Rudolph,

There is some pseudo code in the programmers guide which covers how the address's are calculated:

struct xfont {
 uint32_t signature,
 uint32_t size,
 uint32_t format,
 uint32_t swizzle,
 uint32_t layout_width,
 uint32_t layout_height,
 uint32_t pixel_width,
 uint32_t pixel_height,
 uint32_t start_of_graphic_data;
 uint32_t gptr[];
 uint32_t wptr[];
};
uint32_t cp_address(xfont *xf, uint32_t cp)
{
 uint32_t bytes_per_glyph;
 bytes_per_glyph = xf->layout_width * xf->layout_height;

 if (xf->start_of_graphic_data >= 0x800000)
 //if the graphic data is in flash
 return (xf->start_of_graphic_data +
 xf->gptr[cp / 128] +
 bytes_per_glyph * (cp % 128) / 32);
 else
 //if the graphic data is in RAM_G
 return (xf->start_of_graphic_data +
 xf->gptr[cp / 128] +
 bytes_per_glyph * (cp % 128));
}
uint32_t cp_width(xfont *xf, uint32_t cp)
{
 return *(
 (uint8_t*)xf +
 xf->wptr[cp / 128] +
 (cp % 128));
}
I am still trying to clarify the other issues with the developers.

Best Regards,
BRT Community

Hello,

Thank you for your feedback.
I will look to get the user guide updated accordingly.

Best Regards,
BRT Community

Hello,

Thank you for your question.

Can you just clarify if you are using an ESD global variable or a global variable within your MCU to store the dark mode state of the page?

Best Regards,
BRT Community