Searched refs:port (Results 1 – 25 of 89) sorted by relevance
1234
| /Kernel-v10.6.2/portable/ |
| D | CMakeLists.txt | 14 BCC/16BitDOS/Flsh186/port.c>
18 BCC/16BitDOS/PC/port.c>
20 # ARMv7-M port for Texas Instruments Code Composer Studio
22 CCS/ARM_CM3/port.c
25 # ARMv7E-M port for Texas Instruments Code Composer Studio
27 CCS/ARM_CM4F/port.c
30 # ARMv7-R port for Texas Instruments Code Composer Studio
32 CCS/ARM_Cortex-R4/port.c
35 # Texas Instruments MSP430 port for Texas Instruments Code Composer Studio
37 CCS/MSP430X/port.c
[all …]
|
| D | readme.txt | 1 Each real time kernel port consists of three files that contain the core kernel
2 components and are common to every port, and one or more files that are
15 For example, if you are interested in the [compiler] port for the [architecture]
16 microcontroller, then the port specific files are contained in
18 only port you are interested in then all the other directories can be
|
| /Kernel-v10.6.2/ |
| D | sbom.spdx | 106 FileName: ./portable/MikroC/ARM_CM4F/port.c
107 SPDXID: SPDXRef-File-portable-MikroC-ARM_CM4F-port.c
113 FileName: ./portable/Tasking/ARM_CM4F/port.c
114 SPDXID: SPDXRef-File-portable-Tasking-ARM_CM4F-port.c
120 FileName: ./portable/MSVC-MingW/port.c
121 SPDXID: SPDXRef-File-portable-MSVC-MingW-port.c
127 FileName: ./portable/RVDS/ARM_CM0/port.c
128 SPDXID: SPDXRef-File-portable-RVDS-ARM_CM0-port.c
134 FileName: ./portable/RVDS/ARM7_LPC21xx/port.c
135 SPDXID: SPDXRef-File-portable-RVDS-ARM7_LPC21xx-port.c
[all …]
|
| D | History.txt | 92 + Add Cortex-M35P port. Contributed by @urutva.
93 + Add embedded extension (RV32E) support to the IAR RISC-V port.
126 + Fix build warning in MSP430X port when large data model is used.
127 + Add the ability to use Cortex-R5 port on the parts without FPU.
134 + Fix build issue in POSIX GCC port on Windows Subsystem for Linux (WSL). Contributed
136 + Add portMEMORY_BARRIER to Microblaze port. Contributed by @bbain.
137 + Add portPOINTER_SIZE_TYPE definition for ATmega port. Contributed by @jputcu.
180 + Add vectored mode interrupt support to the RISC-V port.
181 + Add support for RV32E extension (Embedded Profile) in RISC-V GCC port.
223 + Add hardware stack protection support to MicroBlazeV9 port. This ensures that
[all …]
|
| /Kernel-v10.6.2/portable/ThirdParty/ |
| D | README.md | 12 FreeRTOS team supported third party FreeRTOS port:
20 A new FreeRTOS port cannot be directly contributed to this location. Instead,
22 community supported FreeRTOS port based on the community interest.
29 supported FreeRTOS port:
36 A new FreeRTOS port can be directly contributed by a partner. The process to
37 contribute a FreeRTOS port is documented [here](https://github.com/FreeRTOS/FreeRTOS-Kernel-Partner…
44 community supported FreeRTOS port:
47 * Tests may or may not exist for the FreeRTOS port.
50 A new FreeRTOS port can be directly contributed by anyone. The process to
51 contribute a FreeRTOS port is documented [here](https://github.com/FreeRTOS/FreeRTOS-Kernel-Communi…
|
| /Kernel-v10.6.2/portable/GCC/ARM_CM7/ |
| D | ReadMe.txt | 6 the FreeRTOS port provided specifically for r0p1 revisions, as that can be used
9 The first option is to use the ARM Cortex-M4F port, and the second option is to
10 use the Cortex-M7 r0p1 port - the latter containing a minor errata workaround.
13 used, but it is recommended to use the FreeRTOS ARM Cortex-M4F port located in
17 Cortex-M7 r0p1 port located in the /FreeRTOS/Source/portable/GCC/ARM_CM7/r0p1
|
| /Kernel-v10.6.2/portable/IAR/ARM_CM7/ |
| D | ReadMe.txt | 6 the FreeRTOS port provided specifically for r0p1 revisions, as that can be used
9 The first option is to use the ARM Cortex-M4F port, and the second option is to
10 use the Cortex-M7 r0p1 port - the latter containing a minor errata workaround.
13 used, but it is recommended to use the FreeRTOS ARM Cortex-M4F port located in
17 Cortex-M7 r0p1 port located in the /FreeRTOS/Source/portable/IAR/ARM_CM7/r0p1
|
| /Kernel-v10.6.2/portable/RVDS/ARM_CM7/ |
| D | ReadMe.txt | 6 the FreeRTOS port provided specifically for r0p1 revisions, as that can be used
9 The first option is to use the ARM Cortex-M4F port, and the second option is to
10 use the Cortex-M7 r0p1 port - the latter containing a minor errata workaround.
13 used, but it is recommended to use the FreeRTOS ARM Cortex-M4F port located in
17 Cortex-M7 r0p1 port located in the /FreeRTOS/Source/portable/RVDS/ARM_CM7/r0p1
|
| /Kernel-v10.6.2/portable/GCC/MCF5235/ |
| D | readme.md | 1 The MCF5235 port is deprecated. The last FreeRTOS version that includes this port is 10.4.3.
|
| /Kernel-v10.6.2/portable/ARMClang/ |
| D | Use-the-GCC-ports.txt | 1 The FreeRTOS GCC port layer also builds and works with the ARMClang compiler.
2 To use the ARMClang compiler build the port files from FreeRTOS/Source/portable/GCC.
|
| /Kernel-v10.6.2/portable/IAR/RISC-V/chip_specific_extensions/ |
| D | readme.txt | 2 * The FreeRTOS kernel's RISC-V port is split between the the code that is
4 * RISC-V ISA), and code that tailors the port to a specific RISC-V chip:
11 * code that tailors the FreeRTOS kernel's RISC-V port to a specific RISC-V
|
| /Kernel-v10.6.2/portable/IAR/RISC-V/ |
| D | readme.txt | 2 * The FreeRTOS kernel's RISC-V port is split between the the code that is
4 * RISC-V ISA), and code that tailors the port to a specific RISC-V chip:
11 * code that tailors the FreeRTOS kernel's RISC-V port to a specific RISC-V
|
| /Kernel-v10.6.2/portable/GCC/RISC-V/chip_specific_extensions/ |
| D | readme.txt | 2 * The FreeRTOS kernel's RISC-V port is split between the the code that is
4 * RISC-V ISA), and code that tailors the port to a specific RISC-V chip:
11 * code that tailors the FreeRTOS kernel's RISC-V port to a specific RISC-V
|
| /Kernel-v10.6.2/portable/GCC/RISC-V/ |
| D | readme.txt | 2 * The FreeRTOS kernel's RISC-V port is split between the the code that is
4 * RISC-V ISA), and code that tailors the port to a specific RISC-V chip:
11 * code that tailors the FreeRTOS kernel's RISC-V port to a specific RISC-V
|
| /Kernel-v10.6.2/portable/ThirdParty/GCC/ARM_TFM/ |
| D | README.md | 1 # Target of this port
3 This port adds the support that FreeRTOS applications can call the secure
23 To build a project based on this port:
31 …edfirmware.org/TF-M/trusted-firmware-m.git/) to get the source code. This port is supported by TF-…
40 …\ThirdParty\GCC\ARM_TFM``` folder before using this port. Note that TrustZone is enabled in this p…
48 This macro should be configured as 0. In this port, TF-M runs in the Secure Side while FreeRTOS
|
| /Kernel-v10.6.2/portable/IAR/RX700v3_DPFPU/ |
| D | readme.txt | 1 The following table shows which port is recommended to be used.
46 the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems …
50 functionality is used, please modify port.c for the configuration. Please be aware that port.c is
62 …: PriorityDefinitions.h has to be provided for port_asm.s in case of other than RX700v3_DPFPU port.
|
| /Kernel-v10.6.2/portable/IAR/RXv2/ |
| D | readme.txt | 1 The following table shows which port is recommended to be used.
46 the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems …
50 functionality is used, please modify port.c for the configuration. Please be aware that port.c is
62 …: PriorityDefinitions.h has to be provided for port_asm.s in case of other than RX700v3_DPFPU port.
|
| /Kernel-v10.6.2/portable/IAR/RX100/ |
| D | readme.txt | 1 The following table shows which port is recommended to be used.
46 the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems …
50 functionality is used, please modify port.c for the configuration. Please be aware that port.c is
62 …: PriorityDefinitions.h has to be provided for port_asm.s in case of other than RX700v3_DPFPU port.
|
| /Kernel-v10.6.2/portable/IAR/RX600/ |
| D | readme.txt | 1 The following table shows which port is recommended to be used.
46 the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems …
50 functionality is used, please modify port.c for the configuration. Please be aware that port.c is
62 …: PriorityDefinitions.h has to be provided for port_asm.s in case of other than RX700v3_DPFPU port.
|
| /Kernel-v10.6.2/portable/GCC/RX100/ |
| D | readme.txt | 1 The following table shows which port is recommended to be used.
46 the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems …
50 functionality is used, please modify port.c for the configuration. Please be aware that port.c is
62 …: PriorityDefinitions.h has to be provided for port_asm.s in case of other than RX700v3_DPFPU port.
|
| /Kernel-v10.6.2/portable/GCC/RX600/ |
| D | readme.txt | 1 The following table shows which port is recommended to be used.
46 the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems …
50 functionality is used, please modify port.c for the configuration. Please be aware that port.c is
62 …: PriorityDefinitions.h has to be provided for port_asm.s in case of other than RX700v3_DPFPU port.
|
| /Kernel-v10.6.2/portable/GCC/RX600v2/ |
| D | readme.txt | 1 The following table shows which port is recommended to be used.
46 the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems …
50 functionality is used, please modify port.c for the configuration. Please be aware that port.c is
62 …: PriorityDefinitions.h has to be provided for port_asm.s in case of other than RX700v3_DPFPU port.
|
| /Kernel-v10.6.2/portable/GCC/RX700v3_DPFPU/ |
| D | readme.txt | 1 The following table shows which port is recommended to be used.
46 the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems …
50 functionality is used, please modify port.c for the configuration. Please be aware that port.c is
62 …: PriorityDefinitions.h has to be provided for port_asm.s in case of other than RX700v3_DPFPU port.
|
| /Kernel-v10.6.2/portable/Renesas/RX700v3_DPFPU/ |
| D | readme.txt | 1 The following table shows which port is recommended to be used.
46 the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems …
50 functionality is used, please modify port.c for the configuration. Please be aware that port.c is
62 …: PriorityDefinitions.h has to be provided for port_asm.s in case of other than RX700v3_DPFPU port.
|
| /Kernel-v10.6.2/portable/Renesas/RX100/ |
| D | readme.txt | 1 The following table shows which port is recommended to be used.
46 the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems …
50 functionality is used, please modify port.c for the configuration. Please be aware that port.c is
62 …: PriorityDefinitions.h has to be provided for port_asm.s in case of other than RX700v3_DPFPU port.
|
1234
