QDK PIC24/dsPIC-C30 - Quantum Leaps

More documents

Recommendations

Info

QDK PIC24/dsPIC-C30 www.state-machine.com/pic MPLAB IDE, you need to de-select the ICD 2 as the Debugger and select ICD 2 as the Programmer (you cannot configure ICD 2 as a programmer and debugger simultaneously). To program the code into the PIC24/dsPIC device, you click the “Program Target Device” icon. After the programming is done, you can release the device out of reset by clicking the appropriate icon. You can also disconnect the ICD 2 completely and power-cycle the board. The programmed DPP application should start running standalone. 2.3.4 Collecting the QS software trace QS (QP-Spy) is a software tracing facility built into all QP components and also available to the Application code. QS allows you to gain unprecedented visibility into your application by selectively logging almost all interesting events occurring within state machines, the framework, the kernel, and your application code. QS software tracing is minimally intrusive, offers precise time-stamping, sophisticated runtime filtering of events, and good data compression (see Chapter 11 in [PSiCC2]). The dpp-spy.mcp project contains the Spy configuration that enables the QS software tracing and links with the Spy-versions of the QP libraries (see Listing 1). You select the Spy configuration by activating the dpp-spy.mcp project in the MPLAB IDE (see Figure 4). Before you download and start the DPP-Spy configuration to the Explorer 16 board, you should connect the board’s build-in DB9 connector to your workstation via a straight serial cable. Figure 5 shows the QSPY output received from the DPP-Spy configuration. NOTE: Please note that only a small subset of the QSPY records are allowed through the QS filters. Please refer to the source code (bsp.c) and the “QSPY Reference Manual” [QSPY 08] for more information about using the QS filters. You launch the QSPY utility on a Windows PC as follows. Change the directory to the QSPY host utility \tools\qspy\win32\mingw\rel and execute: qspy –cCOM1 –b38400 –O2 –F2 –S2 –E1 –Q1 –P1 –B1 The meaning of the parameters is as follows: -cCOM1 specifies COM port (change to actual COM port number you’re using) -b38400 specifies the baud rate (depends on the oscillator frequency of your board, see Section 7) -O2 specifies the size of an object pointer to 2 bytes -F2 specifies the size of a function pointer to 2 bytes. -E1 specifies the size of an event to 1 byte (an event may have up to 255 bytes). -Q1 specifies the size of a memory queue counter to 1 byte (a event queue can fit up to 255 events). -P1 specifies the size of a memory pool counter to 1 byte (a memory pool can manage up to 255 memory blocks). -B1 specifies the size of a memory block to 1 byte (a memory pool can manage block up to 255 bytes). Copyright © Quantum Leaps, LLC. All Rights Reserved. 10 of 35
QDK PIC24/dsPIC-C30 www.state-machine.com/pic Figure 5: QSpy output from the DPP-QSpy configuration “Dictionary” trace records Time stamp column State entry Transition Internal Transition Copyright © Quantum Leaps, LLC. All Rights Reserved. 11 of 35
Page 1 and 2: QP state machine frameworks for PIC
Page 3 and 4: 1 Introduction This QP Development
Page 5 and 6: QDK PIC24/dsPIC-C30 www.state-machi
Page 11: QDK PIC24/dsPIC-C30 www.state-machi
Page 37: QDK PIC24/dsPIC-C30 www.state-machi

QDK PIC24/dsPIC-C30 - Quantum Leaps

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

Delete template?

Save as template?