BRT Community

Thanks again for your follow-up. I sent a download link for the VAN.mp4 video that's having conversion problems to the email address you provided. I'll be waiting for your response.

Best regards and Happy New Year!

Hello,

The SW team are requesting a copy of the source video for the conversion.
Would you be able to share a link to an upload of the video file or alternately email in a copy to support.emea@brtchip.com?


Best Regards,
BRT Community

✨ Win a Galaxy Watch7 Bluetooth! ✨

We'd love your feedback! Take Bridgetek's quick Customer Survey (3 minutes or less) to help shape our next‑gen products and rate our services.

✅ The survey is anonymous — but leave your email at the end to enter our FREE prize draw.
🎟 Entry is free, no purchase needed.
📅 Promotion runs from 2 Jan 2026 until 31 May 2026.

👉 Click "Done" when finished, and you're automatically entered!

🔒 Info collected is handled per our Privacy Policy.
📌 Terms & Conditions apply.
💡 Your voice matters — and it could win you a Galaxy Watch7!

Link: https://www.surveymonkey.com/r/BRT-Cust-Survey-2026

Hello,

Thank you for the details, i have shared these with the SW development team, and i hope to be back with an update soon.

Best Regards,
BRT Community

I've had some free time lately. I'm sharing the video processing results for version 4.0.1.

You cannot view this attachment.

You cannot view this attachment.

This is the content of the json file.

{
  "eab_version": "4.0",
  "chip_gen": "BT82x",
  "input_name": "VAN.mp4",
  "output_name": "VAN.avi",
  "output_size": 153075816,
  "type": "video",
  "format": "mjpeg",
  "compressed": "no",
  "width": 798,
  "height": 450,
  "pixel_format": "yuvj420p",
  "quality": 4,
  "audio": "yes",
  "playback_frequency": 48000
}
Since version 4.1.0 does not perform the conversion, no file with the JSON extension is generated. These are the processing results it generates.

You cannot view this attachment.

You cannot view this attachment.

Hello,

Thank you for your post.

Quote from: ashrey on December 09, 2025, 06:05:55 PMAs the other thread asks, it also appears that the ST7789V needs to be configured via SPI before it will work in RGB mode, but then after that, SPI communications to the display are no longer needed, is that correct?

Yes, generally this is correct for such parts (but please verify the in the datasheet) that you would configure the display driver during boot, and once this ahs been completed you wouldn't communicate with it again. After which you can perform the FT81x initialization routine.

For reference, here is some example code that would be called for the ILI9488 configuration on the ME810A-HV35R:
https://github.com/Bridgetek/EveApps/blob/master/common/eve_hal/EVE_ILI9488_FT9XX.c

In regards to the configuration of parts such as the ST7789V, there are two approach's you can utilise.

• The first approach would be to utilise the SPI interface on your MCU to perform the configuration, using a spare CS# signal.

As noted in the previous thread you can get an example of the hardware we use in the ME810A-HV35R datasheet.

But it would also be acceptable to use the approach you has suggested to MUX the CS# line to the ST7789V and the FT811 and control this via a GPIO.

• The second approach would be to bit bang the configuration data from your MCU over spare GPIO pins if you have these available.

This would remove the need for the MUX IC if you have some spare GPIO pins available.


Best Regards,
BRT Community

✨ Upgrade your product with Bridgetek TFT Displays! Crisp visuals, responsive touch, and sizes for every project — from 3.5" to 15.6".
✅ High‑resolution ✅ Capacitive or resistive touch ✅ RGB/LVDS integration ✅ Ideal for medical, automotive, industrial & consumer devices
Boost your HMI with our Embedded Video Engine for faster, easier development. 🚀 Make your interface stand out.

I found this thread, which is quite old and suggests making a new thread, so I did:
http://www.brtcommunity.com/index.php?topic=220.0

There also weren't any definitive answers in that thread, and I amhoping that has changed since it was posted.

I have previously used a FT810 with a natively RGB panel, and am now looking at using a FT811 (48pin) with this panel that has a ST7789V controller on it: https://www.buydisplay.com/2-4-inch-ips-240x320-tft-lcd-display-capacitive-touch-screen

I think I have  the connections correct, and am looking for confirmation:
Panel    FT811
VSYNC    VSYNC
HSYNC    HSYNC
DOTCLK  PCLK
DE      DE
DB17:0  R7:2|G7:2|B7:2
RESET    DISP

The RD, WRX, D/CX, CSX, and TE pins from the panel are all unused

As the other thread asks, it also appears that the ST7789V needs to be configured via SPI before it will work in RGB mode, but then after that, SPI communications to the display are no longer needed, is that correct?

My current design already has several devices on the SPI bus and can't natively support another CS, but if the ST7789V only requires a few SPI instructions for initialization, I can can easily MUX the FT811 CS and use an MCU GPIO to control whether SPI traffic selects the ST7789V or the FT811.

Thanks

Can you provide more details on how it "crashes everything" and "crashes the debugger"?  Is there a specific error? 

Do you have FreeRTOS set to check for stack overflows (configCHECK_FOR_STACK_OVERFLOW) ?