Thomas Höhenleitner
Thomas Höhenleitner
The following sequence inside `trice/examples/OpenCM3_STM32F411_Nucleo/main.c` ```C // Depending on mode, either print this string to // UART (mode 0), or the Trice write buffer (mode 200). TRICE( Id( 4030),"Hello, TRICE,...
I propose to close this issue for less issue noise. Normal usage is `trice(...` and all these cases are evaluated for matching value counts. If a user writes `TRICE0(...` or...
Will be opened on demand again.
Usually you do not need to put the parameters count into the trice name. `Trice0(` is as good as `Trice(` when compiling with at least c99. See also issue #279....
Such trice tool check is a good idea, but it would need an additional parsing which would slow down the whole process. Also it is no solution for the limits...
The inserted IDs are expected to be `iD(123)` and not `id(123)` in the shown case.
When you clean the til.json file you need execute `trice i` afterwards, before you compile.
Yes, that is consistent wrong.
In https://github.com/rokath/trice/blob/master/docs/TriceUserGuide.md#922-linited-trice-parser-capabilities there is now this documented as limitation. I close this issue now as we still have #465 and a separate check makes not much sense as explained.
> The use of Trice0 is related to #452 issue (compile on C++) > > ``` > Trice0( variable ); // invalid use > Trice0( "tex %u", variable ); //...