Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility with A590? #5

Open
mheyer32 opened this issue Jun 21, 2021 · 10 comments
Open

Compatibility with A590? #5

mheyer32 opened this issue Jun 21, 2021 · 10 comments

Comments

@mheyer32
Copy link

I'm trying to get a A590 SCSI controller to work on my A500 (with the flash relocator and a TF536 installed).
I can get the system to boot, but it easily runs into a "SCSI bus lockup" with the drive light on and no further activity.
Removing the relocator gets rid of the lockups.

Could this be an autoconfig issue? The A500 doesn't have true autoconfig on the 68k bus, so how does the relocator make its 1mb ram slot visible to the system?

@PR77
Copy link
Owner

PR77 commented Jun 25, 2021

Hi There,

Interesting issue. I don't have an A590 so I can't be sure, but if the system boots it is unlikely an Autoconfig issue. Does the issue only happen when using the Flash Kickstart or both?

Autoconfig is done by data being made available to the CPU at address 0xE80000. The Relocation will block /AS from being asserted until it's autoconfig cycle is complete then /AS in this memory are allowed to other devices - like the TF536 and A590. Do you have FastRAM installed on the A590?

Could you send a screenshot of all of the Autoconfig devices present in the system?

@mheyer32
Copy link
Author

CB634264-7603-48A5-AB19-54FEC7FEECF1
This is with the A590, TF536 and KickRelocator in the machine

@mheyer32
Copy link
Author

I also tried without the TF536. In this case the machine will hang with a SCSI lockup early in the boot.
What you see in the comment above is the machine booting from IDE while the A590 is connected.
The A590 has two MB of fastram installed.

@PR77
Copy link
Owner

PR77 commented Jul 4, 2021

I have no A590 so I am only speculating here, if it boots then perhaps it is not DMA related. I don't expect DMA to be an issue as the relocater doesn't map usable RAM. Does the issue happen when using ROM or FLASH Kickstart?

@mheyer32
Copy link
Author

Using LinuxJedi's FW, I only tested the onboard ROM (not Flash).

Could it be an issue with the A590/A2091 ROM code?

@PR77
Copy link
Owner

PR77 commented Jul 12, 2021

As I don’t have an A590 I can only speculate, but if it is not working also with the ROM KIckstart I suspect the issue might be with something else.

You mentioned the issue is also happening without your accelerator card, what if you remove the relocator and use a 68k direct in the CPU socket?

Do you have a logic analyser or other debugging equipment?

@mheyer32
Copy link
Author

If I remove the relocator and just place a 68k in the socket, it works.

I do have a logic probe and a 4-channel oscilloscope.

@PR77
Copy link
Owner

PR77 commented Jul 13, 2021

When you experience the lockup, does the system freeze or only SCSI access? Have you tried with the original firmware?

Are you able to probe the /AS, /OVR, /DTACK and /BR? Trigger of falling edge of /DTACK.

@mheyer32
Copy link
Author

The hang seems system wide. Even interrupt-driven music players stop playing.
What is weird is that I can even boot from the SCSI device, but certain operations (in particular whatever SysInfo does when you click on a device in the "Drives" menu) cause the lockup.
I tested the original FW, but the same issue applies. I'll try to tap the requested signals, give me some time :-)

@PR77
Copy link
Owner

PR77 commented Aug 28, 2021

Hi There, how are you getting on with the debugging?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants