WinUAE QEMU PPC

[FOL]

Originally Posted by B14ck W01f

Thanks FOL and Toni for all your help.

It seems that the performance is much faster with Direct3D.

The only problem I have now is when I minimize the window and then restore it back, WinUAE immediately goes into a pause state, and I can't access F12. No matter, at least I can cmd-tab out of it without it doing this.

I get this, if its set to Above Normal in Priority settings.
I avoid having to minimise window, just work around it, .

This is logs from beta 15. Morphos not work Im stoped my work to start this system :/

[Locutus]

MOS1.4.5 on QEMU crashes quite early in its boot process.

I vaguely remember reading Balaton Zoltan's patches for QEMU about MOS3.x on Mac99 and i think the issue is actually something fixed in his patch.

If i dont get a lift to SAKU next weekend I think i will have time to do some 'exciting' disassembly and debugging ;-)

Toni:

The github winuae tree only seems to include the qemu glue code, do you have a tree of your hacked up qemu for me?

Also, could you create a build of qemu-uae.dll that provides the gdb stub on a socket? I don't have a Windows build environment setup.

[Toni Wilen]

Originally Posted by Locutus

MOS1.4.5 on QEMU crashes quite early in its boot process.

It does not crash, it "only" hangs in infinite loop. I did some tiny disassembling yesterday and it seems to enable PPC CPU interrupt (sets MSR bits) and then goes in infinite loop ("label: b label") so apparently it expects some interrupt.

My guess is that some feature of CSPPC board is still missing. There are at least 2 unknown bits in CSPPC registers that MOS modifies. I'll post about them in http://eab.abime.net/showthread.php?t=74615 later today.

The github winuae tree only seems to include the qemu glue code, do you have a tree of your hacked up qemu for me?

Also, could you create a build of qemu-uae.dll that provides the gdb stub on a socket? I don't have a Windows build environment setup.

QEMU code is in Frode's github. Ask him, I only compile it for Windows

[Locutus]

Originally Posted by Toni Wilen

It does not crash, it "only" hangs in infinite loop. I did some tiny disassembling yesterday and it seems to enable PPC CPU interrupt (sets MSR bits) and then goes in infinite loop ("label: b label") so apparently it expects some interrupt.

Oh curious! that is not what happens on my setup, could be that i just see a setup error at this point :-) (i only very briefly tried if it worked)

My guess is that some feature of CSPPC board is still missing. There are at least 2 unknown bits in CSPPC registers that MOS modifies. I'll post about them in http://eab.abime.net/showthread.php?t=74615 later today.

'fun'....

QEMU code is in Frode's github. Ask him, I only compile it for Windows

Okay, i'll take a look in the evening, kiitos! :-)

[Toni Wilen]

Originally Posted by Locutus

Oh curious! that is not what happens on my setup, could be that i just see a setup error at this point :-) (i only very briefly tried if it worked)

Crystal ball reply: You have directory filesystem, UAE-controller HDF or any other UAE expansion enabled. You can only use hardware emulated features with "alien" operating systems.

[mulder77]

Just curious: to be able to have more than 128 MB RAM on the CyberStorm PPC, would it be necessary to modify the ROM for the card?
Or are there restrictions within the emulation of the card which disallows more than 128 MB RAM?

[Locutus]

Originally Posted by Toni Wilen

Crystal ball reply: You have directory filesystem, UAE-controller HDF or any other UAE expansion enabled. You can only use hardware emulated features with "alien" operating systems.

My counter target spell says... no, to obvious ;-)

[Toni Wilen]

Originally Posted by Locutus

My counter target spell says... no, to obvious ;-)

Apparently crystal ball is not calibrated for PPC

Anyway, do you get normal autoconfig log messages (if you have any autoconfig devices configured) and then it crashes? What kind of message?

[Locutus]

I'm at work now, so i cant really check right now.

But i will do some bone divinations in the evening and see where it strands

[Toni Wilen]

Originally Posted by mulder77

Just curious: to be able to have more than 128 MB RAM on the CyberStorm PPC, would it be necessary to modify the ROM for the card?
Or are there restrictions within the emulation of the card which disallows more than 128 MB RAM?

Hardware does not restrict it, at least not in emulation, there is space for 1G and a bit more.. (Original space is 0x08000000 to 0x0fffffff. 0x10000000 to 0x3fffffff is basically free). Currently RAM size is limited to 128M via GUI/config file but that limit can be removed easily.

You would need to patch OS4 (assuming you want more RAM for OS4, you can easily have MUCH more RAM under OS3 already..), patching CSPPC flash rom won't help. I quickly tested with 256M and OS4 immediately crashed at boot.

[DarrenHD]

Originally Posted by Toni Wilen

Hardware does not restrict it, at least not in emulation, there is space for 1G and a bit more.. (Original space is 0x08000000 to 0x0fffffff. 0x10000000 to 0x3fffffff is basically free). Currently RAM size is limited to 128M via GUI/config file but that limit can be removed easily.

You would need to patch OS4 (assuming you want more RAM for OS4, you can easily have MUCH more RAM under OS3 already..), patching CSPPC flash rom won't help. I quickly tested with 256M and OS4 immediately crashed at boot.

256MB ram would work in a Blizzard PPC emulated environment - OS4.1 Classic supports up to 256MB of RAM on the Blizzard. But only 128MB on a Cyberstorm as you know.

[mulder77]

I played around with the config files.
If I manually set memory to 256 MB, boot process complains (still within 3.1/68k), that the kernel cannot be loaded.

[B14ck W01f]

Why can't I use the Accelerator board SCSI, if I use the A590/A2091 or the A4091, then the AmigaOS4.1 logo appears as it should, then the hard disk refuses to boot up. IDE is no problem.

[amigafreak68k]

Did you boot from a harddrive which is formerly installed with ide? If so, then please reinstall the system. In the install process of AmigaOS 4 you'll be asked to install also cybppc.device. Maybe this is the problem.

[B14ck W01f]

That means I could have to have WinUAE create a hard drive with a SCSI controller rather than an IDE one.

[Toni Wilen]

Log is wrong (winuaelog.txt, it is only needed when logging option in paths panel is ticked)

Easiest way to confirm if it is simply missing driver from your OS4 installation: start installation from scratch (just like you did when installing with IDE) but mount the install CD as accelerator SCSI unit 1 instead of IDE.

Config is correct (and your existing OS4 installation misses cybppc.device support) if it boots to install selection screen.

[B14ck W01f]

Two more questions:

1. Is cybppc.device support really necessary if you want to install and run the OS with SCSI?
2. Do you recommend creating a SCSI unit 0 hard drive?

Sorry if these questions annoy you, but I am not really used to this PPC stuff.

Toni, I thought that the boot log was appropriate since I had trouble booting the OS with SCSI. My mistake.

[FOL]

Originally Posted by B14ck W01f

Two more questions:

1. Is cybppc.device support really necessary if you want to install and run the OS with SCSI?
2. Do you recommend creating a SCSI unit 0 hard drive?

Sorry if these questions annoy you, but I am not really used to this PPC stuff.

1) Yes, if you want to use Cyberstorm Scsi.

2) Yes, Accelerator Scsi.

I have mine set as;

Accelerator SCSI unit 0 = HDD.
Accelerator SCSI unit 1 = CDROM.

If you go into Cyberstorm flash menu (esc while booting). Disable all scsi devices except Unit 0 and 1 and set unit 1 to CDROM bootable.
You can now boot OS4.1 install CD without the need for floppy.

[Toni Wilen]

Originally Posted by B14ck W01f

I thought that the boot log was appropriate since I had trouble booting the OS with SCSI. My mistake.

winuaebootlog.txt is WinUAE's "boot" phase (display modes, sound devices, input devices, etc.. detection phase), nothing to do with emulated Amiga boot.