- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
-
- NXP Tech Blogs
- Home
- :
- i.MX Forums
- :
- i.MX Processors
- :
- How to build device tree changes?
How to build device tree changes?
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
IMX8M Nano
Yocto build setup from NXP
I want to build a modified device tree for the imx8m nano. I understand the syntax of device tree source files (.dts, dtsi), but I don't know how to get the yocto build to update the DTB: imx8mn-evk.dtb.
I modified imx8mn-evk.dts and built, but my changes do not seem to affect the build. As a test I simply typed garbage into the file and even renamed the file. I expected the build to fail, but no it doesn't. Thing is there's many copies of this file in my build tree. I picked the one under nano/tmp/work-shared/imx8mn-lpddr4-evk/kernel-source/arch/arm64/boot/dts/freescale/ where nano is my build dir. I realize that the files under tmp are only quasi-source files. They come from somewhere else. Maybe modifying them under tmp does not automatically cause the build to see the change. Or I have modified the wrong copy of the file. Or I selected the wrong target to build. I did "bitbake core-image-minimal" thinking that would be good.
IDK whether this is a general yocto issue or something particular to the IMX yocto build. FYI Yocto makes little sense to me in general.
How do I get the yocto build to build changes to the device tree?
Solved! Go to Solution.
Chavira
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @chillinwithscb!
Thank you for contacting NXP Support!
You can follow the next posts to solve the problem.
Best Regards!
Chavira
Chavira
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @chillinwithscb!
Thank you for contacting NXP Support!
You can follow the next posts to solve the problem.
Best Regards!
Chavira
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The info in the link How-to-compile-Linux-Kernel-Image-and-device-tree-using-Yocto is good. I actually had already found that info in NXP docs. But it's spread across two docs. The linked article is a more concise and direct description of the steps.
That said, it was not clear to me from the NXP docs or the article _why_ I'd want to use a standalone build or why it so very complicated to setup. But, I see the value of the standalone build now. And I was able to build an updated DTB.
Thanks.
