From 99d7b02957a3ec0d8443b47c15d703f235f1413d Mon Sep 17 00:00:00 2001 From: Tom Harkness Date: Wed, 7 Oct 2026 08:23:38 +1100 Subject: [PATCH] doc: update PM5-FLIPPER-USAGE.md to current CEP state RF over CEP works now that the FPGA bitstream step is done - it was never actually CEP-blocked. Note CMD_CEP_STATUS (Hardware Status dashboard) and the real open bug (Read Hitag2 over CEP fails with stale cached data, firmware-side). SPI bit-order/phase is confirmed, not pending. Co-Authored-By: Claude Sonnet 5 --- doc/md/PM5_Start_Here/PM5-FLIPPER-USAGE.md | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/doc/md/PM5_Start_Here/PM5-FLIPPER-USAGE.md b/doc/md/PM5_Start_Here/PM5-FLIPPER-USAGE.md index aaa7f1992..f8801f7de 100644 --- a/doc/md/PM5_Start_Here/PM5-FLIPPER-USAGE.md +++ b/doc/md/PM5_Start_Here/PM5-FLIPPER-USAGE.md @@ -36,15 +36,19 @@ Build as usual, CEP is available by default. (`SKIP_CEP=1` to remove CEP support ## What works today - The FAP handshake completing (app leaves "connecting"). -- Standard commands that don't touch the antenna frontend — `hw - version`, `hw status`, memory/flash operations, etc. +- Standard commands — `hw version`, `hw status`, memory/flash operations, + `CMD_CEP_STATUS` (compact binary snapshot: CEP link state, BWM battery, + firmware version — feeds the FAP's Hardware Status dashboard). +- `hf`/`lf` reads in general, same as over USB, once the device's one-time + FPGA bitstream step is done (see `Getting_Started_With_PM5.md`) — CEP + itself doesn't block RF. ## What doesn't (yet) -- Any RF operation over this link — `hf`/`lf` reads, the FAP's "Read Hitag2" - menu item. These need the real PM5 FPGA/RF configuration, which isn't - shipped in this repo. Tracked separately, out of scope for the CEP - transport itself. +- The FAP's "Read Hitag2" menu item specifically. Every attempt over CEP + replies `PM3_EFAILED` with stale cached UID data, even though the same + reader succeeds moments later over plain USB against the same tag. + Firmware-side, root cause open, out of scope for the CEP transport itself. --- @@ -64,7 +68,5 @@ Build as usual, CEP is available by default. (`SKIP_CEP=1` to remove CEP support ## Notes - CEP uses its own reply-routing flag (`g_reply_via_cep`). -- The SPI bit-order/clock-phase settings are a best-effort port from prior - bring-up code, pending confirmation against real Flipper traffic (logic - analyzer). If the handshake never completes, this is the first thing to - check. +- SPI bit-order/clock-phase settings are confirmed correct against real + Flipper traffic (logic analyzer): MSB-first, mode 0, CS active-low.