From 0e06b918a76ec430076cb1f471f069a303bab6b0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=90=D0=BD=D1=82=D0=BE=D0=BD=20=D0=A2=D1=80=D0=BE=D1=88?= =?UTF-8?q?=D0=B8=D0=BD?= Date: Mon, 5 Oct 2026 00:14:32 +0300 Subject: [PATCH] docs: a scripted RFM SELECT should use P2=0C (guide note) The alfa-dsa RFM script work showed a card refusing the P2='00' (FCI) form of a SELECT inside a secured command script with 6A86, while P2='0C' (no response data) executes - and a script has nowhere to put an FCI anyway. Worksheet 1 gains the note (TS 102 226 7.2: the RFM application starts in MF); the repo AGENTS records the observation. Docs only - no code, no version or sw change. --- docs/test-scripts.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/test-scripts.md b/docs/test-scripts.md index 3c11733..d61a7ab 100644 --- a/docs/test-scripts.md +++ b/docs/test-scripts.md @@ -90,6 +90,12 @@ passes an explicit `spi1`; an expanded-format RFM application also expects the wrapped command template (`"format": "expanded"`/`"expanded-ae"`, see the actions table). +A **scripted SELECT inside the secured packet** should ask for no response +data (`P2='0C'`, e.g. `00A4000C02A153`): a card can refuse the `P2='00'` +form (return the FCI) with `6A86` when it arrives inside a command script, +and the script has nowhere to put an FCI anyway. The RFM application starts +in MF (TS 102 226 §7.2), so the selects walk from there. + ### Worksheet 2 - incoming data → particular PoR, no other actions Inline PoR: