Effect Ulit wrote: > Caisson said: > > > Hello All, > > > > I'm trying to find a *full* , numeric sorted, list of all > > possible/imposssible commands for the 16F84 (and others). > > > > No, I'm not trying to generate an assembler that will use these commands as > > a > > means to signature the code (most controllers won't let you read the > > program-memory contents anyway), but to introduce some "break-point" > > instructions into the source-file. > > > > When my dis-assembler/single-stepper hit's one of those, it should perform > > a special > > function. > > > > So, does anyone know ? > > > > By the way: I tried to use MPASM to generate a list of usable opcodes, but > > I do not really trust it's dis-assembler (it disassembles an opcode to > > "TRIS PORTD" just fine, but an 16x84 has got only *two* ports ....) > > > > Regards, > > Rudy Wieser > > > > As far as I know, all the opcodes are in the 16f8x pdf datasheet file > (Table 9-2) freely available from the microchip web site. And the opcodes > that are UNused will have a 'NOP' effect. At least thats what the book says. NOT TRUE! Notably, the CLRW instruction. Because all instructions are R/M/W the original CLRW instruction would read whatever the IND is pointing to. If this happens to be PORTB, your PORTB capture got screwed. I fixed this by redefining CLRW to 0104 (reads FSR instead). Microchip changed the generated opcode in rev 5.00 to fix this. SO, 0100-017F are all CLRW instructions, which read the corresponding registers addressed by the low order bits. For the most part this has no effect (expect PORTB if doing captures, as I do). Robert -- http://www.piclist.com hint: The PICList is archived three different ways. See http://www.piclist.com/#archives for details.