Hi Joep,

Joep Suijs wrote:
> 2008/10/10, Rob Hamerling <[EMAIL PROTECTED]>:
>> PS: Now the dev2jal script doesn't only have to deal with issues with
>> MPlab and the compiler, but also with particular PIC programmers.....
>>
> It seems to be required that this issue is handeled at some stage of
> the developemnt chain to get it to work.
> How is this handeled with other chains, like the assembler and
> microchip c compiler?
> It does not appear so strange to me that the compiler deals with chip
> specifics as much as possible and as a result of that, these detailes
> should be known to the compiler. (that's what's happing, if I
> understand correct).

Of course you are right, but that is not what I meant.  With "issues 
with the compiler" I was thinking of the bugs which are now history with 
release 2.4h, but before that I had to find circumventions.

I did not like a vote with -1 for some of the blink samples just because 
the verify process of a certain PIC programmer doesn't handle fixed (one 
or zero) bits of the corresponding PIC.  I blame the PIC programmer, not 
the device files or blink samples.

On the other hand when it is a popular PIC programmer it will be better 
if we can avoid problems (possibly also with other programmers). And it 
was already on my to-do list to provide better default fuse-bits 
settings in the device files. And after all it wasn't such a big effort 
as I feared. I just don't like it when I have to change my priorities 
because of third party issues..... :-(

I have done some tests with the Wisp648 programmer and Xwisp software as 
delivered by Voti (I normally use my improved variants of these). I 
could reproduce Eur's problems with the current device files and these 
were gone with the new device files with individual PIC-specific default 
fuse bits settings.

Regards, Rob.


-- 
Rob Hamerling, Vianen, NL (http://www.robh.nl/)

--~--~---------~--~----~------------~-------~--~----~
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