Subject:
|
Re: Semaphore(s) locked when task killed.
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Wed, 4 Sep 2002 15:31:33 GMT
|
Viewed:
|
2153 times
|
| |
|
|
In lugnet.robotics.rcx.legos, Joseph Woolley writes:
> I have found that killing a task which is sending data via lnp will cause
> lnp to stop functioning. Turning the brick off then on again will get lnp
> working again. The issue is with the semaphore(s) used in the kernel tasks.
This explains a problem I've been having. I've noticed this exact issue,
but I wasn't sure if I was doing something wrong, or exactly what the
problem was.
I have a program that sends IR messages (for proximity) and after the
program is stopped, it won't send messages, again.
I'm not stopping the tasks. They are stopped by the run button, and
everything works fine after the power is cycled.
Thanks for bringing this to light.
Steve
|
|
Message has 1 Reply:
 | | Re: Semaphore(s) locked when task killed.
|
| Last night I worked on a solution to this. So far it is coming along very good. My proposed solution is to write tasks so that they shutdown when signalled. The user tasks should respond to the run/stop button by shutting down gracefully. If a task (...) (22 years ago, 5-Sep-02, to lugnet.robotics.rcx.legos)
|
Message is in Reply To:
| | Semaphore(s) locked when task killed.
|
| I have found that killing a task which is sending data via lnp will cause lnp to stop functioning. Turning the brick off then on again will get lnp working again. The issue is with the semaphore(s) used in the kernel tasks. Currently there is no (...) (22 years ago, 4-Sep-02, to lugnet.robotics.rcx.legos)
|
7 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
