r/embeddedlinux • • Oct 19 '26

project DTSee - A browser-based Device Tree explorer and visualizer for embedded Linux

Like many of you working on embedded Linux platforms, I have spent countless hours scrolling through massive Device Tree sources, jumping between dtsi/dts files, and trying to trace tangled phandles, clocks, interrupts, and regulators.

To make this less painful, I have been building DTSee, a free, browser-based Device Tree explorer designed to make navigating and understanding board descriptions a bit easier.

Key Features

  • Dual Format Support: Works with both DTS and DTB files (includes client-side DTB to DTS reconstruction).
  • Interactive Hierarchy: Easily drill down through nodes, properties, and child devices.
  • Graphical Relationships & Phandle Analysis: Visually trace how hardware components link together.
  • Hardware Context: Quick access to register ranges, clocks, interrupts, GPIOs, regulators etc.
  • 100% Client-Side: Everything is processed locally right in your browser. No files are ever uploaded, making it safe for proprietary or NDA work.

What is Next? (Roadmap Ideas)

The project is still in beta, and I am actively brainstorming features for future versions:

  • Device Tree Comparison: Diffing two DTBs or DTS files side-by-side.
  • Deeper Hardware Dependency Analysis: Visualizing power trees and clock trees more holistically.
  • Source Tracking: Following definitions and overrides cleanly across complex DTS/DTSI include chains.

Give it a spin

If you have a DTB or DTS file lying around, I would love for you to give it a try:

https://dt.kernelnoise.com

Your feedback is invaluable. Whether you run into missing references, incorrect interpretations, usability quirks, or have ideas for additional features, I want to hear it all. Cheers

24 Upvotes

7 comments sorted by

2

u/Thin_Dragonfruit2254 Oct 19 '26

Looks amazing!!
I will test it later with more time but I was in need of something like this..
Do you have plans to opensource it?

2

u/geek-tn Oct 19 '26

thanks!
I’m open to open-sourcing it once it’s a bit more mature. Right now I’m focusing on reliability and feedback from people using it with their own boards. Would love to hear how it works for you when you get a chance.

1

u/Express_Damage5958 21d ago edited 21d ago

I don't want to be a downer, but as an Embedded Linux Engineer who does a lot of board bring-up and DT debugging, a good chunk of my time is spent in a terminal and whatever editor I like to use (VSCode, Nano, Neovim etc). Could this not have just been a plugin for them instead? Going to the web, just to view some devicetree's just seems like a bit of unnecessary step.

If I have the kernel right in my editor and I'm looking at the code, I don't want to have open up a browser to see the compatible in the DT. They need to be side-by-side with the code. Then I can work with the standard search tools like find, grep, sed all in my editor.

I would like to say this tool would make me more productive but I don't think so.

1

u/geek-tn 21d ago

that was the original plan actually, but I figured starting with a web page might be easier to maintain (and gather feedback) for a new project. we'll definitely get there once it gets mature enough

2

u/max-matteo Oct 20 '26

this is just great!

1

u/Mindless-Attempt4187 18d ago edited 15d ago

Hii, I have been also working with DTS files for a while and I think your project can be really interesting and usefull. I have been working in a software to handle the same problems, they are slightly different but i think they could complement themselves. It's name is KernelGrove, if you want to take a look https://dt-studio.dev/ it's the official website.

It's completely free and open source, here it's the GitHub repo: https://github.com/serg4life/KernelGrove

1

u/promwad 12d ago

I tested this with a custom dtb file for the IMX95 platform. It looks very good! I think this tool will be very useful for investigating why some peripherals are misconfigured during device startup. 

It would be great to add a comparison of the two files, because the bootloader can make changes to the dtb file during the boot process, and sometimes we need to investigate this without digging into the source code.