QEMU question

[judb]

Anyone have a linux box they can download qemu and try executing some of the phatbox software using their arm user mode emulator?

I'd be curious if you can get things to run under there.  I'd try the current release and one of the old BMW ones thats not signed and see if you can get the code to exectue.

[para]

I posted something similar:
http://forum.phathack.com/cgi-bin/yabb/YaBB.cgi?board=dmshack;action=display;num=1111072896

So if one doesn't work, try another emu...

[judb]

Update

busybox from the ramdisk image will run under qemu BUT I cant execute any of the files located on /dos mount point.

I think theres a missing / hidden file of ld-linux.so.2 located in /dos/lib

I dont know where it uncompresses from but its GOT to be there for these to work and if I can get my hands on it I can start emulating the other phatbox files.

[balle]

Anyone have a linux box they can download qemu and try executing some of the phatbox software using their arm user mode emulator?

Have tried to play with this, and can run the applications (hdparm, 51d, phat, phatd and such), but I have not been able to establish a complete phat-environment where I boot from the kernel. Booting a x86-kernel looks like it works and to me it looks like the -kernel parameter is ignored when you run qemu-arm.

Maybe I am missing some parts, I have only done a 'apt-get install qemu' in a Debian system.

[judb]

balle,

can you get any options or output from the 51d or phatd?  or the progpld ?  I want to see how they work.

thanks in advance.

I downloaded qemu and run qemu-arm ./phatd and it fails to run.

are you doing anything else?

[balle]

balle, can you get any options or output from the 51d or phatd?  or the progpld ?  I want to see how they work.

Code: [Select]


peregrin:/usr/local/Phat/PHTSYS# qemu-arm ./hdparm -V
hdparm v3.9
peregrin:/usr/local/Phat/PHTSYS#


The next is with /dos not mounted

Code: [Select]

peregrin:/usr/local/Phat/PHTSYS# qemu-arm ./phatd
74.52:phatd:main      : Corrupted /dos/pkeys2.e
qemu: uncaught target signal 2 (Interrupt) - exiting
peregrin:/usr/local/Phat/PHTSYS#


And with /dos mounted

Code: [Select]


peregrin:/dos# qemu-arm ./phatd
bind: Invalid argument
peregrin:/dos#


If I strace(1) the last command I see that the error is
bind(5, {sa_family=AF_FILE, path="/tmp/phatsock"}, 112) = -1 EINVAL.
Don't remember much about socket-programming, but maybe descriptor 5 already is used in my system or something?

[judb]

could you run the progpld command for me as well?

What did you do to get your qemu environment working?  just compile it or install the rpms?  were there any other libraries you got ahold of?

[balle]

What did you do to get your qemu environment working?  just compile it or install the rpms?  were there any other libraries you got ahold of?

Running Debian. Just did a 'apt-get install qemu' and voila..

But it did download a couple of dependencys also;

Depends: libc6 (>= 2.3.2.ds1-4), libsdl1.2debian (>> 1.2.7-0), zlib1g (>= 1:1.2.1), vgabios, bochsbios, sharutils

But I don't know if these are really needed.

[balle]

could you run the progpld command for me as well?

Code: [Select]


peregrin:/dos# qemu-arm ./progpld
usage: ./progpld filename.dat
peregrin:/dos# qemu-arm ./progpld prog.bif
progpld prog.bif
programming prog.bif
*................................................................................................5498 bytes
ok
peregrin:/dos#


Will try to debug this and see where it actually did put those bytes..

[judb]

hope that didnt just reprogeam something on your motherboard

try renaming the .sig file for prog.bif and see if that file still executes.

[balle]

hope that didnt just reprogeam something on your motherboard

try renaming the .sig file for prog.bif and see if that file still executes.

Same results with or without sigfiles for prog.bif.

Nope, I don't think I have reprogrammed anything here, but the though hit me the first time I ran this, as I do run all this as root as I though that it was required (it isn't).

[judb]

I have poured over the ramdisk and nothing in it seems to require any sig files... so the kernel or the boot loader have to be mounting the PHATSYS partition and scanning for these as if you modify rc.sh (which is called by inittab via /etc/init.d/rcS)

Who's got the kernel source?  I need a copy of it please.

[judb]

Same results with or without sigfiles for prog.bif.

Nope, I don't think I have reprogrammed anything here, but the though hit me the first time I ran this, as I do run all this as root as I though that it was required (it isn't).

Interesting... if we can decode the format of this file I think we have the image for at least one of the CPLD chips and could load our own.

[judb]

hey belle,

do you have the file /usr/gnemul/qemu-arm ?

[balle]

hey belle,

do you have the file /usr/gnemul/qemu-arm ?

Nope, I see that qemu is trying to open this when I use strace, but I don't have this file here.

[judb]

I hate redhat!!

I cant get half this crap to compile due to their using really old modified versions of stuff like python and glibc ... bah!

[judb]

can you see what the swgrli does?

[balle]

can you see what the swgrli does?

Code: [Select]


peregrin/dos>qemu-arm ./swgrli
Cannot open /dev/led, will print light status
Toggle light
peregrin/dos>qemu-arm ./swgrli 1
Cannot open /dev/led, will print light status
Light on
Light off
Light on
Light off
Light on
qemu: uncaught target signal 2 (Interrupt) - exiting
peregrin/dos>

If you 'strings the file you'll see in the end that there is a bit of morsecodes, so I would guess that this is the controller for the leds, and also for the keglady (or whatever her name was).

[judb]

Yeah I just found that and im ht eprocess of running it through a decoder for morse code.

Any other exectueables on the box if you could dump out the command output that would be quite helpful!

Thanks!

[judb]

http://forum.phathack.com/cgi-bin/yabb/YaBB.cgi?board=kegphatbox;action=display;num=1111784731;start=0#7

the morse code decoded in that thread...