docs: sync help/README with the Push commands, Parser and picker UI (v3.5.0)
- README/RUS: the Remote APDU tab has six sub-tabs, not seven; the GP connection-parameter table listed the wrong TLV tags (02/80/01) - it now matches the UI presets (82 Device Identities, 05 Alpha, 81 Command details, 35 Bearer, 03 = default bearer). The Push commands intro names the mode-specific rows (SD params tag in Store, Command Scripting template in Trigger) and the RU text uses the RU sub-pill labels; both READMEs gain the PoR advice bullet (Stepping Stones R7 18.6.3: no PoR on success, on failure SMS-SUBMIT + SPI2 0x20). - help RU: the C-APDU parser section names the Parser pill sub-pills like the EN one; the Push commands intro describes what the mode actually switches and uses the RU sub-pill labels. - sw cache -> simple-v252 (help pages are precached). Docs only; no functional change, version stays 3.5.0.
This commit is contained in:
+1
-1
@@ -230,7 +230,7 @@
|
||||
<p class="text-sm mb-3">Pastes raw APDU hex and renders a collapsible tree. It auto-detects the container: an <strong>Expanded Script</strong> (leading <code class="font-mono text-sm">AA</code> or <code class="font-mono text-sm">AE80</code>, decoded per ETSI TS 102 226 §5.2.1) or a <strong>Compact C-APDU chain</strong> (a sequence of ISO 7816 C-APDUs). Each node shows its label, hex and a short description; parent nodes expand to reveal their sub-elements. The <strong>C-APDU Parser</strong> and <strong>R-APDU parser</strong> are the two sub-pills of the <strong>Parser</strong> pill.</p>
|
||||
|
||||
<h3 id="push-commands" class="text-lg font-medium mb-2">2.7 Push commands</h3>
|
||||
<p class="text-sm mb-3">Groups the commands that make the card dial out. Three sub-pills switch between the forms — <strong>HTTP OTA Trigger (Push SMS)</strong>, <strong>HTTP OTA Store (SD admin params)</strong> and <strong>Channel / link trigger</strong> — and only the selected form is shown; the two GP forms share one set of fields (the mode only changes how the payload is wrapped, and the form heading says which one). They come from different specs and are delivered differently: the administration trigger is a TLV message for the Security Domain (HTTP OTA), a §9 PUSH is a C-APDU (<code class="font-mono text-sm">80 EC 01 P2</code>) for an application that supports BIP and/or CAT_TP.</p>
|
||||
<p class="text-sm mb-3">Groups the commands that make the card dial out. Three sub-pills switch between the forms — <strong>HTTP OTA Trigger (Push SMS)</strong>, <strong>HTTP OTA Store (SD admin params)</strong> and <strong>Channel / link trigger</strong> — and only the selected form is shown; the two GP forms share one set of fields — the selected mode switches the form heading and its mode-specific rows (the SD params tag in Store, the Command Scripting template in Trigger) and wraps the payload accordingly. They come from different specs and are delivered differently: the administration trigger is a TLV message for the Security Domain (HTTP OTA), a §9 PUSH is a C-APDU (<code class="font-mono text-sm">80 EC 01 P2</code>) for an application that supports BIP and/or CAT_TP.</p>
|
||||
|
||||
<h4 id="http-ota" class="font-medium mb-1">Administration session (HTTP OTA)</h4>
|
||||
<p class="text-sm mb-3">Builds the Remote Application Management over HTTP payloads defined in GlobalPlatform <strong>GPC v2.2 Amendment B v1.1</strong> (§4.7). Two modes:</p>
|
||||
|
||||
Reference in New Issue
Block a user