BFG9060 + Cybervision64 + A3000 = incompatibility?

[lioneer]

Hello, i have problem with P96 after upgrading my A3000 with BFG9060 cpu card (i have cpu 68060 rev.6). Right after loading monitor drivers (in my case Cybervision) this driver crash with Software Failure 80000004. Before, with stock 68030 or CPU card A3640, everything works fine. I have newest P96 drivers bought from icomp and newest MMUlibs. Under PAL is working everything without problem.

[alexh]

I was going to say report it over in the P96 forum on icomp.de but I see you already did.

https://forum.icomp.de/index.php?thr...card-crashing/

If you're overclocking your 68060 I would reduce it to 50MHz until you have debugged this.

I would recommend using a spare HDD (or CF) and do a bare re-install of AmigaOS, MMUlib, P96 and as little as possible of anything else and see if it still does it.

With a bare install it is either (a) a real bug in software or (b) a HW bug. I'd think (a) more likely if your system is otherwise stable.

Software Failure 80000004

This is illegal instruction. Most likely a jump/branch to address that does not have program data OR data corruption due to broken HW.

[lioneer]

when I take the card out from Amiga, everything works fine... (with 030 onboard). So, there is collision between BFG and Cybervision64 i think :/ but how to resolve it. My system is 3.2, just with mmu libs and P96 drivers. Nothing more. Very little

[alexh]

Originally Posted by lioneer

there is collision between BFG and Cybervision64 i think :/

If the BFG had an inherent HW incompatibility with Zorro III cards like the CV64 I think we'd have heard about it by now? It is not an uncommon GFX card. There is an issue with BFG and A4000T with bus termination. There is a slim chance you've found an issue which only affects A3000s? But I think it unlikely.

You now have to try to determine if it is a HW fault (broken BFG that sometimes reads bad data from somewhere) or a SW fault (bug in CV64 P96 driver never before triggered).

Maybe discuss with the developer of the BFG? https://gitlab.com/MHeinrichs/a4000-tk/-/issues

And/Or discuss with the developer of P96 (Thomas Richter?) about how to diagnose this in SW using something like enforcer?

[Thomas Richter]

But you did install a 68060.library (and, potentially, with it the mmu.library)

[lioneer]

my Amiga is 3000D, no 4000. So but i dont know, what next... how to resolve this issue... i will try to ask M. Heinrichs too

Originally Posted by alexh

If the BFG had an inherent HW incompatibility with Zorro III cards like the CV64 I think we'd have heard about it by now? It is not an uncommon GFX card. There is an issue with BFG and A4000T with bus termination. There is a slim chance you've found an issue which only affects RevD A4000s? The majority of A4000 users will be RevB. But I think it unlikely.

You now have to try to determine if it is a HW fault (broken BFG that sometimes reads bad data from somewhere) or a SW fault (bug in CV64 P96 driver never before triggered).

Maybe discuss with the developer of the BFG? https://gitlab.com/MHeinrichs/a4000-tk/-/issues

And/Or discuss with the developer of P96 (Thomas Richter?) about how to diagnose this in SW using something like enforcer?

[Thomas Richter]

Here I am, though note that this is not an official support thread, only a "best effort". Mind answering my question about the installed components first?

Next component to identify the cause would be MuForce then (aka "something like the enforcer"), plus either a remote terminal to be connected to the serial port at 9600-8N1, or Sashimi, or syslog if Kick 3.2 is available.

[lioneer]

Hi matthias and guten abend

So my configuration, Amiga 3000D, Kick3.2, freshly installed Workbench 3.2 with newest MMUlibs (aminet) and Picasso96 from iComp.
Cards are BFG9060 with 68060 rev.6, ATBus Clone IDE Zorro (from you) and Phase5 Cybervision64 rtg card. Nothing more.

So next step is what? MuForce tool or syslog? i need more help with those tools, i dont know how to use them
Thank you

Originally Posted by Thomas Richter

Here I am, though note that this is not an official support thread, only a "best effort". Mind answering my question about the installed components first?

Next component to identify the cause would be MuForce then (aka "something like the enforcer"), plus either a remote terminal to be connected to the serial port at 9600-8N1, or Sashimi, or syslog if Kick 3.2 is available.

[Thomas Richter]

Please install SegTracker, MuForce, the disassembler.library (comes with MuForce, or separately), Segtracker (also from Aminet) and Sashimi (from Aminet). Sashimi does something very similar to syslog, which is a ROM component you can activate from the boot menu.

In the startup-sequence, before loading the monitor drivers, run the following:

SegTracker <>NIL: &
MuForce DISPC STACKCHECK STACKLINES=32 <>NIL: &
Sashimi &

then post whatever appears in the Sashimi window.

[lioneer]

I run these commands after setpatch, but only cli with message "sashimi installed ([Ctrl]+C...." appear and after that Software Failure with CyberVision driver. There is no Sashimi window

[patrik]

Don’t you need the RAWIO argument to MuForce for Sashimi to be able to capture its output?

[trixster]

I’m sure I read on the bfg thread on A1K someone was successfully using a bfg with a CyberVision64.

[Thomas Richter]

Originally Posted by lioneer

I run these commands after setpatch, but only cli with message "sashimi installed ([Ctrl]+C...." appear and after that Software Failure with CyberVision driver. There is no Sashimi window

Sorry, please also add the "RAWIO" argument to MuForce which I forgot, and make sure these three commands are started before loading the monitor driver. Probably even move them directly behind SetPatch, and probably even include a "wait 5" behind the last Sashimi command to give the triple some time to start up. I also seem to remember that segtracker does not need to be run in background.

 SetPatch >NIL: ; this command was here before SegTracker MuForce RAWIO DISPC STACKCHECK STACKLINES=32 NIL: & Sashimi & Wait 5

[Thomas Richter]

Originally Posted by lioneer

I run these commands after setpatch, but only cli with message "sashimi installed ([Ctrl]+C...." appear and after that Software Failure with CyberVision driver. There is no Sashimi window

Sorry, please also add the "RAWIO" argument to MuForce which I forgot, and make sure these three commands are started before loading the monitor driver. Probably even move them directly behind SetPatch, and probably even include a "wait 5" behind the last Sashimi command to give the triple some time to start up. I also seem to remember that segtracker does not need to be run in background.

 
SetPatch >NIL: ; this command was here before 
SegTracker 
MuForce RAWIO DISPC STACKCHECK STACKLINES=32 <>NIL: & 
Sashimi & 
Wait 5

[lioneer]

Ok i have screenshot, and video too. How can i send it to you?
Private message?

Thank you

Originally Posted by Thomas Richter

Sorry, please also add the "RAWIO" argument to MuForce which I forgot, and make sure these three commands are started before loading the monitor driver. Probably even move them directly behind SetPatch, and probably even include a "wait 5" behind the last Sashimi command to give the triple some time to start up. I also seem to remember that segtracker does not need to be run in background.

 
SetPatch >NIL: ; this command was here before 
SegTracker 
MuForce RAWIO DISPC STACKCHECK STACKLINES=32 <>NIL: & 
Sashimi & 
Wait 5

[Thomas Richter]

It will probably not require a video, but the output would be most valuable. Would it be possible to save that to a file or to disk, and post it in text form? If not, a screen shot would be helpful. You can either post that here, or use my email address (you find it for example in all aminet uploads).

[lioneer]

sent to email

Originally Posted by Thomas Richter

It will probably not require a video, but the output would be most valuable. Would it be possible to save that to a file or to disk, and post it in text form? If not, a screen shot would be helpful. You can either post that here, or use my email address (you find it for example in all aminet uploads).

[Thomas Richter]

On this output, I am missing the top lines of the "hit", and I actually do not see any illegal instruction exception, just something in the driver that points to an illegal memory access. Thus, could you please press "Ctrl+F" in the sashimi window? This would save its contents to T:Sashimi.out, from where you could copy or transfer it to a PC such that I have the full output available.

Also, please provide an output of ShowConfig.

Thanks,
Thomas

[alexh]

Trying not to derail the work you're doing with Thomas but :

Are you booting from SCSI?

There is a lot of chatter that A3000 + BFG = SCSI errors.

Was your A3000 originally 25MHz or 16MHz?

[lioneer]

I am booting from Zorro IDE card ATBus Clone, and my A3000 is 25MHz.

Originally Posted by alexh

Trying not to derail the work you're doing with Thomas but :

Are you booting from SCSI?

There is a lot of chatter that A3000 + BFG = SCSI errors.

Was your A3000 originally 25MHz or 16MHz?