- Welcome to BRT Community.
News:
Welcome to the Bridgetek Community!
Please read our Welcome Note
Technical Support enquires
please contact the team @ Bridgetek Support
Please refer to our website for detailed information on all our products - Bridgetek - Bridging Technology
Recent posts
#51
General Discussion / FT813 GUI Development Workflow
Last post by Nick - June 24, 2025, 09:21:14 AMHi,
Following on from my introduction here a few months ago, I've now completed my STM32H755 PCB design (and bringup) and I want to start on the GUI development. My display is a Riverdi 800x480 capacitive touch with FT813 and I'm using SPI (1).
I've gone through several of the ESD tutorial videos on YouTube and have been looking at the documents. There's a lot of information to digest and without reading a lot more than I have already I'm not really getting the confidence that I want to know that I'm going in the right direction.
Firstly, my target platform is a custom PCB using STM32H7 with the display and EVE chip mentioned above. ESD wants me to define several aspects of my h/w: host processor, EVE platform, Flash memory etc.. whereas the only thing that seems relevant to me is that I'm using FT813 and I see now way to select a configuration that correlates well with my hardware. Should I worry about this? May I find in future that I can't generate code for my platform?
Secondly, is ESD the best place to start with my GUI, or should I firstly use ESE? I know what I want to implement and don't particularly feel the need to prototype screen layouts. I suppose I'm still unclear about how ESE fits into the development process.
In what I've read so far, the ESD tutorials and examples seem self contained and with no data input/output to/from the host applications. A key requirement of my system is to show real-time views of spectrograms 2D heat maps, so frame-by-frame updates of charts and bit-maps will be needed. Are there any examples that show these kind of data interactions with the GUI?
My overall impression is that GUI dev with the EVE tools that I've seen is quite far from my past experience of WYSIWYG design, with a considerably steeper learning curve. Any tips on how best to get up that curve would be very much appreciated.
Thanks in advance,
Nick
Following on from my introduction here a few months ago, I've now completed my STM32H755 PCB design (and bringup) and I want to start on the GUI development. My display is a Riverdi 800x480 capacitive touch with FT813 and I'm using SPI (1).
I've gone through several of the ESD tutorial videos on YouTube and have been looking at the documents. There's a lot of information to digest and without reading a lot more than I have already I'm not really getting the confidence that I want to know that I'm going in the right direction.
Firstly, my target platform is a custom PCB using STM32H7 with the display and EVE chip mentioned above. ESD wants me to define several aspects of my h/w: host processor, EVE platform, Flash memory etc.. whereas the only thing that seems relevant to me is that I'm using FT813 and I see now way to select a configuration that correlates well with my hardware. Should I worry about this? May I find in future that I can't generate code for my platform?
Secondly, is ESD the best place to start with my GUI, or should I firstly use ESE? I know what I want to implement and don't particularly feel the need to prototype screen layouts. I suppose I'm still unclear about how ESE fits into the development process.
In what I've read so far, the ESD tutorials and examples seem self contained and with no data input/output to/from the host applications. A key requirement of my system is to show real-time views of spectrograms 2D heat maps, so frame-by-frame updates of charts and bit-maps will be needed. Are there any examples that show these kind of data interactions with the GUI?
My overall impression is that GUI dev with the EVE tools that I've seen is quite far from my past experience of WYSIWYG design, with a considerably steeper learning curve. Any tips on how best to get up that curve would be very much appreciated.
Thanks in advance,
Nick
#52
Discussion - EVE / FT81x/BT81x and BT820 Seleae L...
Last post by Rudolph - June 22, 2025, 07:07:49 PMI implemented High Level Analyzers for Saleae Logic 2: https://github.com/RudolphRiedel/Saleae_Logic_HLA
There are two variants, EmbeddedVideoEngine is for FT81x/BT81x and EmbeddedVideoEngine5 is for BT820.
Not perfect or complete, but well, it decodes some stuff, when saving the .csv from the trace I get extra data like this for BT820:
BOOTCFGEN
SETTBOOTCFG
SETDDRTYPE
BOOTCFGEN
SETPLLSP1
SETSYSCLKDIV
ACTIVE
READ REG_BOOT_STATUS Decompressing rom asset image to DDR
READ REG_BOOT_STATUS Attempting to attach to flash
READ REG_BOOT_STATUS Normal running
WRITE REG_PWM_DUTY 0x00000020
WRITE REG_HSIZE 0x00000400
WRITE REG_DISP 0x00000001
WRITE RAM-DL+0x0000 DL_CLEAR_COLOR_RGB 0x000000
WRITE RAM-DL+0x0004 DL_CLEAR 0x000007
WRITE RAM-DL+0x0008 DL_DISPLAY 0x000000
WRITE REG_DLSWAP 0x00000002
WRITE REG_SO_EN 0x00000001
READ REG_CMDB_SPACE 0x3FFC
WRITE REG_CMDB_WRITE CMD_INFLATE
WRITE REG_CMDB_WRITE 0xD8E5DA78
READ REG_CMDB_SPACE 0x3F6C
READ REG_CMDB_SPACE 0x3FFC
WRITE REG_CMDB_WRITE CMD_LOADIMAGE
WRITE REG_CMDB_WRITE 0xE0FFD8FF
READ REG_CMDB_SPACE 0x3FFC
WRITE REG_CMDB_WRITE CMD_NEWLIST
WRITE REG_CMDB_WRITE DL_TAG 0x000000
There are two variants, EmbeddedVideoEngine is for FT81x/BT81x and EmbeddedVideoEngine5 is for BT820.
Not perfect or complete, but well, it decodes some stuff, when saving the .csv from the trace I get extra data like this for BT820:
BOOTCFGEN
SETTBOOTCFG
SETDDRTYPE
BOOTCFGEN
SETPLLSP1
SETSYSCLKDIV
ACTIVE
READ REG_BOOT_STATUS Decompressing rom asset image to DDR
READ REG_BOOT_STATUS Attempting to attach to flash
READ REG_BOOT_STATUS Normal running
WRITE REG_PWM_DUTY 0x00000020
WRITE REG_HSIZE 0x00000400
WRITE REG_DISP 0x00000001
WRITE RAM-DL+0x0000 DL_CLEAR_COLOR_RGB 0x000000
WRITE RAM-DL+0x0004 DL_CLEAR 0x000007
WRITE RAM-DL+0x0008 DL_DISPLAY 0x000000
WRITE REG_DLSWAP 0x00000002
WRITE REG_SO_EN 0x00000001
READ REG_CMDB_SPACE 0x3FFC
WRITE REG_CMDB_WRITE CMD_INFLATE
WRITE REG_CMDB_WRITE 0xD8E5DA78
READ REG_CMDB_SPACE 0x3F6C
READ REG_CMDB_SPACE 0x3FFC
WRITE REG_CMDB_WRITE CMD_LOADIMAGE
WRITE REG_CMDB_WRITE 0xE0FFD8FF
READ REG_CMDB_SPACE 0x3FFC
WRITE REG_CMDB_WRITE CMD_NEWLIST
WRITE REG_CMDB_WRITE DL_TAG 0x000000
#53
Discussion - EVE / Re: BT82x
Last post by Rudolph - June 20, 2025, 01:10:18 PMBRT_AN_086_BT82X-Series-Programming-Guide is out in version 1.1 and I am going over it now.
Here are my observations:
1) The memory region RAM_ERR_REPORT was renamed to RAM_REPORT.
2) The "BT82X data flow" was updated and one detail is that RAM_CMD and RAM_DL are documented to use SRAM.
Which has no user-level implications, but makes me wonder if the whole region from 0x7F000000 to wherever is SRAM.
3) RAM_G is documented to go from 0x00000000 to 0x7EFFFFFF, DDR3 "only" goes to 8Gbit, so RAM_G can "only" go to 0x3FFFFFFF.
4) Host command RESET_PULSE was added.
5) The Initialization Sequence given in the programming guide is different to what the Bridgtek examples are using.
https://github.com/Bridgetek/Eve-MCU-Dev/tree/bt82x-dev
https://github.com/Bridgetek/python-bt82x-dev/tree/development
Not fundamentally, but this is still a bit strange.
from EVE_HAL.c:
The order should not really matter, but I do wonder why RESET_PULSE is in there and why it is placed directly before ACTIVE.
6) REG_LVDSTX_PLLCFG
Following the updated register description for REG_LVDSTX_PLLCFG my code works now.
LVDSPLL_NS went from "Progammable loop divider" to RESERVED with a fixed value of 7, whatever this actually does.
And "Table 21 - LVDSTX Clock Configuration" also has "(scanclk_2x / 2)" under "LVDSTX clock (MHz)".
So, the multiplier is actually the system-pll multiplier which means that for the pixel clock you can only setup 576MHz / (TXLDVIV + 1) - unless you change the system-pll multiplier.
That is pretty bad in regards of the resolution of the pixel-clock, especially after the BT817.
The target for the 1024x600 I am currently using is 51.2MHz with min = 45MHz and max = 57MHz.
And practically the only options are 48MHz or 57.6MHz, as I really do not like the idea of lowering the system clock.
800x480: >25.2/25.4/37.2MHz -> set TXCLKDIV = 10 for 26.2MHz
800x480: >23/25/27MHz -> set TXCLKDIV = 11 for 24MHz
1024x600: >45/51.2/<57 MHz -> 48MHz
1024x768: >52/65/<71 MHz -> 57.6Mhz
1280x720: >57.1/58.1/85MHz -> 57.6MHz or 72MHz
1280x768: >55/60/<65 -> 57.6MHz
1280x800: >66.3/72.4/78.9 MHz -> 72MHz
1366x768: >66.9/72/<80 MHz -> 72MHz
1366x768: >63/76/<96 MHz -> 72MHz
Ok, getting these to work would not be an issue, only hitting 60Hz might.
And no, I do not have these, sourcing inexpensive displays with touch is still a major pain.
7) REG_TOUCH_MODE was removed from the Programming Guide
8 ) Microchip and TI touch controllers were removed from REG_TOUCH_CONFIG
9) REG_CTOUCH_TOUCHn_XY registers are still named 0/A/B/C/4 and not 0/1/2/3/4.
10) new register: REG_LVDSRX_CORE_FRAMES - LVDSRX frame counter - 8 bit value
11) REG_SYS_STAT had bit definitions removed
12) REG_I2S_CFG definition has LENGTH removed, 16-bit is the only supported format
13) REG_GPIO_DIR Bit 15 – 9 changed from "Unused" to "These bits control the direction of GPIO8 to GPIO15." -probably was meant to say GPIO9 to GPIO15
14) REG_GPIO Definition Bit 15 – 9 changed from "Unused" to "General purpose Input/Output pins"
15) The description for REGION has been greatly improved, but there still is no warning that the "dest" parameter is absolute which prevents display list fragments that were built from commands like CMD_TEXT to be used with CMD_APPEND since the translation to display list commands by the co-processor uses REGION for a couple commands now and the generated snippet is very unlikely to be placed at the exaxt same display list address.
16) the C prototypes of several commands are still wrong and use int16_t instead of uint16_t for parameters like width, height, radius and font which must not be negative
17) the C prototype of CMD_TEXTDIM still has this: void cmd_text( uint32_t dimensions ...
18 ) I only briefly checked this, but it looks like the inconsistencies I reported here: http://www.brtcommunity.com/index.php?topic=585.0 are still in place
Oh yes, what I did not mention so far is that there are indeed numerous improvements in the 1.1 version of the BT82x programming guide.
For example the explanation of the Swap Chains.
Here are my observations:
1) The memory region RAM_ERR_REPORT was renamed to RAM_REPORT.
2) The "BT82X data flow" was updated and one detail is that RAM_CMD and RAM_DL are documented to use SRAM.
Which has no user-level implications, but makes me wonder if the whole region from 0x7F000000 to wherever is SRAM.
3) RAM_G is documented to go from 0x00000000 to 0x7EFFFFFF, DDR3 "only" goes to 8Gbit, so RAM_G can "only" go to 0x3FFFFFFF.
4) Host command RESET_PULSE was added.
5) The Initialization Sequence given in the programming guide is different to what the Bridgtek examples are using.
https://github.com/Bridgetek/Eve-MCU-Dev/tree/bt82x-dev
https://github.com/Bridgetek/python-bt82x-dev/tree/development
Not fundamentally, but this is still a bit strange.
from EVE_HAL.c:
Code Select
// Reset the display
MCU_Delay_20ms();
HAL_PowerDown(1);
MCU_Delay_20ms();
HAL_PowerDown(0);
MCU_Delay_20ms();
// Set System PLL NS = 15 for 576MHz
HAL_HostCmdWrite(0xFF, 0xE4, 0x0F, 0x00, 0x00);
// Set System clock divider to 0x17 for 72MHz
HAL_HostCmdWrite(0xFF, 0xE6, 0x17, 0x00, 0x00);
// Set bypass BOOT_BYPASS_OTP, DDRTYPT_BYPASS_OTP and set BootCfgEn
HAL_HostCmdWrite(0xFF, 0xE9, 0xe1, 0x00, 0x00);
// Set DDR Type - 1333, DDR3L, 4096
HAL_HostCmdWrite(0xFF, 0xEB, 0x08, 0x00, 0x00);
// Set DDR, JT, AUD and WD in Boot Control
HAL_HostCmdWrite(0xFF, 0xE8, 0xf0, 0x00, 0x00);
// Clear BootCfgEn
HAL_HostCmdWrite(0xFF, 0xE9, 0xe0, 0x00, 0x00);
// Perform a reset pulse
HAL_HostCmdWrite(0xFF, 0xE7, 0x00, 0x00, 0x00) ;
// Set ACTIVE
HAL_HostCmdWrite(0x00, 0x00, 0x00, 0x00, 0x00) ;
// Delay ~100 mS
for (i = 0; i < 5; i++)
{
MCU_Delay_20ms();
}
The order should not really matter, but I do wonder why RESET_PULSE is in there and why it is placed directly before ACTIVE.
6) REG_LVDSTX_PLLCFG
Following the updated register description for REG_LVDSTX_PLLCFG my code works now.
LVDSPLL_NS went from "Progammable loop divider" to RESERVED with a fixed value of 7, whatever this actually does.
And "Table 21 - LVDSTX Clock Configuration" also has "(scanclk_2x / 2)" under "LVDSTX clock (MHz)".
So, the multiplier is actually the system-pll multiplier which means that for the pixel clock you can only setup 576MHz / (TXLDVIV + 1) - unless you change the system-pll multiplier.
That is pretty bad in regards of the resolution of the pixel-clock, especially after the BT817.
The target for the 1024x600 I am currently using is 51.2MHz with min = 45MHz and max = 57MHz.
And practically the only options are 48MHz or 57.6MHz, as I really do not like the idea of lowering the system clock.
800x480: >25.2/25.4/37.2MHz -> set TXCLKDIV = 10 for 26.2MHz
800x480: >23/25/27MHz -> set TXCLKDIV = 11 for 24MHz
1024x600: >45/51.2/<57 MHz -> 48MHz
1024x768: >52/65/<71 MHz -> 57.6Mhz
1280x720: >57.1/58.1/85MHz -> 57.6MHz or 72MHz
1280x768: >55/60/<65 -> 57.6MHz
1280x800: >66.3/72.4/78.9 MHz -> 72MHz
1366x768: >66.9/72/<80 MHz -> 72MHz
1366x768: >63/76/<96 MHz -> 72MHz
Ok, getting these to work would not be an issue, only hitting 60Hz might.
And no, I do not have these, sourcing inexpensive displays with touch is still a major pain.
7) REG_TOUCH_MODE was removed from the Programming Guide
8 ) Microchip and TI touch controllers were removed from REG_TOUCH_CONFIG
9) REG_CTOUCH_TOUCHn_XY registers are still named 0/A/B/C/4 and not 0/1/2/3/4.
10) new register: REG_LVDSRX_CORE_FRAMES - LVDSRX frame counter - 8 bit value
11) REG_SYS_STAT had bit definitions removed
12) REG_I2S_CFG definition has LENGTH removed, 16-bit is the only supported format
13) REG_GPIO_DIR Bit 15 – 9 changed from "Unused" to "These bits control the direction of GPIO8 to GPIO15." -probably was meant to say GPIO9 to GPIO15
14) REG_GPIO Definition Bit 15 – 9 changed from "Unused" to "General purpose Input/Output pins"
15) The description for REGION has been greatly improved, but there still is no warning that the "dest" parameter is absolute which prevents display list fragments that were built from commands like CMD_TEXT to be used with CMD_APPEND since the translation to display list commands by the co-processor uses REGION for a couple commands now and the generated snippet is very unlikely to be placed at the exaxt same display list address.
16) the C prototypes of several commands are still wrong and use int16_t instead of uint16_t for parameters like width, height, radius and font which must not be negative
17) the C prototype of CMD_TEXTDIM still has this: void cmd_text( uint32_t dimensions ...
18 ) I only briefly checked this, but it looks like the inconsistencies I reported here: http://www.brtcommunity.com/index.php?topic=585.0 are still in place
Oh yes, what I did not mention so far is that there are indeed numerous improvements in the 1.1 version of the BT82x programming guide.
For example the explanation of the Swap Chains.
#54
BRT News / Bridgetek | EVE BT820B
Last post by BRT Marketing - June 20, 2025, 07:14:04 AMReady to create stunning, high-resolution graphical user interfaces (GUIs) with integrated live video for your next product?
Dive into Bridgetek's BT820B, our cutting-edge 5th generation Embedded Video Engine (EVE), designed to revolutionize your UI development.
This video showcases how the BT820B simplifies adding advanced graphics, multi-touch capabilities, and high-fidelity audio to any microcontroller, eliminating the need for a costly MCU upgrade. Discover its powerful features, including LVDS output for displays up to 1920x1200, external DDR3 RAM for complex rendering, and support for various flash storage options.
A key highlight is the BT820B's direct LVDS video input, enabling seamless integration of high-resolution live video into your UI with real-time processing effects like brightening, darkening, and fisheye lens removal. See this in action with our engaging photo booth demo!
We also introduce the VM820C module and MN820 mini module, providing fast-track development and simplified integration into your final product, ensuring a quicker time to market. Explore diverse applications, from vehicle dashboards with live video to medical devices, kiosks, and smart home systems.
What you'll learn:
Elevate your product's user experience with the BT820B.
Watch now to see what's possible!
Connect with us:
Dive into Bridgetek's BT820B, our cutting-edge 5th generation Embedded Video Engine (EVE), designed to revolutionize your UI development.
This video showcases how the BT820B simplifies adding advanced graphics, multi-touch capabilities, and high-fidelity audio to any microcontroller, eliminating the need for a costly MCU upgrade. Discover its powerful features, including LVDS output for displays up to 1920x1200, external DDR3 RAM for complex rendering, and support for various flash storage options.
A key highlight is the BT820B's direct LVDS video input, enabling seamless integration of high-resolution live video into your UI with real-time processing effects like brightening, darkening, and fisheye lens removal. See this in action with our engaging photo booth demo!
We also introduce the VM820C module and MN820 mini module, providing fast-track development and simplified integration into your final product, ensuring a quicker time to market. Explore diverse applications, from vehicle dashboards with live video to medical devices, kiosks, and smart home systems.
What you'll learn:
- The advanced features of the BT820B, our latest 5th generation EVE device.
- How to integrate high-resolution graphics, touch, audio, and live video with any MCU.
- Benefits of the direct LVDS video input and its real-time processing capabilities.
- How Bridgetek's development modules can accelerate your product's time to market.
Elevate your product's user experience with the BT820B.
Watch now to see what's possible!
Connect with us:
- Website: https://brtchip.com/
- Getting Started with EVE: https://brtchip.com/getting-started/
- BRT Community Forum: http://www.brtcommunity.com/
- Bridgetek GitHub (Code Examples): https://bridgetek.github.io/
#55
BRT News / Bridgetek | EVE BT817 and BT81...
Last post by BRT Marketing - June 20, 2025, 07:11:40 AMLooking to implement high-resolution, robust graphical user interfaces (GUIs) in your automotive, medical, or industrial designs?
This video: https://youtu.be/j1bmvfDmDi0
Highlights Bridgetek's BT817 and BT817A Embedded Video Engines (EVE), specifically engineered for demanding applications.
Discover how these powerful EVE devices offer a 3-in-1 solution for adding high-resolution graphics, multi-touch capabilities, and audio to any microcontroller. We'll explore key features like 24-bit color support, non-square pixel displays, direct Quad SPI Flash attachment for large assets, and extensive image/font support for global customization.
A special focus is placed on the BT817A, our AEC-Q100 automotive-qualified device, showcasing its extended temperature range and suitability for critical applications. See a practical demonstration with our bedside patient monitor demo, illustrating smooth real-time updates and comprehensive UI possibilities even with cost-effective MCUs.
From vehicle dashboards and EV charging stations to medical devices and smart building systems, the BT817 and BT817A are designed to enhance product functionality and user experience with minimal design changes and a faster time to market.
What you'll learn:
Ready to build professional and resilient user interfaces for your advanced products?
Watch now to see how Bridgetek's BT817 and BT817A can help you achieve your goals!
Connect with us:
This video: https://youtu.be/j1bmvfDmDi0
Highlights Bridgetek's BT817 and BT817A Embedded Video Engines (EVE), specifically engineered for demanding applications.
Discover how these powerful EVE devices offer a 3-in-1 solution for adding high-resolution graphics, multi-touch capabilities, and audio to any microcontroller. We'll explore key features like 24-bit color support, non-square pixel displays, direct Quad SPI Flash attachment for large assets, and extensive image/font support for global customization.
A special focus is placed on the BT817A, our AEC-Q100 automotive-qualified device, showcasing its extended temperature range and suitability for critical applications. See a practical demonstration with our bedside patient monitor demo, illustrating smooth real-time updates and comprehensive UI possibilities even with cost-effective MCUs.
From vehicle dashboards and EV charging stations to medical devices and smart building systems, the BT817 and BT817A are designed to enhance product functionality and user experience with minimal design changes and a faster time to market.
What you'll learn:
- The core features of the BT817 and BT817A EVE, including their 3-in-1 solution for graphics, touch, and audio.
- Specific benefits of the AEC-Q100 qualified BT817A for automotive and high-reliability applications.
- How EVE handles high-resolution displays, multi-touch, and large graphical assets.
- Real-world application examples, including a detailed medical device demo.
Ready to build professional and resilient user interfaces for your advanced products?
Watch now to see how Bridgetek's BT817 and BT817A can help you achieve your goals!
Connect with us:
- Website: https://brtchip.com/
- Getting Started with EVE: https://brtchip.com/getting-started/
- BRT Community Forum: http://www.brtcommunity.com/
- Bridgetek GitHub (Code Examples): https://bridgetek.github.io/
#56
BRT News / Bridgetek | EVE FT800
Last post by BRT Marketing - June 20, 2025, 07:09:56 AMWant to add a stunning color graphical user interface (GUI) with touch control to your design without a major redesign? This video introduces Bridgetek's FT800 and FT801 Embedded Video Engines (EVE), designed to simplify GUI implementation for any microcontroller.
Watch the video here: https://youtu.be/wK406prJsWk
Learn how the FT800 and FT801 bring powerful 3-in-1 graphics, touch, and audio functions to your product. We'll dive into their object-oriented architecture, efficient touch engine with tagging, and compact VQFN-48 package for easy integration.
We'll also showcase our new IDM2040-21R rotary dial display module, powered by the FT800, demonstrating real-world user interaction with a capacitive touch screen and rotary dial. See how these EVE devices are ideal for a wide range of applications, from smart home controls and medical devices to coffee machines and industrial gauges.
Discover how you can enhance your product, choose the most cost-effective MCU, and achieve a faster time to market with professional GUIs using EVE.
In this video, you'll find out:
Ready to elevate your product's user experience?
Watch now to see the power of Bridgetek's FT800 and FT801!
Connect with us:
Watch the video here: https://youtu.be/wK406prJsWk
Learn how the FT800 and FT801 bring powerful 3-in-1 graphics, touch, and audio functions to your product. We'll dive into their object-oriented architecture, efficient touch engine with tagging, and compact VQFN-48 package for easy integration.
We'll also showcase our new IDM2040-21R rotary dial display module, powered by the FT800, demonstrating real-world user interaction with a capacitive touch screen and rotary dial. See how these EVE devices are ideal for a wide range of applications, from smart home controls and medical devices to coffee machines and industrial gauges.
Discover how you can enhance your product, choose the most cost-effective MCU, and achieve a faster time to market with professional GUIs using EVE.
In this video, you'll find out:
- The core features and benefits of the FT800 and FT801 EVE.
- How EVE simplifies adding graphics, touch, and audio to any MCU.
- Real-world applications of EVE technology.
- An introduction to our IDM2040-21R module and development tools.
Ready to elevate your product's user experience?
Watch now to see the power of Bridgetek's FT800 and FT801!
Connect with us:
- Website: https://brtchip.com/
- Getting Started with EVE: https://brtchip.com/getting-started/
- BRT Community Forum: http://www.brtcommunity.com/
- Bridgetek GitHub (Code Examples): https://bridgetek.github.io/
#57
BRT News / Bridgetek | EVE Introduction
Last post by BRT Marketing - June 20, 2025, 07:07:20 AMLooking to enhance your product with a stunning graphical user interface (GUI) without overhauling your entire design? Discover Bridgetek's Embedded Video Engine (EVE) – a game-changing solution that brings high-resolution graphics, touch, and audio to any microcontroller.
In this video: https://youtu.be/Fh01VzJFz30
We explore how EVE simplifies GUI development, allowing you to choose the most cost-effective MCU for your application while still delivering a professional and intuitive user experience. Learn about EVE's evolution, its latest features (including support for large LVDS displays and live video input), and how its object-oriented graphics engine streamlines your design process.
Whether you're working on automotive displays, medical devices, or smart appliances, EVE offers a flexible and powerful way to integrate advanced GUIs. We'll also highlight our comprehensive design tools and code examples to help you get started quickly.
What you'll learn:
Ready to create amazing user interfaces?
Watch now to see how Bridgetek's EVE can transform your product!
Connect with us:
In this video: https://youtu.be/Fh01VzJFz30
We explore how EVE simplifies GUI development, allowing you to choose the most cost-effective MCU for your application while still delivering a professional and intuitive user experience. Learn about EVE's evolution, its latest features (including support for large LVDS displays and live video input), and how its object-oriented graphics engine streamlines your design process.
Whether you're working on automotive displays, medical devices, or smart appliances, EVE offers a flexible and powerful way to integrate advanced GUIs. We'll also highlight our comprehensive design tools and code examples to help you get started quickly.
What you'll learn:
- How EVE enables advanced graphics, touch, and audio with any MCU.
- Key features of the EVE family, including the latest BT820B.
- The benefits of using EVE over traditional MCU-based graphics.
- An overview of Bridgetek's design tools and resources.
Ready to create amazing user interfaces?
Watch now to see how Bridgetek's EVE can transform your product!
Connect with us:
- Website: https://brtchip.com/
- Getting Started with EVE: https://brtchip.com/getting-started/
- BRT Community Forum: http://www.brtcommunity.com/
- Bridgetek GitHub (Code Examples): https://bridgetek.github.io/
#58
BRT News / Mini-Module MN820 VS Credit-Ca...
Last post by BRT Marketing - June 16, 2025, 03:12:09 AMChoose Wisely. Choose Simply.
Our Credit Card Size Module #VM820C and Mini Module #MN820 offer distinct pathways to visual innovation.
Which one is right for you?
Link to our full FAQ page for more details: https://brtchip.com/faqs/
Share with us your thoughts in this thread about what you would like to learn next about the Mini-Module MN820.
Our Credit Card Size Module #VM820C and Mini Module #MN820 offer distinct pathways to visual innovation.
Which one is right for you?
Link to our full FAQ page for more details: https://brtchip.com/faqs/
Share with us your thoughts in this thread about what you would like to learn next about the Mini-Module MN820.
#59
Discussion - EVE / Re: BT822
Last post by BRT Community Admin - June 11, 2025, 01:51:49 PMHi Jori,
Good to hear you have used previous EVE series IC`s. To aid with quick BT820 design we have brought out MN820 Mini Module.
The module includes the BT820 BGA and on-board 1Gbit DDR3L memory.
Developers can also seamlessly integrate the BT820B into their products by using the MN820 and connecting it via a 100-pin board-to-board connector to their application PCB. This approach reduces development time and eliminates the complexity of designing the high-speed DDR3 subsystem, allowing for a low-cost PCB implementation.
best regards
Community Admin
Good to hear you have used previous EVE series IC`s. To aid with quick BT820 design we have brought out MN820 Mini Module.
The module includes the BT820 BGA and on-board 1Gbit DDR3L memory.
Developers can also seamlessly integrate the BT820B into their products by using the MN820 and connecting it via a 100-pin board-to-board connector to their application PCB. This approach reduces development time and eliminates the complexity of designing the high-speed DDR3 subsystem, allowing for a low-cost PCB implementation.
best regards
Community Admin
#60
Discussion - EVE / Re: BT822
Last post by jori - June 11, 2025, 12:53:11 PMI don't have a specific project in mind. Just for testing. For now, I'm using FT800, BT815 and BT817 in my projects. I'm asking because BT820 is a BGA package and needs additional external RAM, which complicates the creation of the board itself, it will most likely have to be at least a 4-layer board. According to the specifications that came out some time ago, BT822 will have a built-in 1Gbit RAM, which will significantly simplify the creation of the board. Most likely, the package will not be BGA either, since it will not need the additional pins for communication with external RAM.