status = "ok" is not one of the five values in the Devicetree Specification v0.4
(okay, disabled, reserved, fail, fail-sss).
dtc has no opinion about it - it is just a string. Zephyr marks the node present only for the exact
value okay, so the sensor quietly leaves the build and you debug the driver instead of the line.
23 rules, 50 snippets. This page runs the same 23 rules the extension runs, in your browser, on nothing you upload.
Everything above is free and needs no key, no account and no network - every one of the 23 rules and all 50 snippets run on the file you have open, for as long as you like. The licence buys scale, a file you can hand over, and repetition:
One-time, $29. A freelance embedded software engineer bills about $103 an hour (contractrates.fyi, 2026); a staff embedded firmware engineer's hour averages $58.66 (ZipRecruiter, June 2026). 7-day refund, no questions. Works offline; the key is checked once, then every 7 days.
It reads a config file line by line and reports the spellings that parse but do not mean what you
wrote - status = "ok", a compatible with no comma, address-cells
without the #, an unquoted TOML edition. 23 rules over seven languages, plus
50 snippets. No toolchain, no build context, no network.
They highlight and complete, and inside a configured Zephyr or nRF context they resolve bindings -
that part they do better than this pack. They do not grade a bare .overlay pasted out of a
vendor forum, and they say nothing about the TOML, .properties, .ahk,
.rpy or .ink files sitting in the same repo.
Because enabled is the English word and every other config format in the repo uses it.
Devicetree does not: the value that turns a node on is okay and nothing else. It is the exact
shape of mistake that reads correct and builds clean.