Thanks Byron,

I was thinking already along the same lines. I did check the bootloader 
(I am using the one by Shane Tolmie) and the LVP is on by default. A 
quick change to that should fix the RB3 issue.

I do wholeheartedly agree with you on the benefits of using a 
bootloader. It is by far the easiest way of working with a pic, for the 
reasons that you have mentioned. Being a hobbyist, it has simplified my 
project enormously.

My comment was one of frustration, born out of a *long* day. I must 
exercise what grown-up people like to call self-control ...

Byron A Jeff wrote:

>On Thu, Sep 09, 2004 at 04:55:09PM -0400, Spiros wrote:
>  
>
>>Arghhhh ...
>>
>>I thought using the bootloader was too good to be true ... thanks for 
>>setting me straight Jason.
>>    
>>
>
>Im my opinion it is the best method as it gives flexibility to the 
>interface, is in circuit, often giving a debugging back channel.
>
>BTW the solution to your problem is simple: reprogram the bootloader
>into the part with the LVP config bit disabled. This will free up RB3.
>
>The only bit I'd really like to have control over is one of the two
>that you really can't have control over: the WDT bit. If the part can
>disable the WDT then the WDT becomes useless.
>
>The other BTW is LVP. Interesting question if LVP was changable
>in software should it be disabled. Note that a LVP programmer cannot
>disable LVP, only an HVP programmer can. Rationale is that if an LVP
>programmer can disable LVP, then the programmer cannot program the part
>anymore.
>
>BAJ
>_______________________________________________
>http://www.piclist.com
>View/change your membership options at
>http://mailman.mit.edu/mailman/listinfo/piclist
>
>  
>
_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist