Home

Welcome to the qemu wiki! or one of many branches of the master.

I'm going to try to keep this up to date with the master, keep Raspberry PI working, and keep the windows build going.

Currently the PI2 works but not the 1.

Some of my tools for build and running have crept in as well. If you want to building windows you'll need cygwin with a full set of tools.

The shell scripts are setup to build for 64bit windows.

One of the objectives was to mange seamless development of low level code in an IDE. I have managed this with Netbeans. It is not quite as smooth as I would like but it works.

First set up the run command like so

C:\cygwin64\home\John-Bradley\qemu-main\bin\debug\x86_64-w64-mingw64\arm-softmmu\qemu-system-arm.exe -machine raspi2 -smp 1 -bios C:\cygwin64\home\John-Bradley\circle\sample\03-screentext\kernel7.img -usbdevice keyboard -s -S

You may need to set the working directory to the QEMU directory.

Then attach debugger.

selecting

Debugger: gdbserver

Target: remote tcp::1234

Project: 03-screentext

A video of a demo running a modified version of Circle's GPIO demo, to show output and input https://www.youtube.com/watch?v=qGhURwTTUSA&feature=youtu.be this is a version running on Linux. https://www.youtube.com/watch?v=-dbyGP2sY6U others https://www.youtube.com/playlist?list=PLc0ox62iQmOLaHEo7RycpCF-D6kzNPBfN

Firstly, I run the DummyPanel, then start QEMU with the SimpleGPIO app, it pauses to see if I want connect debug. In this case I don't so I unpause. The initial connection is made before the pause as part of QEMUs internal setup of the PI emulator. If the Panel is not running there is no problem but also no I/O. If QEMU is stopped the connection breaks and will be remade if QEMU is restarted.

The First 1/4 of IO set to Output Next 1/4 to input and the rest ignored the Flash at 47 is the onboard LED.

The Quality of the code in GDummyPanel.cc is about -1. See https://github.com/flypie/GDummyPanel