Searched refs:running (Results 1 – 25 of 125) sorted by relevance
12345
/ThreadX-v6.4.1/ports_smp/mips32_interaptiv_smp/green/src/ |
D | tx_thread_smp_core_get.mip | 39 /* This function gets the currently running core number and returns it.*/
|
D | tx_thread_smp_protect.mip | 40 /* This function gets protection for running inside the ThreadX */
|
/ThreadX-v6.4.1/ports_smp/cortex_a5x_smp/green/example_build/tgt/ |
D | standalone_ram.ld | 17 // Program layout for running out of RAM.
|
D | standalone_romcopy.ld | 18 // and then running out of RAM.
|
D | resource_readme.txt | 4 running on your target. You may use these files as is or use them as examples
|
/ThreadX-v6.4.1/ports_smp/cortex_a5x_smp/green/src/ |
D | tx_thread_smp_core_get.a64 | 50 /* This function gets the currently running core number and returns it.*/
|
D | tx_thread_smp_protect.a64 | 50 /* This function gets protection for running inside the ThreadX */
|
/ThreadX-v6.4.1/ports_smp/mips32_interaptiv_smp/gnu/src/ |
D | tx_thread_schedule.S | 167 la $9, _tx_el_thread_running # Build address of thread running event routine
|
/ThreadX-v6.4.1/ports_smp/mips32_interaptiv_smp/green/example_build/ |
D | demo_threadx_ram_interAptiv.ld | 26 // Program layout for running out of RAM.
|
/ThreadX-v6.4.1/ports/cortex_m7/ghs/src/ |
D | tx_thread_context_restore.arm | 42 ;/* if no thread was running, the function returns to the scheduler. */
|
/ThreadX-v6.4.1/ports/cortex_m3/ghs/src/ |
D | tx_thread_context_restore.arm | 42 ;/* if no thread was running, the function returns to the scheduler. */
|
/ThreadX-v6.4.1/ports/cortex_m4/ghs/src/ |
D | tx_thread_context_restore.arm | 42 ;/* if no thread was running, the function returns to the scheduler. */
|
/ThreadX-v6.4.1/ports/rxv1/ccrx/src/ |
D | tx_thread_context_save.src | 123 ; /* Otherwise, not nested, check to see if a thread was running. */ 133 BEQ __tx_thread_idle_system_save ; Yes, idle system is running - idle restore
|
/ThreadX-v6.4.1/ports/rxv2/ccrx/src/ |
D | tx_thread_context_save.src | 124 ; /* Otherwise, not nested, check to see if a thread was running. */ 134 BEQ __tx_thread_idle_system_save ; Yes, idle system is running - idle restore
|
/ThreadX-v6.4.1/ports/rxv3/ccrx/src/ |
D | tx_thread_context_save.src | 124 ; /* Otherwise, not nested, check to see if a thread was running. */ 134 BEQ __tx_thread_idle_system_save ; Yes, idle system is running - idle restore
|
/ThreadX-v6.4.1/ports/rxv1/gnu/src/ |
D | tx_thread_context_save.S | 123 BEQ __tx_thread_idle_system_save ; Yes, idle system is running - idle restore
|
/ThreadX-v6.4.1/ports/rxv1/iar/src/ |
D | tx_thread_context_save.s | 123 BEQ __tx_thread_idle_system_save ; Yes, idle system is running - idle restore
|
/ThreadX-v6.4.1/ports/rxv2/gnu/src/ |
D | tx_thread_context_save.S | 134 BEQ __tx_thread_idle_system_save ; Yes, idle system is running - idle restore
|
/ThreadX-v6.4.1/ports_module/rxv2/iar/module_manager/src/ |
D | tx_thread_context_save.s | 130 BEQ __tx_thread_idle_system_save ; Yes, idle system is running - idle restore
|
/ThreadX-v6.4.1/ports/rxv2/iar/src/ |
D | tx_thread_context_save.s | 134 BEQ __tx_thread_idle_system_save ; Yes, idle system is running - idle restore
|
/ThreadX-v6.4.1/ports/rxv3/gnu/src/ |
D | tx_thread_context_save.S | 134 BEQ __tx_thread_idle_system_save ; Yes, idle system is running - idle restore
|
/ThreadX-v6.4.1/ports/rxv3/iar/src/ |
D | tx_thread_context_save.s | 134 BEQ __tx_thread_idle_system_save ; Yes, idle system is running - idle restore
|
/ThreadX-v6.4.1/ports/linux/gnu/ |
D | readme_threadx.txt | 40 Once the application calls tx_kernel_enter, ThreadX starts running and 65 the ThreadX application running with privilege. The following command is used
|
/ThreadX-v6.4.1/ports_smp/linux/gnu/ |
D | readme_threadx.txt | 40 Once the application calls tx_kernel_enter, ThreadX SMP starts running and 65 the ThreadX SMP application running with privilege. The following command is used
|
/ThreadX-v6.4.1/ports_smp/mips32_interaptiv_smp/green/ |
D | readme_threadx.txt | 47 how to get the ThreadX evaluation running under the MIPS interAptiv MALTA board. 84 running and you should observe messages being displayed on the MALTA board. 256 Initialization is done exclusively in VPE 0, which is the default running VPE 258 wait until VPE 0 completes the initialization before they start running.
|
12345