exxos's DFB1 trials

[Steve]

I wasn't thinking it'd reboot or anything. I was thinking hddriver.prg would load and go 'oh, I'm already loaded' and quit gracefully. But yeah I don't have any reason to doubt you, maybe it does 're-load' itself into fast ram. There *is* a noticeable speed benefit so it's probably best to just run an xferate test in each situation to see if it's actually happening as you say. That'd be more conclusive test than setting folder cache.

[Badwolf]

I'm confused as to what the aim is with this double-loading a TSR, TBH. If it's to experiment with 'load into TT-RAM', then try my patched TOS in flash. It declares TT-RAM early and even provides an FRB (not that stock HDDriver uses it on the Falcon -- that's what AB40FIX did).

BW

[Rustynutt]

I'm not up to date on your patched TOS.
If it loads TT RAM when the DFBX initializes, then yes, HD Driver would run from TT RAM (flags set), without having to rerun it from the auto folder. Of course, goes without saying :)

Still pretty far back, thought "we" were still using an auto folder program to load TT RAM. Wasn't that called MAPROM or something? I've tried to keep up with the threads/post.
That was the whole reason for this conversation. So the point is really moot :)

Just for giggles, tested that on the AB040, after initializing the MMU, and it indeed loads TT RAM into the system.

The benefits, if you believe bench marks, is kind of like the performance you get from running a RAM disk in TT RAM.
There is also a throughput performance, but it's been a while since looking at benchmarks.

The only reason I've went on about it, is it's just been a practice I've always done.
On my setup with the NOVA, it's limited to 4mb ST RAM, and that gets ate up quick.

And yes Steve, I use V7.93, and it doesn't complain no matter how many times it's launched. Noticed that V12.XX (?) does do exactly what you are saying, it says driver already loaded. Never really looked into it. Uwe made so many changes after V7.93, I gave up. The latest version is great for configuration all sorts of new devices, that I don't use (and I use a lot!).

But with DFBX TOS loading TT RAM at boot, discussion closed :)

[Atari74user]

@exxos Am I right by thinking you have tested the DFBX1 without your clock patch? I appreciate it is recommended, but thought I saw that somewhere, I believe in this thread.

I ask as I installed the DFBX1 today for a quick play. I have yet to install your clock patch (V2 I think), but the DFBX1 or my Falcon was being grumpy. It got to the flashed TOS 4.04 logo, but didn't get any further. Of course everything works fine when disabling the DFBX1, and also when disabling Options to run at stock Falcon speed, just not at 40MHz. I did flash EmuTOS just to see if flashing was OK, which it was, and I can see ALTRAM is fine. So a good few ticks in boxes, just not with 40MHz at present, with either flashed TOS 4.04 or EmuTOS, although appreciate I haven't installed the clock patch yet.

[exxos]

My original fa!con doesn't have a clock patch but that doesn't mean anything with a sample set of one. Recap of the PSU, flash the new firmware, then clock patch would be what I would do.

[Atari74user]

I thought I had seen it somewhere, thanks, but yeah I appreciate the recommended prerequisites and your point. Cheers for that, time to tick off the to do list 👍

[exxos]

My ZIF sockets finally came. So did a bit more to my FPU test adapter today. Can't do much as hands hurting a lot again :(

Capture.PNG

[Rustynutt]

Nice :)

Pain with your hands suck. Makes what use to be fairly easy and fun, work.
Some days are "drop" days, everything you pick up falls from your hand.

OT, pulled a groin muscle over a week ago. Ontop of everything else, now think I'll have to pick up a cane.

[exxos]

I have updated the main website with a little bit of more info on known issues, this time with the MC68030 CPU in relating to operating voltage.

https://exxosforum.co.uk/atari/last/DFB1X/index.htm

Your Falcon PSU MUST output 5.00V minimum (5.10v - 5.20v is better) otherwise a lot of 030 CPUs will crash after about 10minutes. You can use this voltage adjuster mod if needed. Your PSU should also be recapped. This CPU issue should not be confused with thermal problems, but I always advise using the CPU with a heatsink anyway. Also note this problem of "voltage to low" happens whether the DFB1X is running at 40MHz or 50MHz.

I found this problem purely by accident. I was testing a new batch of 25 030 CPUs and now and then I would get one which failed. I did not think anything much of it at the time. But later on I started getting regular failures.

Long story short, the voltage on my power supply had dropped to 4.87V. This did not make sense because I had my voltage adjuster board should have been outputting 4.25V or thereabouts. Another long story short, I don't know why the voltage was so low, it was not the preset and the mod because I had poked it and smacked it around all over the place anyway. Turns out simply unplugging and plugging back in the DFB1X solved the low voltage problem. How the heck that is even possible I have no idea. So I retested every CPU at 5.20V and they now all passed.

So what is basically told me was that around 50% of CPUs would not run at 4.87V. Running them at 5.00V worked fine, but I generally run them at 5.2-5.3V to warm them up more during testing.

As to if this is specific to the DFB1X booster, or the CPU, I don't know. But I would assume that as most of the logic runs and 3.3 anyway, that it would be purely down to the CPU voltage.

Also note this problem does not matter if you run at 40MHz or 50MHz. It will not run at 4.87V either way.

So I thought I would document this because the whole thing has been rather weird. But indeed, anyone running a DFB1/X should probably make sure their power supply is outputting at least 5.00V otherwise you could potentially have stability issues which mimic a thermal problem but are actually not !

IMG_2212.JPG

[smoore100]

Is the installation of the DFB1 as simple as it sounds, just plugging in to expansion port and adding a heatsink?

If so, which of the two heatsinks in the store would be better, or at least a good compromise as I want to be able to put the lid back on the Falcon at some point?

The new Exxos PSU output was measured as 5.01 so should be ok there - I think.