*****************************************************************************/\r
#define TRC_CFG_SNAPSHOT_MODE TRC_SNAPSHOT_MODE_RING_BUFFER\r
\r
-/*******************************************************************************\r
- * TRC_CFG_SCHEDULING_ONLY\r
- *\r
- * Macro which should be defined as an integer value.\r
- *\r
- * If this setting is enabled (= 1), only scheduling events are recorded.\r
- * If disabled (= 0), all events are recorded.\r
- *\r
- * For users of Tracealyzer Free Edition, that only displays scheduling events, this\r
- * option can be used to avoid storing other events.\r
- *\r
- * Default value is 0 (store all enabled events).\r
- *\r
- ******************************************************************************/\r
-#define TRC_CFG_SCHEDULING_ONLY 0\r
-\r
/*******************************************************************************\r
* TRC_CFG_EVENT_BUFFER_SIZE\r
*\r
#define TRC_CFG_NMUTEX 90\r
#define TRC_CFG_NTIMER 250\r
#define TRC_CFG_NEVENTGROUP 90\r
+#define TRC_CFG_NSTREAMBUFFER 5\r
+#define TRC_CFG_NMESSAGEBUFFER 5\r
\r
-/******************************************************************************\r
- * TRC_CFG_INCLUDE_MEMMANG_EVENTS\r
- *\r
- * Macro which should be defined as either zero (0) or one (1).\r
- *\r
- * This controls if malloc and free calls should be traced. Set this to zero (0)\r
- * to exclude malloc/free calls, or one (1) to include such events in the trace.\r
- *\r
- * Default value is 1.\r
- *****************************************************************************/\r
-#define TRC_CFG_INCLUDE_MEMMANG_EVENTS 1\r
-\r
-/******************************************************************************\r
- * TRC_CFG_INCLUDE_USER_EVENTS\r
- *\r
- * Macro which should be defined as either zero (0) or one (1).\r
- *\r
- * If this is zero (0) the code for creating User Events is excluded to\r
- * reduce code size. User Events are application-generated events, like\r
- * "printf" but for the trace log and the formatting is done offline, by the\r
- * Tracealyzer visualization tool. User Events are much faster than a printf\r
- * and can therefore be used in timing critical code.\r
- *\r
- * Default value is 1.\r
- *****************************************************************************/\r
-#define TRC_CFG_INCLUDE_USER_EVENTS 1\r
-\r
-/*****************************************************************************\r
- * TRC_CFG_INCLUDE_ISR_TRACING\r
- *\r
- * Macro which should be defined as either zero (0) or one (1).\r
- *\r
- * If this is zero (0), the code for recording Interrupt Service Routines is\r
- * excluded, in order to reduce code size.\r
- *\r
- * Default value is 1.\r
- *\r
- * Note: tracing ISRs requires that you insert calls to vTraceStoreISRBegin\r
- * and vTraceStoreISREnd in your interrupt handlers.\r
- *****************************************************************************/\r
-#define TRC_CFG_INCLUDE_ISR_TRACING 1\r
-\r
-/*****************************************************************************\r
- * TRC_CFG_INCLUDE_READY_EVENTS\r
- *\r
- * Macro which should be defined as either zero (0) or one (1).\r
- *\r
- * If one (1), events are recorded when tasks enter scheduling state "ready".\r
- * This allows Tracealyzer to show the initial pending time before tasks enter\r
- * the execution state, and present accurate response times.\r
- * If zero (0), "ready events" are not created, which allows for recording\r
- * longer traces in the same amount of RAM.\r
- *\r
- * Default value is 1.\r
- *****************************************************************************/\r
-#define TRC_CFG_INCLUDE_READY_EVENTS 1\r
-\r
-/*****************************************************************************\r
- * TRC_CFG_INCLUDE_OSTICK_EVENTS\r
- *\r
- * Macro which should be defined as either zero (0) or one (1).\r
- *\r
- * If this is one (1), events will be generated whenever the OS clock is\r
- * increased. If zero (0), OS tick events are not generated, which allows for\r
- * recording longer traces in the same amount of RAM.\r
- *\r
- * Default value is 0.\r
- *****************************************************************************/\r
-#define TRC_CFG_INCLUDE_OSTICK_EVENTS 1\r
\r
/******************************************************************************\r
* TRC_CFG_INCLUDE_FLOAT_SUPPORT\r
*****************************************************************************/\r
#define TRC_CFG_INCLUDE_FLOAT_SUPPORT 0\r
\r
-/******************************************************************************\r
- * TRC_CFG_INCLUDE_OBJECT_DELETE\r
- *\r
- * Macro which should be defined as either zero (0) or one (1).\r
- *\r
- * This must be enabled (1) if tasks, queues or other\r
- * traced kernel objects are deleted at runtime. If no deletes are made, this\r
- * can be set to 0 in order to exclude the delete-handling code.\r
- *\r
- * Default value is 1.\r
- *****************************************************************************/\r
-#define TRC_CFG_INCLUDE_OBJECT_DELETE 1\r
-\r
/*******************************************************************************\r
* TRC_CFG_SYMBOL_TABLE_SIZE\r
*\r
#define TRC_CFG_NAME_LEN_MUTEX 15\r
#define TRC_CFG_NAME_LEN_TIMER 15\r
#define TRC_CFG_NAME_LEN_EVENTGROUP 15\r
+#define TRC_CFG_NAME_LEN_STREAMBUFFER 15\r
+#define TRC_CFG_NAME_LEN_MESSAGEBUFFER 15\r
\r
/******************************************************************************\r
*** ADVANCED SETTINGS ********************************************************\r
projects / freertos / blobdiff