PPC Support in FS-UAE

[amigafreak68k]

There seems to be also some problems with general PPC emulation. "lha_wos" (WarpOS version of the lha archiver also slows down the system! I'd tested this with some archives (mostly mui custom classes needed for SimpleMail). In case of slow down the system is nearly unusable.

[B14ck W01f]

Does anyone experience random lockups in 2.5.18dev?

[amigafreak68k]

If my last post looks like an lockup, than yes.

[B14ck W01f]

I mean when you try certain things in AmigaOS 4.1, like trying to reboot the system once installation completes and testing the AHI preferences.

[amigafreak68k]

Yes. Look at the post before my last post! I've also corrupt files - i.e. downloaded archives - on harddisk (cybppc.device), but I must trst if this is filesystem or device related!

[amigafreak68k]

To simply test the software reboot, only type "reboot" in CLI. For me it always freezes the system. I'll test this now on WinUAE.

Edit: In WinUAE I get a green screen in case of software reboot. I get also green screen, if I use A + A + Ctrl. I get no crash, if I use F12 + "Reset"

In fact the same behavior as in FS-UAE. Definitely a FS-UAE-only-problem

[FrodeSolheim]

@amigafreak68k It's always a good idea to compare with WinUAE . Does the FS-UAE problem only occur with the "slirp" version?

[amigafreak68k]

No. Same behavior with normal version

[mulder77]

Is there a chance to add a local filesystem as an additional disk to the Cyberstorm PPC SCSI controller?
No matter how I try, this disk is always added as uae-0 according to the ESM.

I tried to increase the priority, but it seems to be ignored ("hard_drive_0_priority = 6"). So Kickstart 3.1 tries to boot off this local filesystem instead of the attached HDF.

OS4 kernel then won't boot, even if I chose DH0 (first partition on cybppc HDF file) from the 3.1 ESM.

[FrodeSolheim]

@mulder77 No, directory hard drives are implemented via emulated m68k file system handlers directly installed into AmigaOS - there's no HD controller involved.

Likewise, these directory hard drives cannot function under AmigaOS 4.

(Additionally, enabling directory hard drives also implicitly enables the UAE boot ROM - which interferes - so make sure no UAE virtual devices are enabled when running AmigaOS4)

[Foul]

Frode, for my reboot problem, i made a minimal config test :

The goal is to boot the startup-sequence then it load blizkick to map the kickstart (and modules) into rom to speedup system, reboot one time and load Workbench.

fs-uae2.5.11dev :
With 060 config : Normal boot/reboot and workbench loaded
With PPC config : Blizkick and no reboot (blizkick freeze on displayed cli window)

fs-uae2.5.12dev and all next :
With 060 config : Normal boot/reboot and workbench loaded
With PPC config : Blizkick and no reboot (freeze on black screen)

When freezing, just reboot manually (CTRL+A+A) and Workbench load...

Config file :

[fs-uae]
amiga_model = A1200/020

hard_drive_1 = /media/Amiga/Downloads/test/

kickstart_file = Kickstart v3.1 rev 40.68 (1993)(Commodore)(A1200).rom

#PPC config
uae_cpuboard_type = BlizzardPPC
uae_cpuboardmem1_size = 128
cpuboard_flash_file = blizzardppc_060_44.71.rom

#060 Config
#uae_cpuboard_type = Blizzard1260
#uae_cpuboardmem1_size = 128
#cpuboard_flash_file = Blizzard_1260.rom

uae_cpu_model = 68060
uae_fpu_model = 68060

uae_maprom = 0xf0000000

Just swap PPC/060 Config to test.

Minimal Directory/Hardrive attached (just replace media/Amiga/Downloads/test/ path to yours)

Thank you

[Foul]

Another simple test to do to get stucked on a black screen :

get PPCTestDisk : http://powerup.amigaworld.de/download.php?id=59

Boot with :

[fs-uae]
amiga_model = A1200/020

floppy_drive_0 = ppctest.dms

kickstart_file = Kickstart v3.1 rev 40.68 (1993)(Commodore)(A1200).rom

uae_cpuboard_type = BlizzardPPC
uae_cpuboardmem1_size = 128
cpuboard_flash_file = blizzardppc_060_44.71.rom

uae_cpu_model = 68060
uae_fpu_model = 68060

and Amiga Boot and stay Frozen on black screen...

Anyone can test and confirm plz ?

edit : i removed qemu-uae.so to test and Floppy is booting... so it's related to the plugin... i join it if anyone want to test :

http://goo.gl/HkSo9R : qemu-uae-linux-x86-64.zip 8.4 Mo

[mulder77]

I can confirm the behavior.
I even tried to boot with no startup sequence, but no luck either.

I have my own compiled version of the plugin here. As soon as I disable the plugin, boot process is ok.

[FrodeSolheim]

@Foul The issue is that you are using a 68020-based model (which defaults to A1200 speed / cycle exact), and manually override the CPU to 68060 without also specifying uae_cpu_speed = max. It hangs because the PPC CPU is started (presumably by the Blizzard ROM), and the PPC CPU does not work without fastest-possible mode.

[Foul]

added uae_cpu_speed = max , System Boot, but crash/reboot just after WarpOS Test...

Run fine with PowerUP Test.

[FrodeSolheim]

Originally Posted by Foul

System Boot, but crash/reboot just after WarpOS Test...

Not a bug.

Phase5 releases the BlizzardPPC hardware and puts the ppc.library into the Flash ROM. It is started at boot time and can't be deactivated. As a consequence, WarpUp doesn't work on these boards (...).
(http://cd.textfiles.com/amigaplus/so..._english.guide)

[Foul]

Nothing more... you're the Best

[amigafreak68k]

Yes! The very best! I hope he'll not lost the enthusiasm to debug the other bug just like Toni

[FrodeSolheim]

@amigafreak68k It was easy to reproduce the crash with Ctrl+A+A (actually, it happens about 50-70% of the time here, while other times I either get a green screen or it works).

The good news is that I believe I have fixed it (a bit more testing required)

[amigafreak68k]

Originally Posted by FrodeSolheim

(a bit more testing required)

You know a address