Merge branch 'main' into out-of-bounds

Author: fdesbiens

rtos-docs/netx-duo/netx-duo-bsd/chapter2.adoc

@@ -44,7 +44,7 @@ In order to use NetX Duo BSD the entire distribution mentioned previously should
 The ThreadX library must define `bsd_errno` in the thread local storage. We recommend the following procedure:
 
 . In _tx_port.h_, set one of the TX_THREAD_EXTENSION macros as follows:
- ** `#define TX_THREAD_EXTENSION_3     int bsd_errno`
+ ** `#define TX_THREAD_EXTENSION_3     int bsd_errno;`
 . Rebuild the ThreadX library.
 
 NOTE: If TX_THREAD_EXTENSION_3 is already used, the user is free to use one of the other TX_THREAD_EXTENSION macros.

rtos-docs/threadx/appendix-e.adoc

@@ -215,7 +215,7 @@ source code. However, to enable the reuse, macros are used to replace
 data structures specific to each core with function calls or an array
 indexed by core, like the following:
 
-image::misra-Compliance/image1.png[Image that shows an array indexed by core.]
+image::media/misra-Compliance/image1.png[Image that shows an array indexed by core.]
 
 Technically, this isn't replacing a reserved identifier, but the
 MISRA-C:2004 specification indicates that anything with an underscore
@@ -248,13 +248,13 @@ C-STAT 1.4.4 MISRA-C:2004 and MISRA C:2012. The following figures show
 the MISRA C rules checked by C-STAT (and should also serve as a
 compliance matrix):
 
-image::misra-Compliance/image2.png[Image that shows IAR EWARM 8.11.1.]
+image::media/misra-Compliance/image2.png[Image that shows IAR EWARM 8.11.1.]
 
-image::misra-Compliance/image3.png[Image that shows C-STAT 1.4.4.]
+image::media/misra-Compliance/image3.png[Image that shows C-STAT 1.4.4.]
 
-image::misra-Compliance/image4.png[Image that shows MISRA-C:2004.]
+image::media/misra-Compliance/image4.png[Image that shows MISRA-C:2004.]
 
-image::misra-Compliance/image5.png[Image that shows MISRA C:2012.]
+image::media/misra-Compliance/image5.png[Image that shows MISRA C:2012.]
 
 *Figure 1: MISRA-C:2004/MISRA C:2012 Compliance Matrix*
 
@@ -276,7 +276,7 @@ achieve full MISRA compliance. In addition to building ThreadX SMP with
 *_TX_MISRA_ENABLE_*, the ThreadX project should have the C dialect C89
 specified and strict language conformance selected, as follows:
 
-image::misra-Compliance/image6.png[Screenshot that shows strict language conformance.]
+image::media/misra-Compliance/image6.png[Screenshot that shows strict language conformance.]
 
 Next, if the version of ThreadX does not have a pre-built
 *_tx_misra.s_* assembly file, the *_tx_misra.c_* file should be