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.
Dear Keil,
We are using the STM32F3 discovery board, and used the RTX with the demo code. When we compile, it says SVC_Handler multiply defined; Systick multiply defined etc.
I was wondering if you have met this problem before and know how to solve. Many of us have this problem.
Thanks. Jack
with out knowing about your system it looks like your trying to debounce a USB plugin event
so would ask the questions about your software design
Do you need to be systicks accurate (why not have a seperate RTX task that monitors and debounces IO states and sends events to tasks when the debounce events have occured)
If there are no other ways around it you can ( if you have the right Keil license) modify and change the RTX source and build you own RTX lib. I did before the os_get_time function was included in the RTX.
Rebuild the RTX library and call a function that you write from the rt_systick routine in rt_System.c. Place it just after the os_time++ line.
There are MANY ways to solve a problem. Some are better than others. Ones that do not work should not be considered. Modifying the OS MAY work, but it is not always or often the best way.
Modifying the OS MAY work, but it is not always or often the best way.
agree 100% would rather just trust what I am given and only resort to this if I cant get around it any other way
"agree 100% would rather just trust what I am given and only resort to this if I cant get around it any other way"
If you have a library designed for use with a busy-loop. And you want to make use of this library together with an RTOS. Then it really is quite likely that you have to do something about the (now incorrect) assumptions in that library.
And you still haven't told us what issues you have with using other timer interrupts?
Or using the timer services provided by the OS?
The fundamental problem seems to be the insistence on taking some bare-metal code which was never designed for an RTOS, and just dumping RTX onto it.
Even if SysTick can be kludged, there is a high risk that (as Per hinted) there will be other issues where this code is simply not right for RTOS use.