Hi Rob,

I was about to ask for permission ;-) to update the device files one
> more time. MPLAB 8.15 came out and it has some improvements. I generated
> new device files and saw several changes. Most are however of minor
> importance. Some of the more important changes apply mostly to the newer
> (maybe even future) PICs which are probably not used yet. Since some
> errors which I 'fixed' in the .dev files are back in 8.15 I need some
> time to be sure everything is OK.
> So I guess 'no more device files updates' when we release soon, and we
> keep some improvements in the pipeline!


Maybe we can deal with this issue a better way. Here's what I have in
mind...

If device files are updated, we should ideally perform tests again, just to
be sure( and I'll modify "jallib" script to also include device files
revision to log history). Now, as you say, changes may be minor. Maybe
there's even no changes at all ! As the hex file is the last form before
going to the PIC (jal, asm, etc,...), we could run md5sum on hex files, and
compare these sums between previous and current device files. This will
point to the files which result in changes, and hopefully show those which
did not. After all, changes might occur in part of device files that we may
not even use...

I don't even know if everybody here has run tests against your last devive
files updates. I personally did not have time yet. Since we currently have
no log/track of our test results, we just cannot know (but using jallib
script will fix). So I'd say to update them...

The real problem is the validation process is far too long, and block the
unvalidated map for too long time. We need to find a way to make it faster.


Seb

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/jallib?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to