Thomas Höhenleitner comments

Results 196 comments of


                                            Thomas Höhenleitner

Handling of preprocessor-defined strings in TRICE macro

Maybe you can write inside your header file ```c #include "trice.h" #define DUMMY_STRING TRICE( "msg:The string is dummy string\n"); ``` and in your C-file ``` void fn(void){ DUMMY_STRING } ```...

trice -e DUMP works well only with workaround code

Merged with #291 and #286

Implement TREX encoding to reduce trice data

https://github.com/rokath/trice/blob/master/docs/TriceMessagesEncoding.md#reduced-ideas

Implement TREX encoding to reduce trice data

See [TriceV1.0 spec draft](https://github.com/rokath/trice/blob/master/docs/TriceV1.0Specification.md) and [TCOBS](https://github.com/rokath/trice/blob/master/docs/TCOBSSpecification.md) spec in doc Folder.

Implement TREX encoding to reduce trice data

Works in trex2 branch in direct mode and deferred mode is wip.

Create tests for some taget mode variants using CGO

Merged with #286

TRICEs with \n need to regard line offset

Merged with #286 and #291

Add check til.json option

If one user checks in and pushes a til.json with a new Id A and an other user asigns Id A to a different trice and pulling til.json afterwards, there...

Add check til.json option

Merged with #291

Add check til.json option

The **trice** tool should perform such check internally when til.json is updated and emit a warning. The user than can correct the til.json file manually.