First 5 now in store. https://www.exxosforum.co.uk/atari/store2/#0260 I again remind people that I cannot guarantee that it will work on everyone's Falcons "out of the box" but that is the ain, and indeed there will be firmware updates where you need to be reasonably competent and know ho...

Been doing some more testing and I think 40MHz is just going to become the "norm" currently. Though I don't think this is the bottom line of it all. If I remember rightly the TTRam is effectively access that 25MHz Badwolf ? Either way I don't think it would be necessarily running at the fu...

While trying to decide whether to stick with NVDI 2.51, I compared 2.51 to 5.03 using GEMBench. It appears that 5.03 is a little slower than 2.51.NVDICMP.png I do believe that 5 is a bit slower than 2.5 IIRC. Though if I remember rightly WARP9 is faster still, but has more compatibility problems. S...

stephen_usher wrote: ↑Thu Jun 29, 2023 10:32 am What benefit does the FPU have in normal (games etc.) software have?

None really. Think only BadMood may use it ?

Let's try and keep politics off the forum please

I did a quick test to not speed up the CPU on FPU access and got 281% in GB6. For reference: CPU & FPU 40MHz = 248% CPU & FPU 50MHz = 311% CPU 16MHz, FPU 50MHz = 281% So I guess the FPU is effectively running at about 45MHz :shrug: Though while this could possibly "trick" 40MHz CPU...

I'm starting to think all the 030 cpus have been reprinted as the latest mask. According my my google-foo people claim earlier masks can only do up to 40mhz. Though it's seemingly a thermal issue with the CPU as a fan blowing over it helps. But not enough for stable operation. Mostly it fails on FPU...

Does anyone know if it's possible to read the CPU mask via software like on the CT60 ?

You could try GB6 and see if you get drifting results over time. It uses the 200hz timer tick for the results calculations.

mikro wrote: ↑Wed Jun 28, 2023 9:43 am @exxos oh, now it occured to me: isn't possible that you got confused that this is a RMW cycle? I.e. it's not a write per se, it's an OR against the hardware register.

Hmmm I'll have to check the timings diagram but I'd assume write would still actually go low ?