| /Kernel-v11.1.0/portable/IAR/STR91x/ |
| D | port.c | 215 u16 * a, in prvFindFactors() argument
225 *a = a0 = ( ( n - 1 ) / 65536ul ) + 1; in prvFindFactors()
226 *b = b0 = n / *a; in prvFindFactors()
228 for( ; *a <= 256; ( *a )++ ) in prvFindFactors()
230 *b = n / *a; in prvFindFactors()
231 err = ( int32_t ) *a * ( int32_t ) *b - ( int32_t ) n; in prvFindFactors()
233 if( abs( err ) > ( *a / 2 ) ) in prvFindFactors()
236 err = ( int32_t ) *a * ( int32_t ) *b - ( int32_t ) n; in prvFindFactors()
242 a0 = *a; in prvFindFactors()
252 *a = a0; in prvFindFactors()
[all …]
|
| /Kernel-v11.1.0/portable/IAR/MSP430X/ |
| D | data_model.h | 42 #define pushm_x pushm.a
43 #define popm_x popm.a
44 #define push_x pushx.a
45 #define pop_x popx.a
51 #define pushm_x pushm.a
52 #define popm_x popm.a
53 #define push_x pushx.a
54 #define pop_x popx.a
55 #define mov_x movx.a
56 #define cmp_x cmpx.a
|
| /Kernel-v11.1.0/ |
| D | MISRA.md | 6 designed for small-embedded devices, it needs to have a very small memory
22 MISRA C:2012 Dir 4.7: If a function returns error information, then that error
36 from the assembly code in the port files. Therefore, adding a declaration in
43 and therefore, not declared in a header file.
56 MISRA C:2012 Rule 11.1: Conversions shall not be performed between a pointer to
66 MISRA C:2012 Rule 11.3: A cast shall not be performed between a pointer to
67 object type and a pointer to a different object type.
70 - This rule prohibits casting a pointer to object into a pointer to a
72 leading to undefined behavior. Even if the casting produces a correctly
86 This rule prohibits conversion of a pointer to void into a pointer to
[all …]
|
| D | History.txt | 7 + Add stream batching buffer. A stream batching buffer differs from a stream
8 buffer when a task reads from a non-empty buffer:
9 - The task reading from a non-empty stream buffer returns immediately
11 - The task reading from a non-empty steam batching buffer blocks until the
30 + Add a config option to the FreeRTOS SMP Kernel to set the default core
53 + Update the POSIX port to use a timer thread for tick interrupts instead of
95 + Add a template FreeRTOSConfig.h, inclusive of an abbreviated explanation of
96 each configuration item. Application writers can use this template as a
98 + Add a template FreeRTOS port which can be used as a starting point for
99 developing a new FreeRTOS port.
[all …]
|
| D | README.md | 7 ports only. This repository is referenced as a submodule in
14 included, and the correct include paths configured. Once a demo application is
24 Also for contributing and creating a Pull Request please refer to
38 Add the following into your project's main or a subdirectory's `CMakeLists.txt`:
49 In case you prefer to add it as a git submodule, do:
56 - Add a freertos_config library (typically an INTERFACE library) The following assumes the director…
73 In case you installed FreeRTOS-Kernel as a submodule, you will have to add it as a subdirectory:
80 - this particular example supports a native and cross-compiled build option.
122 - The ```./portable``` directory contains the files that are specific to a particular microcontroll…
127 …he ```./template_configuration``` directory contains a sample `FreeRTOSConfig.h` to help jumpstart…
[all …]
|
| /Kernel-v11.1.0/.github/ |
| D | pull_request_process.md | 3 …hat a Pull Request (PR) goes through when a pull request is submitted to a git repository in the F…
15 …ack the progress of pull requests and ensure that they are reviewed and merged in a timely manner.
17 …ws, one of which must be from the CODEOWNER of the reposiroty, are required for a PR to be merged.
22 Once a pull request (PR) is submitted, it goes through the following stages:
29 2. The assignee assigns a reviewer from the FreeRTOS Team to the PR.
34 4. The reviewer approves the PR and assigns a second reviewer.
51 The status of a PR is indicated through GitHub labels added by Reviewers/Assignees. The following a…
53 …y decide to skip some stages depending on the type of PR. For example, a PR with a simple doc upda…
64 The length of time required to review a PR is unpredictable and varies from PR to PR since it depen…
85 …a new feature to FreeRTOS, please get confirmation beforehand that the FreeRTOS team and community…
[all …]
|
| D | CONTRIBUTING.md | 3 Thank you for your interest in contributing to our project. Whether it's a bug report, new feature,…
15 …a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vul…
18 ## Submitting a bugs/feature request
19 Have a bug to report or feature to request? Follow these steps:
21 2. If your search turns up empty, create a new topic in the [forums](https://forums.freertos.org/) …
24 When creating a new topic on the forums or filing an issue, please include as many relevant details…
34 Contributions via pull requests are much appreciated. Before sending us a pull request, please ensu…
40 To send us a pull request, please:
46 5. Send us a pull request, answering any default questions in the pull request interface.
50 GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork…
[all …]
|
| D | SECURITY.md | 1 ## Reporting a Vulnerability
3 If you discover a potential security issue in this project we ask that you notify AWS/Amazon Securi…
5 Please do **not** create a public github issue.
|
| D | CODEOWNERS | 1 # Each line is a file pattern followed by one or more owners.
4 # the repo. Unless a later match takes precedence,
6 # review when someone opens a pull request.
10 # precedence. When someone opens a pull request that only
12 # owner(s) will be requested for a review.
|
| /Kernel-v11.1.0/portable/ThirdParty/XCC/Xtensa/ |
| D | readme_xtensa.txt | 20 The Xtensa configurable architecture supports a vast space of processor
33 thread-safety on a per task basis (for use in tasks only, not interrupt
41 This port also includes a simple example application that may run on
42 a supported board or the Xtensa instruction set simulator (ISS). There
43 are also a couple of test programs used in maintaining the port, which
55 Minimal support for certain evaluation boards is provided via a board
56 independent XTBSP API implemented by a board specific library distributed
59 is not a tradtional RTOS "board support package" with RTOS specific
62 (a "raw" platform), but you will have to provide the clock frequency
81 All source is provided along with a Makefile that works for any host
[all …]
|
| /Kernel-v11.1.0/portable/ThirdParty/ |
| D | README.md | 3 FreeRTOS third party ports can be supported by the FreeRTOS team, a FreeRTOS
11 These third party FreeRTOS ports are supported by the FreeRTOS team. For a
21 the FreeRTOS team will decide to take ownership of a partner supported or a
28 These FreeRTOS ports are supported by a FreeRTOS partner. For a partner
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…
43 These FreeRTOS ports are supported by the FreeRTOS community members. For a
51 contribute a FreeRTOS port is documented [here](https://github.com/FreeRTOS/FreeRTOS-Kernel-Communi…
|
| /Kernel-v11.1.0/portable/ThirdParty/GCC/Xtensa_ESP32/include/ |
| D | FreeRTOSConfig_arch.h | 91 #define configASSERT( a ) \ argument
92 if( unlikely( !( a ) ) ) { \
97 #define configASSERT( a ) assert( a ) argument
|
| /Kernel-v11.1.0/examples/ |
| D | README.md | 4 …Demo](https://github.com/FreeRTOS/FreeRTOS/tree/main/FreeRTOS/Demo) to find a list of pre-configur…
10 …a minimal FreeRTOS example project, which uses the configuration file in the template_configuratio…
11 * The [coverity](./coverity) directory contains a project to run [Synopsys Coverity](https://www.sy…
12 * The [template_configuration](./template_configuration) directory contains a sample configuration …
|
| /Kernel-v11.1.0/portable/ThirdParty/GCC/ATmega/ |
| D | readme.md | 7 This port provides a basis for supporting all modern ATmega devices using either the Enhanced Watch…
12 - TimerN - a 16-bit Timer which will be configured by the user.
14 …o generate phase correct PWM timing (for example) and they would be wasted as a simple System Tick.
16 …two devices the `EIND` register need to be preserved during a context switch. Also, due to a limit…
22 … to Pins, and they can be used for more simple timing tasks, requiring only a single counting dire…
28 … generate the System Tick does not impact its use as a watch dog. It can be configured to generate…
36 …ddresses. However, focusing on just the ATmega family only two devices have a large Flash requirin…
39 …- providing a `portTASK_FUNCTION_PROTO()` with the linker attribute `.lowtext` which is used to en…
47 …a very time critical process is running, based on microsecond timing generated by one of the Timer…
51 Using `NO_BLOCK` is optional, and should only be done if a critical Timer should interrupt the Sche…
[all …]
|
| /Kernel-v11.1.0/portable/ThirdParty/CDK/T-HEAD_CK802/ |
| D | portmacro.h | 126 #define portCLEAR_INTERRUPT_MASK_FROM_ISR( a ) RestoreLocalPSR( a ) argument
164 #define portYIELD_FROM_ISR( a ) vTaskSwitchContext() argument
|
| /Kernel-v11.1.0/portable/MemMang/ |
| D | heap_2.c | 69 #define heapMULTIPLY_WILL_OVERFLOW( a, b ) ( ( ( a ) > 0 ) && ( ( b ) > ( heapSIZE_MAX / ( a ) )… argument
72 #define heapADD_WILL_OVERFLOW( a, b ) ( ( a ) > ( heapSIZE_MAX - ( b ) ) ) argument
|
| D | heap_4.c | 68 #define heapMULTIPLY_WILL_OVERFLOW( a, b ) ( ( ( a ) > 0 ) && ( ( b ) > ( heapSIZE_MAX / ( a ) … argument
71 #define heapADD_WILL_OVERFLOW( a, b ) ( ( a ) > ( heapSIZE_MAX - ( b ) ) ) argument
74 #define heapSUBTRACT_WILL_UNDERFLOW( a, b ) ( ( a ) < ( b ) ) argument
|
| /Kernel-v11.1.0/portable/IAR/RL78/ |
| D | portmacro.h | 51 …th your selected memory model combination. If a far data model is required it is recommended to al…
55 …th your selected memory model combination. If a far code model is required it is recommended to al…
|
| /Kernel-v11.1.0/portable/IAR/AVR32_UC3/ |
| D | exception.s82 | 7 * Permission is hereby granted, free of charge, to any person obtaining a copy of
85 // EVBA must be aligned with a power of two strictly greater than the EVBA-
214 // All interrupts call a C function named _get_interrupt_handler.
216 // R12 a pointer to a user-provided interrupt handler.
240 movne pc, r12 // If this was not a spurious interrupt (R12 != NULL), jump to the handler.
241 rete // If this was a spurious interrupt (R12 == NULL), return from event handler.
263 movne pc, r12 // If this was not a spurious interrupt (R12 != NULL), jump to the handler.
264 rete // If this was a spurious interrupt (R12 == NULL), return from event handler.
286 movne pc, r12 // If this was not a spurious interrupt (R12 != NULL), jump to the handler.
287 rete // If this was a spurious interrupt (R12 == NULL), return from event handler.
[all …]
|
| /Kernel-v11.1.0/examples/coverity/ |
| D | coverity_misra.config | 28 …s but declared in portable.h which is included in multiple source files. As a result, these defini…
64 … "reason": "Allow to convert between a pointer to object and an interger type for stack alignment."
68 "reason": "Allow to use multiple break statements in a loop."
76 "reason": "Allow to update the parameters of a function."
|
| D | README.md | 2 FreeRTOS-Kernel is MISRA C:2012 compliant. This directory contains a project to
31 commands in a terminal:
36 2. Create the build files using CMake in a `build` directory:
64 HTML report should now be generated in a directory named `html-output`.
|
| /Kernel-v11.1.0/portable/IAR/RISC-V/chip_specific_extensions/ |
| D | readme.txt | 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
18 * compiler's!) include path. For example, if the chip in use includes a core
|
| /Kernel-v11.1.0/portable/IAR/RISC-V/ |
| D | readme.txt | 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
18 * compiler's!) include path. For example, if the chip in use includes a core
|
| /Kernel-v11.1.0/portable/GCC/RISC-V/chip_specific_extensions/ |
| D | readme.txt | 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
18 * compiler's!) include path. For example, if the chip in use includes a core
|
| /Kernel-v11.1.0/portable/GCC/RISC-V/ |
| D | readme.txt | 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
18 * compiler's!) include path. For example, if the chip in use includes a core
|
