diff options
Diffstat (limited to 'test')
| -rw-r--r-- | test/coverage/halconf.h | 34 | ||||
| -rw-r--r-- | test/test.c | 2 | ||||
| -rw-r--r-- | test/test.dox | 8 |
3 files changed, 28 insertions, 16 deletions
diff --git a/test/coverage/halconf.h b/test/coverage/halconf.h index 2829fb066..50f223ef8 100644 --- a/test/coverage/halconf.h +++ b/test/coverage/halconf.h @@ -56,6 +56,13 @@ #endif
/**
+ * @brief Enables the EXT subsystem.
+ */
+#if !defined(HAL_USE_EXT) || defined(__DOXYGEN__)
+#define HAL_USE_EXT FALSE
+#endif
+
+/**
* @brief Enables the GPT subsystem.
*/
#if !defined(HAL_USE_GPT) || defined(__DOXYGEN__)
@@ -98,6 +105,13 @@ #endif
/**
+ * @brief Enables the RTC subsystem.
+ */
+#if !defined(HAL_USE_RTC) || defined(__DOXYGEN__)
+#define HAL_USE_RTC FALSE
+#endif
+
+/**
* @brief Enables the SDC subsystem.
*/
#if !defined(HAL_USE_SDC) || defined(__DOXYGEN__)
@@ -185,6 +199,13 @@ /* MAC driver related settings. */
/*===========================================================================*/
+/**
+ * @brief Enables an event sources for incoming packets.
+ */
+#if !defined(MAC_USE_EVENTS) || defined(__DOXYGEN__)
+#define MAC_USE_EVENTS TRUE
+#endif
+
/*===========================================================================*/
/* MMC_SPI driver related settings. */
/*===========================================================================*/
@@ -235,16 +256,9 @@ #endif
/*===========================================================================*/
-/* PAL driver related settings. */
-/*===========================================================================*/
-
-/*===========================================================================*/
-/* PWM driver related settings. */
-/*===========================================================================*/
-
-/*===========================================================================*/
/* SDC driver related settings. */
/*===========================================================================*/
+
/**
* @brief Number of initialization attempts before rejecting the card.
* @note Attempts are performed at 10mS intevals.
@@ -316,10 +330,6 @@ #define SPI_USE_MUTUAL_EXCLUSION TRUE
#endif
-/*===========================================================================*/
-/* UART driver related settings. */
-/*===========================================================================*/
-
#endif /* _HALCONF_H_ */
/** @} */
diff --git a/test/test.c b/test/test.c index 41662308c..74069415c 100644 --- a/test/test.c +++ b/test/test.c @@ -328,6 +328,8 @@ msg_t TestThread(void *p) { test_println("***");
test_print("*** Kernel: ");
test_println(CH_KERNEL_VERSION);
+ test_print("*** Compiled: ");
+ test_println(__DATE__ " - " __TIME__);
#ifdef CH_COMPILER_NAME
test_print("*** Compiler: ");
test_println(CH_COMPILER_NAME);
diff --git a/test/test.dox b/test/test.dox index 296e2145e..114b2af85 100644 --- a/test/test.dox +++ b/test/test.dox @@ -46,15 +46,15 @@ * for this execution test, it is done automatically by a script because
* the entire sequence can take hours).<br>
* All the tests results are included as reports in the OS distribution
- * under @p ./docs/reports.
+ * under <tt>./docs/reports</tt>.
* - <b>Ports</b>. The port code is tested by executing the kernel test
* suite on the target hardware. A port is validated only if it passes all
* the tests. Speed and size benchmarks for all the supported architectures
* are performed, both size and speed regressions are <b>monitored</b>.
* - <b>HAL</b>. The HAL high level code and device drivers implementations
- * are tested by use in the various demos and/or by users.
+ * are tested through specific test applications under <tt>./testhal</tt>.
* - <b>Various</b>. The miscellaneous code is tested by use in the various
- * demos and/or by users.
+ * demos.
* - <b>External Code</b>. Not tested, external libraries or components are
* used as-is or with minor patching where required, problems are usually
* reported upstream.
@@ -65,7 +65,7 @@ * subsystems and can report a failure/success status and/or a performance
* index as the test suite output.<br>
* The test suite is usually activated in the demo applications by pressing a
- * button on the target board, see the readme into the various demos
+ * button on the target board, see the readme file into the various demos
* directories. The test suite output is usually sent through a serial port
* and can be examined by using a terminal emulator program.
*
|