I'm sorry to exhume this topic but I'd be glad to get the source code as well especially since I develop on exotic host hardware (OpenBSD, Alpine Linux, macOS) and requiring a Windows VM to run a command line utility to convert a font sounds a bit tedious. What are the reasons besides the need to kept the fnt_cvt.exe file proprietary? I mean, are there such secret in the custom data font file format?

You'll help lot of people by releasing those utilities.

Meanwhile i don't know, where to seek else. I just can make assumptions.

My display is about 1 year old, maybe i have an older silicon of the BT817Q?

Rudolph, could you make your startup sequence public( initialization parameters )?

BRT Community, do you have any advice meanwhile?

I did compress Ubuntu-Light.ttf with 4x4, although this makes the binary pretty huge without benefit.
I also saw this huge "layout width" but it just worked for me.

Very strange.

After remembering to a layout width of "96" and Rudolph's wish to use 8x8 as a standard
i tried also 8x8 compression instead of 4x4.

Now the layout width is "64" and wonder it works. Also the file size of the glyph is about the half.

Further tries with a font size of 28, 29 and 32 failed again (Ubuntu Light, 8x8).

A font size of 31 with 12x12 workes fine.

A font size of 41 with 12x12 doesn't work.

A font size of 37 with 12x12 workes fine.


It seems the result is depending on a relationship of the font size to compression ratio.
As Rudolph's and my experience differ slighty, i asume that we have possible different sources of the ttf-files.

Some relations fit, some not.


I also would suggest to add one point more to Rudolph's wish list:

Please store "automatically" all parameters entered on closing EAB and restore them while starting again.
Especially the last used directories for opening and creating.

I added the MT25QL01GBBB, thank you, but I wonder if it actually works properly since I saw in the datasheet that it uses two 512MBit dies in the package.

But now I wonder what Flash exactly is Riverdi using on their EVE4 modules.
My RVT70HSBNWC00-B is populated with a chip from Micron, the markings are "MT" "IGA17", "RW213" and "FBNP".
My RVT50HSBNWC00-B is populated with a chip from Micron, the markings are "MT" "IIA17", "RW213" and "JBRQ".
My RVT101HSBNWC00-B is populated with a chip from Micron, the markings are "MT" "0DA17", "RW256" and "J2F1".
All do have BGA cases.

A quick search for Micron 512MBit flash chips did not tell me what devices exactly these are.

Thank you for this idea - didn't come to my mind.

Hi Rudolph, you can add MT25QL01GBBB to the list (specifically tested MT25QL01GBBB1EW9-0SIT):

Manufacturer   Chip   Size(MBit)   Detect   Erase   Read/Write   CMD_FLASHFAST
Micron   MT25QL01GBBB   1024   Yes   Yes   Yes   Yes

Ok, I went back and converted Ubuntu-Light.ttf with exactly your settings.
The output is the same, only my "Font Preview" is showing the font at perhaps half the size than in your screen shot.
My .map file has the .xfont at 113536.

I almost copied your code:

    if (E_OK == EVE_init_flash())
    {
        EVE_cmd_flashread(MEM_FONT1, 113536, (309|3)+1); /* copy .xfont from FLASH to RAM_G, offset and length are from the .map file */
    }

    EVE_cmd_dl( CMD_DLSTART );
    EVE_cmd_dl(CLEAR_COLOR_RGB(51,51,51));
    EVE_cmd_dl( CLEAR( 1, 1, 1 ) );
    EVE_cmd_dl( VERTEX_FORMAT(0) );
    EVE_cmd_setfont2( 12, MEM_FONT1,       0 );
    EVE_cmd_dl( DL_END ); // does not do anything here
    EVE_cmd_dl( DL_DISPLAY );
    EVE_cmd_dl( CMD_SWAP );
    EVE_execute_cmd();

    EVE_cmd_dl( CMD_DLSTART );
    EVE_cmd_dl(CLEAR_COLOR_RGB(0,0,18));
    EVE_cmd_dl( CLEAR( 1, 1, 1 ) );
    EVE_cmd_text( 10,  10, 12, 0, "Quick fox at 120°C ");
    EVE_cmd_dl( DL_END ); // does not do anything here
    EVE_cmd_dl( DL_DISPLAY );
    EVE_cmd_dl( CMD_SWAP );
    EVE_execute_cmd();

And it still works, I get the line displayed at the top of the screen.

I am re-installing EAB now, I may have changed something before.
I redid it all, looks like I either modified EAB or previously did not install from scratch, or both.
The new .glyph file is different for some reason.
But the result is still the same, the line is printed just fine.

Hello,

Unfortunately the development team are unable to share the methodology used to produce the .raw file form the ASTC file at this moment in time.

However it is possible to view .raw files within our EVE Screen Editor utility directly, by adding the .raw file as content, after whihc you can click and drag this onto the screen to generate preview.

Please see the attached screen shot of a .raw file from an 4x4 ASTC conversion being previewed in EVE Screen Editor.

Best Regards,
BRT Community

Hi,
Thanks for your update, we are doing some testing and are discussing with our R&D team to understand this issue, and will update very soon,

Thanks Rudolph, we have also passed those to our R&D team, they seem like some good suggestions:

In regards of EAB 2.10.2 I found a couple of things a bit odd.
- why is "Reserve Space" not set as default?
- why is "L8" selected by default for "Extended Format"?
- why is the ASTC set to 4x4 by default instead of a more reasonable 8x8?
- why is this SampleApp generated every single time? can we please have a switch for that which defaults to off?

Best Regards, BRT Community