Could you try a heuristic approach at run time? Perhaps query one of the peripherals which is not implemented in the simulator to determine if the code is simulating or runnning on hardware. While this is a bit of a nasty hack (and should to be _thoroughly_ documented) it might work for your use. On 25 April 2013 01:39, Barry Gershenfeld wrote: > "Read processor ID": No, this already can be done, and this value would > not change just because you were in debug mode. If I simulate an 18F6622= , > it will tell me it's a 6622 no regardless of what I set in MPLAB's progra= m > or debug menu. > > "Or something": Well, yes, but it's the type of debugger I need to > identify. In a world where everything is complete, I could tell an ICD3 > from a RealICE from a PICKIT2 from an MPLAB-SIM. In reality, I only need > to know about the MPLAB-SIM. > > > > On Wed, Apr 24, 2013 at 2:19 PM, Charles Craft >wrote: > > > http://www.microchip.com/forums/m363024.aspx > > > > I don't have a solution but wanted to restate the question. > > Ideally you would like to read the processor ID (or something similar) > > at run time and have it indicate that it is a simulated part. > > > > chuckc > > > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > --=20 Brendan Gillatt http://www.brendangillatt.co.uk --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .