It looks to me like you're disassembling unprogrammed memory. The org
commands are leaving gaps of unprogrammed memory. When you disassemble it,
it shows whatever op-code corresponds to all ones.

Harold


> I can see now what you mean. (see attached picture)
>
> Tamas
>
>
>
> On 18 August 2012 11:52, Tamas Rudnai <tamas.rudnai@gmail.com> wrote:
>
>> Hi John,
>>
>> Can you show the test code and the generated disassembly code?
>>
>> Tamas
>>
>>
>> On 18 August 2012 10:35, John Coppens <john@jcoppens.com> wrote:
>>
>>> Hi all.
>>>
>>> Anyone know why some 'retlw 0' might appear after linking in mplabx?
>>> I normally use gpasm, but wanted to see if mpasm would generate the
>>> same code. I was surprised that two of the retlw's appeared at the
>>> start of the hex file, and probably others elsewhere, as the mpasm
>>> generated code is 5 or 6 instructions larger.
>>>
>>> Also, I can't seem to control the order of linking from the IDE, though
>>> there was a reference this would be implemented by version 1.10
>>>
>>> John
>>>
>>> --
>>> http://www.piclist.com PIC/SX FAQ & list archive
>>> View/change your membership options at
>>> http://mailman.mit.edu/mailman/listinfo/piclist
>>>
>>
>>
>>
>> --
>> int main() { char *a,*s,*q; printf(s=3D"int main() { char *a,*s,*q;
>> printf(s=3D%s%s%s, q=3D%s%s%s%s,s,q,q,a=3D%s%s%s%s,q,q,q,a,a,q); }",
>> q=3D"\"",s,q,q,a=3D"\\",q,q,q,a,a,q); }
>>
>
>
>
> --
> int main() { char *a,*s,*q; printf(s=3D"int main() { char *a,*s,*q;
> printf(s=3D%s%s%s, q=3D%s%s%s%s,s,q,q,a=3D%s%s%s%s,q,q,q,a,a,q); }",
> q=3D"\"",s,q,q,a=3D"\\",q,q,q,a,a,q); }
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>


--=20
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
Not sent from an iPhone.
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.