docs: SB-LoRa rev 2 plan: running from the module's flash leaves the app's features intact (all data is in RAM databases); note the copy-to-RAM alternative

This commit is contained in:
rich committed 2026-11-09 13:30:49 -05:00
1 parent 62d22b59dc
commit 99b66a2cf9
1 file changed
+2 -1
+2 -1
View File
@@ -37,7 +37,8 @@ A 16-bit-wide 3.3 V NOR flash at the start of csSlot0 (CS0*), as the Springboard
- Candidate: SST39VF1601C (2 MB, x16, 70 ns, TSOP-48, 1.2 mm). Room for the app and the Map basemap.
- WE* is wired so the app can rewrite the flash itself: HotSync a new .prc to RAM, then update the module from the app.
- A write-protect jumper.
- Software: an app running from the module is read-only, so it must not write to its own resource database. To check before rev 2.
- Software: only the app's own code and resources are read-only when it runs from the module. Checked: all of its data (channels, contacts, messages, beam inbox, screenshots, map) is in RAM databases on card 0, and it never writes to its own database, so nothing changes. To keep the Map basemap in flash too, `map_form.c` must also look on card 1. The alarms (`bgcheck.c`, `sb_spi.c`) point at the app's database, and they go away with the module, which is fine because the radio does too.
- Alternative: a small Welcome app on the flash that copies VisorMesh into RAM when it's missing or older, so the app runs from RAM exactly as it does now.
This takes CS0*, so the radio link moves to csSlot1 (CS1*). The flash needs about 20 address lines and all 16 data lines, so rev 2 is expected to be a 4-layer board.