Update stream buffer tests to try resetting a statically allocated stream buffer before deleting it (tests fix in code).
Update trace recorder library.
diff --git a/FreeRTOS/Demo/Common/Minimal/StreamBufferDemo.c b/FreeRTOS/Demo/Common/Minimal/StreamBufferDemo.c
index a9058d5..5d93f57 100644
--- a/FreeRTOS/Demo/Common/Minimal/StreamBufferDemo.c
+++ b/FreeRTOS/Demo/Common/Minimal/StreamBufferDemo.c
@@ -644,6 +644,7 @@
 			string, but no data is written into the buffer so any valid address

 			will do. */

 			xTempStreamBuffer = xStreamBufferCreateStatic( sizeof( ucTempBuffer ), sbTRIGGER_LEVEL_1, ucTempBuffer, &xStaticStreamBuffer );

+			xStreamBufferReset( xTempStreamBuffer );

 			vStreamBufferDelete( xTempStreamBuffer );

 		}

 	}

diff --git a/FreeRTOS/Demo/WIN32-MSVC/Trace_Recorder_Configuration/trcConfig.h b/FreeRTOS/Demo/WIN32-MSVC/Trace_Recorder_Configuration/trcConfig.h
index 8da52ca..37345d4 100644
--- a/FreeRTOS/Demo/WIN32-MSVC/Trace_Recorder_Configuration/trcConfig.h
+++ b/FreeRTOS/Demo/WIN32-MSVC/Trace_Recorder_Configuration/trcConfig.h
@@ -98,6 +98,160 @@
  * TRC_RECORDER_MODE_STREAMING

  ******************************************************************************/

 #define TRC_CFG_RECORDER_MODE TRC_RECORDER_MODE_SNAPSHOT

+/******************************************************************************

+ * TRC_CFG_FREERTOS_VERSION

+ *

+ * Specify what version of FreeRTOS that is used (don't change unless using the

+ * trace recorder library with an older version of FreeRTOS).

+ *

+ * TRC_FREERTOS_VERSION_7_3						If using FreeRTOS v7.3.x

+ * TRC_FREERTOS_VERSION_7_4						If using FreeRTOS v7.4.x 

+ * TRC_FREERTOS_VERSION_7_5_OR_7_6				If using FreeRTOS v7.5.0 - v7.6.0

+ * TRC_FREERTOS_VERSION_8_X						If using FreeRTOS v8.X.X

+ * TRC_FREERTOS_VERSION_9_0_0					If using FreeRTOS v9.0.0

+ * TRC_FREERTOS_VERSION_9_0_1					If using FreeRTOS v9.0.1

+ * TRC_FREERTOS_VERSION_9_0_2					If using FreeRTOS v9.0.2

+ * TRC_FREERTOS_VERSION_10_0_0					If using FreeRTOS v10.0.0 or later

+ *****************************************************************************/

+#define TRC_CFG_FREERTOS_VERSION TRC_FREERTOS_VERSION_10_0_0

+

+/*******************************************************************************

+ * TRC_CFG_SCHEDULING_ONLY

+ *

+ * Macro which should be defined as an integer value.

+ *

+ * If this setting is enabled (= 1), only scheduling events are recorded.

+ * If disabled (= 0), all events are recorded (unless filtered in other ways).

+ *

+ * Default value is 0 (= include additional events).

+ ******************************************************************************/

+#define TRC_CFG_SCHEDULING_ONLY 0

+

+ /******************************************************************************

+ * TRC_CFG_INCLUDE_MEMMANG_EVENTS

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * This controls if malloc and free calls should be traced. Set this to zero (0)

+ * to exclude malloc/free calls, or one (1) to include such events in the trace.

+ *

+ * Default value is 1.

+ *****************************************************************************/

+#define TRC_CFG_INCLUDE_MEMMANG_EVENTS 1

+

+ /******************************************************************************

+ * TRC_CFG_INCLUDE_USER_EVENTS

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * If this is zero (0), all code related to User Events is excluded in order 

+ * to reduce code size. Any attempts of storing User Events are then silently

+ * ignored.

+ *

+ * User Events are application-generated events, like "printf" but for the 

+ * trace log, generated using vTracePrint and vTracePrintF. 

+ * The formatting is done on host-side, by Tracealyzer. User Events are 

+ * therefore much faster than a console printf and can often be used

+ * in timing critical code without problems.

+ *

+ * Note: In streaming mode, User Events are used to provide error messages

+ * and warnings from the recorder (in case of incorrect configuration) for

+ * display in Tracealyzer. Disabling user events will also disable these

+ * warnings. You can however still catch them by calling xTraceGetLastError

+ * or by putting breakpoints in prvTraceError and prvTraceWarning.

+ *

+ * Default value is 1.

+ *****************************************************************************/

+#define TRC_CFG_INCLUDE_USER_EVENTS 1

+

+ /*****************************************************************************

+ * TRC_CFG_INCLUDE_ISR_TRACING

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * If this is zero (0), the code for recording Interrupt Service Routines is

+ * excluded, in order to reduce code size.

+ *

+ * Default value is 1.

+ *

+ * Note: tracing ISRs requires that you insert calls to vTraceStoreISRBegin

+ * and vTraceStoreISREnd in your interrupt handlers.

+ *****************************************************************************/

+#define TRC_CFG_INCLUDE_ISR_TRACING 1

+

+ /*****************************************************************************

+ * TRC_CFG_INCLUDE_READY_EVENTS

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * If one (1), events are recorded when tasks enter scheduling state "ready".

+ * This allows Tracealyzer to show the initial pending time before tasks enter

+ * the execution state, and present accurate response times.

+ * If zero (0), "ready events" are not created, which allows for recording

+ * longer traces in the same amount of RAM.

+ *

+ * Default value is 1.

+ *****************************************************************************/

+#define TRC_CFG_INCLUDE_READY_EVENTS 1

+

+ /*****************************************************************************

+ * TRC_CFG_INCLUDE_OSTICK_EVENTS

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * If this is one (1), events will be generated whenever the OS clock is

+ * increased. If zero (0), OS tick events are not generated, which allows for

+ * recording longer traces in the same amount of RAM.

+ *

+ * Default value is 1.

+ *****************************************************************************/

+#define TRC_CFG_INCLUDE_OSTICK_EVENTS 1

+

+ /*****************************************************************************

+ * TRC_CFG_INCLUDE_EVENT_GROUP_EVENTS

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * If this is zero (0), the trace will exclude any "event group" events.

+ *

+ * Default value is 0 (excluded) since dependent on event_groups.c

+ *****************************************************************************/

+#define TRC_CFG_INCLUDE_EVENT_GROUP_EVENTS 1

+

+ /*****************************************************************************

+ * TRC_CFG_INCLUDE_TIMER_EVENTS

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * If this is zero (0), the trace will exclude any Timer events.

+ *

+ * Default value is 0 since dependent on timers.c

+ *****************************************************************************/

+#define TRC_CFG_INCLUDE_TIMER_EVENTS 1

+

+ /*****************************************************************************

+ * TRC_CFG_INCLUDE_PEND_FUNC_CALL_EVENTS

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * If this is zero (0), the trace will exclude any "pending function call" 

+ * events, such as xTimerPendFunctionCall().

+ *

+ * Default value is 0 since dependent on timers.c

+ *****************************************************************************/

+#define TRC_CFG_INCLUDE_PEND_FUNC_CALL_EVENTS 1

+

+/*******************************************************************************

+ * Configuration Macro: TRC_CFG_INCLUDE_STREAM_BUFFER_EVENTS

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * If this is zero (0), the trace will exclude any stream buffer or message

+ * buffer events.

+ *

+ * Default value is 0 since dependent on stream_buffer.c (new in FreeRTOS v10)

+ ******************************************************************************/

+#define TRC_CFG_INCLUDE_STREAM_BUFFER_EVENTS 1

 

 /*******************************************************************************

  * Configuration Macro: TRC_CFG_RECORDER_BUFFER_ALLOCATION

@@ -118,19 +272,6 @@
 #define TRC_CFG_RECORDER_BUFFER_ALLOCATION TRC_RECORDER_BUFFER_ALLOCATION_STATIC

 

 /******************************************************************************

- * TRC_CFG_FREERTOS_VERSION

- *

- * Specify what version of FreeRTOS that is used (don't change unless using the

- * trace recorder library with an older version of FreeRTOS).

- *

- * TRC_FREERTOS_VERSION_7_3_OR_7_4				If using FreeRTOS v7.3.0 - v7.4.2

- * TRC_FREERTOS_VERSION_7_5_OR_7_6				If using FreeRTOS v7.5.0 - v7.6.0

- * TRC_FREERTOS_VERSION_8_X						If using FreeRTOS v8.X.X

- * TRC_FREERTOS_VERSION_9_X						If using FreeRTOS v9.X.X

- *****************************************************************************/

-#define TRC_CFG_FREERTOS_VERSION	TRC_FREERTOS_VERSION_9_X

-

-/******************************************************************************

  * TRC_CFG_MAX_ISR_NESTING

  *

  * Defines how many levels of interrupt nesting the recorder can handle, in

diff --git a/FreeRTOS/Demo/WIN32-MSVC/Trace_Recorder_Configuration/trcSnapshotConfig.h b/FreeRTOS/Demo/WIN32-MSVC/Trace_Recorder_Configuration/trcSnapshotConfig.h
index 657fe33..8bb9221 100644
--- a/FreeRTOS/Demo/WIN32-MSVC/Trace_Recorder_Configuration/trcSnapshotConfig.h
+++ b/FreeRTOS/Demo/WIN32-MSVC/Trace_Recorder_Configuration/trcSnapshotConfig.h
@@ -70,22 +70,6 @@
 #define TRC_CFG_SNAPSHOT_MODE TRC_SNAPSHOT_MODE_RING_BUFFER

 

 /*******************************************************************************

- * TRC_CFG_SCHEDULING_ONLY

- *

- * Macro which should be defined as an integer value.

- *

- * If this setting is enabled (= 1), only scheduling events are recorded.

- * If disabled (= 0), all events are recorded.

- *

- * For users of Tracealyzer Free Edition, that only displays scheduling events, this

- * option can be used to avoid storing other events.

- *

- * Default value is 0 (store all enabled events).

- *

- ******************************************************************************/

-#define TRC_CFG_SCHEDULING_ONLY 0

-

-/*******************************************************************************

  * TRC_CFG_EVENT_BUFFER_SIZE

  *

  * Macro which should be defined as an integer value.

@@ -129,76 +113,9 @@
 #define TRC_CFG_NMUTEX			90

 #define TRC_CFG_NTIMER			250

 #define TRC_CFG_NEVENTGROUP		90

+#define TRC_CFG_NSTREAMBUFFER	5

+#define TRC_CFG_NMESSAGEBUFFER	5

 

-/******************************************************************************

- * TRC_CFG_INCLUDE_MEMMANG_EVENTS

- *

- * Macro which should be defined as either zero (0) or one (1).

- *

- * This controls if malloc and free calls should be traced. Set this to zero (0)

- * to exclude malloc/free calls, or one (1) to include such events in the trace.

- *

- * Default value is 1.

- *****************************************************************************/

-#define TRC_CFG_INCLUDE_MEMMANG_EVENTS 1

-

-/******************************************************************************

- * TRC_CFG_INCLUDE_USER_EVENTS

- *

- * Macro which should be defined as either zero (0) or one (1).

- *

- * If this is zero (0) the code for creating User Events is excluded to

- * reduce code size. User Events are application-generated events, like

- * "printf" but for the trace log and the formatting is done offline, by the

- * Tracealyzer visualization tool. User Events are much faster than a printf

- * and can therefore be used in timing critical code.

- *

- * Default value is 1.

- *****************************************************************************/

-#define TRC_CFG_INCLUDE_USER_EVENTS 1

-

-/*****************************************************************************

- * TRC_CFG_INCLUDE_ISR_TRACING

- *

- * Macro which should be defined as either zero (0) or one (1).

- *

- * If this is zero (0), the code for recording Interrupt Service Routines is

- * excluded, in order to reduce code size.

- *

- * Default value is 1.

- *

- * Note: tracing ISRs requires that you insert calls to vTraceStoreISRBegin

- * and vTraceStoreISREnd in your interrupt handlers.

- *****************************************************************************/

-#define TRC_CFG_INCLUDE_ISR_TRACING 1

-

-/*****************************************************************************

- * TRC_CFG_INCLUDE_READY_EVENTS

- *

- * Macro which should be defined as either zero (0) or one (1).

- *

- * If one (1), events are recorded when tasks enter scheduling state "ready".

- * This allows Tracealyzer to show the initial pending time before tasks enter

- * the execution state, and present accurate response times.

- * If zero (0), "ready events" are not created, which allows for recording

- * longer traces in the same amount of RAM.

- *

- * Default value is 1.

- *****************************************************************************/

-#define TRC_CFG_INCLUDE_READY_EVENTS 1

-

-/*****************************************************************************

- * TRC_CFG_INCLUDE_OSTICK_EVENTS

- *

- * Macro which should be defined as either zero (0) or one (1).

- *

- * If this is one (1), events will be generated whenever the OS clock is

- * increased. If zero (0), OS tick events are not generated, which allows for

- * recording longer traces in the same amount of RAM.

- *

- * Default value is 0.

- *****************************************************************************/

-#define TRC_CFG_INCLUDE_OSTICK_EVENTS 1

 

 /******************************************************************************

  * TRC_CFG_INCLUDE_FLOAT_SUPPORT

@@ -218,19 +135,6 @@
  *****************************************************************************/

 #define TRC_CFG_INCLUDE_FLOAT_SUPPORT 0

 

-/******************************************************************************

- * TRC_CFG_INCLUDE_OBJECT_DELETE

- *

- * Macro which should be defined as either zero (0) or one (1).

- *

- * This must be enabled (1) if tasks, queues or other

- * traced kernel objects are deleted at runtime. If no deletes are made, this

- * can be set to 0 in order to exclude the delete-handling code.

- *

- * Default value is 1.

- *****************************************************************************/

-#define TRC_CFG_INCLUDE_OBJECT_DELETE 1

-

 /*******************************************************************************

  * TRC_CFG_SYMBOL_TABLE_SIZE

  *

@@ -265,6 +169,8 @@
 #define TRC_CFG_NAME_LEN_MUTEX			15

 #define TRC_CFG_NAME_LEN_TIMER			15

 #define TRC_CFG_NAME_LEN_EVENTGROUP 	15

+#define TRC_CFG_NAME_LEN_STREAMBUFFER 	15

+#define TRC_CFG_NAME_LEN_MESSAGEBUFFER 	15

 

 /******************************************************************************

  *** ADVANCED SETTINGS ********************************************************

diff --git a/FreeRTOS/Demo/WIN32-MingW/Trace_Recorder_Configuration/trcConfig.h b/FreeRTOS/Demo/WIN32-MingW/Trace_Recorder_Configuration/trcConfig.h
index 8da52ca..37345d4 100644
--- a/FreeRTOS/Demo/WIN32-MingW/Trace_Recorder_Configuration/trcConfig.h
+++ b/FreeRTOS/Demo/WIN32-MingW/Trace_Recorder_Configuration/trcConfig.h
@@ -98,6 +98,160 @@
  * TRC_RECORDER_MODE_STREAMING

  ******************************************************************************/

 #define TRC_CFG_RECORDER_MODE TRC_RECORDER_MODE_SNAPSHOT

+/******************************************************************************

+ * TRC_CFG_FREERTOS_VERSION

+ *

+ * Specify what version of FreeRTOS that is used (don't change unless using the

+ * trace recorder library with an older version of FreeRTOS).

+ *

+ * TRC_FREERTOS_VERSION_7_3						If using FreeRTOS v7.3.x

+ * TRC_FREERTOS_VERSION_7_4						If using FreeRTOS v7.4.x 

+ * TRC_FREERTOS_VERSION_7_5_OR_7_6				If using FreeRTOS v7.5.0 - v7.6.0

+ * TRC_FREERTOS_VERSION_8_X						If using FreeRTOS v8.X.X

+ * TRC_FREERTOS_VERSION_9_0_0					If using FreeRTOS v9.0.0

+ * TRC_FREERTOS_VERSION_9_0_1					If using FreeRTOS v9.0.1

+ * TRC_FREERTOS_VERSION_9_0_2					If using FreeRTOS v9.0.2

+ * TRC_FREERTOS_VERSION_10_0_0					If using FreeRTOS v10.0.0 or later

+ *****************************************************************************/

+#define TRC_CFG_FREERTOS_VERSION TRC_FREERTOS_VERSION_10_0_0

+

+/*******************************************************************************

+ * TRC_CFG_SCHEDULING_ONLY

+ *

+ * Macro which should be defined as an integer value.

+ *

+ * If this setting is enabled (= 1), only scheduling events are recorded.

+ * If disabled (= 0), all events are recorded (unless filtered in other ways).

+ *

+ * Default value is 0 (= include additional events).

+ ******************************************************************************/

+#define TRC_CFG_SCHEDULING_ONLY 0

+

+ /******************************************************************************

+ * TRC_CFG_INCLUDE_MEMMANG_EVENTS

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * This controls if malloc and free calls should be traced. Set this to zero (0)

+ * to exclude malloc/free calls, or one (1) to include such events in the trace.

+ *

+ * Default value is 1.

+ *****************************************************************************/

+#define TRC_CFG_INCLUDE_MEMMANG_EVENTS 1

+

+ /******************************************************************************

+ * TRC_CFG_INCLUDE_USER_EVENTS

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * If this is zero (0), all code related to User Events is excluded in order 

+ * to reduce code size. Any attempts of storing User Events are then silently

+ * ignored.

+ *

+ * User Events are application-generated events, like "printf" but for the 

+ * trace log, generated using vTracePrint and vTracePrintF. 

+ * The formatting is done on host-side, by Tracealyzer. User Events are 

+ * therefore much faster than a console printf and can often be used

+ * in timing critical code without problems.

+ *

+ * Note: In streaming mode, User Events are used to provide error messages

+ * and warnings from the recorder (in case of incorrect configuration) for

+ * display in Tracealyzer. Disabling user events will also disable these

+ * warnings. You can however still catch them by calling xTraceGetLastError

+ * or by putting breakpoints in prvTraceError and prvTraceWarning.

+ *

+ * Default value is 1.

+ *****************************************************************************/

+#define TRC_CFG_INCLUDE_USER_EVENTS 1

+

+ /*****************************************************************************

+ * TRC_CFG_INCLUDE_ISR_TRACING

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * If this is zero (0), the code for recording Interrupt Service Routines is

+ * excluded, in order to reduce code size.

+ *

+ * Default value is 1.

+ *

+ * Note: tracing ISRs requires that you insert calls to vTraceStoreISRBegin

+ * and vTraceStoreISREnd in your interrupt handlers.

+ *****************************************************************************/

+#define TRC_CFG_INCLUDE_ISR_TRACING 1

+

+ /*****************************************************************************

+ * TRC_CFG_INCLUDE_READY_EVENTS

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * If one (1), events are recorded when tasks enter scheduling state "ready".

+ * This allows Tracealyzer to show the initial pending time before tasks enter

+ * the execution state, and present accurate response times.

+ * If zero (0), "ready events" are not created, which allows for recording

+ * longer traces in the same amount of RAM.

+ *

+ * Default value is 1.

+ *****************************************************************************/

+#define TRC_CFG_INCLUDE_READY_EVENTS 1

+

+ /*****************************************************************************

+ * TRC_CFG_INCLUDE_OSTICK_EVENTS

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * If this is one (1), events will be generated whenever the OS clock is

+ * increased. If zero (0), OS tick events are not generated, which allows for

+ * recording longer traces in the same amount of RAM.

+ *

+ * Default value is 1.

+ *****************************************************************************/

+#define TRC_CFG_INCLUDE_OSTICK_EVENTS 1

+

+ /*****************************************************************************

+ * TRC_CFG_INCLUDE_EVENT_GROUP_EVENTS

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * If this is zero (0), the trace will exclude any "event group" events.

+ *

+ * Default value is 0 (excluded) since dependent on event_groups.c

+ *****************************************************************************/

+#define TRC_CFG_INCLUDE_EVENT_GROUP_EVENTS 1

+

+ /*****************************************************************************

+ * TRC_CFG_INCLUDE_TIMER_EVENTS

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * If this is zero (0), the trace will exclude any Timer events.

+ *

+ * Default value is 0 since dependent on timers.c

+ *****************************************************************************/

+#define TRC_CFG_INCLUDE_TIMER_EVENTS 1

+

+ /*****************************************************************************

+ * TRC_CFG_INCLUDE_PEND_FUNC_CALL_EVENTS

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * If this is zero (0), the trace will exclude any "pending function call" 

+ * events, such as xTimerPendFunctionCall().

+ *

+ * Default value is 0 since dependent on timers.c

+ *****************************************************************************/

+#define TRC_CFG_INCLUDE_PEND_FUNC_CALL_EVENTS 1

+

+/*******************************************************************************

+ * Configuration Macro: TRC_CFG_INCLUDE_STREAM_BUFFER_EVENTS

+ *

+ * Macro which should be defined as either zero (0) or one (1).

+ *

+ * If this is zero (0), the trace will exclude any stream buffer or message

+ * buffer events.

+ *

+ * Default value is 0 since dependent on stream_buffer.c (new in FreeRTOS v10)

+ ******************************************************************************/

+#define TRC_CFG_INCLUDE_STREAM_BUFFER_EVENTS 1

 

 /*******************************************************************************

  * Configuration Macro: TRC_CFG_RECORDER_BUFFER_ALLOCATION

@@ -118,19 +272,6 @@
 #define TRC_CFG_RECORDER_BUFFER_ALLOCATION TRC_RECORDER_BUFFER_ALLOCATION_STATIC

 

 /******************************************************************************

- * TRC_CFG_FREERTOS_VERSION

- *

- * Specify what version of FreeRTOS that is used (don't change unless using the

- * trace recorder library with an older version of FreeRTOS).

- *

- * TRC_FREERTOS_VERSION_7_3_OR_7_4				If using FreeRTOS v7.3.0 - v7.4.2

- * TRC_FREERTOS_VERSION_7_5_OR_7_6				If using FreeRTOS v7.5.0 - v7.6.0

- * TRC_FREERTOS_VERSION_8_X						If using FreeRTOS v8.X.X

- * TRC_FREERTOS_VERSION_9_X						If using FreeRTOS v9.X.X

- *****************************************************************************/

-#define TRC_CFG_FREERTOS_VERSION	TRC_FREERTOS_VERSION_9_X

-

-/******************************************************************************

  * TRC_CFG_MAX_ISR_NESTING

  *

  * Defines how many levels of interrupt nesting the recorder can handle, in

diff --git a/FreeRTOS/Demo/WIN32-MingW/Trace_Recorder_Configuration/trcSnapshotConfig.h b/FreeRTOS/Demo/WIN32-MingW/Trace_Recorder_Configuration/trcSnapshotConfig.h
index 657fe33..8bb9221 100644
--- a/FreeRTOS/Demo/WIN32-MingW/Trace_Recorder_Configuration/trcSnapshotConfig.h
+++ b/FreeRTOS/Demo/WIN32-MingW/Trace_Recorder_Configuration/trcSnapshotConfig.h
@@ -70,22 +70,6 @@
 #define TRC_CFG_SNAPSHOT_MODE TRC_SNAPSHOT_MODE_RING_BUFFER

 

 /*******************************************************************************

- * TRC_CFG_SCHEDULING_ONLY

- *

- * Macro which should be defined as an integer value.

- *

- * If this setting is enabled (= 1), only scheduling events are recorded.

- * If disabled (= 0), all events are recorded.

- *

- * For users of Tracealyzer Free Edition, that only displays scheduling events, this

- * option can be used to avoid storing other events.

- *

- * Default value is 0 (store all enabled events).

- *

- ******************************************************************************/

-#define TRC_CFG_SCHEDULING_ONLY 0

-

-/*******************************************************************************

  * TRC_CFG_EVENT_BUFFER_SIZE

  *

  * Macro which should be defined as an integer value.

@@ -129,76 +113,9 @@
 #define TRC_CFG_NMUTEX			90

 #define TRC_CFG_NTIMER			250

 #define TRC_CFG_NEVENTGROUP		90

+#define TRC_CFG_NSTREAMBUFFER	5

+#define TRC_CFG_NMESSAGEBUFFER	5

 

-/******************************************************************************

- * TRC_CFG_INCLUDE_MEMMANG_EVENTS

- *

- * Macro which should be defined as either zero (0) or one (1).

- *

- * This controls if malloc and free calls should be traced. Set this to zero (0)

- * to exclude malloc/free calls, or one (1) to include such events in the trace.

- *

- * Default value is 1.

- *****************************************************************************/

-#define TRC_CFG_INCLUDE_MEMMANG_EVENTS 1

-

-/******************************************************************************

- * TRC_CFG_INCLUDE_USER_EVENTS

- *

- * Macro which should be defined as either zero (0) or one (1).

- *

- * If this is zero (0) the code for creating User Events is excluded to

- * reduce code size. User Events are application-generated events, like

- * "printf" but for the trace log and the formatting is done offline, by the

- * Tracealyzer visualization tool. User Events are much faster than a printf

- * and can therefore be used in timing critical code.

- *

- * Default value is 1.

- *****************************************************************************/

-#define TRC_CFG_INCLUDE_USER_EVENTS 1

-

-/*****************************************************************************

- * TRC_CFG_INCLUDE_ISR_TRACING

- *

- * Macro which should be defined as either zero (0) or one (1).

- *

- * If this is zero (0), the code for recording Interrupt Service Routines is

- * excluded, in order to reduce code size.

- *

- * Default value is 1.

- *

- * Note: tracing ISRs requires that you insert calls to vTraceStoreISRBegin

- * and vTraceStoreISREnd in your interrupt handlers.

- *****************************************************************************/

-#define TRC_CFG_INCLUDE_ISR_TRACING 1

-

-/*****************************************************************************

- * TRC_CFG_INCLUDE_READY_EVENTS

- *

- * Macro which should be defined as either zero (0) or one (1).

- *

- * If one (1), events are recorded when tasks enter scheduling state "ready".

- * This allows Tracealyzer to show the initial pending time before tasks enter

- * the execution state, and present accurate response times.

- * If zero (0), "ready events" are not created, which allows for recording

- * longer traces in the same amount of RAM.

- *

- * Default value is 1.

- *****************************************************************************/

-#define TRC_CFG_INCLUDE_READY_EVENTS 1

-

-/*****************************************************************************

- * TRC_CFG_INCLUDE_OSTICK_EVENTS

- *

- * Macro which should be defined as either zero (0) or one (1).

- *

- * If this is one (1), events will be generated whenever the OS clock is

- * increased. If zero (0), OS tick events are not generated, which allows for

- * recording longer traces in the same amount of RAM.

- *

- * Default value is 0.

- *****************************************************************************/

-#define TRC_CFG_INCLUDE_OSTICK_EVENTS 1

 

 /******************************************************************************

  * TRC_CFG_INCLUDE_FLOAT_SUPPORT

@@ -218,19 +135,6 @@
  *****************************************************************************/

 #define TRC_CFG_INCLUDE_FLOAT_SUPPORT 0

 

-/******************************************************************************

- * TRC_CFG_INCLUDE_OBJECT_DELETE

- *

- * Macro which should be defined as either zero (0) or one (1).

- *

- * This must be enabled (1) if tasks, queues or other

- * traced kernel objects are deleted at runtime. If no deletes are made, this

- * can be set to 0 in order to exclude the delete-handling code.

- *

- * Default value is 1.

- *****************************************************************************/

-#define TRC_CFG_INCLUDE_OBJECT_DELETE 1

-

 /*******************************************************************************

  * TRC_CFG_SYMBOL_TABLE_SIZE

  *

@@ -265,6 +169,8 @@
 #define TRC_CFG_NAME_LEN_MUTEX			15

 #define TRC_CFG_NAME_LEN_TIMER			15

 #define TRC_CFG_NAME_LEN_EVENTGROUP 	15

+#define TRC_CFG_NAME_LEN_STREAMBUFFER 	15

+#define TRC_CFG_NAME_LEN_MESSAGEBUFFER 	15

 

 /******************************************************************************

  *** ADVANCED SETTINGS ********************************************************