BRT Community

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.

Unit: EVE3x-39A-BLH-TPC
Company: EFJohnson Technologies
Website: https://www.smode.io

Smode Media Server using the EVE3x-39A-BLH-TPC, a 3.9" 1U USB Interface, 480x128 Graphic Bar TFT Display 1U, Capacitive Touch with a 1000cd/m2 Sunlight Readable backlight!



You cannot view this attachment.

You cannot view this attachment.

At Bridgetek, we specialize in innovative bridging and HMI technologies—including our powerful Embedded Video Engine (EVE) ICs and modules. In this video, we showcase a smart home controller built on the IDP-1000-04A smart display module, powered by our BT817 graphics controller.

Looking to create robust, high-resolution graphical user interfaces (GUIs) for challenging environments like automotive or medical applications? Discover the power of Bridgetek's BT817A Embedded Video Engine (EVE), an AEC-Q100 qualified solution designed for reliability and performance.

In this video, we showcase our BT817A-based bedside monitor demo, highlighting its smooth, real-time screen updates, intuitive touch interactions, and multi-language support. See how the BT817A's extensive graphics capabilities allow you to build feature-rich UIs using cost-effective MCUs, such as the Raspberry Pi RP2040 on our MM2040 EV module.

Unlock Powerful Embedded Graphics with Bridgetek FT800 EVE!

Integrate stunning Human-Machine Interface (HMI) solutions and embedded graphics into your products seamlessly. This video introduces Bridgetek's FT800 Embedded Video Engine (EVE) ICs and modules, simplifying user interface (UI) development without complex, graphics-heavy MCUs.

Discover how the FT800 empowers you to effortlessly add vibrant graphics, responsive touch capabilities, and audio to virtually any microcontroller. We showcase the IDM2040-21R module, featuring the FT800 driving a crisp 2.1-inch circular color screen, perfect for smart home controls and other intuitive applications. See firsthand how EVE's intelligent touch tagging and tracking features handle the heavy lifting, allowing you to create sophisticated UIs with cost-effective MCUs that lack onboard graphics.

Hi Nick,

Thanks for posting your findings, our R&D team are currently checking on this and we'll post a reply very soon,

Best Regards, BRT Community

Hi,

My success getting responses from this forum is not good so far so I might be wasting my time, but I'll try..

I believe there's a bug in one of the source modules for FT_Eve_Hal in ESD. When using display lists in ESD the following fail to compile due to unknown type argb32_t:

EVE_CoDl_colorArgb_ex and EVE_CoDl_clearColorArgb_ex. Other display lists that set color have the same issue.

I found an old thread probably related to this that refers to a change of type name.

I was able to fix compilation and get display lists correctly assigning colour with this change:

// Colour type fixed by Nick
//ESD_PARAMETER(c, Type = argb32_t, DisplayName = "Color")
ESD_PARAMETER(c, Type = ft_argb32_t, DisplayName = "Color")

That's in EVE_CoDl.h. Anyone who cares should be able to find the issue I'm referring to, and the several places where the same problem arises.

Nick

Hi Paul,

I was really hoping for a general explanation of the points that I had asked about, having overcome the problem that I initially encountered.

Thanks,
Nick