- 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
- :
- 2301158_en-US
2301158_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2301158_en-US
2301158_en-US
Hi Team,
I have built the NXP T2080 SDK by following the instructions in the NXP documentation:
https://docs.nxp.com/bundle/GUID-39A0A446-70E5-4ED7-A580-E7508B61A5F1/page/GUID-D2622091-1637-4D51-9...
The build completes successfully. Now, I want to boot QEMU using the binaries generated from this build.
Could someone please suggest the correct way to boot QEMU using the binaries built from the NXP T2080 SDK?
Thanks in advance for your help.
1. Please refer to section "11.2.5.6.1.2 Deploy KVM using fsl-image-core Image" in the SDK 2.0 1703 user manual to build Linux Kernel image with KVM supported and build rootfs filesystem with qemu included.
2. Please login host Linux OS and config ethernet 192.168.1.xx.
Please get guest images as the following.
Guest kernel image (/boot/uImage)
Guest root filesystem (/home/root/guest.rootfs.ext2.gz)
QEMU (/usr/bin/qemu-system-ppc or qemu-system-ppc64)
3. In host Linux, please setup guest OS with the following command.
$ qemu-system-ppc64 -h
$ qemu-system-ppc64 -enable-kvm -m 512 -nographic -M ppce500 -kernel uImage -initrd rootfs.ext2.gz -append "root=/dev/ram rw console=ttyS0,115200" -serial tcp::4444,server,telnet -net nic -S
after guest bootuping, you can quit qemu monitor by input 'q' letter.
4. on guest console:
telnet 192.168.1.xxx 4444
5. on host qemu , see upper , input 'c' to continue guest booting.
startup guest booting.