As the subject says, I ended up debugging a piece of standard hex code, whi=
ch is
supposed to work (but fails to work) on pic16f628 (non A), which was output=
 by
the jal compiler. I had to take apart the hex with a disassembler (gpdasm).=
 And
behold, it uses the opcode 0x0065 which is not a valid opcode according to =
the
pdf datasheet. Nice?!. So gpdasm decodes it as tris, it is used like:

  0821 movf SomeReg, w
  0065 tris 0x65

After staring at this for a while, I summoned help from search engines and =
found
this:

=20
http://www.micro-examples.com/public/microex-navig/doc/087-pic16-secret-opc=
ode.html

Seriously, what is going on?! And who uses undocumented opcodes in a free a=
nd
popular compiler (jal?!). Wouter can you please dot the i's here? Thanks. A=
nd
Scott D. (gnupic tools co-author), since that tris must be coming from a ta=
ble?
Belonging to what cpu from the microchip pic series please?

Any more easter eggs to look forward to?

tia for discussion/answers,

-- Peter


--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.