DeviceTree Visual Editor catch-22

[Dave Littell]

I'd like to use the DeviceTree Visual Editor to create the DTS for a custom board starting with only the bare device.  But it seems for some reason that the DeviceTree Visual Editor only works if it's hung off some build configuration for some app.  A build configuration must be created for that magical app which can't be created without a DTS, so some pre-existing dev kit board must  be used to get the app to get the build configuration to get the DeviceTree Visual Editor to work at all.  So now the clean, device-only DTS I wanted to start with is polluted with the dev kit DTS which was required to get the app to get the build configuration to get the DeviceTree Visual Editor to work...  Did I miss anything in this funhouse of frustration?  Does this strike anyone as "fundamentally conceptually broken"?

How can I use the DeviceTree Visual Editor starting with a bare device and not have that unnecessary app cluttering up the DTS which I then have to jump through hoops to clean up?

Thanks,

Dave

[AHaug]

Hello again!

As mentioned in  DTS file editing autocomplete, etc. there's quite a few resources that I would like to recommend in addition to https://docs.nordicsemi.com/bundle/nrf-connect-vscode/page/guides/work_with_devicetree_editor.html. I think https://docs.nordicsemi.com/bundle/nrf-connect-vscode/page/guides/work_with_devicetree_editor.html#how-to-access-the-devicetree-visual-editor should answer the question in this case.

Kind regards,
Andreas

[Dave Littell]

Thanks very much - I'll see if I can find the Golden Nugget!