IAR PowerPac RTOS User Guide

More documents

Recommendations

Info

Additional InformationThis function does not return.Example#include "RTOS.H"OS_STACKPTR int StackHP[128], StackLP[128]; /* Task stacks */OS_TASK TCBHP, TCBLP; /* Task-control-blocks */static void HPTask(void) {while (1) {OS_Delay (10);}}static void LPTask(void) {while (1) {OS_Delay (50);}}/*********************************************************************** main**********************************************************************/void main(void) {OS_IncDI(); /* Initially disable interrupts */OS_InitKern(); /* initialize OS */OS_InitHW(); /* initialize Hardware for OS *//* You need to create at least one task here ! */OS_CREATETASK(&TCBHP, "HP Task", HPTask, 100, StackHP);OS_CREATETASK(&TCBLP, "LP Task", LPTask, 50, StackLP);OS_Start(); /* Start multitasking */}Different builds of IAR PowerPac RTOSIAR PowerPac RTOS comes in different builds, or versions of the libraries. The reason for different builds is thatrequirements vary during development. While developing software, the performance (and resource usage) is not asimportant as in the final version which usually goes as release version into the product. But during development, evensmall programming errors should be caught by use of assertions. These assertions are compiled into the debug versionof the IAR PowerPac RTOS libraries and make the code a bit bigger (about 50%) and also slightly slower than therelease or stack check version used for the final product.This concept gives you the best of both worlds: a compact and very efficient build for your final product (release orstack check versions of the libraries), and a safer (though bigger and slower) version for development which will catchmost of the common application programming errors. Of course, you may also use the release version of IARPowerPac RTOS during development, but it will not catch these errors.PROFILINGIAR PowerPac RTOS supports profiling in profiling builds. Profiling makes precise information available about theexecution time of individual tasks. You may always use the profiling libraries, but they induce certain overhead suchas bigger task control blocks, additional ROM (approximately 200 bytes) and additional runtime overhead. Thisoverhead is usually acceptable, but for best performance you may want to use non-profiling builds of IAR PowerPacRTOS if you do not use this feature.22IAR PowerPac RTOSfor ARM CoresPPRTOS-2
Basic conceptsLIST OF LIBRARIESIn your application program, you need to let the compiler know which build of IAR PowerPac RTOS you are using.This is done by defining a single identifier prior to including RTOS.h.Build Define DescriptionR: Release OS_LIBMODE_R Smallest, fastest buildS: Stack check OS_LIBMODE_S Same as release, plus stack checkingD: Debug OS_LIBMODE_D Maximum runtime checkingTable 2: List of librariesPPRTOS-223
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: Basic conceptsThe flowchart below i
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 and 86:
Event objectsExampleif (OS_EVENT_Wa
Page 87 and 88:
Event objectsExampleOS_EVENT_Reset(
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

Create successful ePaper yourself

Delete template?

Save as template?