Searching \ for '16c84 data EEPROM use' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: techref.massmind.org/techref/microchip/memory.htm?key=data
Search entire site for: '16c84 data EEPROM use'.

Truncated match.
PICList Thread
'16c84 data EEPROM use'
1997\01\24@034032 by John Sanderson

flavicon
face
Dear PIC.ers,
Thanx to all you who gave me info on using a PC game port to attempt
making measurements. A non-starter of an idea, it turns out....   :(
..
I've tried following faithfully everything uchip tells me to do
(espec. RTBM) re writing data to the eeprom area in the 16c84, but can't
get past  MPASM's  response - the source is (almost) verbatim ex
c84 data sheet.

LOC  OBJECT CODE     LINE SOURCE TEXT
 VALUE

0000                     0067        spacee  equ     0x000
.............................
0007 3055            0089              movlw   0x055           ;fairy-godmother
value
Warning: Argument out of range: eecon2 (137).  Least significant bits
used.
0008 0089              0090         movwf   eecon2
0009 30AA            0091         movlw   0x0AA           ;another FG
Warning: Argument out of range: eecon2 (137).  Least significant bits
used.
000A 0089             0092         movwf   eecon2
Warning: Argument out of range: eecon1 (136).  Least significant bits
used.
000B 1488              0093         bsf     eecon1,eewr     ;set write control
bit
                              0094
..
All searches of previous piclist digests, uchip advanced tut.
examples and FAQ searches have turned up (yet) not one example of
doing this. It's got to be routine !! What am I doing wrong?
Any advice or directions will bestow upon the sender a place in my will.
email from John Sanderson   /   JS Controls, Boksburg, RSA
Manufacturer & purveyor of laboratory force testing apparatus
and related products and services.
Tel/fax: Johannesburg 893 4154    Cellphone 082 453 4815

1997\01\24@034032 by John Sanderson

flavicon
face
Dear PIC.ers,
Thanx to all you who gave me info on using a PC game port to attempt
making measurements. A non-starter of an idea, it turns out....   :(
..
I've tried following faithfully everything uchip tells me to do
(espec. RTBM) re writing data to the eeprom area in the 16c84, but can't
get past  MPASM's  response - the source is (almost) verbatim ex
c84 data sheet.

LOC  OBJECT CODE     LINE SOURCE TEXT
 VALUE

0000                     0067        spacee  equ     0x000
.............................
0007 3055            0089              movlw   0x055           ;fairy-godmother
value
Warning: Argument out of range: eecon2 (137).  Least significant bits
used.
0008 0089              0090         movwf   eecon2
0009 30AA            0091         movlw   0x0AA           ;another FG
Warning: Argument out of range: eecon2 (137).  Least significant bits
used.
000A 0089             0092         movwf   eecon2
Warning: Argument out of range: eecon1 (136).  Least significant bits
used.
000B 1488              0093         bsf     eecon1,eewr     ;set write control
bit
                              0094
..
All searches of previous piclist digests, uchip advanced tut.
examples and FAQ searches have turned up (yet) not one example of
doing this. It's got to be routine !! What am I doing wrong?
Any advice or directions will bestow upon the sender a place in my will.
email from John Sanderson   /   JS Controls, Boksburg, RSA
Manufacturer & purveyor of laboratory force testing apparatus
and related products and services.
Tel/fax: Johannesburg 893 4154    Cellphone 082 453 4815

1997\01\24@061546 by John Sanderson

flavicon
face
------- Forwarded Message Follows -------
From:          Self <Single-user mode>
To:            spam_OUTpiclistTakeThisOuTspammitvma.mit.edu
Subject:       16c84 data EEPROM use
Date:          Fri, 24 Jan 1997 10:34:17

Dear PIC.ers,
Thanx to all you who gave me info on using a PC game port to attempt
making measurements. A non-starter of an idea, it turns out....   :(
..
I've tried following faithfully everything uchip tells me to do
(espec. RTBM) re writing data to the eeprom area in the 16c84, but can't
get past  MPASM's  response - the source is (almost) verbatim ex
c84 data sheet.

LOC  OBJECT CODE     LINE SOURCE TEXT
 VALUE

0000                     0067        spacee  equ     0x000
.............................
0007 3055            0089              movlw   0x055           ;fairy-godmother
value
Warning: Argument out of range: eecon2 (137).  Least significant bits
used.
0008 0089              0090         movwf   eecon2
0009 30AA            0091         movlw   0x0AA           ;another FG
Warning: Argument out of range: eecon2 (137).  Least significant bits
used.
000A 0089             0092         movwf   eecon2
Warning: Argument out of range: eecon1 (136).  Least significant bits
used.
000B 1488              0093         bsf     eecon1,eewr     ;set write control
bit
                              0094
..
All searches of previous piclist digests, uchip advanced tut.
examples and FAQ searches have turned up (yet) not one example of
doing this. It's got to be routine !! What am I doing wrong?
Any advice or directions will bestow upon the sender a place in my will.
email from John Sanderson   /   JS Controls, Boksburg, RSA
Manufacturer & purveyor of laboratory force testing apparatus
and related products and services.
Tel/fax: Johannesburg 893 4154    Cellphone 082 453 4815

1997\01\24@061546 by John Sanderson

flavicon
face
------- Forwarded Message Follows -------
From:          Self <Single-user mode>
To:            .....piclistKILLspamspam@spam@mitvma.mit.edu
Subject:       16c84 data EEPROM use
Date:          Fri, 24 Jan 1997 10:34:17

Dear PIC.ers,
Thanx to all you who gave me info on using a PC game port to attempt
making measurements. A non-starter of an idea, it turns out....   :(
..
I've tried following faithfully everything uchip tells me to do
(espec. RTBM) re writing data to the eeprom area in the 16c84, but can't
get past  MPASM's  response - the source is (almost) verbatim ex
c84 data sheet.

LOC  OBJECT CODE     LINE SOURCE TEXT
 VALUE

0000                     0067        spacee  equ     0x000
.............................
0007 3055            0089              movlw   0x055           ;fairy-godmother
value
Warning: Argument out of range: eecon2 (137).  Least significant bits
used.
0008 0089              0090         movwf   eecon2
0009 30AA            0091         movlw   0x0AA           ;another FG
Warning: Argument out of range: eecon2 (137).  Least significant bits
used.
000A 0089             0092         movwf   eecon2
Warning: Argument out of range: eecon1 (136).  Least significant bits
used.
000B 1488              0093         bsf     eecon1,eewr     ;set write control
bit
                              0094
..
All searches of previous piclist digests, uchip advanced tut.
examples and FAQ searches have turned up (yet) not one example of
doing this. It's got to be routine !! What am I doing wrong?
Any advice or directions will bestow upon the sender a place in my will.
email from John Sanderson   /   JS Controls, Boksburg, RSA
Manufacturer & purveyor of laboratory force testing apparatus
and related products and services.
Tel/fax: Johannesburg 893 4154    Cellphone 082 453 4815

1997\01\24@080948 by hoss karoly

flavicon
face
John Sanderson wrote:
>
> I've tried following faithfully everything uchip tells me to do
> (espec. RTBM) re writing data to the eeprom area in the 16c84, but can't
> get past  MPASM's  response - the source is (almost) verbatim ex
> c84 data sheet.
>

I have a proven working version which I used in many projects

it's in parallax assembly but if you need it . Drop me a line
with your own e-mail address . I don't want to load the list down
with routines .

bye
charley

1997\01\24@080948 by hoss karoly

flavicon
face
John Sanderson wrote:
>
> I've tried following faithfully everything uchip tells me to do
> (espec. RTBM) re writing data to the eeprom area in the 16c84, but can't
> get past  MPASM's  response - the source is (almost) verbatim ex
> c84 data sheet.
>

I have a proven working version which I used in many projects

it's in parallax assembly but if you need it . Drop me a line
with your own e-mail address . I don't want to load the list down
with routines .

bye
charley

1997\01\24@092250 by myke predko

flavicon
face
John,

>LOC  OBJECT CODE     LINE SOURCE TEXT
>  VALUE
>
>0000                     0067        spacee  equ     0x000
>.............................
>0007 3055            0089              movlw   0x055           ;fairy-godmother
> value
>Warning: Argument out of range: eecon2 (137).  Least significant bits
>used.
>0008 0089              0090         movwf   eecon2
>0009 30AA            0091         movlw   0x0AA           ;another FG
>Warning: Argument out of range: eecon2 (137).  Least significant bits
>used.
>000A 0089             0092         movwf   eecon2
>Warning: Argument out of range: eecon1 (136).  Least significant bits
>used.
>000B 1488              0093         bsf     eecon1,eewr     ;set write control
> bit
>                               0094

The warnings you are getting are stating that the "eecon2" addresses that
you are using aren't valid (only 7 Bit addresses are valid).

Two things.

1.  Have you set the Bank Register (RP0) Appropriately?  (ie put in the bsf
STATUS, RP0 before doing this code.)

2.  Once this is done, you can get rid of the messages by changing the
instructions to:

 movwf  eecon2 & 0x07F

Which clears the Most Significant Bit (and puts the address in a valid range
for the bank).

Have you tried running this code through the simulator (and was the write
accomplished)?  While the simulator would have you believe that an EEPROM
write happens almost immediately after setting EECON1.WR, it in fact takes a
very long time.

Good luck!

myke
{Quote hidden}

"I don't do anything that anybody else in good physical condition and
unlimited funds couldn't do" - Bruce Wayne

1997\01\24@092250 by myke predko

flavicon
face
John,

>LOC  OBJECT CODE     LINE SOURCE TEXT
>  VALUE
>
>0000                     0067        spacee  equ     0x000
>.............................
>0007 3055            0089              movlw   0x055           ;fairy-godmother
> value
>Warning: Argument out of range: eecon2 (137).  Least significant bits
>used.
>0008 0089              0090         movwf   eecon2
>0009 30AA            0091         movlw   0x0AA           ;another FG
>Warning: Argument out of range: eecon2 (137).  Least significant bits
>used.
>000A 0089             0092         movwf   eecon2
>Warning: Argument out of range: eecon1 (136).  Least significant bits
>used.
>000B 1488              0093         bsf     eecon1,eewr     ;set write control
> bit
>                               0094

The warnings you are getting are stating that the "eecon2" addresses that
you are using aren't valid (only 7 Bit addresses are valid).

Two things.

1.  Have you set the Bank Register (RP0) Appropriately?  (ie put in the bsf
STATUS, RP0 before doing this code.)

2.  Once this is done, you can get rid of the messages by changing the
instructions to:

 movwf  eecon2 & 0x07F

Which clears the Most Significant Bit (and puts the address in a valid range
for the bank).

Have you tried running this code through the simulator (and was the write
accomplished)?  While the simulator would have you believe that an EEPROM
write happens almost immediately after setting EECON1.WR, it in fact takes a
very long time.

Good luck!

myke
{Quote hidden}

"I don't do anything that anybody else in good physical condition and
unlimited funds couldn't do" - Bruce Wayne

1997\01\25@031117 by Leon Heller

flavicon
picon face
In message <199701241237.KAA04688spamKILLspamphantom.pix.za>, John Sanderson
<.....js000026KILLspamspam.....PIXIE.CO.ZA> writes
>Dear PIC.ers,
>Thanx to all you who gave me info on using a PC game port to attempt
>making measurements. A non-starter of an idea, it turns out....   :(
>..
>I've tried following faithfully everything uchip tells me to do
>(espec. RTBM) re writing data to the eeprom area in the 16c84, but can't
>get past  MPASM's  response - the source is (almost) verbatim ex
>c84 data sheet.

Here's the code I use (I got a bit of help from the PICLIST myself, when
I couldn't get it to work). The assembler generates some warnings, but
the code seems to work, and I've never bothered to change it.

;WRITE BYTE TO DATA MEMORY EEPROM - BYTE IN EEDATA, ADDRESS IN EEADR
;*******************************************************************

EEPROM_WR
       BSF     STATUS,RP0      ;BANK 1
       BCF     INTCON,GIE      ;DISABLE INTERRUPTS
       BSF     EECON1,WREN     ;SET WRITE ENABLE
       MOVLW   55H             ;SET THINGS UP
       MOVWF   EECON2
       MOVLW   0AAH
       MOVWF   EECON2
       BSF     EECON1,WR       ;WRITE BYTE TO EEPROM
EE1
       BTFSC   EECON1,WR       ;WR BIT CLEAR?
       GOTO    EE1             ;NO - LOOP BACK
       BCF     INTCON,GIE      ;YES - ENABLE INTERRUPTS
       BCF     STATUS,RP0      ;BANK 0
       RETURN

;READ BYTE FROM DATA MEMORY EEPROM - ADDRESS IN EEADR, RETURNS DATA IN
EEDATA
;***********************************************************************
****

EEPROM_RD
       BSF     STATUS,RP0      ;BANK 1
       BSF     EECON1,RD       ;EE READ
       BCF     STATUS,RP0      ;BANK 0
       RETURN

Leon
--
Leon Heller, G1HSM
EraseMEleonspam_OUTspamTakeThisOuTlfheller.demon.co.uk
Tel: +44 (0) 118 947 1424 (home)
    +44 (0) 1344 385556 (work)

1997\01\25@031117 by Leon Heller

flavicon
picon face
In message <199701241237.KAA04688spamspam_OUTphantom.pix.za>, John Sanderson
<@spam@js000026KILLspamspamPIXIE.CO.ZA> writes
>Dear PIC.ers,
>Thanx to all you who gave me info on using a PC game port to attempt
>making measurements. A non-starter of an idea, it turns out....   :(
>..
>I've tried following faithfully everything uchip tells me to do
>(espec. RTBM) re writing data to the eeprom area in the 16c84, but can't
>get past  MPASM's  response - the source is (almost) verbatim ex
>c84 data sheet.

Here's the code I use (I got a bit of help from the PICLIST myself, when
I couldn't get it to work). The assembler generates some warnings, but
the code seems to work, and I've never bothered to change it.

;WRITE BYTE TO DATA MEMORY EEPROM - BYTE IN EEDATA, ADDRESS IN EEADR
;*******************************************************************

EEPROM_WR
       BSF     STATUS,RP0      ;BANK 1
       BCF     INTCON,GIE      ;DISABLE INTERRUPTS
       BSF     EECON1,WREN     ;SET WRITE ENABLE
       MOVLW   55H             ;SET THINGS UP
       MOVWF   EECON2
       MOVLW   0AAH
       MOVWF   EECON2
       BSF     EECON1,WR       ;WRITE BYTE TO EEPROM
EE1
       BTFSC   EECON1,WR       ;WR BIT CLEAR?
       GOTO    EE1             ;NO - LOOP BACK
       BCF     INTCON,GIE      ;YES - ENABLE INTERRUPTS
       BCF     STATUS,RP0      ;BANK 0
       RETURN

;READ BYTE FROM DATA MEMORY EEPROM - ADDRESS IN EEADR, RETURNS DATA IN
EEDATA
;***********************************************************************
****

EEPROM_RD
       BSF     STATUS,RP0      ;BANK 1
       BSF     EECON1,RD       ;EE READ
       BCF     STATUS,RP0      ;BANK 0
       RETURN

Leon
--
Leon Heller, G1HSM
KILLspamleonKILLspamspamlfheller.demon.co.uk
Tel: +44 (0) 118 947 1424 (home)
    +44 (0) 1344 385556 (work)

1997\01\25@220457 by Sarunas Cepulis

flavicon
face
John Sanderson wrote:
>
> Dear PIC.ers,
> Thanx to all you who gave me info on using a PC game port to attempt
> making measurements. A non-starter of an idea, it turns out....   :(
> ..
> I've tried following faithfully everything uchip tells me to do
> (espec. RTBM) re writing data to the eeprom area in the 16c84, but can't
> get past  MPASM's  response - the source is (almost) verbatim ex
> c84 data sheet.
>
> LOC  OBJECT CODE     LINE SOURCE TEXT
>   VALUE
>
> 0000                     0067        spacee  equ     0x000
> .............................
> 0007 3055            0089              movlw   0x055
;fairy-godmother
{Quote hidden}

Hi,
Try just :
       movlw   0x55
       ....
       movlw   0xAA
Best regards,
       Saras.

More... (looser matching)
- Last day of these posts
- In 1997 , 1998 only
- Today
- New search...