TF1260 Testing FW

[PainDictator]

Think we covered this. try putting a blank cf card in the internal IDE slot and see if that helps.

Helps

I can also confirm that the problem dissappeared after I have upgraded my ROMs to 3.2.2.

[CCRider]

Just watched Big Time on IT4 and it is fine.
Lovely high Res pics and dreamy AGA plasma.

If TFTools from the same archive is not working it suggests you don't have IT4 uploaded.

Maybe try again? Are you using a Raspberry Pi? Quite easy to be in the wrong folder and flash the wrong firmware.

All I have for flashing is a Xilinx USB Platform Cable (Chinese knockoff, of course). And boy, is it picky to get its software working...

Just so you guys know: I ended up getting a Pi Zero W, and flashed the newest firmware successfully.

[Ralph]

What program can I use to see what firmware is on my TF1260?

[supaduper]

What program can I use to see what firmware is on my TF1260?

Sysinfo just click on the BOARDS option

[Lamaman1971]

Hi Folks, as we are into mid-july, with no further discussion around issues, I wanted to ask the firmware testers if IT4 remains a reliable choice?

[masterofdisaster]

For me Iteration 4 seems stable enough (Haven't tried IT1-IT3, went straight from alpha to IT4). Built-in IDE is much faster than on alpha. The Workbench feels much more responsive. The only incompatibility I personally came across is with Nexus 7 demo working only when booted without startup-sequence, in that situation according to Sysinfo CPU is detected as 68040 and FPU is off. Also ADOOM seems to stutter a lot more than before. I run my 060 Rev6 at 66MHz if that matters at all.
Other than that seems to be stable for me. I have not tested the IDE port on tf1260 though. I am running AmigaOS 3.2.2.1 with it's corresponding Kickstart version.

[Lamaman1971]

Thanks! It seems to have resolved some niggling WHDLoad issues for me too.

[masterofdisaster]

The adoom slowdowns seem to happen when game is accessing CF drive. I always thought that the game preloads the whole wad file into ram upon startup but that seems not to be the case.

[LL2k23]

I was having issues using my Xilinx Platform Cable (the "Programming Properties" dialog on iMPACT insisted in being blank, with no options), so I followed this article, about generating a SVF file before programming the flash. Apparently, it just pretends to be writing...

Could it be that the CPLD is write-protected?

Back to square one, I guess... Sorry for taking your time.

Same here too, no Programming Properties on Impact after binary choice, using DLC9LC USB noname programmer ... how did you solve that?

[CCRider]

Same here too, no Programming Properties on Impact after binary choice, using DLC9LC USB noname programmer ... how did you solve that?

By going the RPi way...