aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorSelene ToyKeeper2023-11-03 11:30:46 -0600
committerSelene ToyKeeper2023-11-03 11:30:46 -0600
commit0d515d67a0048094e2aba1cd2e4c131d57883dfe (patch)
treea1be01d9f4ce3af2476dd230084e065b268aa770 /docs
parent'./make clean' should remove generated .cpp files too (diff)
downloadanduril-0d515d67a0048094e2aba1cd2e4c131d57883dfe.tar.gz
anduril-0d515d67a0048094e2aba1cd2e4c131d57883dfe.tar.bz2
anduril-0d515d67a0048094e2aba1cd2e4c131d57883dfe.zip
added docs/which-hex-file.md to answer the #1 FAQ
Diffstat (limited to 'docs')
-rw-r--r--docs/which-hex-file.md39
1 files changed, 39 insertions, 0 deletions
diff --git a/docs/which-hex-file.md b/docs/which-hex-file.md
new file mode 100644
index 0000000..380cff9
--- /dev/null
+++ b/docs/which-hex-file.md
@@ -0,0 +1,39 @@
+# How to figure out which .hex file to use
+
+1. Use the version check function (15 or more clicks from Off) to find out
+ which flavor of the firmware the light has installed. WRITE THIS DOWN.
+
+2. Look up the model number in the MODELS file, to get the name and MCU type:
+ https://toykeeper.net/torches/fsm/anduril2/MODELS
+
+3. Find the newest firmware for that model.
+ https://toykeeper.net/torches/fsm/anduril2/?C=M;O=D
+
+If the version doesn't include a model number, you may be able to find
+the model in the PRODUCTS file to see which version it probably uses:
+
+ https://bazaar.launchpad.net/~toykeeper/flashlight-firmware/anduril2/view/head:/PRODUCTS
+
+
+## Version Check Formats
+
+The Version Check function should blink out a series of numbers in one of
+several formats:
+
+ - NNNN-YYYY-MM-DD
+ Anduril 2 from 2023-05 or later.
+ It's a model number and build date,
+ with "buzz" flashes between sections.
+ NNNN: model number
+ YYYY: year
+ MM: month
+ DD: day
+
+ - YYYYMMDDNNNN
+ Anduril 2 from 2023-05 or earlier.
+ It's a build date and model number.
+
+ - YYYYMMDD
+ This is an old Anduril 1 version. It's just a build date.
+ If the model name isn't obvious, try looking it up in the PRODUCTS file.
+