DAT address at run-time
ShawnRD
Posts: 10
Hello all,
Is it possible to determine the memory address of the DAT block data on the eeprom, and
also to write back to that address with an updated value. All values are byte size. I have a 32kb
eeprom installed on my ppdb. I can modify the ram data but need to save it back to eeprom
so it will reboot with the new data. I appreciate any/all help in advance.
Thank you,
Shawn
Is it possible to determine the memory address of the DAT block data on the eeprom, and
also to write back to that address with an updated value. All values are byte size. I have a 32kb
eeprom installed on my ppdb. I can modify the ram data but need to save it back to eeprom
so it will reboot with the new data. I appreciate any/all help in advance.
Thank you,
Shawn
Comments
Shawn
Typical forum service.
without a post. So much info and help makes learning and experimenting a real pleasure.
btw, this is for an air compressor controller for work. 15 in VGA display and keyboard for param changes,8 ch ADC for analog sensors
OPTO22 modules to control load/unload valves,ect. Have all working but the param changes part, something to do now for Monday.
Thanks again,
Shawn
I typed my original reply from a netbook in bed. Sorry it was so short. Normally I would have linked to the page discussing the EEPROM datalogger. I just noticed I ended my sentence (in original post) with a coma instead of a period. I don't type as well in the dark on my netbook as I do at my regular computer (I'm on it now).
I'm not sure if the EEPROM object still has the problem of not releasing he I2C lines (I just checked, it does). I posted a modification to the object that does release the lines in case you have other I2C devices.
Duane
I made a note of this. Right now just the one eeprom, but may need I/O expander to monitor status of more inputs,8 in/8 out right now. considering 2nd,larger (512kb?)
eeprom to log what was happened to lead up to the machine breaking down (overheat,low oil,ect.). Ohh, maybe a touchscreen instead of a keyboard. mmmm
Shawn
I had to check. You're right the PPDB does just have a 32K EEPROM. Many Propeller boards come with 64K chips.
You could even go larger than a 512kb EEPROM. There are also 1024kb (128KB) EEPROMs that work with the Prop. The A0 pin isn't connected internally so you can access the upper 64K by changing the address. I'm using a 1024kb chip in one of my datalogger projects.
I had to keep all the wires on the bottom of the board with the EEPROM chip so it wouldn't interfer with my being able to connect and disconnect the transceiver on the top of the board.
The red wire is connected to the A1 pin (pulling it high) so it has a different address than the boot EEPROM. As I previously mentioned, pulling the A0 pin high wouldn't have had any affect on the EEPROMs address so I used the A1 pin instead.
I can't quite figure out why this stuff is so fun.
Duane
to log the status of all inputs. 16 bytes/sec for 10 hr/day = 576kb.
Shawn
Shawn