AN: Capstone Dive Computer Example - Quantum Leaps

More documents

Recommendations

Info

Application Note: Capstone Dive Computer Example www.state-machine.com (13-14) These global pointers represent active objects in the application and are used for posting events directly to active objects. Because the pointers can be initialized at compile time, they are declared const, sot that they can be placed in ROM. The active object pointers are “opaque”, because they cannot access the whole active object, but only the part inherited from the QActive structure. Copyright © Quantum Leaps, LLC. All Rights Reserved. 12 of 29
Application Note: Capstone Dive Computer Example www.state-machine.com 2.4 Step 4: Designing the State Machines At the application level, you can mostly ignore such aspects of active objects as the separate task contexts, or event queues, and view them predominantly as state machines. In fact, your main job in developing QP application consists of elaborating the state machines of your active objects. 2.4.1 Capstone State Machine Figure 5 shows the state machine associated with Capstone active object. The explanation section immediately following the state diagram explains the main interesting points. Figure 5 Capstone state machine. Copyright © Quantum Leaps, LLC. All Rights Reserved. 13 of 29
Page 1 and 2: QP state machine framework example
Page 3 and 4: 1 Introduction This Application Not
Page 5 and 6: Application Note: Capstone Dive Com
Page 13: Application Note: Capstone Dive Com
Page 19 and 20: (2) Each active object in the appli
Page 21 and 22: eturn Q_HANDLED(); } } (11) return
Page 23 and 24: (7) The memory buffer for the “sm
Page 31: Application Note: Capstone Dive Com

AN: Capstone Dive Computer Example - Quantum Leaps

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

Delete template?

Save as template?