Adapted to FLEX encoding

README.md

@@ -52,7 +52,7 @@ Tiny & fast trace code for embedded device real-time PC logging (trace ID visual
 
 ## `TRICE` macros for C & C++ code
 
-- Real fast (**under 40 CPU clocks per trace possible!!!**)
+- Real fast (**12 CPU clocks per trice possible!!!**)
 - TRICE in your code **reduces the needed FLASH memory** because the instrumentation code is very small (can be less 150 bytes FLASH and about 100 bytes RAM) and no printf library code nor log strings are inside the embedded device anymore.
 
 ## Possible Use Cases
@@ -69,13 +69,14 @@ Tiny & fast trace code for embedded device real-time PC logging (trace ID visual
 - Using trice with an **RTOS** gives the option for detailed **task timing analysis**. Because of the very short execution time of a trice you could add
 
 ```c
-    TRICE8( "sig:task %d -> %d: ", previousTaskID, nexTaskID );
-    TRICE32( "tim:tick=%d\n", clock );
+    Trice8_2i( "sig:task %d -> %d: ", previousTaskID, nexTaskID );
+    Trice16_1i( "tim:tick=%d\n", clock );
 ```
 
  to the scheduler and vizualize the output on PC. The same is possible for **interrupt timing analysis**.
 
-- `TRICE16( "tim: myFunc %d\n", sysTick );` before and after a function call lets you easy measure the function execution time.
+- Mixed case trice macros are short trices and the letter i at the end says **i**nside critical section. (FLEX encoding)
+- `Trice16_1s( "tim: myFunc %d\n", sysTick );` before and after a function call lets you easy measure the function execution time.
 - As graphical vizualisation you could use a tool similar to https://github.com/sqshq/sampler.
 - TRICE has intentionally no target timestamps for performance reasons. On the PC you can display the *reception timestampts*. But you can add own **timestamps as parameters** for exact embedded time measurements. Having several devices with trice timestamps, **network timing measurement** is possible.