Hello,

Thank you for your post.

For example, chapter 5 Interrupt handling example whole project which can be imported to STM cube IDE and built will be really helpful. I hit a lot of issues during the build with variadic functions eg: ESD_METHOD, the second question what is the purpose of using all these variadic function as METHOD, PARAMETER etc?

Unfortunately the file size limit on the forum prevents me from attaching the examples, I can forward the files to you via a file sharing service if this is acceptable?

On the variadic function point, i would need to clarify with the developers why the ESD framework utilises these. If this is an significant issue i can forward you a lower level STM32 library for EVE which does not use variadic functions, however this is not compatible with ESD.

Best Regards,
BRT Community

Hello,

Thank you for your question.

We have recently become aware of this issue where EAB reports the failure to convert a space character, the development team are curranty updating EAB to resolve this issue.


However the developers have noted that this should not affect the customer font when utilized in your application, you should be able to use the SPACE character in CMD_TEXT for example. Alternately you can utilize the hex representation of the ASCII character (0x21) in CMD_TEXT:

Please see attached for an example of a custom font being utilised where EAB has reported that the space character has failed to convert.

Best Regards,
BRT Community

The latest CleO resources (1.1.2) are available and can be downloaded from the attached .zip file, these include the CleO documentation, PC Tools, Arduino Libraries and SD Card Images.

Please use the following link to download the package:
CleO Resrouces (1.1.2)

Best Regards.
BRT Community

Hello,

You can download the installation package for the newest version of EVE Asset Builder (EAB 2.5.0) from the following link: https://brtchip.com/ic-module/toolchains/

Additionally, 'BRT_AN_054 EVE Asset Builder User Guide' can be found here: https://brtchip.com/ic-module/document/programming-guides/

Best regards

BRT Community

Hello,

Thank you for the update.

I have managed to test the provided font file with ESE to verify the behavior.

Again I was seeing that the font file being used does not include some of the input characters that you wish to convert. Please see "Font Preview.PNG", this is from the Windows preview of the file but I note the same behavior in EAB. As a result the conversion output contains these characters and not the desired "./:()-" characters (see "isfdV11BoldPlus55_22.png").

Using the following display list I was able to display the font correctly:

CLEAR(1,1,1)
CMD_DLSTART
CMD_SETFONT2(5, 0, 48)
CMD_TEXT(100, 198, 5, 0, "12345 \x33 \x36 \x37 \x38 \x39 \x3A \x3B \x3C \x3D \x3f \x3E  ")
CMD_NUMBER(111, 259, 5, 0, 987654321)
Note: I performed the EAB conversion using RAM_G +0 as the address, see below for the command line:

/*Command Line: fnt_cvt.exe -f legacy -C BT81X -i C:/Users/~/Desktop/Spyy Font Question/isfdV11BoldPlus55.ttf -s 22 -d  0 -c setfont2 -l 48 -g -u C:/Users/~/Desktop/Spyy Font Question/isfdFont V4.txt -o C:/Users/~/Desktop/Spyy Font Question -O 4*/
The result can be seen in the ESE.PNG file.

Setting the first character to 48 in the conversion command line allows us to utilize CMD_NUMBER with the given numerals, we can then print the remaining characters in CMD_TEXT with their hex representation. Note, the convertor is assuming that input character list conforms to the ASCII standard layout, so character number 58 is a colon ( in ASCII but in your input set it is a full-stop (.), as such you cannot use the full-stop in CMD_TEXT to print a full-stop but you can use the hex value 0x3A.

If you are seeing a different preview for the given font file or a different output from EAB please let me know.

Best Regards,
BRT Community

Hello,

Thank you for your question.

Can you just confirm how you are loading the font in your application code?
Is this the same as the "*_L8.c" file?

Could you also confirm how you are calling CMD_TEXT or CMD_NUMBER in your code?

As a note the BITMAP_SOURCE value is calculated in the following manner:
(Address of data in RAM_G) + (Metric Block size) – (32 characters worth of (stride * height))

Can I get you to try reconverting the font with the first character set as 48? Please also try the SETFONT2 option.
The CMD_NUMBER command will take the font widths from the standard ASCII positions, so you need to adjust for this fact.

The CMD_TEXT command then can use the hex value of the position of the character in the font file to display a given character. For example: CMD_TEXT(191, 295, 5, 0, "\x30 ")

However when testing this I noticed that the following symbols did not convert correctly:

./:()-
It appears as if these are not included in your font source file.

Best Regards,
BRT Community

Hi Darren,

One thing to check is that it looks like you may have the FT812 selected and only devices from BT81x onwards have the Flash feature. Therefore please ensure to select BT815/6/7/8 to use Flash.

Also, ensure that your flash file is in the same directory as the exe (looks like you have this in your screenshot already) and you can then just type WindowLayout__Flash.bin when it asks for the flash file.

If you see issues where it still gives an error, copy the following dll file and paste into the same directory as your exe and your flash bin file (assuming default installation). Then re-run your exe and it should accept your flash name when you type it in.
Public\Documents\EVE Screen Designer\Libraries\FT_Eve_Hal\Bin\Simulation\mx25lemu.dll

Hope it helps,

Best Regards, BRT Community

Hello,

Thank you for the details, I must apologies I mistyped when asking for the ESD version, i did mean to ask for the ESE version.

I have tested with ESE 4.2.0 and found that an MPSSE device should appear in the devices tab, irrespective of an EVE device being connected to its SPI signals.

Is this behavior repeatable across different host PCs?
Could you please let me know the path that ESE is installed on your host PC?


And just to clarify yes, you are correct ESD does not natively support the STM32, however we do have a porting guide available for ESD projects to the STM32:
https://brtchip.com/wp-content/uploads/2021/06/ESD-4.10-Exported-Project-Porting-Guide-for-STM32L4-Discovery-Board-and-FreeRTOS.pdf

The other development approach would be to utilize ESE to create static displays and then copy these display lists into a lower level STM32 EVE library where you can then program any screen logic required,

Best Regards,
BRT Community