Avoid legacy OTA proof collisions
This commit is contained in:
1 parent
dc4a8808c0
commit
610eef7529
7 files changed
+136
-19
No files matched your search
+19
-2
@@ -240,7 +240,19 @@ check fails.
|
||||
|
||||
### 1. Start the temporary OTA channel
|
||||
|
||||
On the source node, destination node, and every intermediate repeater, run:
|
||||
First save the current `ota config` output. For a direct source-to-destination link, set both OTA-enabled
|
||||
endpoints to direct-only mode before starting the transfer:
|
||||
|
||||
```text
|
||||
ota config hops 0
|
||||
```
|
||||
|
||||
Do not use `hops 1` as extra margin on a direct link. It tells a receiving repeater to retransmit each direct
|
||||
DATA/PROOF packet; that unnecessary half-duplex transmission can make it miss the source's next fragment,
|
||||
especially with older single-block receivers. Use `hops 1` only when one real intermediate relay is required,
|
||||
`hops 2` for two, and so on. This setting is saved, so restore the original value after the maintenance window.
|
||||
|
||||
On the source node, destination node, and every intermediate repeater, then run:
|
||||
|
||||
```text
|
||||
tempradio 909.950,250,5,5,120
|
||||
@@ -295,6 +307,10 @@ Monitor the transfer:
|
||||
ota status
|
||||
```
|
||||
|
||||
For a powered bench update where restart-resume is not needed, `ota config checkpoint 0` on the destination
|
||||
removes periodic progress writes. It is a smaller optimization than selecting the correct hop count and it
|
||||
trades away persisted mid-download resume; restore the previous checkpoint cadence afterward.
|
||||
|
||||
The update is ready when the status says `ready to install`. Discovery is background traffic, while an
|
||||
active OTA download is primary mesh traffic. At the temporary-radio settings in this guide, allow roughly
|
||||
**one hour** for a typical ESP32 full image over a quiet, direct link. That is a planning estimate, not an
|
||||
@@ -340,7 +356,8 @@ ota status
|
||||
- **nRF52 reports a base mismatch:** the file passed to `--base` is not the exact application running on
|
||||
the destination. Rebuild the delta from the correct saved `firmware.hex`.
|
||||
- **The download stalls:** check the source, destination, and intermediate repeaters. Restart matching,
|
||||
overlapping temporary-radio windows if one expired.
|
||||
overlapping temporary-radio windows if one expired. On a direct link, also require `ota config hops 0`;
|
||||
a larger reach makes a repeater destination unnecessarily echo source packets.
|
||||
- **The serial port is busy:** close the serial terminal before starting `motatool serve`.
|
||||
- **The destination rejects the package:** verify the source files, their `EndF` trailers, the package's
|
||||
target/hardware identity, and the result of `motatool verify`.
|
||||
|
||||
+14
-7
@@ -519,10 +519,14 @@ OTA_LEAVES: manifest_id[4] frag_idx(1) frag_total(1) bytes[] # up
|
||||
reassembly bitmap (<=16 fragments/block; 1 KB blocks = 7). `OTA_PROOF` is a single packet and needs no mask.
|
||||
- **Data and proof remain separate packets, without a normal extra round trip.** A server retains requested
|
||||
blocks in a bounded descriptor queue, admits at most one response per main-loop pass, and sends one
|
||||
`OTA_PROOF` after each block's requested fragments. The receiver uses an airtime/path-aware proof grace
|
||||
(never less than 500 ms) and defers `OTA_REQ_PROOF` while any flight slot still expects DATA. Thus a missing
|
||||
early proof cannot make the receiver transmit into the rest of a legitimate half-duplex response train.
|
||||
After the complete-flight deadline, only one slot's missing fragments/proof is requested at a time.
|
||||
`OTA_PROOF` after each block's requested fragments. Before admitting that proactive proof, the source leaves
|
||||
an airtime/duty-aware 100-3000 ms RX turnaround gap. It accounts for one active transmission plus the two
|
||||
paced-response queue credits. A legacy receiver uses the gap to send its immediate
|
||||
`OTA_REQ_PROOF`; receiving that explicit request bypasses the remaining gap, avoiding a proof/request
|
||||
collision and an otherwise multi-second legacy retry. A newer receiver uses an airtime/path-aware proof
|
||||
grace (never less than 500 ms) and defers `OTA_REQ_PROOF` while any flight slot still expects DATA. Thus a
|
||||
missing early proof cannot make the receiver transmit into the rest of a legitimate half-duplex response
|
||||
train. After the complete-flight deadline, only one slot's missing fragments/proof is requested at a time.
|
||||
|
||||
### 8.5 Sizing against `MAX_PACKET_PAYLOAD = 184`
|
||||
|
||||
@@ -674,9 +678,12 @@ Manifest fragments are retained as bounded response jobs and admitted one at
|
||||
a time. Their source-side gap follows the active maximum packet airtime and
|
||||
dispatcher duty spacing, clamped to 100-1000 ms. The 100 ms floor protects
|
||||
fast radios' TX-to-RX turnaround; the cap keeps the receiver's one-second
|
||||
manifest progress/retry observation responsive. Relay collision delay is a
|
||||
separate setting: active OTA floods honor the relay role's configured
|
||||
`txdelay`, and the deployment runner temporarily uses `0.3` on managed relays.
|
||||
manifest progress/retry observation responsive. The source uses the same
|
||||
radio-aware 100-3000 ms drain/turnaround gap before an unsolicited block proof,
|
||||
but immediately serves a
|
||||
legacy receiver's explicit `OTA_REQ_PROOF`. Relay collision delay is a separate
|
||||
setting: active OTA floods honor the relay role's configured `txdelay`, and the
|
||||
deployment runner temporarily uses `0.3` on managed relays.
|
||||
|
||||
**What to plug into `--serial`.** Use the USB serial console of an OTA-enabled MeshCore node built with
|
||||
`OTA_FOLDER_SERIAL`. The node must have a working LoRa radio plus an
|
||||
|
||||
@@ -118,7 +118,7 @@ python3 tools/lora_ota/rak3401_mota_chain.py \
|
||||
--source-shares-controller \
|
||||
--target-key 63d8df63 \
|
||||
--temp-radio 909.950,500,5,5,120 \
|
||||
--ota-hops 1 \
|
||||
--ota-hops 0 \
|
||||
--motatool /path/to/motatool \
|
||||
--yes
|
||||
```
|
||||
@@ -179,7 +179,7 @@ after every bridge reboot:
|
||||
powersaving off
|
||||
set radio.rxps off
|
||||
set rxdelay 0
|
||||
ota config hops 1
|
||||
ota config hops 0
|
||||
tempradio 909.950,500,5,5,120
|
||||
```
|
||||
|
||||
@@ -187,7 +187,10 @@ tempradio 909.950,500,5,5,120
|
||||
failure. The actual source failure was an oversized USB CDC reply; current
|
||||
firmware splits those reads. Some historical bridge builds may report RXPS as
|
||||
unsupported while already operating continuously. Verify the reported state
|
||||
and do not substitute a normal reboot for the one-time watchdog reset.
|
||||
and do not substitute a normal reboot for the one-time watchdog reset. Direct
|
||||
tests use `hops 0`: `hops 1` makes the target echo each source response despite
|
||||
there being no intermediate relay, increasing half-duplex loss and legacy
|
||||
three-second retries.
|
||||
|
||||
Put the source on the identical TempRadio tuple. If it is a binary-mode Full
|
||||
Companion, the current `motatool` can switch modes for the serving session:
|
||||
|
||||
Reference in new issue
Block a user