Repository navigation
Wizard: offer defib for a protected NOR chip only where its agent runs - #542
Conversation
The note under `sf lock 0` told every NOR install that defib's flash agent unlocks the chip over the serial console. defib has an agent for twenty HiSilicon and Goke chips (`_CHIP_TO_AGENT` in its agent/client.py), and none for Novatek, Ingenic, SigmaStar, Fullhan, Anyka or the rest, so an NT98566 owner was sent to a tool that cannot flash their camera (#537). Those chips now get lock_caveat_programmer_html, the same note ending on the external programmer alone. A catalogue row for a memory variant (HI3516CV610-DDR3-128M) counts as its chip. The golden changes for the 124 SoCs without an agent and no other: their documents name the new note. Fixes #537
PR Summary by QodoOffer defib only for NOR chips with a supported flash agent
AI Description
Diagram
High-Level Assessment
Files changed (10)
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can keep summaries lean with Findings visible per group, which tucks the rest behind a View link |
The note under
sf lock 0told every NOR install that defib's flash agentunlocks the chip over the serial console. defib has an agent for twenty
HiSilicon and Goke chips (
_CHIP_TO_AGENTin its agent/client.py), and nonefor Novatek, Ingenic, SigmaStar, Fullhan, Anyka or the rest, so an NT98566
owner was sent to a tool that cannot flash their camera (#537).
Those chips now get lock_caveat_programmer_html, the same note ending on the
external programmer alone. A catalogue row for a memory variant
(HI3516CV610-DDR3-128M) counts as its chip.
The golden changes for the 124 SoCs without an agent and no other: their
documents name the new note.
Fixes #537