How (NOT) to Diagnose TF536 IDE Speed issues.

[terriblefire]

I will actually write a test firmware and create an adf to test this tomorrow. Will not have fastmem bit will expose a test port that can peek internal card signals

[terriblefire]

Reviewing the code its possible that if one of the FC lines was shorted low you'd also get screwed up interrupts.

[8 Bit Dreams]

Just try to install a fresh copy of 3.1.4 WB, and You'll get same pattern..
Haven't dug deeper yet, need to compare startup sequence with classic WB to see what's the difference and what may cause this..

[arkadiusz.makarenko]

Just try to install a fresh copy of 3.1.4 WB, and You'll get same pattern..
Haven't dug deeper yet, need to compare startup sequence with classic WB to see what's the difference and what may cause this..

I have just done it on crappy slow sd card. It loaded in 1min 40sek. Still far to 6 minutes.
I have noticed that around 1min some patch was loaded.

[Mario_PL]

The problem occurs even if the partitions are empty and starts from the goteka, it takes about 3 minutes to read the partition at startup

[8 Bit Dreams]

@arkadiusz.makarenko
Was it with 3.1 or 3.1.4? This is probably caused by setpatch in last one, will post my findings later today

[arkadiusz.makarenko]

@arkadiusz.makarenko
Was it with 3.1 or 3.1.4? This is probably caused by setpatch in last one, will post my findings later today

Kickstart 3.1
3.1.4 wb

[terriblefire]

The problem occurs even if the partitions are empty and starts from the goteka, it takes about 3 minutes to read the partition at startup

Test with clean 3.1 and only one partition. That will rule out hardware faults

[terriblefire]

So I tested, and nothing changes it is just as slow.
I have already accepted that probably the pcb is damaged

If you have actually measured what i have told you to then the PCB is fine. Its very simple things to make the speed of the IDE work. If there is continuity from BUSEN to the bus buffers, IDEINT to the IDE headers, the FC lines are not shorted together and same for IPL lines then then there is nothing else involved. You have already said you have checked these so the PCB is fine.

It will be bad soldering somewhere or bad measuring. Because you have not supplied any photos or scope measurements.. so obviously your ego will not let you believe it can be your problem so it must be someone else.

The soldering must be very bad if you will not post a photo.

[terriblefire]

Let me be 110% clear about what needs to be measured. Maybe you will find the "issue with the pcb" that you insist is there... Because the checks you've done so far would suggest their is nothing wrong with the PCB. You've said you've checked these things and these are all the factors that control IDE speed. I've completely reviewed the code in the last 24 hours.

1. Check IPL0-2 (all three lines) are not shorted to themselves, any other pins, GND or VCC(33). AND that they are connected to the 68k socket AND 030 socket.
3. Same for FC.
3.Check BUSEN is not shorted to any data lines or GND AND that it is are connected to the bus buffers is connected to the bus buffers on the bottom of the board.
4. Check IDEINT is connected to the CPLD. Use a SCOPE to check it toggles HIGH and LOW. Check the resistor connected to the IDEINT line is soldered ok.

If you dont show some results here i'm assuming your just reflowing stuff randomly and not actually checking. This is what people who do no know what they are doing do. I can point you to some Louis Rossmann videos on the subject of people who just randomly change things and hope.

If you dont post some photos I will assume you are completely incompetent at soldering and lock this thread.