The recommended method is via xpm.

Overview

The xPack QEMU Arm can be installed automatically, via xpm (the recommended method), or manually, by downloading and unpacking one of the portable archives.

Easy install

The easiest way to install QEMU is by using the binary xPack, available as @xpack-dev-tools/qemu from the npmjs.com registry.

Prerequisites

The only requirement is a recent xpm, which is a portable Node.js command line application. To install it, follow the instructions from the xpm install page.

Install

With xpm available, installing the latest version of the package is quite easy:

$ xpm install --global @xpack-dev-tools/qemu-arm@latest

This command will always install the latest available version, in the central xPacks repository, which is a platform dependent folder (check the output of the xpm command or the actual folder used on your platform).

xPacks aware tools, like the Eclipse Embedded CDT plug-ins automatically identify binaries installed with xpm and provide a convenient method to manage paths.

Uninstall

To remove the installed xPack, the command is similar:

$ xpm uninstall --global @xpack-dev-tools/qemu-arm

(Note: not yet implemented. As a temporary workaround, simply remove the xPacks/@xpack-dev-tools/qemu folder, or one of the versioned subfolders.)

Manual install

For all platforms, the xPack QEMU Arm binaries are released as portable archives that can be installed in any location.

The archives can be downloaded from the GitHub Releases page.

Download

The Windows versions of xPack QEMU Arm are packed as ZIP files. Download the latest version named like:

  • xpack-qemu-arm-2.8.0-7-win32-x64.zip
  • xpack-qemu-arm-2.8.0-7-win32-x32.zip

Select the -x64 file for 64-bit Windows machines and the -x32 file for 32-bit Windows machines.

Unpack

Unpack the archive and copy it into the %userprofile%\AppData\Roaming\xPacks\qemu-arm (for example C:\Users\ilg\AppData\Roaming\xPacks\qemu-arm) folder; according to Microsoft, AppData\Roaming is the recommended location for installing user specific packages.

To check if QEMU starts, use the following command:

C:\Users\ilg>C:\Users\ilg\AppData\Roaming\xPacks\qemu-arm\xpack-qemu-arm-2.8.0-7\bin\qemu-system-gnuarmeclipse.exe" --version
xPack 64-bit QEMU emulator version 2.8.0-7 (v2.8.0-7-20180523-6-gee07085299-dirty)
Copyright (c) 2003-2016 Fabrice Bellard and the QEMU Project developers

Drivers

For usual Cortex-M emulation, there are no special drivers required.

Download

The macOS version of xPack QEMU Arm is packed as a .tar.gz archive. Download the latest version named like:

  • xpack-qemu-arm-2.8.0-7-darwin-x64.tgz

Unpack

To install QEMU, unpack the archive and move it to /${HOME}/opt/xPacks/qemu-arm/xpack-qemu-arm-2.8.0-7:

$ mkdir -p ~/opt
$ cd ~/opt

$ tar xvf ~/Downloads/xpack-qemu-arm-2.8.0-7-darwin-x64.tgz
$ chmod -R -w xPacks/qemu-arm/xpack-qemu-arm-2.8.0-7

The result is a structure like:

$ tree -L 2 /Users/ilg/Library/xPacks/qemu-arm/xpack-qemu-arm-2.8.0-7
/Users/ilg/Library/xPacks/qemu-arm/xpack-qemu-arm-2.8.0-7/
├── README.md
├── bin
│   ├── libSDL2-2.0.0.dylib
│   ├── libSDL2_image-2.0.0.dylib
│   ├── libgcc_s.1.dylib
│   ├── libglib-2.0.0.dylib
│   ├── libgthread-2.0.0.dylib
│   ├── libiconv.2.dylib
│   ├── libintl.8.dylib
│   ├── libpixman-1.0.dylib
│   ├── libstdc++.6.dylib
│   ├── libz.1.2.11.dylib
│   ├── libz.1.dylib -> libz.1.2.11.dylib
│   └── qemu-system-gnuarmeclipse
├── distro-info
│   ├── CHANGELOG.md
│   ├── licenses
│   ├── patches
│   └── scripts
└── share
    ├── doc
    └── qemu

8 directories, 14 files

To check if QEMU starts, use:

$ ~/opt/xPacks/qemu-arm/xpack-qemu-arm-2.8.0-7/bin/qemu-system-gnuarmeclipse --version
xPack 64-bit QEMU emulator version 2.8.0-7 (v2.8.0-4-20190211-47-g109b69f49a-dirty)
Copyright (c) 2003-2016 Fabrice Bellard and the QEMU Project developers

Download

The GNU/Linux versions of xPack QEMU Arm are packed as plain archives. Download the latest version named like:

  • xpack-qemu-arm-2.8.0-7-linux-x64.tgz
  • xpack-qemu-arm-2.8.0-7-linux-x32.tgz

As the name implies, these are GNU/Linux tar.gz archives; they were build on CentOS, but can be executed on most recent GNU/Linux distributions. Select the -x64 file for 64-bit machines and the -x32 file for 32-bit machines.

Unpack

To install QEMU, unpack the archive and move it to /${HOME}/opt/xPacks/qemu-arm/xpack-qemu-arm-2.8.0-7:

$ mkdir -p ~/opt
$ cd ~/opt

$ tar xvf ~/Downloads/xpack-qemu-arm-2.8.0-7-linux-x64.tgz
$ chmod -R -w xPacks/qemu-arm/xpack-qemu-arm-2.8.0-7

The result is a structure like:

$ tree -L 2 '/home/ilg/opt/xPacks/qemu-arm/xpack-qemu-arm-2.8.0-7'
/home/ilg/opt/xPacks/qemu-arm/xpack-qemu-arm-2.8.0-7/
├── bin
│   ├── libglib-2.0.so.0 -> libglib-2.0.so.0.5600.4
│   ├── libglib-2.0.so.0.5600.4
│   ├── libgthread-2.0.so.0 -> libgthread-2.0.so.0.5600.4
│   ├── libgthread-2.0.so.0.5600.4
│   ├── libiconv.so.2 -> libiconv.so.2.6.0
│   ├── libiconv.so.2.6.0
│   ├── libjpeg.so.9 -> libjpeg.so.9.2.0
│   ├── libjpeg.so.9.2.0
│   ├── libpixman-1.so.0 -> libpixman-1.so.0.38.0
│   ├── libpixman-1.so.0.38.0
│   ├── libpng16.so.16 -> libpng16.so.16.36.0
│   ├── libpng16.so.16.36.0
│   ├── libSDL2-2.0.so.0 -> libSDL2-2.0.so.0.9.0
│   ├── libSDL2-2.0.so.0.9.0
│   ├── libSDL2_image-2.0.so.0 -> libSDL2_image-2.0.so.0.2.2
│   ├── libSDL2_image-2.0.so.0.2.2
│   ├── libz.so.1 -> libz.so.1.2.11
│   ├── libz.so.1.2.11
│   └── qemu-system-gnuarmeclipse
├── distro-info
│   ├── CHANGELOG.md
│   ├── licenses
│   ├── patches
│   └── scripts
├── libexec
├── README.md
└── share
    ├── doc
    └── qemu

9 directories, 21 files

To check if QEMU starts and is recent, use:

$ ~/opt/xPacks/qemu-arm/xpack-qemu-arm-2.8.0-7/bin/qemu-system-gnuarmeclipse --version
xPack 64-bit QEMU emulator version 2.8.0-7 (v2.8.0-4-20190211-47-g109b69f49a-dirty)
Copyright (c) 2003-2016 Fabrice Bellard and the QEMU Project developers

UDEV & Drivers

For usual Cortex-M emulation, there are no special UDEV definitions or drivers required.

Edit

Comments on the content of this page that might be useful for other readers are welcomed here. For question and general support, please use the project forums.