Searched full:files (Results 1 – 25 of 698) sorted by relevance
12345678910>>...28
| /Kernel-v10.6.2/ |
| D | README.md | 4 This repository contains FreeRTOS kernel source/header files and kernel ports only. This repository…
6 …files included, and the correct include paths configured. Once a demo application is building and…
71 - The root of this repository contains the three files that are common to
73 three files. croutine.c implements the optional co-routine functionality - which
76 - The ```./portable``` directory contains the files that are specific to a particular microcontroll…
79 - The ```./include``` directory contains the real time kernel header files.
82 FreeRTOS files are formatted using the "uncrustify" tool. The configuration file used by uncrustify…
100 Note that only the FreeRTOS Kernel source files are checked for proper spelling, the portable secti…
|
| D | History.txt | 359 in more files.
435 files, removing the need for application writers to add prototypes into
436 the C files in which they define the functions.
712 + Updated trace recorder files to the latest version.
956 + Ensure none of the variables in the common kernel files are initialised to
1310 + Correct the __NVIC_PRIO_BITS setting in the LPC18xx.h header files
1358 + Core kernel files now pass PC-Lint V8 static checking without outputting
1404 files have been removed from FreeRTOS/Demo/Common.
1437 + Corrected header comments in the het.c and het.h files (RM48/TMS570 demo).
1537 + Added comments in the FreeRTOSConfig.h files associated with Cortex-M3 and
[all …]
|
| /Kernel-v10.6.2/portable/ |
| 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
9 + The other directories each contain files specific to a particular
11 specific files the directory contains.
16 microcontroller, then the port specific files are contained in
|
| /Kernel-v10.6.2/portable/ThirdParty/GCC/ARM_TFM/ |
| D | README.md | 40 Please copy all the files in ```freertos_kernel\portable\GCC\ARM_CM[23|33|55|85]_NTZ``` into the ``…
69 To enable calling TF-M services by the Non-Secure Side, the files below should be included in the F…
70 * files in ```trusted-firmware-m\build\install\interface\src```
71 …files contain the implementation of PSA Functional Developer APIs which can be called by Non-Secur…
72 * files in ```trusted-firmware-m\build\install\interface\include```
73 These files are the necessary header files to call TF-M services.
|
| /Kernel-v10.6.2/.github/ |
| D | CODEOWNERS | 11 # modifies JS files, only @js-owner and not the global
20 # In this example, @doctocat owns any files in the build/logs
25 # The `docs/*` pattern will match files like
26 # `docs/getting-started.md` but not further nested files like
|
| /Kernel-v10.6.2/portable/ARMv8M/ |
| D | ReadMe.txt | 3 Do not use the files located here! These file are copied into separate
7 If your Armv8-M and Armv8.1-M application uses TrustZone then use the files from the
10 If your Armv8-M and Armv8.1-M application does not use TrustZone then use the files from
|
| D | copy_files.py | 8 # * this software and associated documentation files (the "Software"), to deal in
39 # Files to be compiled in the Secure Project
64 # Files to be compiled in the Non-Secure Project
156 # Copy Secure Files
162 # Copy Non-Secure Files
|
| /Kernel-v10.6.2/portable/ARMv8M/non_secure/ |
| D | ReadMe.txt | 3 Do not use the files located here! These file are copied into separate
7 If your Armv8-M/Armv8.1-M application uses TrustZone then use the files from the
10 If your Armv8-M/Armv8.1-M application does not use TrustZone then use the files from
|
| /Kernel-v10.6.2/portable/ARMv8M/secure/ |
| D | ReadMe.txt | 3 Do not use the files located here! These file are copied into separate
7 If your Armv8-M/Armv8.1-M application uses TrustZone then use the files from the
10 If your Armv8-M/Armv8.1-M application does not use TrustZone then use the files from
|
| /Kernel-v10.6.2/.github/workflows/ |
| D | kernel-checks.yml | 33 # Collect all affected files
34 - name: Collecting changed files
35 uses: lots0logs/gh-action-get-changed-files@2.1.4
|
| /Kernel-v10.6.2/portable/GCC/RISC-V/chip_specific_extensions/RISCV_MTIME_CLINT_no_extensions/ |
| D | freertos_risc_v_chip_specific_extensions.h | 8 * this software and associated documentation files (the "Software"), to deal in
38 * + Header files called freertos_risc_v_chip_specific_extensions.h contain the
40 * chip. There are multiple freertos_risc_v_chip_specific_extensions.h files
|
| /Kernel-v10.6.2/portable/GCC/RISC-V/chip_specific_extensions/RISCV_no_extensions/ |
| D | freertos_risc_v_chip_specific_extensions.h | 8 * this software and associated documentation files (the "Software"), to deal in
38 * + Header files called freertos_risc_v_chip_specific_extensions.h contain the
40 * chip. There are multiple freertos_risc_v_chip_specific_extensions.h files
|
| /Kernel-v10.6.2/portable/IAR/RISC-V/chip_specific_extensions/RV32I_CLINT_no_extensions/ |
| D | freertos_risc_v_chip_specific_extensions.h | 8 * this software and associated documentation files (the "Software"), to deal in
38 * + Header files called freertos_risc_v_chip_specific_extensions.h contain the
40 * chip. There are multiple freertos_risc_v_chip_specific_extensions.h files
|
| /Kernel-v10.6.2/portable/GCC/RISC-V/chip_specific_extensions/RV32I_CLINT_no_extensions/ |
| D | freertos_risc_v_chip_specific_extensions.h | 8 * this software and associated documentation files (the "Software"), to deal in
38 * + Header files called freertos_risc_v_chip_specific_extensions.h contain the
40 * chip. There are multiple freertos_risc_v_chip_specific_extensions.h files
|
| /Kernel-v10.6.2/portable/WizC/PIC18/ |
| D | Install.bat | 12 set FED=C:\Program Files\FED\PIC_C
23 set FED=C:\Program Files\FED\PIXIE
105 echo Copying Files...
137 echo Setting files to ReadOnly
|
| /Kernel-v10.6.2/portable/ThirdParty/XCC/Xtensa/ |
| D | xtensa_rtos.h | 9 * this software and associated documentation files (the "Software"), to deal in
36 * and macros for use primarily by Xtensa assembly coded source files.
38 * Macros in this header map callouts from generic Xtensa files to specific
39 * RTOS functions. It may also be included in C source files.
217 Ensures RTOS specific files need only include this one Xtensa-generic header.
|
| /Kernel-v10.6.2/portable/GCC/RISC-V/chip_specific_extensions/Pulpino_Vega_RV32M1RM/ |
| D | freertos_risc_v_chip_specific_extensions.h | 8 * this software and associated documentation files (the "Software"), to deal in
38 * + Header files called freertos_risc_v_chip_specific_extensions.h contain the
40 * chip. There are multiple freertos_risc_v_chip_specific_extensions.h files
|
| /Kernel-v10.6.2/portable/ThirdParty/GCC/Xtensa_ESP32/include/ |
| D | xtensa_rtos.h | 12 * a copy of this software and associated documentation files (the
38 * and macros for use primarily by Xtensa assembly coded source files.
40 * Macros in this header map callouts from generic Xtensa files to specific
41 * RTOS functions. It may also be included in C source files.
221 * Ensures RTOS specific files need only include this one Xtensa-generic header.
|
| /Kernel-v10.6.2/portable/IAR/ARM_CM55/secure/ |
| D | secure_context_port_asm.s | 8 * this software and associated documentation files (the "Software"), to deal in
35 the code is included in C files but excluded by the preprocessor in assembly
36 files (__ICCARM__ is defined by the IAR C compiler but not by the IAR assembler. */
|
| /Kernel-v10.6.2/portable/IAR/ARM_CM85/secure/ |
| D | secure_context_port_asm.s | 8 * this software and associated documentation files (the "Software"), to deal in
35 the code is included in C files but excluded by the preprocessor in assembly
36 files (__ICCARM__ is defined by the IAR C compiler but not by the IAR assembler. */
|
| /Kernel-v10.6.2/portable/IAR/ARM_CM23/secure/ |
| D | secure_context_port_asm.s | 8 * this software and associated documentation files (the "Software"), to deal in
35 the code is included in C files but excluded by the preprocessor in assembly
36 files (__ICCARM__ is defined by the IAR C compiler but not by the IAR assembler. */
|
| /Kernel-v10.6.2/portable/IAR/ARM_CM35P/secure/ |
| D | secure_context_port_asm.s | 8 * this software and associated documentation files (the "Software"), to deal in
35 the code is included in C files but excluded by the preprocessor in assembly
36 files (__ICCARM__ is defined by the IAR C compiler but not by the IAR assembler. */
|
| /Kernel-v10.6.2/portable/IAR/ARM_CM33/secure/ |
| D | secure_context_port_asm.s | 8 * this software and associated documentation files (the "Software"), to deal in
35 the code is included in C files but excluded by the preprocessor in assembly
36 files (__ICCARM__ is defined by the IAR C compiler but not by the IAR assembler. */
|
| /Kernel-v10.6.2/portable/ARMv8M/secure/context/portable/IAR/ARM_CM33/ |
| D | secure_context_port_asm.s | 8 * this software and associated documentation files (the "Software"), to deal in
35 the code is included in C files but excluded by the preprocessor in assembly
36 files (__ICCARM__ is defined by the IAR C compiler but not by the IAR assembler. */
|
| /Kernel-v10.6.2/portable/ARMv8M/secure/context/portable/IAR/ARM_CM23/ |
| D | secure_context_port_asm.s | 8 * this software and associated documentation files (the "Software"), to deal in
35 the code is included in C files but excluded by the preprocessor in assembly
36 files (__ICCARM__ is defined by the IAR C compiler but not by the IAR assembler. */
|
12345678910>>...28
