Need help with write function

[sayzer]

Hi Chris,
EEPROM is already a reserved word.
So in your code, you should be using a different name for EEPROM subroutine, say WriteRom.

EEPROM 0,[0,0]  
'This will write 0 to EEPROM location 0 
'and 0 to EEPROM location 1.
'works only during the programming of PIC
'Not each time PIC powers up
                                                                                                 
Beep var byte
Flash var byte


Gosub readrom   
'Since EEPROM locations 0 and 1 have known values now,
'we can read and store them.
'This will be done each time PIC powers up.
'So each time PIC powers up we will get the last saved values.

Start:

if portb.4=1 then
  beep=beep+1
  gosub WriteRom      'We Write the new value into EEPROM.
  gosub ReadRom       'Then we read it right away and store it.
  if beep=1 then high portb.0
endif

if portb.3=1 then 
   flash=flash+1
   gosub WriteRom      'We Write the new value into EEPROM.
   gosub ReadRom       'Then we read it right away and store it.
   if flash=2 then high portb.1
endif

goto start


WriteRom:
    write 0, beep   'Takes approx. 10mSec to complete.
    pause 15
    write 1, flash
    pause 15
    return

ReadRom:
    read 0, beep   'Reading is almost instantenous
    read 1, flash
    return

end

- In your code, when will you "low" the ports after you pull them high?
- Pulling the ports high is(are) inside the IF statements; are not they supposed to be outside the IF statements but inside the main loop?



-----------------------------------------------

[Christopher4187]

Thanks Melanie, Paul, Sayzer and Arch. I have been successful in writing and reading a 16F688. Just one question in response to the post by Sayzer. I used the data command, write command and read command. I see Sayzer used the EEPROM to store the variables and when looking at the PBP manual, I don't understand what the difference is. Just by using Data to program, read to view and write to store, everything worked great. What's the difference between Data and EEPROM and why would someone choose EEPROM over Data?

[mister_e]

Unless you want to use the 'label' feature as stated in the DATA section, there's no difference as same program the internal EEPROM at programming time.

The main difference is just in the way to write the statement.

I feel that one or the other is an BASICStamp statement...

Now i don't know why but i always use the DATA statement... or MPASM assembler DE