EEPROM writes and reads

[Acetronics2]

Hi, Boroko

Here's an example of what I usually do ...

	mesure 		VAR WORD
	duree  		VAR WORD
	dureeprog  	VAR WORD
	dureeral	VAR WORD
	dureesafe	VAR WORD
	echantillon	VAR WORD
	lastok		VAR WORD

	delay    	VAR BYTE
	wrong 		VAR BYTE
	ohoh		VAR BYTE
	
	side 		VAR BIT
	flagbougie 	VAR BIT
	battok		VAR BIT
	dejavu		VAR BIT
	 	 
	PORTA = 0
	PORTB = 0

'Pour 16F628

	CMCON = 7
	CCP1CON = 0

' End of Config.

'******************************************************************************
'  EEPROM checking
'******************************************************************************


	Read 2,dureeprog.lowbyte
	Read 1,dureeprog.highbyte
	Read 3,side
	Read 5,dureesafe.lowbyte
	Read 4,dureesafe.highbyte
	Read 7,dureeral.lowbyte
	Read 6,dureeral.highbyte
'	Read 8,flagbougie 		'Seulement si déverrouillé, sinon 0

	IF ( dureeprog <> $FFFF ) AND ( dureesafe <> $FFFF ) AND ( dureeral <> $FFFF ) Then 
	
	lastok     = dureesafe ' If memory programmed
	flagbougie = 0         ' Start on locked position ... for safety.

	GoTo locked            ' Starting address

	EndIF
	

'******************************************************************************
' Measure of programming pulse
'******************************************************************************


	IF reset = 0 Then mesurepro   ' If jumper ON jump to programming mode

'******************************************************************************
' Check if programming jumper ON and lock if not
'******************************************************************************


 oubli: 

	error = 1
	Pause 50
	error = 0
	Pause 50

	GoTo oubli

	
'********************************************************************
  mesurepro: ' Programming mode

	led = 1 : error = 1


 mesurepro1:

	Pause 50
	led = 0 : error = 0

...
...

Looks EXACTLY what Darrel told you ... no ???

Alain

[boroko]

Hi Alain,

I see that you have given an example of what Darrel was saying (thanks), but I don't understand why you needed to READ the data in that order. Obviously to get .lowbyte and then .highbyte,but why is that necessary?

Is that just for your application or is that something that I need to pay attention to?

Is there anything wrong with just storing it in order in the first place?

My understanding is that you cut this example out of one of your existing apps and the rest of the code doesn't necessarily apply to mine, right?

For mine, I believe that I would do the IF/THEN to check for $FFFF, and if it were blank, give it a start value.


Darrel,
Thanks for your feedback. I didn't see that I wasn't getting to the first "call DlyTime" just before main been executed.

Guys, thanks for looking at. Sometimes the finer points are the ones that are hard to catch. "codeblind" has a nice ring to it ;-}

[Acetronics2]

Hi Alain,

I see that you have given an example of what Darrel was saying (thanks), but I don't understand why you needed to READ the data in that order. Obviously to get .lowbyte and then .highbyte,but why is that necessary?
Is that just for your application or is that something that I need to pay attention to?

Is there anything wrong with just storing it in order in the first place?

Hi, Boroko

Here, it's on your own ... you place your variables in the order you want ... just always use the same order, not to mix them ...

My understanding is that you cut this example out of one of your existing apps and the rest of the code doesn't necessarily apply to mine, right?

For mine, I believe that I would do the IF/THEN to check for $FFFF, and if it were blank, give it a start value.

YES, of course ... may be you already have noted I'm suddently a bit lazy when giving "already cooked" food ...

Alain

[boroko]

Alain,
Thanks for the answer. I was pretty sure that I understood it, but I still remember when I would hang on every word of advise that came from someone that I respected. I remember trying to figure out every possible meaning of a suggestion and feeling frustrated. Now, because of those memories, I try and close the loop and give a conclusion so that everyone can gain from the advise. Thank you for offering it so that we could learn.

Bo