1: Try some basic C constructs like loops, arrays, value tests using if-else, a switch statement etc. You can stop in places and inspect the loop counters, see how arrays are indexed, where the switch statement goes when you set different values for the switch argument etc. Play with timers and interrupts. Explore the peripherals. Whatever you feel you are weak on. Code it up and step it through. In this case, the simulator/debugger can be an instructor.
2: Yes! I would take what you just did and run it on the hardware using your PK3 as a debugger. That will give you some experience before the code gets more complex.
3: Yes, a real PK3 will interface to the target PIC's internal debug hardware. There usually are some limitations, number of breakpoints etc, that are chip-dependent. You can see what they are in the MPLABX dashboard window. You will be able to do the things you did in the sim i.e. set breakpoints, inspect and modify memory registers etc.
2: Yes! I would take what you just did and run it on the hardware using your PK3 as a debugger. That will give you some experience before the code gets more complex.
3: Yes, a real PK3 will interface to the target PIC's internal debug hardware. There usually are some limitations, number of breakpoints etc, that are chip-dependent. You can see what they are in the MPLABX dashboard window. You will be able to do the things you did in the sim i.e. set breakpoints, inspect and modify memory registers etc.
Last edited:




