• State Not Answered
  • Locked Locked
  • Replies 22 replies
  • Subscribers 21 subscribers
  • Views 10826 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

SVC_Handler multiply defined

Jack Lee

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

Parents
  • 0 in reply to Andy Neil

    Hi Andrew,

    Apologies for the confusions. Would like to clarify:-

    The demo code I am using is the one provided for stm32F3 discovery board.
    It's supposed to work hand in hand with Keil - it does compile but not when you include a RTX in it. Quite surprizing for 2 big partnership companies.

    The main requirement for the Keil RTOS for stm32f3 is the systick timer.
    The funny thing is, systick is taken up (or stolen) by the demo code itself which initializes it and uses it for all sorts of stuff including USB interface.

    So, there is a conflict - i.e. you can't use stm32 demo code (i.e. standard peripheral drivers) with Keil RTX. That's bum.

    Thanks anyway - I wonder if Keil knows about this, I bet they're too busy.

    Best regards,
    Jack
    (from your message I know you don't know the answer anyway - but thanks for your passion to help others, it's nice)

Reply
  • 0 in reply to Andy Neil

    Hi Andrew,

    Apologies for the confusions. Would like to clarify:-

    The demo code I am using is the one provided for stm32F3 discovery board.
    It's supposed to work hand in hand with Keil - it does compile but not when you include a RTX in it. Quite surprizing for 2 big partnership companies.

    The main requirement for the Keil RTOS for stm32f3 is the systick timer.
    The funny thing is, systick is taken up (or stolen) by the demo code itself which initializes it and uses it for all sorts of stuff including USB interface.

    So, there is a conflict - i.e. you can't use stm32 demo code (i.e. standard peripheral drivers) with Keil RTX. That's bum.

    Thanks anyway - I wonder if Keil knows about this, I bet they're too busy.

    Best regards,
    Jack
    (from your message I know you don't know the answer anyway - but thanks for your passion to help others, it's nice)

Children
  • 0 in reply to Jack Lee

    It's 'C' source code for an ARM Target; Keil provides 'C' tools for ARM targets.

    "it does compile but not when you include a RTX in it. Quite surprizing for 2 big partnership companies"

    Not at all!

    It's provided as "bare-metal" code; it is not designed for use with an RTOS; it makes no claim to do so.

    "The main requirement for the Keil RTOS for stm32f3 is the systick timer"

    Eh??!!

    There is no need to go to the lengths of an RTOS just to use a timer!!

    As the demo itself illustrates, the SysTick timer is perfectly usable without any RTOS!

    "The funny thing is, systick is taken up (or stolen) by the demo code itself"

    Why is that funny?!

    The demo is demonstrating the use of the chip's features - including the SysTick timer.