- 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
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- Wireless Connectivity
- 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
-
- 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
- MCUXpresso Training Hub
-
- 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
-
- Home
- :
- QorIQ Processing Platforms
- :
- QorIQ
- :
- Re: Anyone tried to run u-boot under qemu-system-ppc64 on a T1040RDB?
Anyone tried to run u-boot under qemu-system-ppc64 on a T1040RDB?
- 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
The Freescale 1.7SDK (yes, I have not yet made the jump to 1.8) has the u-boot-qoriq_2014.07.bb recipe.
Within the u-boot source tree, there is a machine/board target of qemu-ppce500, which appears to be the target to use under qemu/KVM for PowerPC. However, when trying to start a KVM instance with the resulting u-boot image, it appears to immediately freeze/stop. So I am wondering if anyone has already accomplished this.
Notes:
I have tried the following:
qemu-system-ppc64 -enable-kvm -M ppce500 -nographic -bios u-boot.bin
qemu-system-ppc64 -enable-kvm -M ppce500 -nographic -pflash u-boot.bin
qemu-system-ppc64 -enable-kvm -M ppce500 -nographic -kernel u-boot.elf
The last line, with the -kernel, is (attempting) to boot the ELF format image of the u-boot binary. The reason for this was I was attempting to connect a remote instance of GDB to QEMU to debug what was happening, and GDB did not like the non-ELF formats.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My intention in running u-boot was that I wanted to have, within the virtual machine instance, a boot loader that could choose between one of two different images/kernels to boot - a primary and backup. The backup would be booted if an upgrade or configuration of the primary failed. The goal had been to use u-boot to handle the decision making.
However, since booting u-boot in QEMU/KVM does not appear to be supported under the t1040rdb at the moment, I used an alternative solution.
The virtual machine boots into a first-stage initial RAM disk with its own kernel. Within that RAM disk, a script determines which image should be booted next, then a kexec call is used to boot the target kernel/image. This gets around the lack of u-boot support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My intention in running u-boot was that I wanted to have, within the virtual machine instance, a boot loader that could choose between one of two different images/kernels to boot - a primary and backup. The backup would be booted if an upgrade or configuration of the primary failed. The goal had been to use u-boot to handle the decision making.
However, since booting u-boot in QEMU/KVM does not appear to be supported under the t1040rdb at the moment, I used an alternative solution.
The virtual machine boots into a first-stage initial RAM disk with its own kernel. Within that RAM disk, a script determines which image should be booted next, then a kexec call is used to boot the target kernel/image. This gets around the lack of u-boot support.
scottwood
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I believe you're supposed to use the -bios option to run U-Boot in QEMU -- but it's possible that the QEMU in the SDK is too old. Running U-Boot in QEMU is a feature that was added upstream; it's not a supported SDK feature AFAIK. Try downloading the latest upstream QEMU.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you. Trying the latest QEMU gets me closer.
The default 'u-boot.e500' image which is packaged with QEMU will not load, but an ELF format u-boot binary built out of the SDK will load - but only as long as I do not have '-enable-kvm' added.
I will continue to investigate.
