Hi Rob,
Performed quick tests, results are very different, as per hex and asm
files. Tested using blink sample and 18f4550.jal. __config appears to be
different for instance, I'm not sure if this is expected. Still
investigating on other ways to compare.
$ diff -n sample/18f4550_blink.asm sample/18f4550_blink_new.asm
9,11c9,11
< __config 0x00300000, 0x00
< __config 0x00300001, 0x0c
< __config 0x00300002, 0x1f
---
> __config 0x00300000, 0x20
> __config 0x00300001, 0xcc
> __config 0x00300002, 0x3f
14,15c14,15
< __config 0x00300005, 0x83
< __config 0x00300006, 0x81
---
> __config 0x00300005, 0x87
> __config 0x00300006, 0xa1
("<" is for previous device files, ">" is for new ones)
Can you provide a device for 18f27j53 so I can test several samples on my
jaluino bee board ?
Cheers
Seb
On 29 July 2013 20:33, Sebastien Lelong <[email protected]> wrote:
> Hi Rob,
>
>
>> Thanks for having a look and report.
>> I would appreciate much more feedback from you and others. Without
>> feedback it looks like nobody is interested in device files for future PICs
>> (not supported by the now obsolete MPLAB) and I wasted my time....
>>
>
> Please be sure you're not wasting your time. I'm sorry I can't spend much
> time on this these days, that should be better now. I'll try to provide a
> way to systematically compare previous and new devices files as I mentioned
> earlier !
>
> Cheers
> Seb
>
--
Sébastien Lelong
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/jallib.
For more options, visit https://groups.google.com/groups/opt_out.
