Home
last modified time | relevance | path

Searched refs:a (Results 1 – 25 of 191) sorted by relevance

12345678

/FreeRTOS-Kernel/portable/IAR/STR91x/
A Dport.c226 *b = b0 = n / *a; in prvFindFactors()
228 for( ; *a <= 256; ( *a )++ ) in prvFindFactors()
230 *b = n / *a; in prvFindFactors()
242 a0 = *a; in prvFindFactors()
252 *a = a0; in prvFindFactors()
260 uint16_t a; in prvSetupTimerInterrupt() local
319 for( ; *a <= 256; ( *a )++ ) in prvFindFactors()
321 *b = n / *a; in prvFindFactors()
333 a0 = *a; in prvFindFactors()
343 *a = a0; in prvFindFactors()
[all …]
/FreeRTOS-Kernel/portable/IAR/MSP430X/
A Ddata_model.h42 #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
/FreeRTOS-Kernel/
A DMISRA.md6 designed for small-embedded devices, it needs to have a very small memory
43 and therefore, not declared in a header file.
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
86 This rule prohibits conversion of a pointer to void into a pointer to
97 - The conversion from a pointer to void into a pointer to EventGroup_t is
98 safe because it is a pointer to EventGroup_t, which is returned to the
108 - The conversion from a pointer to void into a pointer to EventGroup_t is
109 safe because it is a pointer to EventGroup_t, which is passed as a
[all …]
A DHistory.txt27 hangs when a thread dies while holding a mutex.
143 buffer when a task reads from a non-empty buffer:
488 - Add a check to heap_2 to track if a memory block is allocated to
766 a user reported error whereby a task continues to run for a short time
1049 xTaskCreateStatic(), being a newer function, used a uint32_t.
1124 a reference for projects that do not include a FreeRTOS heap.
1510 + Previously, when a task left the Blocked state, a context switch was
1657 returns a value).
1793 (which would not be a normal usage model for a mutex).
2801 a co-routine.
[all …]
A DREADME.md7 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
44 Add the following into your project's main or a subdirectory's `CMakeLists.txt`:
55 In case you prefer to add it as a git submodule, do:
79 In case you installed FreeRTOS-Kernel as a submodule, you will have to add it as a subdirectory:
86 - this particular example supports a native and cross-compiled build option.
133 …he ```./template_configuration``` directory contains a sample `FreeRTOSConfig.h` to help jumpstart…
175 There is additionally a
182 and you believe this is a mistake, then add the word to
[all …]
/FreeRTOS-Kernel/.github/
A Dpull_request_process.md3 …hat a Pull Request (PR) goes through when a pull request is submitted to a git repository in the F…
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.
53 …y decide to skip some stages depending on the type of PR. For example, a PR with a simple doc upda…
85 …a new feature to FreeRTOS, please get confirmation beforehand that the FreeRTOS team and community…
87 …a single PR. Lets say you are developing feature-x and you come across poorly named variables or …
93 …etimes reviewers make mistakes. If a reviewer has requested you to make changes and you feel stron…
104 * Maintain a clean project
110 …ecause of a feature freeze due to an upcoming release. During this time, only bug fixes are taken …
[all …]
A DCONTRIBUTING.md3 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:
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…
51 [creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
[all …]
A DSECURITY.md1 ## 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.
A DCODEOWNERS1 # 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.
/FreeRTOS-Kernel/portable/ThirdParty/
A DREADME.md3 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…
/FreeRTOS-Kernel/portable/ThirdParty/GCC/Xtensa_ESP32/include/
A DFreeRTOSConfig_arch.h91 #define configASSERT( a ) \ argument
92 if( unlikely( !( a ) ) ) { \
97 #define configASSERT( a ) assert( a ) argument
/FreeRTOS-Kernel/examples/
A DREADME.md4 …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 …
/FreeRTOS-Kernel/portable/ThirdParty/GCC/ATmega/
A Dreadme.md7 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…
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…
57 …es that the stack will always be above the heap, and does a check for this when responding to a `m…
[all …]
/FreeRTOS-Kernel/portable/ThirdParty/CDK/T-HEAD_CK802/
A Dportmacro.h126 #define portCLEAR_INTERRUPT_MASK_FROM_ISR( a ) RestoreLocalPSR( a ) argument
164 #define portYIELD_FROM_ISR( a ) vTaskSwitchContext() argument
/FreeRTOS-Kernel/portable/MemMang/
A Dheap_2.c69 #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
A Dheap_4.c68 #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
/FreeRTOS-Kernel/portable/IAR/AVR32_UC3/
A Dexception.s827 * 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 …]
/FreeRTOS-Kernel/portable/IAR/RL78/
A Dportmacro.h51 …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…
/FreeRTOS-Kernel/portable/IAR/RISC-V/chip_specific_extensions/
A Dreadme.txt4 * 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
/FreeRTOS-Kernel/portable/IAR/RISC-V/
A Dreadme.txt4 * 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
/FreeRTOS-Kernel/portable/GCC/RISC-V/
A Dreadme.txt4 * 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
/FreeRTOS-Kernel/portable/GCC/RISC-V/chip_specific_extensions/
A Dreadme.txt4 * 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
/FreeRTOS-Kernel/portable/ThirdParty/GCC/RP2040/
A DREADME.md7 …phores, queues from pico_sync) between FreeRTOS tasks and code executing on a non FreeRTOS core, o…
9 Note that whilst this SMP version can be run on just a single (either) core, it is probably
21 This will locate the FreeRTOS kernel if it is a direct sub-module of your project, or if you provid…
26 version, you can include the FreeRTOS-Kernel support later in your CMake build (possibly in a subdi…
/FreeRTOS-Kernel/examples/coverity/
A DREADME.md2 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`.
A Dcoverity_misra.config32 …s but declared in portable.h which is included in multiple source files. As a result, these defini…
68 … "reason": "Allow to convert between a pointer to object and an interger type for stack alignment."
72 "reason": "Allow to use multiple break statements in a loop."
80 "reason": "Allow to update the parameters of a function."

Completed in 36 milliseconds

12345678