Problem with saving to EEPROM...

[NavMicroSystems]

Tear,

the DATA statement doesn't work that way, see PBP Manual section 5.11

I guess you can't expect someone to help you any further with the "spaghetti"-code you have posted, because it is "unreadable"

It is no surprise that one gets lost with this kind of code.

In addition:

some CRLF in your posting would have increased readabiltiy dramatically.

[Tear]

Hi,

After more testing I have found out that using the DATA and EEPROM command are not writing the value to the EEPROM. Below is test code to see if the value I want to place in EEPROM is written to it. Unfourtantly it doesnt work and doesnt work with any value. Looking at the manual it said that you need to do the READ and WRITE command in seperate bytes since I am using words to hold values larger than 255.

Here is the example code:


Delay var word

EEPROM 0, [1500]
read 0, Delay.BYTE0
Read 1, Delay.BYTE1

if Delay = 1500 then
goto loop
else
goto Flash
endif

Flash:
high PORTB.3
pause 500
low PORTB.3
pause 500
goto flash

''Start of program!
Loop:
'Run program



No matter what number I try to use for the EEPROM command the light will always go to the flash loop saying that it isnt reading the same value.

~Michael

[NavMicroSystems]

again:

the DATA statement doesn't work the way you are using it, see PBP Manual section 5.11

the EEPROM statement doesn't work that way either, see PBP Manual section 5.18

DATA WORD 1500
would do the trick.

OR: split your word into two bytes and use:

DATA @0,$DC,$05
(Attention, LowByte is first in this example!)

If you want the HighByte first you have got to swap the Byte order in your READ and WRITE statemenst as well.

B.T.W.
you could make your life a lot easier by moving to a more up to date PIC like the 16F628 or 16F88 (which is Loader compatible!) or one of the many others...

...you could get rid of the external Resonator (or Crystal with it's Caps)

Another thing I have seen in your code example is:
your Buttons appear to be active HIGH, means you have got to have PullDown resistors at the corresponding PIC Pins.

If you would reverse this logic you could even get rid of these resistors and use the PICs internal weak pullups.

[Tear]

Sorry for reposting the same thing. I read the manual and even though PICBasic makes it a lot easier for coding I am not strong at it at all. 99% of my experience as a student is in building circuits (just finished my sophmore year of EE).

I have one question though, if you dont mind. Using DATA WORD 1500 works, but I am guessing that it places it at memory slot 0 of the EEPROM. How can I place another variable like this after the first one? I am sure that I need to includethe address in the command somehow.

Thanks,
Michael

[NavMicroSystems]

I have one question though, if you dont mind. Using DATA WORD 1500 works, but I am guessing that it places it at memory slot 0 of the EEPROM. How can I place another variable like this after the first one? I am sure that I need to includethe address in the command somehow.

OK,
we are talking about the DATA statement.
It preloads the EEPROM at program time.

If you want to specify a location (other than the current pointer position) there is only one choice:
use DATA @Location,Byte1,Byte0.......

There is NO way of specifying a location (other than the current pointer position) a WORD is to be written to.

But this is not much of a problem, since the WORD is written to the location starting from the current pointer position.
(Bear in mind, a WORD is written LowByte first!)


So:

DATA @0,$11,$22
DATA WORD $AABB
DATA $33
DATA $44
DATA WORD $CCDD

would result in the following EEPROM content:
11 22 BB AA 33 44 DD CC

Just try it !

However,
I would always use DATA with Bytes (since READ and WRITE only deal with Bytes), because later on in your program is a lot easier, you don't, have to remember wether or not you have to swap the order of the two bytes you have just "READ".