Actions
Forum Thread Details
  • Replies 35 replies
  • Subscribers 502 subscribers
  • Views 4525 views
  • Users 0 members are here
Related

Have a question about Micrium's embedded software? Ask our Expert, Matt Gordon

e14 Contributor

This thread has been closed to new questions.

However, we welcome you to Post Your Question about Embedded in the element14 Community Embedded group. You'll find many fellow members and experts who have just the answer you're looking to find! 

 

Thank You, Your Friends at element14 Community

image

 

Matt Gordon

Matt Gordon is a senior applications engineer at Micrium.  He began his career developing device drivers, kernel ports, and example applications for Micrium's customers.  Drawing on this experience, Matt has written multiple articles on embedded software.  He also heads Micrium's training program and regularly teaches classes on real-time kernels and other embedded software components.  Matt holds a bachelor's degree in computer engineering from Georgia Tech, Georgia in the USA.


Parents

  • Hi,

     

    1. I am using OSFlagPend(ucos-iii) to block a thread to wait for an event for 180seconds (OS_CFG_TICK_RATE_HZ is 1000u).

    It is working fine i.e when the event is posted my thread is resuming the execution but when it doesn't receive any event within specified time it is getting blocked.

    Normally it should resume execution when timeout happens. Any Ideas?


    2. One more problem is ...delay function OSTimeDlyHMSM is not working, when I used OSTimeDlyHMSM(0,0,30,0,OS_OPT_TIME_HMSM_NON_STRICT ,&oserr); the thread is getting blocked forever.

    Any idea?

  • in reply to e14 Contributor

    Are you able to determine whether or not tick interrupts are actually occurring?  Both of the problems that you've described could result from the tick interrupt not being initialized properly.

Reply Children
  • in reply to e14 Contributor

    Hi MattGordon_Micrium,

     

    Thnaks for the reply.

    the tick interrupt was initialized properly but the problem was the clock frequency( currently assigned cpu_clk_freq=32MHz), it is generating two tick interrupts for a second.
    I think this is the reason for my driver thread getting blocked (as I used 30 seconds which is almost equal to 4hours with two interrupts for a second ).
    When I changed it to cpu_clk_freq / /OSCfg_TickRate_Hz(1000Hz), it is generating too many interrupts per second and the driver is behaving abnormally(suspecting CPU overloaded with tick interrupts).