TF4060 Beta Program

[ShootTheCore]

Sorry for the slow response - other obligations kept me away from my Amiga for a few days.

ChipNoCache tooltip fixed the problem for me. Thank you for investigating and resolving the problem. Should it be reported to the WHDLoad team?

[saft6luck]

tf4060r5_18533_2024_08_21_121f718_alpha.zip

EDIT: Tested on A4000CR with Fastlane Z3. Stable AF

Tested on an A4000T and A4000D+: much better. What happend to the cpuspeed command? And, is this change available in an official release, too?

@ShootTheCore Did you try this? I get frustrated when i give a solution and i get silence because then i dont know how to help the next person who asks.

I can feel your pain. How should someone even feel when he never gets an answer to basic questions? Good to see you are aware of this, too.

[matt020]

There is a pattern of behavior I see here.

[terriblefire]

Tested on an A4000T and A4000D+: much better. What happend to the cpuspeed command? And, is this change available in an official release, too?

No i'm working on the next official release. Its painful to get all these machines working at once.

[saft6luck]

@terriblefire about the A4000T boot problem:
The 53C710 needs a synchronous bus cycle termination via _STERM to work correctly while the 68030 bus also uses _DSACK0 and _DSACK1 to indicate the memory size for asynchronous cycles. To fix this, the A4000T has a _STERM generator in case a 53C710 bus master transfer is acknowledge via _DSACK1. This parallel, but different cycle termination might interfere with the TF4060 bus interface (bus sizing?).

Maybe you can check that this isn't causing the boot problem?

[terriblefire]

@terriblefire about the A4000T boot problem:
The 53C710 needs a synchronous bus cycle termination via _STERM to work correctly while the 68030 bus also uses _DSACK0 and _DSACK1 to indicate the memory size for asynchronous cycles. To fix this, the A4000T has a _STERM generator in case a 53C710 bus master transfer is acknowledge via _DSACK1. This parallel, but different cycle termination might interfere with the TF4060 bus interface (bus sizing?).

Maybe you can check that this isn't causing the boot problem?

No this isnt the issue. Its true it does need STERM but the A4000T GAL will generate it for us.

[terriblefire]

Sorry let me be clear. The issue isnt that i cant get the 4000T to work. I can. The issue is making the 4000T, 3000T, AA3000+ all work at the same time and clock to 100Mhz. Any 3 of these i can get at once.

[Maximilian]

Would it be a big issue if there were a few different firmwares for different machines?

This card should be easy to flash, so not a big problem to change it.
Maybe the CPUspeed program can also show witch firmware is loaded so that it is easy to check that you are running the correct firmware.

[saft6luck]

Sorry let me be clear. The issue isnt that i cant get the 4000T to work. I can. The issue is making the 4000T, 3000T, AA3000+ all work at the same time and clock to 100Mhz. Any 3 of these i can get at once.

For the time being, I would support to create a firmware version which lets the TF4060 run on an A4000T/A4000D+ with the original 53c710 driver (spoiler). The update process isn't that hard and will work even when the TF4060 isn't able to boot.

[terriblefire]

Sorry let me be clear. The issue isnt that i cant get the 4000T to work. I can. The issue is making the 4000T, 3000T, AA3000+ all work at the same time and clock to 100Mhz. Any 3 of these i can get at once.

For the time being, I would support to create a firmware version which lets the TF4060 run on an A4000T/A4000D+ with the original 53c710 driver (spoiler). The update process isn't that hard and will work even when the TF4060 isn't able to boot.

This was released June 2024 already.