Diagnostic messages encapsulated in your host communication protocol to a dedicated diagnostic console on the host.Use this for measuring percent of time spent in a critical routine (for example ISR) directly readable with a voltmeter.Īnd planned in advance for your software: Test pad tied to GPIO for triggering scope or measuring duration.In case you need to blink SOS or a numeric status code, or otherwise make internal state visible. I like to glue a header strip to the edge of the board for an easy connection to the scope/logic analyzer, and solder wires from the test pads to the header.any important signals you'll need to access.
PCB test pads or even headers, especially important with today's tiny component sizes, for:.2) Plan what you must, and how you are going to debug on target.Ī few things best planned in advance on your PCB: Run from a test command or even at startup. Then ported to the embedded target with embedded test cases.įor each C++ class I usually add a QwikTest() member that verifiesĬlass functionality, built only in debug builds, and
#Iar 8051 crash code#
1) When ever possible, do NOT debug on embedded target.Īlgorithmic code is best developed and debugged on a host,
0 kommentar(er)
