You can always use the "Program Memory" window in MPLAB IDE. Selecting the tab "Symbolic" (on the bottom) shows the disassembled code with symbolic debug information. Isaac Em 29/11/2013 20:51, James Cameron escreveu: > You always have the .hex to fall back on. One can get quite good at > recognising instructions. Once trick I've used is to highlight > specific hex values in different colours of text. Datasheet in one > hand, hex in the other. > > I don't know the compiler or assembler you are using, but most do have > an ability to output the details you need. This is because the > compiler writer often needs it. Have to hope it is documented. > > On Fri, Nov 29, 2013 at 12:03:29PM -0500, Neil wrote: >> Yes, but it will make calls to the library routines -- will the =20 >> disassembler give me the breakdown (disassembly) of those delay =20 >> routines? That would be nice... I'll have to check when I'm at that =20 >> computer. >> >> >> >> >> Quoting Marcel Duchamp : >> >>> On 11/28/2013 12:03 PM, Neil wrote: >>> If you think it's down to the difference between the two delay routines= , >>> I would compile each version and examine the output assembly listing. >>> >> >> --=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 --=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 .