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) ?

Hello,

Thank you for the screenshots.

Unfortunately I have been unable to reproduce the issue with the input test videos I have utilised.

If you select the 'Command Line' tab beside the 'Output Log' you can view the commands used to generate the file:

eab_tools pre82x video -i "C:/Users/Public/Documents/EVE Asset Builder 4.1.0/Assets For Test/Pre-BT82X/Video Converter Test/big_buck_bunny_h264.mp4" -o "C:/Users/Public/Documents/EVE Asset Builder 4.1.0/work_space/output" -q 4 -r 850:480 -s 48000 -t 25.00

ffmpeg.exe -i "C:/Users/Public/Documents/EVE Asset Builder 4.1.0/Assets For Test/Pre-BT82X/Video Converter Test/big_buck_bunny_h264.mp4" -threads 8 -hide_banner -v error -y -s 850:480 -r 25.0 -c:v mjpeg -pix_fmt yuvj420p -acodec pcm_u8 -ac 1 -ar 48000 -q:v 4 -shortest "C:/Users/Public/Documents/EVE Asset Builder 4.1.0/work_space/output/big_buck_bunny_h264.avi"
We can then add the "-v verbose" & "-report" flags to the ffmpeg command:

C:\Users\Public\Documents\EVE Asset Builder 4.1.0\work_space\output>ffmpeg.exe -i "C:/Users/Public/Documents/EVE Asset Builder 4.1.0/Assets For Test/Pre-BT82X/Video Converter Test/big_buck_bunny_h264.mp4" -threads 8 -hide_banner -v error -y -s 850:480 -r 25.0 -c:v mjpeg -pix_fmt yuvj420p -acodec pcm_u8 -ac 1 -ar 48000 -q:v 4 -shortest -report -v verbose "C:/Users/Public/Documents/EVE Asset Builder 4.1.0/work_space/output/big_buck_bunny_h264.avi"
We can run this command by selecting the 'Command Prompt' button on the right hand side of EAB.

For my test this produces the following output:

[h264 @ 0000019cdd2f9100] Reinit context to 864x480, pix_fmt: yuv420p
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'C:/Users/Public/Documents/EVE Asset Builder 4.1.0/Assets For Test/Pre-BT82X/Video Converter Test/big_buck_bunny_h264.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    encoder         : Lavf57.25.100
  Duration: 00:00:42.75, start: 0.000000, bitrate: 2031 kb/s
    Stream #0:0(eng): Video: h264 (High), 1 reference frame (avc1 / 0x31637661), yuv420p(left), 850x480 (864x480), 1897 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
    Metadata:
      handler_name    : VideoHandler
    Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 128 kb/s (default)
    Metadata:
      handler_name    : SoundHandler
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> mjpeg (native))
  Stream #0:1 -> #0:1 (aac (native) -> pcm_u8 (native))
Press [q] to stop, [?] for help
[h264 @ 0000019cdd323fc0] Reinit context to 864x480, pix_fmt: yuv420p
[graph_1_in_0_1 @ 0000019cdf5ae740] tb:1/44100 samplefmt:fltp samplerate:44100 chlayout:0x3
[format_out_0_1 @ 0000019cdf5aeb00] auto-inserting filter 'auto_resampler_0' between the filter 'Parsed_anull_0' and the filter 'format_out_0_1'
[auto_resampler_0 @ 0000019cdf5ee280] ch:2 chl:stereo fmt:fltp r:44100Hz -> ch:1 chl:mono fmt:u8 r:48000Hz
[graph 0 input from stream 0:0 @ 0000019cdf040440] w:850 h:480 pixfmt:yuv420p tb:1/12800 fr:25/1 sar:0/1
[scaler_out_0_0 @ 0000019cdf040800] w:850 h:480 flags:'bicubic' interl:0
[swscaler @ 0000019ce00b5f40] deprecated pixel format used, make sure you did set range correctly
[scaler_out_0_0 @ 0000019cdf040800] w:850 h:480 fmt:yuv420p sar:0/1 -> w:850 h:480 fmt:yuvj420p sar:0/1 flags:0x4
Output #0, avi, to 'C:/Users/Public/Documents/EVE Asset Builder 4.1.0/work_space/output/big_buck_bunny_h264.avi':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    ISFT            : Lavf58.49.100
    Stream #0:0(eng): Video: mjpeg, 1 reference frame (MJPG / 0x47504A4D), yuvj420p(pc, left), 850x480, q=2-31, 200 kb/s, 25 fps, 25 tbn, 25 tbc (default)
    Metadata:
      handler_name    : VideoHandler
      encoder         : Lavc58.99.100 mjpeg
    Side data:
      cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: N/A
    Stream #0:1(eng): Audio: pcm_u8 ([1][0][0][0] / 0x0001), 48000 Hz, mono, u8, 384 kb/s (default)
    Metadata:
      handler_name    : SoundHandler
      encoder         : Lavc58.99.100 pcm_u8
No more output streams to write to, finishing.=00:00:37.98 bitrate=8667.4kbits/s speed=  38x
frame= 1068 fps=903 q=4.0 Lsize=   45947kB time=00:00:42.72 bitrate=8810.8kbits/s speed=36.1x
video:43866kB audio:2002kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.173016%
Input file #0 (C:/Users/Public/Documents/EVE Asset Builder 4.1.0/Assets For Test/Pre-BT82X/Video Converter Test/big_buck_bunny_h264.mp4):
  Input stream #0:0 (video): 1068 packets read (10131496 bytes); 1068 frames decoded;
  Input stream #0:1 (audio): 1841 packets read (684385 bytes); 1839 frames decoded (1883136 samples);
  Total: 2909 packets (10815881 bytes) demuxed
Output file #0 (C:/Users/Public/Documents/EVE Asset Builder 4.1.0/work_space/output/big_buck_bunny_h264.avi):
  Output stream #0:0 (video): 1068 frames encoded; 1068 packets muxed (44918847 bytes);
  Output stream #0:1 (audio): 1840 frames encoded (2049672 samples); 1840 packets muxed (2049672 bytes);
  Total: 2908 packets (46968519 bytes) muxed
[AVIOContext @ 0000019cdd313d00] Statistics: 10 seeks, 188 writeouts
[AVIOContext @ 0000019cdd300580] Statistics: 10886642 bytes read, 2 seeks

C:\Users\Public\Documents\EVE Asset Builder 4.1.0\work_space\output>
As well as a .log file for the conversion in the output folder.

Would you be able to share the results you are seeing for these flags in your conversion on EAB v4.1.0?

Best Regards,
BRT Community

Correct video processing with EVE-AB 4.0.1You cannot view this attachment.

Error with identical video file, in EVE-AB 4.1.0You cannot view this attachment.

Hello,

Thank you for your post.

Unfortunately it appears that the imgur links are region blocked, and we are unable to view the details in them.

Would you be able to re-share the screenshots, attach them to a post, or share the details of the settings you have used and the error message?

Best Regards,
BRT Community

I've already tried modifying the parameters in different ways to convert the file, but the result is always the same: conversion failed!



I reverted to version 4.0.1, which doesn't have this type of error.

Overview

Introducing our range of sensors and actuator devices supporting the popular Modbus protocol. With robust yet aesthetically pleasing enclosures and a range of mounting options, they are ideal for connecting to new and existing Modbus systems, such as Building management controllers, smart home controls, Industrial controllers, computers, and via wireless bridges (for example Modbus to LoRaWAN bridges).

With Modbus RTU, you can daisy-chain large numbers of devices over long distances using cost-effective cabling, providing both power and data. Mix and match the sensors, sensor adapters and actuators from our range on the same network, and on existing buses with other Modbus RTU devices.

Link : https://brtchip.com/getting-started-with-modbus-products/

Just saw that EAB 4.1.0 is finally: out https://brtchip.com/eab/

While that is impressive, that does not really solve the availability of BT82x modules.
Yes, buying panels turned out to be a pain by itself, but usually that is a problem that can be solved with throwing money at it - thinking about single units here for evaluation or to play with, thinking in production level amounts I would send a suit from procurement to get me what I want (and I wish I was there).

However, the fun starts when adapting the panel to the VM820C - and the touch.
That is why I am also thinking about designing a board for the MN820.

So I prefer integrated modules.
And based on the experience with the VM820C so far, I would go for the option with 1GBit DDR3L and even no external flash (the option to solder a SOIC-8 would still be nice), as long as there is a micro-sd socket.