• State Not Answered
  • Locked Locked
  • Replies 43 replies
  • Subscribers 21 subscribers
  • Views 6515 views
  • Users 0 members are here
2025 survey

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.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Are you using RTX? Can you help me?

Tamir Michael

Hello,

I have a major problem with RTX and Keil don't seem to be able to help (as they want a simple scenario to cause the problem, but I cannot give them the hardware of course. Maybe I can make it go wrong using an evaluation board).
I'm using RTX as the backbone of a product that needs to run for extended periods of time without reboot (weeks...).
The problem is that RTX stops executing arbitrary tasks at arbitrary moments - they remain 'ready' but not get services. Today I discovered a task entering 'WAIT_MUT' while not using ANY mutex. My question: Are there any tips using RTX correctly? I am growing totally frustrated and tired of this, what am I supposed to tell the client?! I'm using latest and so expensive RL-ARM without any results whatsoever.
Can you share your experience with me?

Thanks you for your attention,

Tamir

Parents
  • 0 in reply to Uli Behrenbeck

    Uli,

    Thanks for your reply. I made it home in a collapsed state :-)

    Here is the deal: the system kept on crashing even after removing all mutexes. I did find 2 problems due:
    1. There was a path in the program that attempted to lock a mutex while at interrupt context. a little assembly magic solved that.
    2. there was a problem in the communication task that could have locked the direction of the RS-485. I don't fully understand why, but the code is now more solid.

    The controllers are now running on my desk. If they don't hang by Monday, I think I can consider the situation as an improvement, even though the system used to crash before I started using mutexes etc and ran for over a week before without a problem (only lately it became so unstable). I will post what happened.

Reply
  • 0 in reply to Uli Behrenbeck

    Uli,

    Thanks for your reply. I made it home in a collapsed state :-)

    Here is the deal: the system kept on crashing even after removing all mutexes. I did find 2 problems due:
    1. There was a path in the program that attempted to lock a mutex while at interrupt context. a little assembly magic solved that.
    2. there was a problem in the communication task that could have locked the direction of the RS-485. I don't fully understand why, but the code is now more solid.

    The controllers are now running on my desk. If they don't hang by Monday, I think I can consider the situation as an improvement, even though the system used to crash before I started using mutexes etc and ran for over a week before without a problem (only lately it became so unstable). I will post what happened.

Children
No data