BRT Community

Hello,

I modified a font, Reglo-Bold, adding a "degree" symbol but I'm unable to actually display it.  For some reason, depending on how I try to display it, it'll show up as a '0'.  I'm confident the symbol is there and in the correct position.  I viewed the images created by EVE Asset Builder v2.10.2 and it's there.

FontFolio Screenshot
You cannot view this attachment.

EVE Asset Builder Preview Last Screenshot
You cannot view this attachment.

EVE Asset Builder Font Index HTML Screenshot
You cannot view this attachment.

I've tried a bunch of different ways to display it:

snprintf(buf, sizeof buf, "%d " "\u00B0" "   F", temperature);
TFT_qspi_cmd_text(75, 120, 31, EVE_OPT_CENTERY, buf);

I'm not really sure what I'm doing wrong or maybe something like this isn't possible?

Any insight would be greatly appreciated.

Kindest regards.

Ok, this could answer to this topic: http://www.brtcommunity.com/index.php?topic=428.msg2117#msg2117

I've seen that issue is resolved in new version of ESD in Esd_Render function.

Thanks, so it was the "Display list instruction overfetch".
I even already had BRT_TN_005_BT81x_Errata_Technical_Note.pdf.

I just was not looking under https://brtchip.com/document/technical-notes/ , maybe add (Errata) to that one as well?

Oh, and another small thing, "Programming and User Guides" is sorted by date, newest on top, could that perhaps be done on "IC Data Sheets" and "Application Notes" as well?

Hello,

Details of the Errata can be found in the following Technical notes:

BRT_TN_005_BT81x_Errata_Technical_Note

BRT_TN_006_BT88x_Errata_Technical_Note

best Regards

BRT Community Admin

This seems important... so I am boosting this post.

Introduction

Adding a graphical touch HMI (Human Machine Interface) to a product is a great way to enhance the user experience. But the benefits go way beyond this: It adds flexibility to accommodate new features (both now and in future), helps overcome obsolescence of traditional controls, and enables a family of products to share a common HMI platform with strong brand visibility, while remaining easily customizable and supporting multiple languages.

Thanks to the innovative Embedded Video Engine (EVE) from Bridgetek, designing or updating products with a graphical touch display interface is fast and easy to do, even when the engineers have no prior experience with touch screen graphical HMIs. The graphical display, touch and even audio can be added to the existing MCU over SPI or Quad-SPI (QSPI). Along with extensive design software tools and examples, this solution ensures the product can benefit from the advantages in a short timescale.

Learn More : https://brtchip.com/discover-the-new-intelligent-display-panels-idp-from-bridgetek/

I recently found this:
https://brtchip.com/wp-content/uploads/2024/04/Errata-notification-2024-R2.pdf

It states:
"We are reaching out to notify an important Errata that has been identified on our BT81x / BT88x series. This
Errata pertains to specific user applications, which may affect the functionality or performance of the product
under certain conditions."


What this does not state is what the actual issue might be.
So, what is it?

Given the date of release this could appear in a version of BT81X programming guide later than 2.4.
But I don't see anything in the 2.5, 2.6 or 2.7 history that indicates an issue.

I vaguely recall seeing extra DISPLAY commands added to the end of the command list to address some issue, is this related to this erratum?

no up on this?

The PCB800099 has arrived and five minutes later I realized that I am not prepared.
I need a cable with 2mm 30pin headers on both side.
And checking the pinout of CN2 on the VM820C and the LVDS pinout on the PCB800099, these are almost the same, except that polarity is different for all signals, so _P and _N swapped.

Unfortunately 30pin to 30pin LVDS cables apparently are rare, could not find any for speedy delivery, looks like I will be soldering tomorrow...

Edit: looking for information for the PCB800099 I came across a list on Alibaba.com for exactly the board I have with the exact same silkscreen and the "30P LVDS Interface connector: Pin definition:" contradicts the silkscreen - oh dear.