Tool · Device tree anatomy
This is what is actually inside a .dtb.
A device tree is the file that tells the kernel what hardware it is standing on: which pins are wired to what, how the screen wants its signal, where the WiFi module gets its power. It is a binary, and nobody reads a binary — so here is one, opened up.
Drop your own file, or start from four real ones. Everything is parsed in your browser.
Drop your .dtb here
Or start from one of the four real files below. Everything is read in the browser; nothing is uploaded or written.
Game Console R35S/R36S fix by lcdyk
rk3326-..ux.dtb, a forum build · 88.1 KB · 467 nodes · md5 30cd03ac7844be2aa3f67ad395b60656
rockchip,rk3326-odroidgo3-linux · rockchip,rk3326
Fingerprint table: this file is not listed
A corrected R36S tree of unknown provenance. Its model string signs it "fix by lcdyk".
Panel
- Resolution
- 640 × 480
- Pixel clock
- 29.000 MHz
- Refresh
- 59.94 Hz
- Init sequence
- 773 bytes
- Reset pin
- GPIO3 pin 16 (active high)
- Enable pin
- not declared
732 pixel clocks per line, 661 lines per frame → 59.94 Hz. Same resolution, different refresh: the difference is entirely these gaps.
Pins
muxed to a bus (SDIO) driven as a GPIO both
- GPIO1·22 sdio-bus4 — function 1
- GPIO1·23 sdio-bus4 — function 1
- GPIO1·24 sdio-bus4 — function 1
- GPIO1·25 sdio-bus4 — function 1
- GPIO0·3 cd · dwmmc@ff370000
- GPIO3·14 cd · dwmmc@ff380000
- GPIO3·16 reset · panel@0
- GPIO3·11 amux-a · odroidgo3-joypad
- GPIO3·8 amux-b · odroidgo3-joypad
- GPIO3·13 amux-en · odroidgo3-joypad
- GPIO2·22 simple-audio-card,hp-det · rk817-sound
WiFi power
- Regulator
- vcc_wifi
- Always on
- yes (regulator-always-on)
- In suspend
- has a suspend state
Keys and audio
- button@0
- code 115 · GPIO2 pin 0 (active high)
- button@1
- code 114 · GPIO2 pin 1 (active high)
- Volume step
- 3
- Headphone detect
- GPIO2 pin 22 (active high)
| Field | rf3536k3ka | r36sFix | r50s | uboot |
|---|---|---|---|---|
| model string | Rockchip rk3326 evb lpddr3 v12 board for linux≠ | Game Console R35S/R36S fix by lcdyk≠ | GameConsole R40S≠ | Arkos4Clone GameConsole R50S≠ |
| Resolution | 640×480≠ | 640×480≠ | 480×800≠ | 480×800≠ |
| Refresh | 58.5 Hz≠ | 59.94 Hz≠ | 60.01 Hz≠ | 63.42 Hz≠ |
| Pixel clock | 30.000 MHz≠ | 29.000 MHz≠ | 30.000 MHz≠ | 30.000 MHz≠ |
| Init sequence | 370 bytes≠ | 773 bytes≠ | 164 bytes≠ | 164 bytes≠ |
| Reset pin | GPIO3 pin 27 (active high)≠ | GPIO3 pin 16 (active high)≠ | GPIO3 pin 16 (active high)≠ | GPIO3 pin 16 (active high)≠ |
| WiFi always on | not declared≠ | yes≠ | not declared≠ | yes≠ |
| WiFi pins | 1·22 1·23 1·24 1·25 | 1·22 1·23 1·24 1·25 | 1·22 1·23 1·24 1·25 | 1·22 1·23 1·24 1·25 |
| Control pins | 16≠ | 7≠ | 8≠ | 3≠ |
| Nodes | 547≠ | 467≠ | 465≠ | 451≠ |
What you are looking at
A .dtb is the compiled form of a text file written by whoever designed the board. The b is for blob, and that is the whole idea: the kernel reads a flat, uncompressed block of nodes and properties at boot, with no interpretation and no probing. If a node is wrong or missing, the hardware it describes simply does not come up — usually with no error anywhere.
The four samples show what that means in practice. They are four genuine files from community flashing packs, not illustrations. Two of them carry a model string naming an R36S, and they still disagree about the display: identical 640×480 panel, identical pixel clock, different blanking intervals, and therefore a different refresh rate. A third is from an R40S and describes a portrait 480×800 panel — a completely different display in a file with almost the same name.
How to read the pin map
An RK3326 exposes its general-purpose pins in banks of 32, numbered GPIO0 to GPIO4. Each pin can do one thing at a time: carry a bus signal, act as a plain on/off line, or sit idle. The map above fills a cell for every pin the file assigns, in one of two colours — a pin handed to a bus controller (the WiFi SDIO lines, for instance) or a pin the kernel is told to drive as a GPIO. Hover any filled cell to see what it is for.
The detail that matters most when a peripheral misbehaves is that a pin can only hold one assignment. If two things in a design want the same pin, the tree can describe only one of them, and the other either fights for it or never works. That is a hardware fact the file has to live with, not something a better file can fix.
What this cannot tell you
It does not identify your board. The identifier does that, by hashing the file against a community table. This page only reads the file you hand it, so a tree nobody has ever catalogued prints exactly as well as a known one — and a value the file does not declare is shown as not declared rather than filled in from a similar board.
It also cannot tell you whether the file is correct for your unit. A tree that describes the wrong panel parses perfectly. The numbers here are what the file claims; the screen is what decides whether those claims are true.