Compiling error with STM32IDE cube #547

baobuibk · 2025-07-05T12:14:49Z

baobuibk
Jul 5, 2025

Hi,

I am start using TRICE and try to make the first project. I copy the src folder to the project and copy the triceConfig.h, triceUART.h and SEGGER_RTT_Conf.h from the example. However, when I do the compiling I got many errors. Most of them come from the line #define TRICE_UNUSED(x) (void)(x);
trice/src/trice.h:17:26: error: expected identifier or '(' before 'void'

Please tell me how to fix it. Thanks

rokath · 2025-07-05T13:20:47Z

rokath
Jul 5, 2025
Maintainer

Just copying files into your project is not enough. Their bare existence gets them not compiled in some cases. You need to tell your IDE, that these are additional files to compile into your project. I cannot give advice how to do that with the STM32IDE.
Anyway, the Trice library code should compile without any errors. As long you do not use any trice("hello\n"); in your code, the linker will not link Trice library objects. You need in one of your project files, for example main.c to#include "trice.h" first, and then in a function use trice("hello\n");. This will then cause compile errors because of the missing iD(123). To get this done, call trice insert. The insertion shuld be called automatically by your IDE. You need to configure that in your IDE. Read https://github.com/rokath/trice/blob/master/docs/TriceUserManual.md#start-with-trice. If this is not detailed enough, please tell what to improve.

1 reply

baobuibk Jul 5, 2025
Author

Hi,

Thanks for your reply.
The code get compiled, this is why I get errors. I did not use any trice function, just try compiling the trice source code, but the compiler generate alot of errors. The errors look similar to the following:

90 | #define TriceN( p, s, n, ...) TRICE_UNUSED(p) TRICE_UNUSED(s) TRICE_UNUSED(n)
| ^~~~~~~~~~~~
../Dev/MiddleWare/trice/src/trice.c:937:6: note: in expansion of macro 'TriceN'
937 | void TriceN(int tid, char const* fmt, void* buf, uint32_t n) {
| ^~~~~~
../Dev/MiddleWare/trice/src/trice8.c: In function 'TRice8fn_12':
../Dev/MiddleWare/trice/src/trice8.c:556:9: warning: implicit declaration of function 'TRice8m_12'; did you mean 'TRice8_12'? [-Wimplicit-function-declaration]
556 | TRice8m_12(tid, v0, v1, v2, v3, v4, v5, v6, v7, v8, v9, v10, v11);
| ^~~~~~~~~~
| TRice8_12
../Dev/MiddleWare/trice/src/trice.c:937:62: error: expected identifier or '(' before '{' token

rokath · 2025-07-05T17:05:52Z

rokath
Jul 5, 2025
Maintainer

Just as a hint: https://github.com/rokath/trice/blob/master/docs/TriceUserManual.md#possible-compiler-issue-when-using-trice-macros-without-parameters-on-old-compiler-or-with-strict-c-settings.

But I guess you have a different issue here.

90 | #define TriceN( p, s, n, ...) TRICE_UNUSED(p) TRICE_UNUSED(s) TRICE_UNUSED(n) tells that TRICE_OFF is 1 for trice.c probably.
556 | TRice8m_12(tid, v0, v1, v2, v3, v4, v5, v6, v7, v8, v9, v10, v11); tells that TRICE_OFF is 0 for trice8.c probably.

We need an explanation for that.

Please check all your project files (also the settings) for any "TRICE" sub string (case insensitive).
Please compare the Trice library source files you use, with the fresh downloaded folder. No changes , no additional files!
Please check your development environment setup. You should be able to run ./testAll.sh and ./testAll.sh full on your mashine. That should compile everything error free.
Please share more information, for example:
- the ./testAll.sh output file testAll.log as link
- your triceConfig.h here
- your full compiler output as link
- If you fixed it in-between by yourself, the reason

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Compiling error with STM32IDE cube #547

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 1 reply

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

Compiling error with STM32IDE cube #547

Uh oh!

baobuibk Jul 5, 2025

Replies: 2 comments · 1 reply

Uh oh!

rokath Jul 5, 2025 Maintainer

Uh oh!

baobuibk Jul 5, 2025 Author

Uh oh!

rokath Jul 5, 2025 Maintainer

baobuibk
Jul 5, 2025

Replies: 2 comments 1 reply

rokath
Jul 5, 2025
Maintainer

baobuibk Jul 5, 2025
Author

rokath
Jul 5, 2025
Maintainer