summaryrefslogtreecommitdiff
path: root/docs/memory.txt
diff options
context:
space:
mode:
authorcheapie <no-email-for-you@example.com>2021-02-21 03:50:59 -0600
committercheapie <no-email-for-you@example.com>2021-02-21 03:50:59 -0600
commitf0ce172302a02c854a52bae449e6dd4c4287f949 (patch)
tree393a106ed0feba7403018519d28ae004b265a56c /docs/memory.txt
parent39a7904f07b943c8ce464ec4486f208ff78ec109 (diff)
downloaddigistuff-f0ce172302a02c854a52bae449e6dd4c4287f949.tar
digistuff-f0ce172302a02c854a52bae449e6dd4c4287f949.tar.gz
digistuff-f0ce172302a02c854a52bae449e6dd4c4287f949.tar.bz2
digistuff-f0ce172302a02c854a52bae449e6dd4c4287f949.tar.xz
digistuff-f0ce172302a02c854a52bae449e6dd4c4287f949.zip
Split documentation from README out into separate files
Diffstat (limited to 'docs/memory.txt')
-rw-r--r--docs/memory.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/memory.txt b/docs/memory.txt
new file mode 100644
index 0000000..8463c20
--- /dev/null
+++ b/docs/memory.txt
@@ -0,0 +1,7 @@
+How to use the RAM and EEPROM chips:
+First, set a channel.
+Messages should consist of a table, with "command" set to either "read" or "write". "address" should be set to the number (0-31) of the 512-character block to read or write, and if writing then "data" should contain the data to write.
+Example (to write - reading is similar, but with no data):
+ {command = "write",address = 7,data = "9a91a9e451b94dc262972557ab0d406f"}
+
+The RAM and EEPROM chips behave identically, except that the RAM chip loses its contents when dug whereas the EEPROM does not.