- 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
- Neural Processing UnitsNeural Processing Units
- 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
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Translated Content
- :
- Multi Source Translation Content
- :
- 2079362_zh-CN
2079362_zh-CN
2079362_zh-CN
2079362_zh-CN
我正准备使用带有 Linux 的 i.MX 8M Plus 片上系统 (SoC) 启动我的定制板。为了实现这一点，我创建了一个元层并建立了一个基于现有 imx8mp-lpddr4-evk.conf 的 custom-machine.conf 文件。此外，我修改了 u-boot-imx_2024.04.bbappend 文件中的 SRC_URI 变量，使其指向我的 GitHub 存储库，其中包含基于原始 u-boot-imx 修改后的 U-Boot 源代码。
在验证新机器和 U-Boot 是否正常运行的初始阶段，我复制或修改了与 i.MX 8MP EVK 相关的文件，并做了最少的改动。我主要更改了电路板名称、地址和其他必要的详细信息，以测试其在 i.MX 8MP EVK 上的运行。您可以在此处查看所有修改。
只要不对从 imx8mp_evk_defconfig 复制的 custom_board_defconfig 文件进行任何修改，我就可以在评估套件 (EVK) 上成功启动 U-Boot。但是，当我尝试仅更改设备树名称时，U-Boot 无法在 EVK 上启动，并且串行控制台上没有输出。
具体变化如下：
- CONFIG_DEFAULT_DEVICE_TREE ：从“imx8mp-evk”更改为“imx8mp-ifs”
- CONFIG_DEFAULT_FDT_FILE ：从“imx8mp-evk.dtb”更改为“imx8mp-ifs.dtb”
你好，
请将 arch/arm/dts/imx8mp-evk-u-boot.dtsi 复制到 arch/arm/dts/imx8mp-ifs-u-boot.dtsi，然后重试。
此致，
志明
无评分