TF1260 on ACA500
Posted: 10 Aug 2021 05:23
Having a bout of insomnia and got shown a salty comment from Jens about the TF1260...
I cant resist this poke back TF1260s sold 300+, ACA1260s sold 0.. Maybe he should just try to build a USB card that doesnt fry itself..
Anyways i noticed that @E-Penguin had asked about it.. Well there are a couple of things i realized
1. TF1260 Ram is not Autoconfig. Its fixed at 0x08000000 range. This only works with A1200 3.1 ROMs.
- This was done because otherwise Mediator doesnt work. It never expects a CPU card to have 2 autoconfig devices.
2. Probably i have got a bug in CONFIG_OUT so that its always set to high. It really doesnt matter if you use the TF1260 for its intended purpose.
Unsure of what the specific fault with the ACA500 is but it might be some of the hacks added to the TF1260 to make the mediator work smoothly that caused it. It does resampling of DSACK in the ZII range because the fall times from Mediator are up to 15ns appart. i.e. it can look like a byte ack when its really a longword.
I cant resist this poke back TF1260s sold 300+, ACA1260s sold 0.. Maybe he should just try to build a USB card that doesnt fry itself..
Anyways i noticed that @E-Penguin had asked about it.. Well there are a couple of things i realized
1. TF1260 Ram is not Autoconfig. Its fixed at 0x08000000 range. This only works with A1200 3.1 ROMs.
- This was done because otherwise Mediator doesnt work. It never expects a CPU card to have 2 autoconfig devices.
2. Probably i have got a bug in CONFIG_OUT so that its always set to high. It really doesnt matter if you use the TF1260 for its intended purpose.
Unsure of what the specific fault with the ACA500 is but it might be some of the hacks added to the TF1260 to make the mediator work smoothly that caused it. It does resampling of DSACK in the ZII range because the fall times from Mediator are up to 15ns appart. i.e. it can look like a byte ack when its really a longword.