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

os_tmr_create() doesn't work

Thursday Children

I used os_tmr_create().
But, always return value is NULL!!
Why!!?

I saw os_tmr_create() defined in rt_Timer.c file.
There is the following codes in the first conditional expression.

if (tcnt == 0 || m_tmr == NULL) { return (NULL);
}

I think that the return value becomes NULL because "m_tmr" is NULL.
How can I set the value to "m_tmr"?

Someone helps.

Parents
  • 0 in reply to Dan Curran

    We are now using FreeRTOS which is in my opinion a far superior product, and is free (except OpenRTOS and SafeRTOS). It has a much better queuing system and a much better singling system (forget about the 16 or was it 32 signals per RTX task) and it scalable - which saves you ROM/RAM footprint. It also has a built-in support for a Cortex MPU (RTX does not). Stable, fast, free and reliable. Why not?
    No compaints about RTX - it gets the job done, but it binds us to Keil products which is something we are not going to be using for a long time.

Reply
  • 0 in reply to Dan Curran

    We are now using FreeRTOS which is in my opinion a far superior product, and is free (except OpenRTOS and SafeRTOS). It has a much better queuing system and a much better singling system (forget about the 16 or was it 32 signals per RTX task) and it scalable - which saves you ROM/RAM footprint. It also has a built-in support for a Cortex MPU (RTX does not). Stable, fast, free and reliable. Why not?
    No compaints about RTX - it gets the job done, but it binds us to Keil products which is something we are not going to be using for a long time.

Children
No data