From: Duarte Silva <duarte.silva@serializing.me>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Support for NetLogic XLP Processors
Date: Sun, 22 Mar 2015 11:13:37 +0000 [thread overview]
Message-ID: <8111192.6dZICC2BlA@lczc1207b1zdcs> (raw)
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
Hi guys,
I have been struggling to get some binaries compiled for NetLogic XLP
processor to run under QEMU. I have tried a bunch of things (most going back
and forth) and always get the following error message:
qemu: uncaught target signal 4 (Illegal instruction) - core dumped
Illegal instruction
I tried to debug it using GDB but to no avail. Does anybody have ideas? I'm
running QEMU 2.2.1.
Thanks for any help, cheers,
Duarte
[-- Attachment #2: cpuinfo.txt --]
[-- Type: text/plain, Size: 1204 bytes --]
system type : Netlogic XLP SoC
processor : 0
physical id : 0
cpu model : XLP208 Rev B0 (Secure Boot) FPU @500 MHz
BogoMIPS : 402.73
wait instruction : yes
microsecond timers : yes
tlb_entries : 544
extra interrupt vector : yes
hardware watchpoint : yes, count: 1, address/irw mask: [0x0fff]
ASEs implemented :
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
processor : 1
physical id : 1
cpu model : XLP208 Rev B0 (Secure Boot) FPU @500 MHz
BogoMIPS : 402.61
wait instruction : yes
microsecond timers : yes
tlb_entries : 544
extra interrupt vector : yes
hardware watchpoint : yes, count: 1, address/irw mask: [0x0fff]
ASEs implemented :
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
processor : 2
physical id : 2
cpu model : XLP208 Rev B0 (Secure Boot) FPU @500 MHz
BogoMIPS : 405.42
wait instruction : yes
microsecond timers : yes
tlb_entries : 544
extra interrupt vector : yes
hardware watchpoint : yes, count: 1, address/irw mask: [0x0fff]
ASEs implemented :
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
[-- Attachment #3: binary-info.txt --]
[-- Type: text/plain, Size: 1001 bytes --]
ELF Header:
Magic: 7f 45 4c 46 01 02 01 00 00 00 00 00 00 00 00 00
Class: ELF32
Data: 2's complement, big endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: EXEC (Executable file)
Machine: MIPS R3000
Version: 0x1
Entry point address: 0x404860
Start of program headers: 52 (bytes into file)
Start of section headers: 425808 (bytes into file)
Flags: 0x808e1105, noreorder, cpic, 32bitmode, unknown CPU, o32, mips64r2
Size of this header: 52 (bytes)
Size of program headers: 32 (bytes)
Number of program headers: 9
Size of section headers: 40 (bytes)
Number of section headers: 33
Section header string table index: 32
next reply other threads:[~2015-03-22 11:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 11:13 Duarte Silva [this message]
2015-03-25 11:26 ` [Qemu-devel] Support for NetLogic XLP Processors Duarte Silva
2015-03-25 13:13 ` James Hogan
2015-03-25 14:20 ` Duarte Silva
2015-03-25 14:44 ` Leon Alrae
2015-03-25 14:54 ` Leon Alrae
2015-03-25 15:38 ` Duarte Silva
2015-03-25 17:33 ` Leon Alrae
2015-03-25 23:54 ` Duarte Silva
2015-03-26 9:29 ` Leon Alrae
2015-03-26 9:34 ` James Hogan
2015-03-26 9:54 ` Duarte Silva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8111192.6dZICC2BlA@lczc1207b1zdcs \
--to=duarte.silva@serializing.me \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).