|
|||||||||||
Technical Support On-Line Manuals RL-ARM User's Guide (MDK v4) ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
With RTX KernelEven though RL-TCPnet is designed as a stand alone TCP/IP Operating System, you can use it with the RTX kernel. This is useful for large complex applications, where different jobs are implemented as tasks. In this case, the basic framework is different because the functions from the stand alone framework are moved into tasks. The following tasks are introduced:
Here is a framework for the RTX kernel application: #include <RTL.h> __task void tcp_tick (void) { os_itv_set (10); while (1) { os_itv_wait (); /* Timer tick every 100 ms */ timer_tick (); } } __task void tcp_main (void) { while (1) { main_TcpNet (); os_tsk_pass (); } } __task void tcp_init (void) { system_init (); init_TcpNet (); os_tsk_create (tcp_tick, 2); os_tsk_create (tcp_main, 1); /* Init done, terminate this task. */ os_tsk_delete_self (); } void main (void) { os_sys_init (tcp_init); } Follow these guidelines when using RL-TCPnet with the RTX kernel:
| ||||||||||
|
Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.