Truncated match.
PICList
Thread
'Debugging code without an ICE'
1995\09\21@234148
by
ian smart
At the moment I debug the difficilt problems in my PIC code by sending the
debug values as RS232 chars to my PC running Procomm and log the results.
While this works OK its slow to make changes.
What other techniques can be used in this debugging enviroment. I have never
seen a debug monitor used with PICS I gather the lack of ram and code space
restricts this type of debugging to the larger 8031 and 68hc11 type processors.
I would welcome any good suggestions on speeding up the debug cycle
Thanks
-------------------------------------------------------------------
Sender Ian Smart
Location Electronic Structure Of Materials Centre
Flinders University Adelaide Australia
Email spam_OUTian.smartTakeThisOuT
cc.flinders.edu.au
-------------------------------------------------------------------
1995\09\26@191437
by
mlk
On Fri, 22 Sep 1995, ian smart wrote:
>
> What other techniques can be used in this debugging enviroment.
Ian,
I have been using a logic analyzer as the debugging tool for my
16C57 project. I have some spare I/O so I output diagnostic codes to
flag the operation of individual segments of code. I also output results
as needed so that I can check them.
The logic analyzer is great because I can observe the external
events as well such as serial access to an A/D. Logic analyzers are
expensive but I found an old Tektronics DAS 9100 for $300 in an
electronics salvage place. I don't think they knew what they had.
Good Luck,
Martin Kirk
Arizona State University
.....mlkKILLspam
@spam@asu.edu
(602) 582-5718
More... (looser matching)
- Last day of these posts
- In 1995
, 1996 only
- Today
- New search...