??? 10/22/08 23:00 Read: times |
#159270 - Hard coded values Responding to: ???'s previous message |
Alan, you really need to find out about using labels rather than hard coded values in your code. Whilst it may not be causing the problem in this instance, it certainly will cause you problems in the future. Also, why does the readee routine place the returned value in 46h? The more conventional method would return the value in the ACC. Set yourself some rules in passing parameters - byte in ACC, word in R2,3 etc... It makes you code easier to read and easier to write.
At a guess, I'd say your problem is that you're not waiting for the write to complete before reading/writing another value. |
Topic | Author | Date |
stacking numbers in memory code problem | 01/01/70 00:00 | |
does readee put its value in 46H? | 01/01/70 00:00 | |
readee reads memory | 01/01/70 00:00 | |
Your code looks good to me | 01/01/70 00:00 | |
it looks awful to me | 01/01/70 00:00 | |
it was indented | 01/01/70 00:00 | |
like this | 01/01/70 00:00 | |
Instructions | 01/01/70 00:00 | |
yes, yes, ok | 01/01/70 00:00 | |
Guided/unguided? | 01/01/70 00:00 | |
EEPROM not final | 01/01/70 00:00 | |
Hard coded values | 01/01/70 00:00 | |
that can't be it | 01/01/70 00:00 | |
Are you 199% sure?? | 01/01/70 00:00 | |
Here is the WRITEEE code | 01/01/70 00:00 | |
HA! figured it out![]() | 01/01/70 00:00 |