BRT Community

Hi Rudolph,

We have one of those modules available now so will give it a try here and let you know if we can see it happening,

Best Regards, BRT Community

Hi,

For these fonts, it is required to use CMD_ROMFONT. Please see section 5.70 in the Programming Guide for examples.
https://brtchip.com/wp-content/uploads/2025/07/BRT_AN_033_BT81X-Series-Programming-Guide.pdf

Here we set the font 34 to user handle 1.

cmd_romfont(1, 34);
cmd_text(60, 32, 1, 0, "34");

Hope it helps, Best Regards, BRT Community

Our R&D team will be updating the tool to use the latest driver and we'll let you know when the version is released,

Best Regards, BRT Community

Hello,

Thank you for the update, I'm glad to hear that you have managed to get the conversion to work via the command line.

Yes the -q option in ffmpeg.exe relates to the quality of the conversion:
-q q                use fixed quality scale (VBR)
Best Regards,
BRT Community

Hello,

Thank you for sharing the source video file.

Unfortunately the development team were not able to recreate the issue on their test machine.
They have asked for some logs of the EAB conversion process

QuoteCan we recommend the user open EAB's command prompt (by clicking the bottom button in left-side panel), run these command lines in turn and share the result log:

eab_tools video -i path/to/VAN.mp4 -r 798:450 -o "path/to/output" -q 4 -s 48000 -f 3 -c MIX -t 29.97

ffmpeg.exe -i "path/to/VAN.mp4" -threads 16 -hide_banner -y -s 798:450 -pix_fmt yuvj420p -r 29.97 -c:v mjpeg -q:v 4 -c:a pcm_s16le -ar 48000 -ac 1 "path/to/output/VAN.avi"

Best Regards,
BRT Community

Great to see your new module with Power Delivery support

We'll request our R&D team to update the DLL in our software tools to the latest one so that your PD-based will work and we'll let you know here when it is available,

Thanks for reporting this,

Best Regards, BRT Community

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

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

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

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

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

Hi Rudolph, VDC,

We have a range of displays available now too from Bridgetek including a 10.1" 1920x1200 panel which you can use with the VM820C credit card module. It has a capacitive touch panel.

Here is the link to the 1920x1200 panel 10.1" display 1920x1200

We also have a 15.6" panel with capacitive touch too which you can find here: 15.6" panel with capacitive touch
 
Let us know if you have any questions on them or if you would like any further information,

Best Regards, BRT Community

Hi Rudolph,

The new EAB and the associated extensions are currently being completed and should be available by end-September. We'll keep you updated here,

Best Regards, BRT Community

Hello kumaichi,

Thank you for your post.

It is certainly a curious issue in relation to the FreeRTOS implementation.

I would be interested to know whether moving the REG_PWM_DUTY call to either of the indicated places below  results in different behaviour:

    TFT_qspi_cmd_setrotate(0);

    TFT_qspi_write16(REG_GPIOX_DIR, 0xFFFF);
    TFT_qspi_write16(REG_GPIOX, 0xFFFF);

        <---------------------- TO HERE

    /* after this display is visible on the LCD */
    TFT_qspi_write8(REG_PCLK, DispPCLK);

    //while (TFT_busy() != E_OK){};
    TFT_qspi_WaitCmdfifo_empty();

    /* If the status of the flash is 0 (INIT) Attach it */
    while (EVE_FLASH_STATUS_DETACHED == TFT_qspi_read8(REG_FLASH_STATUS))
    {
        TFT_qspi_dl_cmd(CMD_FLASHATTACH);
    }

    /* Initialize the onboard flash and put in FAST mode
    * Need to check the return value and not proceed if
    * there is an error so we can read in the Fonts
    */
    if (TFT_init_flash() == E_OK)
    {
        /* Read the image from the flash */
        uint32_t flashCommands[] =
        {
                CMD_FLASHREAD, (uint32_t) MEM_FONT34, (uint32_t) 198592, (uint32_t) 280 + 40,
                CMD_FLASHREAD, (uint32_t) CAR_IMAGE_HORIZONTAL, (uint32_t) 198912, (uint32_t) 92000 + 32
        };

        TFT_qspi_cmd_burst(flashCommands,    sizeof(flashCommands) / sizeof(flashCommands[0]));

        while (TFT_busy() != E_OK)
        {
        };

        TFT_qspi_WaitCmdfifo_empty();
    }

        <---------------------- OR HERE

    TFT_qspi_dl_cmd(CMD_DLSTART);
    TFT_qspi_dl_cmd(DL_CLEAR_COLOR_RGB | WHITE);
    TFT_qspi_dl_cmd(DL_CLEAR | CLR_COL | CLR_STN | CLR_TAG);
    TFT_qspi_dl_cmd(DL_BEGIN);

    TFT_qspi_dl_cmd(COLOR_RGB(120, 6, 6));

    TFT_qspi_cmd_setfont2(13, MEM_FONT34, 0); /* assign bitmap handle to a custom font */
    TFT_qspi_cmd_text((DispWidth / 2), (DispHeight / 5) - 15, 13, EVE_OPT_CENTERX, "Please wait...");

    TFT_qspi_dl_cmd(COLOR_RGB(20, 20, 130));

    TFT_qspi_cmd_spinner(DispWidth / 2, DispHeight / 2, 0, 0);

    //TFT_qspi_write8(REG_PWM_DUTY, 25); 

i.e. is it specifically this call causing the issue, or is just where the call is being executed in the sequence of SPI writes that is the problem.

Can i ask if you are observing the write taking place on the SPI bus when the issue occurs?


Best Regards,
BRT Community

Hi Rudolph,

Glad that you like the new extensions. We'll check when the new EAB will be released and will post back here with an update very soon,

Best Regards, BRT Community