We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
"RL-TCPnet is designed as a stand alone TCP/IP Operating System. This means it does not need any external RTOS or File System to run. It has an integrated tiny task scheduler that manages timeouts, events, and internal tasks." Are the tiny task scheduler preemptive?
The ARM RTX kernel is pre-emptive. See: www.keil.com/.../rlarm_ar_preempt_multit.htm
He was asking about the "integrated tiny task scheduler" within RL-TCPnet
Or is this "integrated tiny task scheduler" the same as ARM RTX?
Maybe if he'd given the context for his quote, as requested, that would be obvious...?
Yes, ten minutes not spent on writing a good question, normally results in many days of not receiving a good (or any at all) answer.
I can't understand why that takes so long to learn.
My answer was an attempt to help.
RL-ARM contains both RTX + TCPnet (see: http://www.keil.com/support/man/docs/rlarm/). Scheduling is done with the RTX kernel.
But he is quoting something as saying, "RL-TCPnet is designed as a stand alone TCP/IP Operating System ... it does not need any external RTOS ... It has an integrated tiny task scheduler..."
He hasn't cited the source, so we can't check if it's a faithful quote...
However, the question seems to be, "When RL-TCPnet is used without an external RTOS is its scheduling preemptive?"
Then again, as he's made no attempt whatsoever to clarify the question, he's presumably lost interest...
:-(
The quote appears to be from this page:
www.keil.com/.../rlarm_tn_using_standalone.htm
the rest of the text on that page certainly seems to suggest a non-preemptive system to me...
RL-TCPnet has an own integrated scheduler and can run with or without RTX. The RL-TCPnet schedule is not preemptive and the TCPnet also does not require it.
However it also does not allow you to add further tasks.
Do you have a problem using TCPnet?