Hi,
I generally try to use the serial port as my debugging tool...
Well, I cannot say the same about mine. Most my projects use communication between MCU and other devices (another MCU, PC etc); and often and often it is done via UART. So I can not use UART as report channel because at least two reasons:
- it is busy with application I need test;
- the timers 1 and 2 are used with program and so there is no way to set appropriate bitrate of UART.
Moreover there is another limitation of UART - it brokes real time execution. You know, printf() takes alot of time; even if you use own routines then it needs additional support which eats a time/resource/ISR. Btw, to connect MCU UART to PC/RS232 you need additional hardware converter as well.
So what I talk about, hmmm...
Yeah! Mahmood, use just simle LED(s). Remember that each one may be off and on. With very little additional work it may even blink! (=
Divide your program at steps. Light LED if step 1 is passed; then modify program for LED switched on after second step etc... It helps to recognize a place where your program fails.
Finaly, read about people say here. They are codemasters and you will get alot of suggestion, I am sure.
Good days!