DFBX1 Issues

[Steve]

@VadimK you need to find a 5v test point... There is both 5v and 3.3v on the DFB.

[Badwolf]

@VadimK you need to find a 5v test point... There is both 5v and 3.3v on the DFB.

Quite!

It should be clearly labelled and the one below the 030 should be the 5V one (you would also have 5V on the oscillator socket), but do double check!

Probably the biggest drop I'd expect to see would be half a volt. If it genuinely is 3.3V, I don't think you'd boot at all!

EDIT: I looked a picture of DFB1X & it's J4. [J5 has the labelling slightly off -- that's the 3V3 one]

BW

[VadimK]

Quite!

It should be clearly labelled and the one below the 030 should be the 5V one (you would also have 5V on the oscillator socket), but do double check!

Probably the biggest drop I'd expect to see would be half a volt. If it genuinely is 3.3V, I don't think you'd boot at all!

EDIT: I looked a picture of DFB1X & it's J4. [J5 has the labelling slightly off -- that's the 3V3 one]

BW

Yep, I was measuring wrong thing. On J4 there is 5.002V.

BTW I bought my Falcon recently, and I’m not sure if the PSU has been recapped. Is there a way to verify if this has been done?

[Steve]

@VadimK Take some good pictures of your PSU caps and the bridge rectifier. We might be able to tell. But it's good that the DFB1X is getting over 5v.

[charon030]

I thought, I'd share my trouble I had with the DFBX1, maybe someone else will find this useful someday..

After installation, I always got many bombs during the boot process. I had no idea what was going on and thought something is wrong with my clock patch or something else. PSU was re-capped. The flash was disabled.

But then I had an epiphany that HDDriver since version 11 or so supports the blitter to speed up hard disk accesses. Of course I enabled that feature at the time... Turning usage of the blitter in HDRiver off (with the DFB1X removed) helped and the board started to work like a charm.

Another issue was that it wouldn't boot when enabling the flash and removing the TOS ROM chip. I think that was caused by a flash that was not pre-programmed with TOS (even though stated on the product page). So after flashing myself, this also worked.

Thanks for that really great piece of hardware!

[exxos]

@charon030 Thanks for the report. Yeah I can imagine blitter will be unhappy with drive access, probably its running in TTram and then the blitter can't access TTram and it dies. I will add that info to the known issues page..

[charon030]

Hi again,

I think my post might have been incorrect regarding the flash. I mixed the 40/50 MHz jumper with the bank select jumper..

However, now that I discovered this, I realized that the board doesn't boot when the Flash is enabled and the board is set to 50 MHz. 40 MHz with Flash enabled works fine, 50 MHz with Flash disabled works fine, too.

50 MHz with Flash enabled results in TOS showing the logo and getting stuck, e.g. while printing the "Memory Test" on screen. EmuTOS is also freezing early in the boot process.

Is this a known issue? I'm running the latest firmware 1.05. The voltage measured on the DFBX1 board is 5.18V, which is pretty much the highest value I still feel comfortable with.

Thanks
Matthias

[exxos]

Are you removing the motherboard ROM ? Or soldering on the bodge wire with firmware V105 ?

Also if you reflashed with conflicting ROM's then you could have corrupted the flash while programming.

[charon030]

The motherboard ROM is still there and I added the cable to R213 to disable the output enable of the ROM, as shown for Firmware 1.05.

[exxos]

The motherboard ROM is still there and I added the cable to R213 to disable the output enable of the ROM, as shown for Firmware 1.05.

That should be fine then.. There's no reason for it not work that I know of. I suggest do a erase and re-flash of both banks to make sure your flash is good. Also make sure the flash jumper is making good contact.