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
Well, the only test I was running was with a SSP as SPI Master interfacing to a single slave and exchanging an identical command/request sequence using Modbus ASCII protocol. No changes were made to the code when I removed the USB connection from the ULINK. It hasnt died since I did this. The frames exhanged were upwards of 2.7 million after a successful weekend run. Before the ULINK was removed I was consistently failing at a fraction of the frames reported. I cannot say that this is your problem but it is another angle you need to consider...
As I noted above, my issue is resolved already. It was all about addressing FlashFS's SD card driven card from exception mode, as well as a path that locked a mutex from exception mode. Once removed, no hangup were experienced anymore.