Return-Path: robot-board@oberon.com Received: by media.mit.edu (5.57/DA1.0.4.amt) id AA28924; Wed, 17 Nov 93 13:26:19 -0500 Received: from ([127.0.0.1]) by oberon.com (4.1/SMI-4.1_Armado.MX) id AA25306; Wed, 17 Nov 93 13:26:02 EST Date: Wed, 17 Nov 93 13:26:02 EST Message-Id: <9311171824.AA15810@pepper.Eng.Sun.COM> Errors-To: gkulosa@oberon.com Reply-To: cmcmanis@frstprsn.Eng.Sun.COM Originator: robot-board@oberon.com Sender: gkulosa@oberon.com Precedence: bulk From: cmcmanis@frstprsn.Eng.Sun.COM (Chuck McManis) To: Multiple recipients of list Subject: Re: S/W Debugger for MB? X-Listprocessor-Version: 6.0b -- ListProcessor by Anastasios Kotsikonas > In short, how can I write my MB code in Micro-C and use a software > simulator/monitor to debug it? Thanks in advance for any suggestions. I've found that, in general, the amount of C code you can 'fit' into the miniboard is small enough that just staring at the code is enough to find most if not all bugs. (If you get three pages of code into the thing you're lucky) On the other hand it is useful to do debugging and sometimes printing out to the serial port isn't an option (like the miniboard is riding on its power supply which is headed for a cliff :-)) In such situations it is fairly easy to put LEDs on unused bits in port C and turn them on at appropriate times. By soldering a resistor on one of the low power ones you can just "plug it in" between the output ping and the 5V line. Then drive the output pin low to turn on the LED. --Chuck