TouchGFX NEMA Libraries

[desmond]

Hello,

We are in the process of integrating TouchGFX into our workflow and back-end build systems. We are using a STM32U599.

Please see my question with respect to the tree below

1. What is the difference between TouchGFXNema and NemaGFX libraries?
2. What does the wc16 suffix on the libraries mean?

Middlewares/ST/touchgfx_components/
└── gpu2d
    ├── NemaGFX
    │   ├── include
    │   └── lib
    │       └── core
    │           └── cortex_m33
    │               └── gcc
    │                   ├── libnemagfx.a
    │                   ├── libnemagfx-float-abi-hard.a
    │                   ├── libnemagfx-float-abi-hard-wc16.a
    │                   └── libnemagfx-wc16.a
    └── TouchGFXNema
        ├── include
        │   └── touchgfx_nema
        └── lib
            └── cortex_m33
                └── gcc
                    ├── libtouchgfxnema.a
                    └── libtouchgfxnema-float-abi-hard.a

[desmond]

A bit of digging around here is what I found please confirm

•  `touchgfx_nema` uses `NemaGFX`
• `wc16` likely relates to the word count which likely means the largest word uses in the library is 16 bits.

Under what conditions would you use libraries with `wc16` version of the library?

[LouisB · Accepted solution]

Hi @desmond ,

In short for your questions:

1. The NemaGFX libs are low-level drivers for the Neochrome GPU2D. The TouchGFXNema libs are the binding layer between the nema drivers and the touchgfx core library.
   

2. That depends on your project settings. To my knowledge 16bit word count is rarely used, but we supply a lib that can work with those projects as well.

I hope that answers your question,
Regards,

[desmond]

Sound good. Will circle back if we have issue integrating it.

Thanks

[LouisB]

Hello @desmond ,

You are welcomed, don't hesitate if you have another question.

Regards,