How (NOT) to Diagnose TF536 IDE Speed issues.

[Mario_PL]

Edited by PhilC

Original thread request was for the following:

I built this TF536 card and I have a problem with it.
The problem is that WB runs very long about 3 minutes.
Regardless of whether the attached mSD adapter or CF adapter.

I've cleaned up the thread to try and make it more useful. Some of it may not track correctly or be slightly confusing because of deleted comments etc.

[terriblefire]

This is usually caused by the interrupt path not working.. three things to check .. You will need obv and the board file from github

1. IDEINT has a good connection to the IDE interface. Check for shorts. Without this signal no interrupts.
- if you have a scope watch for transitions.
2. Check IPL lines are connected well to the CPLD. No shorts etc.
- check for transitions at the CPLD if you can.
3. Check that BUSEN on the bus buffers is not shorted and toggles on drive activity.

Also check D3 (D19) is conected from the CPLD to the bus buffers. If this was open it would cause the issue you see too.

[terriblefire]

I checked everything and it's ok.
And the card still does not work properly with the mSD or CF adapter

CF/SD Card asserts IDEINT..... High BTW.

IPL lines should select interrupt level 2.

When TF536 accesses INTENR bit 3 should be asserted.

Something is stopping this happening.

You'll need to watch IDEINT on a scope first, then BUSEN on buffers.

[8 Bit Dreams]

i had that that issue using SD2ide when i haven't set Max Transfer Rate, maybe it's worth to change it to 0x1FE00?

[terriblefire]

In my experience a dead board Is very rare. Send pictures and show us measurements on a scope.

I’ve seen people with 30 years of experience of soldering miss a short. It’s easy to convince yourself there isn’t an issue but there actually is. It’s 90% likely to be your soldering that’s caused it. 9% chance of component failure and less than 1% chance of a bad board. The board house Does complete Electrical testing of all boards.

So if you can’t be bothered to take a couple of pictures and share some measurements then I’ll just assume it’s bad soldering

[alenppc]

I built, give or take, 600 various TF boards and I still mess up occasionally... it happens.

[PhilC]

I've done 6 this weekend and one crashes every time on memory access, I know if I remove the FPGA there will be a hidden bridge underneath it.

Other 5 work fine.

For my first TF536 it took me a day to get it right solder wise and don't mention the TF534, I still hate them.

[8 Bit Dreams]

May i ask You is it a clean install with MMULibs installed, You are using ClassicWB or You are using WB Image installed on WinUAE? im asking because i can repeat Your scenario:
Just take a clean card, install 3.1.4 nothing else and try to reboot: a voilà - boot time is 6 minutes

Have You tried to use one of the Classic WB Images?

[arkadiusz.makarenko]

All connections are correct, no short circuits or breaks.
And the card, how it worked so long, starts with mSD.
Maybe the board is damaged, I don't know.
I'm letting go of the subject, waste of time and nerves.

Do you want to try different images? I have just completed setting up 2gb image. It is not extra fast boot, but it takes less than a minute to load.
If still is painfully slow then you could post it to me, and I can have a look at it?

[Mario_PL]

I never use any WinUAE installers, only the Amiga installer. I have 3.1 Kickstart and 3.1 also Workbench.
The mmulib package is installed.
Such a curiosity: When I start amige only from the goteka, it starts as fast as it does from the goteka, but when the mSD adapter is connected and I start from the goteka, it starts just as slowly. I mean, it reads disk partitions long.
The xilinx system has already been removed, I gave a different one and it is still the same.