| ??? 10/22/08 17:46 Read: times |
#159266 - EEPROM not final Responding to: ???'s previous message |
Final design uses a FRAM. Just using the 640 EEPROM to develop code - then using SEEVAL board to unplug and view contents of memory to make sure code works. FRAM is SMD and must not be removable in final design.
Initially write #55H to all 50 memory locations used for this "stacking" routine as actual stored numbers will not reach that high. If main processor sees #55H it knows that location was not filled with valid data yet and is ignored. This also tells me writing to those locations is no problem (WRITEEE) and reading is no problem (READEE) as over 200 locations in memory are used for data and are updated frequently. Can unplug memory chip and view with SEEVAL to confirm. So write and read EEPROM subroutines work fine - this simple stacking routine is the last bit of code to finish up. |
| 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 |