1. Debugging an Application Lab

2. Build/Debug Process A start Load Closest Sample “debug” into MULTI editor Cut and Paste Changes into Sample Build Modified Sample Syntax Errs? Correct Syntax y Connect to Target Board Start Debugger Download Application Set Needed Breakpoints B n

3. Build/Debug Process (2) B Run Application (F5) Inject Test Input Ran OK? y Locate Problem Modify Problem Code A n Covered Test Cases? n Build ROM Version y Re-Test Release Party

4. PEEK/POKE Lab

5. This is the main builder window Building the Project

6. Once all files are present in project workspace, building is readily done Building the Project

7. The Baseline Application Project Configuration Files (*.bld); Source path, System include directories, etc. Included Libraries; ThreadX, TCP/IP Stack, Drivers, BSP Integration C and Assembly Source Files; Common to all Projects Linker File (*.lx); Map the Software to the Hardware Memory Map

8. Perform Final Initializations Spawn all BSP Threads Path to Application Entry Point BSPROOT.C Creates Root Thread tx_thread_create() netosStartup() applicationStart() In root.c Contains main()

9. “Hello World” From root.c…

10. Connecting to Target (1of 3) In the Builder, choose Remote > Connect to Target.

11. Connecting to Target (2 of 3) Enter OCDSERV command line.

12. Connecting to Target (3 of 3) Two new windows »IN/OUT –Displays Printf’s »TARGET—can read/write to Memory/CPU

13. Starting Debugger In the Builder select Debug > debug

14. Debugger Features Set Break Points-Software and Hardware Step through code Examine C-code Examine Interlaced Assembly Examine values of variables, registers, memory

15. Debugger Windows Interlaced Assembler displayed Color enhanced buttons

16. Download code to Target Click “play” button or (F5)

17. Run Program Program is Running Use breakpoints or step through code

18. “PEEK/POKEing” variables Globals –Use “Browse/Globals” –Double-click the variable of interest to see contents –Address will appear in command window –If structure, click to display members, double click to see contents –Right-click the popup box to change value Local variables –Use View/Local Variables –Works similar to “Browse/Globals” above Double click a variable name from debugger C listing to get a watch popup box

19. “PEEK/POKEing” Memory Click “View/Memory” Enter address of interest in popup box Select radix using button Click on a row to change the contents Explore other options of the popup box

20. “PEEK/POKEing” registers Remember, most registers of interest on Net+ARM are memory- mapped. Consult your Hardware Reference Guide. For ARM processor registers: –Use “View/Registers” –In the popup box, right-click a register number to change it. CAREFUL!