'PICLIST Digest - 1 Dec 1998 to 2 Dec 1998'
> Whats the fix to make the picstart+ work reliably on windows 95 (i already
> turned off the FIFO) on the port. It seems that the comms is too fast or
> somthing as it works ok intermittantly mplab is 3.4 and firmware in picstart
> is v1.2
> Any tips will save loads of stress turning to violance.......
> Cheers Steve.......
I think firmware 1.50 fixed up some COMMs problems.
> Dear colleagues,
> It's the first time that I program a PIC microcontroller and I'm
> experiencing a little problem. I'm working with a UV erasable PIC12C508
> and so far I erased the device correctly. The calibration value for the
> internal oscillator was obviously erased, but I don't know how to
> reprogram this value. I have a document (DS40139D) downloaded from the
> Microchip Web Page and it says that "the calibration value must be read
> prior to erasing the part, so it can be reprogrammed correctly later". I
> read the value that was pre-programmed, but there isn't any kind of
> information about reprogramming this calibration value.
> Could someone help me with this problem? It's fundamental to me this
> calibration value because I'm using the internal oscillator.
You need at the end of your code
ORG 1FFH ;assuming '508
movlw xx ;where xx is the CAL value you wrote down
For OTP parts the above has already been done by MChip.
Peter L. Peres
On Thu, 3 Dec 1998, Mike DeMetz wrote:
> You need at the end of your code
> ORG 1FFH ;assuming '508
> movlw xx ;where xx is the CAL value you wrote down
> For OTP parts the above has already been done by MChip.
Since we're at it, could you (all) please post typical calibartion values
to the list. I'll post mine, from a set of 508's and 509's too as soon as
I finish what I'm doing now (with other processors - and in other
imho this would give a good starting value in case of oops. Is 0x80 a good
>Since we're at it, could you (all) please post typical calibartion values
>to the list. I'll post mine, from a set of 508's and 509's too as soon as
>I finish what I'm doing now (with other processors - and in other
>imho this would give a good starting value in case of oops. Is 0x80 a good
I have : 508 = 0xE0
509 = 0xF0
More... (looser matching)
- Last day of these posts
- In 1998
, 1999 only
- New search...