IAR PowerPac RTOS User Guide

More documents

Recommendations

Info

****** global functions ********************************************/void HW_Wait(void) {OS_EVENT_Wait(&_HW_Event);}void HW_Free(void) {OS_EVENT_Set(&_HW_Event);}void HW_Init(void) {OS_CREATETASK(&_TCBHW, "HWTask", _HWTask, 25, _StackHW);OS_EVENT_Create(&_HW_Event);}/********************************************************************//********************************************************************/static void HPTask(void) {HW_Wait(); /* Wait until HW module is set up */while (1) {OS_Delay (50);}}static void LPTask(void) {HW_Wait(); /* Wait until HW module is set up */while (1) {OS_Delay (200);}}/*********************************************************************** main**********************************************************************/int main(void) {OS_IncDI(); /* Initially disable interrupts */OS_InitKern(); /* Initialize OS */OS_InitHW(); /* Initialize Hardware for OS */HW_Init(); /* Initialize HW module *//* You need to create at least one task before calling OS_Start() */OS_CREATETASK(&TCBHP, "HP Task", HPTask, 100, StackHP);OS_CREATETASK(&TCBLP, "LP Task", LPTask, 50, StackLP);OS_SendString("Start project will start multitasking !\n");OS_Start(); /* Start multitasking */return 0;}OS_EVENT_Reset()DescriptionResets the specified event object to non-signaled state.Prototypevoid OS_EVENT_Reset (OS_EVENT* pEvent)ParameterDescriptionpEventTable 94: OS_EVENT_Reset() parameter listAdditional InformationPointer to the event object which should be reset to non-signaled state.pEvent has to address an existing event object, which has been created before by a call of OS_EVENT_Create().The debug version of IAR PowerPac RTOS will check whether pEvent addresses a valid event object and will callOS_Error() with the error code OS_ERR_EVENT_INVALID in case of an error.86IAR PowerPac RTOSfor ARM CoresPPRTOS-2
Event objectsExampleOS_EVENT_Reset(&_HW_Event); /* Reset event object to non-signaled state */OS_EVENT_Pulse()DescriptionSignals an event object and resumes waiting tasks, then resets the event object to non-signaled state.Prototypevoid OS_EVENT_Pulse (OS_EVENT* pEvent);ParameterDescriptionpEventTable 95: OS_EVENT_Pulse() parameter listAdditional InformationIf any tasks are waiting at the event object, the tasks are resumed. The event object remains un-signaled. The debugversion of IAR PowerPac RTOS will check whether pEvent addresses a valid event object and will callOS_Error() with the error code OS_ERR_EVENT_INVALID in case of an error.OS_EVENT_Get()DescriptionReturns the state of an event object.Prototypeunsigned char OS_EVENT_Get (OS_EVENT* pEvent);ParameterDescriptionpEventTable 96: OS_EVENT_Get() parameter listReturn value0: Event object is not set to signaled state1: Event object is set to signaled state.Additional InformationBy calling this function, the actual state of the event object remains unchanged. pEvent has to address an existingevent object, which has been created before by a call of OS_EVENT_Create(). The debug version of IAR PowerPacRTOS will check whether pEvent addresses a valid event object and will call OS_Error() with error codeOS_ERR_EVENT_INVALID in case of an error.OS_EVENT_Delete()DescriptionDeletes an event object.Prototypevoid OS_EVENT_Delete (OS_EVENT* pEvent);ParameterDescriptionpEventTable 97: OS_EVENT_Delete() parameter listAdditional InformationTo keep the system fully dynamic, it is essential that event objects can be created dynamically. This also means therehas to be a way to delete an event object when it is no longer needed. The memory that has been used by the eventobject’s control structure can then be reused or reallocated.It is your responsibility to make sure that:●●Pointer to the event object which should be pulsed.Pointer to an event object who’s state should be examined.Pointer to an event object which should be deleted.the program no longer uses the event object to be deletedthe event object to be deleted actually exists (has been created first)PPRTOS-287
Page 1 and 2:
IAR PowerPac RTOSUser GuidePPRTOS-2
Page 3 and 4:
PrefaceWelcome to the IAR PowerPac
Page 5 and 6:
ContentsPreface ...................
Page 7 and 8:
ContentsOS_WaitCSema() ............
Page 9 and 10:
ContentsOS_LeaveInterrupt() .......
Page 11 and 12:
Introduction to IAR PowerPacRTOSWha
Page 13 and 14:
Basic conceptsTasksIn this context,
Page 15 and 16:
Basic conceptsPREEMPTIVES MULTITASK
Page 17 and 18:
Basic conceptsMAILBOXES AND QUEUESA
Page 19 and 20:
Basic conceptsThe active task may b
Page 21 and 22:
Basic conceptsThe flowchart below i
Page 23 and 24:
Basic conceptsLIST OF LIBRARIESIn y
Page 25 and 26:
Task routinesIntroductionA task tha
Page 27 and 28:
Task routinesOS_CREATETASK() can be
Page 29 and 30:
Task routinesExampleThe following e
Page 31 and 32:
Task routinesExampleint sec,min;voi
Page 33 and 34:
Task routinesAdditional Information
Page 35 and 36: Task routinesReturn valueOS_TASKID:
Page 37 and 38: Software timersSoftware timerA soft
Page 39 and 40: Software timers#define OS_CREATETIM
Page 41 and 42: Software timersOS_SetTimerPeriod()D
Page 43 and 44: Software timersAdditional Informati
Page 45 and 46: Software timersAdditional Informati
Page 47 and 48: Software timersExampleOS_TIMER TIME
Page 49 and 50: Resource semaphoresIntroductionReso
Page 51 and 52: Resource semaphoresResource semapho
Page 53 and 54: Resource semaphoresOS_Request()Desc
Page 55 and 56: Counting SemaphoresIntroductionCoun
Page 57 and 58: Counting SemaphoresPrototypevoid OS
Page 59 and 60: Counting SemaphoresReturn value0: I
Page 61 and 62: MailboxesWhy mailboxes?In the prece
Page 63 and 64: MailboxesMailboxes API function ove
Page 65 and 66: MailboxesExampleSingle-byte mailbox
Page 67 and 68: MailboxesPrototypevoid OS_GetMail (
Page 69 and 70: MailboxesOS_WaitMail()DescriptionWa
Page 71 and 72: QueuesWhy queues?In the preceding c
Page 73 and 74: QueuesReturn valueThe size of the r
Page 75 and 76: QueuesExamplestatic void MemoryTask
Page 77 and 78: Task eventsIntroductionTask events
Page 79 and 80: Task eventsExampleOS_WaitEventTimed
Page 81 and 82: Task eventsPrototypechar OS_ClearEv
Page 83 and 84: Event objectsIntroductionEvent obje
Page 85: Event objectsExampleif (OS_EVENT_Wa
Page 89 and 90: Heap type memory managementANSI C o
Page 91 and 92: Fixed block size memory poolsIntrod
Page 93 and 94: Fixed block size memory poolsProtot
Page 95 and 96: Fixed block size memory poolsProtot
Page 97 and 98: StacksIntroductionThe stack is the
Page 99 and 100: InterruptsIntroductionIn this chapt
Page 101 and 102: InterruptsRules for interrupt handl
Page 103 and 104: InterruptsOS_LeaveInterruptNoSwitch
Page 105 and 106: InterruptsNesting interrupt routine
Page 107 and 108: Critical RegionsIntroductionCritica
Page 109 and 110: System variablesIntroductionThe sys
Page 111 and 112: Configuration for your targetsystem
Page 113 and 114: Time measurementIntroductionIAR Pow
Page 115 and 116: Time measurementPrototypeU32 OS_Get
Page 117 and 118: Time measurementPrototypeOS_U32 OS_
Page 119 and 120: RTOS-aware debuggingThis chapter de
Page 121 and 122: RTOS-aware debuggingTimersA softwar
Page 123 and 124: DebuggingRuntime errorsSome error c
Page 125 and 126: DebuggingValue Define Description17
Page 127 and 128: Performance and resource usageThis
Page 129 and 130: Performance and resource usageThe c
Page 131 and 132: Performance and resource usage*/sta
Page 133 and 134: ReentranceAll routines that can be
Page 135 and 136: LimitationsThe following limitation
Page 137 and 138:
Source code of kernel and libraryIn
Page 139 and 140:
Additional modulesKeyboard manager:
Page 141 and 142:
FAQ (frequently asked questions)Q:
Page 143 and 144:
GlossaryActive TaskCooperativemulti
Page 145 and 146:
IndexIndexAAdditional modules . . .
Page 147:
IndexOS_WaitSingleEventTimed(). . .
show all

IAR PowerPac RTOS User Guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?