• State Not Answered
  • Locked Locked
  • Replies 43 replies
  • Subscribers 22 subscribers
  • Views 7015 views
  • Users 0 members are here
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

    Hi all,

    I am using the At91sam7s128 with MDK 3.20 and ULINK2 and having this similar problem.

    My RTX clock interval is set to 1 ms and UART task has higher priority (2) than other tasks.

    I have 64 boards running exactly same firmware. A PC is always polling these 64 boards for the data. Randomly, one or two boards will stop running after a random time (from hours to days). However some boards are running for weeks without any problems.

    I caught this problem once with debugger and found it stops in the os_idle_demon and will not switch to other tasks that are ready for service.

    Regards,

    Xiao

Reply
  • 0

    Hi all,

    I am using the At91sam7s128 with MDK 3.20 and ULINK2 and having this similar problem.

    My RTX clock interval is set to 1 ms and UART task has higher priority (2) than other tasks.

    I have 64 boards running exactly same firmware. A PC is always polling these 64 boards for the data. Randomly, one or two boards will stop running after a random time (from hours to days). However some boards are running for weeks without any problems.

    I caught this problem once with debugger and found it stops in the os_idle_demon and will not switch to other tasks that are ready for service.

    Regards,

    Xiao

Children