Searched refs:them (Results 1 – 23 of 23) sorted by relevance
/ThreadX-v6.4.1/ports_smp/cortex_a5x_smp/green/example_build/tgt/ |
D | resource_readme.txt | 4 running on your target. You may use these files as is or use them as examples 32 program sections and assign them to specific addresses in memory.
|
/ThreadX-v6.4.1/test/smp/cmake/threadx_smp/ |
D | CMakeLists.txt | 25 # Pick up the port specific variables and apply them
|
/ThreadX-v6.4.1/ |
D | CMakeLists.txt | 24 # Pick up the port specific variables and apply them
|
D | README.md | 167 …each provided in their own repository, but there are dependencies between them, as shown in the fo…
|
/ThreadX-v6.4.1/ports_module/cortex_a7/gnu/example_build/ |
D | sample_threadx.ld | 154 can access them all, and initialized data all before uninitialized, so 214 of the section so we begin them at 0. */
|
/ThreadX-v6.4.1/ports/cortex_a9/gnu/example_build/ |
D | sample_threadx.ld | 154 can access them all, and initialized data all before uninitialized, so 214 of the section so we begin them at 0. */
|
/ThreadX-v6.4.1/ports/arm9/gnu/example_build/ |
D | sample_threadx.ld | 154 can access them all, and initialized data all before uninitialized, so 214 of the section so we begin them at 0. */
|
/ThreadX-v6.4.1/ports/arm11/gnu/example_build/ |
D | sample_threadx.ld | 154 can access them all, and initialized data all before uninitialized, so 214 of the section so we begin them at 0. */
|
/ThreadX-v6.4.1/ports/cortex_a15/gnu/example_build/ |
D | sample_threadx.ld | 154 can access them all, and initialized data all before uninitialized, so 214 of the section so we begin them at 0. */
|
/ThreadX-v6.4.1/ports/cortex_a17/gnu/example_build/ |
D | sample_threadx.ld | 154 can access them all, and initialized data all before uninitialized, so 214 of the section so we begin them at 0. */
|
/ThreadX-v6.4.1/ports/cortex_a12/gnu/example_build/ |
D | sample_threadx.ld | 154 can access them all, and initialized data all before uninitialized, so 214 of the section so we begin them at 0. */
|
/ThreadX-v6.4.1/ports_arch/ARMv7-A/threadx/ports/gnu/example_build/ |
D | sample_threadx.ld | 154 can access them all, and initialized data all before uninitialized, so 214 of the section so we begin them at 0. */
|
/ThreadX-v6.4.1/ports/cortex_a8/gnu/example_build/ |
D | sample_threadx.ld | 154 can access them all, and initialized data all before uninitialized, so 214 of the section so we begin them at 0. */
|
/ThreadX-v6.4.1/ports/cortex_a5/gnu/example_build/ |
D | sample_threadx.ld | 154 can access them all, and initialized data all before uninitialized, so 214 of the section so we begin them at 0. */
|
/ThreadX-v6.4.1/ports/cortex_a7/gnu/example_build/ |
D | sample_threadx.ld | 154 can access them all, and initialized data all before uninitialized, so 214 of the section so we begin them at 0. */
|
/ThreadX-v6.4.1/ports/cortex_r5/gnu/example_build/ |
D | sample_threadx.ld | 154 can access them all, and initialized data all before uninitialized, so 214 of the section so we begin them at 0. */
|
/ThreadX-v6.4.1/ports/cortex_r4/gnu/example_build/ |
D | sample_threadx.ld | 154 can access them all, and initialized data all before uninitialized, so 214 of the section so we begin them at 0. */
|
/ThreadX-v6.4.1/common/ |
D | CMakeLists.txt | 9 # These files can be overridden by setting them in the variable list named TX_SRC_OVERRIDES
|
/ThreadX-v6.4.1/ports_smp/mips32_interaptiv_smp/green/example_build/ |
D | init_cp0.mip | 110 // RAMHACK: Use vectored interrupts (Cause.IV) to isolate them from other exceptions.
|
/ThreadX-v6.4.1/test/smp/cmake/threadx_smp/common_smp/ |
D | CMakeLists.txt | 11 # These files can be overridden by setting them in the variable list named TX_SRC_OVERRIDES
|
/ThreadX-v6.4.1/ports/xtensa/xcc/ |
D | readme_threadx.txt | 248 can be fully customized in tx_application_define by assigning to them: 360 cycles between interrupts to process them. 434 does not expect them to be preserved). On an interrupt, callee-saved 496 the ".L" and ".Ln" prefixes from local labels if you want them visible. 571 mentioned because there is code to handle them in xtensa_vectors.S. 747 them. The interrupt/exception hooks are described in xtensa_rtos.h .
|
/ThreadX-v6.4.1/utility/rtos_compatibility_layers/OSEK/ |
D | threadx_osek_readme.txt | 33 and link or assigned them as needed. See below for a list of object creation functions.
|
/ThreadX-v6.4.1/ports/cortex_r4/ac6/ |
D | readme_threadx.txt | 13 Now that the projects are in the workspace directory, import them into DS by
|