This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ReadWrite EEPROM in 89S8252

I got a code, and modified it to run..
But i can't seem to get the code correct.
it has to do with XDATA but i can't seem to get it right.

#include <AT898252.H>
#include "lcd.c"


BYTE ReadEEPROM(int addr)
{
	char EEdata;
	WMCON |= 0x08; // Enable EEPROM memory space

	EEdata = addr; // --> how do u write here?

	WMCON &= 0xF7; // Disable EEPROM memory space
	return(EEdata);
}

// To write a single byte to a location in EEPROM.

void WriteEEPROM(int addr, char EEdata)
{
	WMCON |= 0x08; // Enable EEPROM memory space
	WMCON |= 0x10; // Enable EEPROM memory write

	addr = EEdata; --> how do u write here?

	msdelay(15);
	WMCON &= 0xEF; // Disable EEPROM memory write
	WMCON &= 0xF7; // Disable EEPROM memory space
}


here's the assembly version..it worked..
but didn't manage to convert it into C.


WMCON DATA 96h ; watchdog and memory control register
EEMEN EQU 00001000b ; EEPROM access enable bit
EEMWE EQU 00010000b ; EEPROM write enable bit
WDTRST EQU 00000010b ; EEPROM RDY/BSY bit
ADDRESS EQU 10H
DATAS EQU 0AAH

; EEPROM read example.

;orl WMCON, #EEMEN ; enable EEPROM accesses
;mov dptr, #ADDRESS ; address to read
;movx a, @dptr ; read EEPROM
;xrl WMCON, #EEMEN ; disable EEPROM accesses

; EEPROM write example, utilizing fixed delay for write cycle.
; Delay is worst case (10 ms). Code for delay is not shown.
; Write is followed by verify (read and compare), but code to handle
; verification failure is not shown.


orl WMCON, #EEMEN ; enable EEPROM accesses
orl WMCON, #EEMWE ; enable EEPROM writes

mov dptr, #ADDRESS ; address to write
mov a, #DATAS ; data to write
movx @dptr, a ; write EEPROM

xrl WMCON, #EEMWE ; disable EEPROM writes
xrl WMCON, #EEMEN ; disable EEPROM accesses

Parents
  • "the assembly version ... worked.
    but didn't manage to convert it into C."


    Then leave it in assembler!
    There is absolutely no point whatsoever in converting it to 'C' - just to break it!!

    It is perfectly acceptable & normal to have a project containing both 'C' and assembler modules.

    There is no problem calling assembler from 'C' and vice-versa - there is a whole section in the C51 manual that tells you how to do it!

Reply
  • "the assembly version ... worked.
    but didn't manage to convert it into C."


    Then leave it in assembler!
    There is absolutely no point whatsoever in converting it to 'C' - just to break it!!

    It is perfectly acceptable & normal to have a project containing both 'C' and assembler modules.

    There is no problem calling assembler from 'C' and vice-versa - there is a whole section in the C51 manual that tells you how to do it!

Children
No data