#160 Error when launching QEMU debug from eclipse Luna

[Mohamed Galal El-Din]

I receive the following error when trying to launch a "GDB QEMU Debugging" session from Eclipse Luna (same error occurs with Mars). Attached is a screenshot of the error message.

Below are the details

full plug-in version: GNU ARM C/C++ QEMU Debugging 2.1.1.201508071246
Java version "1.7.0_79"
Eclipse version: ** 4.4.2.20150219-0708
CDT version: 8.6.0.201502131403
Platform: Ubuntu 15.04 64-bits
Toolchain: arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.9.3 20150529
any exceptions related to ilg.gnuarmeclipse**:

!ENTRY ilg.gnuarmeclipse.debug.gdbjtag 4 0 2015-08-09 08:27:20.614
!MESSAGE QEMU failed with code (127).

[Liviu Ionescu (ilg)]

did you properly set the path to qemu?

if so, could you start the program in a terminal with --version?

[Mohamed Galal El-Din]

I followed the steps in the http://gnuarmeclipse.livius.net/blog/ and used all the default paths as recommended.

/opt/gnuarmeclipse/qemu/2.3.50-201508041609-dev/bin$ ./qemu-system-gnuarmeclipse -board help
Supported boards:
Mapple LeafLab Arduino-style STM32 microcontroller board (r5)
NUCLEO-F103RB ST Nucleo Development Board for STM32 F1 series
NUCLEO-F411RE ST Nucleo Development Board for STM32 F4 series
NetduinoGo Netduino GoBus Development Board with STM32F4
NetduinoPlus2 Netduino Development Board with STM32F4
OLIMEXINO-STM32 Olimex Mapple (Arduino-like) Development Board
STM32-E407 Olimex Development Board for STM32F407ZGT6
STM32-H103 Olimex Header Board for STM32F103RBT6
STM32-P103 Olimex Prototype Board for STM32F103RBT6
STM32-P107 Olimex Prototype Board for STM32F107VCT6
STM32F4-Discovery ST Discovery kit for STM32F407/417 lines
STM32F4-Discovery2 ST Discovery kit for STM32F407/417 lines
STM32F429I-Discovery ST Discovery kit for STM32F429/439 lines
generic Generic Cortex-M board; use -mcu to define the device

I selected Mapple board to test with, and here is the result

/opt/gnuarmeclipse/qemu/2.3.50-201508041609-dev/bin$ ./qemu-system-gnuarmeclipse -board Mapple --image ~/workspace_luna/hello_cortex_m/Debug/hello_cortex_m.elf
Hello ARM World!
System clock: 8000000 Hz
Second 1
Second 2
Second 3
Second 4

So the application is working properly on the command line. Does this answer your question?

[Liviu Ionescu (ilg)]

seems ok.
Unfortunately I'm not in the office to further help you.

[Mohamed Galal El-Din]

Thanks for your help so far.

But with that said, is it correct to assume that the problem is in the interface between the QEMU Eclipse Plugin and the QEMU exe?

[Liviu Ionescu (ilg)]

That's correct. The first thing to check is QEMU path, then the launch configuration.

[Mohamed Galal El-Din]

Attached is a screenshot for the QEMU path (Eclipse preference).

[Mohamed Galal El-Din]

And this is a screenshot for the launch configuration

[Mohamed Galal El-Din]

I tried the same exact installation steps with all default paths unchanged on Windows 7 and it worked as expected. So my problem seems to be in Linux only (if that might help).

[Liviu Ionescu (ilg)]

could you try the steps described in http://gnuarmeclipse.livius.net/blog/blinky-project/ and let me know the result?

[Mohamed Galal El-Din]

Thanks Liviu,

I tried the tutorial you sent step by step. And it led to the same results

"QEMU failed with code (127)."

[Liviu Ionescu (ilg)]

you were right, there was a rpath problem with the GNU/Linux packages; I could reproduce it only with the 32-bits QEMU while running on a 64-bit machine, but the problem was there for all versions.

I fixed it and republished the debian32 and debian64 archives; please test them and let me know if this solved your problem.

[Mohamed Galal El-Din]

Tried it and it works as expected. Thanks for the fix.

[Liviu Ionescu (ilg)]

you're welcome, thank you for helping improve this project.