exxos's Atari, Amiga & retro forum

Hello,

just received DFB1X card (thank you exxos for shipping to Germany again!) :D

But before I install it I have a few questions.

It looks like it has firmware v104 according to the sticker on the card. At the bottom of https://exxosforum.co.uk/atari/last/DFB1X/ there is a section "FIRMWARE V105 MODIFICATION" where it says that with v105 it is no longer necessary to remove the ROM chip from the motherboard when a small hardware modification is made.

Unfortunately I wasn't able to find a link to download firmware v105 in the "FIRMWARE / SOFTWARE / TOOLS" section, the last verstion available there is still v104.

Does anyone know were to get v105?

Or is it also possible to use the DFB1X with firmware v104 while keeping the ROM on the motherboard installed?

There is no release of the updated firmware yet unfortunately (**), so you will have to remove the motherboard ROM after flashing your OS in the flash.

(**) I think the firmware has actually gone up a couple more revisions, but I cannot remember offhand what the changes were .. But really need some BETA testers to do tests before I release the firmware publicly anyway...

EDIT:

You cannot run Flash and the motherboard ROM at the same time (other than when the DFB1X is disabled that is) because the blitter will trigger both the flash and the motherboard ROM at the same time upon access. So will end up with a bus conflict between the flash and the ROM if they are not the exact same version.

Thanks a lot for the quick response and the clarifications :thumbup:

So out with the ROM chip it is for now then ;)

I would be willing to help with beta testing new firmware, but if it still requires a special programmer to get new firmware installed I'd have to try to find one of these programmers first (and figure out if it can be used on Linux or macOS, since I don't have any Windows systems).

don_apple wrote: 13 Feb 2025 18:26 I would be willing to help with beta testing new firmware, but if it still requires a special programmer to get new firmware installed I'd have to try to find one of these programmers first (and figure out if it can be used on Linux or macOS, since I don't have any Windows systems).

I use one of these programmers but I did buy it a million years ago, there is probably alternatives by now... I think "USB blaster" might be one ? No idea about Linux or macs though will likely the other forum members can explain all that..

Though I would just get to grips with the accelerator before looking to update it anyway ;)

Waveshare do a far cheaper clone of the Xilinx "cable" which looks identical other than the branding.

stephen_usher wrote: 13 Feb 2025 19:59 Waveshare do a far cheaper clone of the Xilinx "cable" which looks identical other than the branding.

Do you mean this one: https://www.waveshare.com/platform-cable-usb.htm ?

Ooo is this a firmware bug carried over from DFB1? It's not intended you should remove the onboard ROM for the original, but just glancing at the verilog it does look like an external (blitter) access could trigger both. I may have to scope that.

Incidentally, as an alternative (especially if you use MAPROM), then simply disabling the flash with the jumper block at the top right will let you use the motherboard ROM exclusviely.

BW

Badwolf wrote: 14 Feb 2025 13:28 Ooo is this a firmware bug carried over from DFB1? It's not intended you should remove the onboard ROM for the original, but just glancing at the verilog it does look like an external (blitter) access could trigger both. I may have to scope that.

I don't recall what the DFB1 firmware did exactly. I think on the DFB1 only the CPU was allowed to access flash, which would cause the blitter to malfunction if used without NVDI etc. But on the DFB1X, blitter (or anything else) can access flash..

The "side effect" is the MB ROM needs to be removed. As blitter access will trigger the flash AND the MB ROM. Though there's a new fix which when the flash is disabled, or DFB1X is disabled (so you can program the flash) the MB ROM is enabled automatically. So you don't need to worry about it at all then.

The V105 firmware is the new firmware with the modded code, but I think I am on V107 now, can't remember why. Its a test firmware at this point so no official release until someone wants to try it. That is basically what confused the OP as he couldn't find the firmware.

exxos wrote: 14 Feb 2025 13:38 I don't recall what the DFB1 firmware did exactly. I think on the DFB1 only the CPU was allowed to access flash, which would cause the blitter to malfunction if used without NVDI etc. But on the DFB1X, blitter (or anything else) can access flash..

Ah, ok. So this is a known variation. I've been mistakenly running both with ROM installed in that case and might explains some of my recent EmuTOS crashes! :oops:

The intended and desired behaviour in DFB1 was no external access to flash ROM (except when the board is in client mode).

Since blitter can't access TT-RAM anyway I didn't see it not accessing flash as an issue (it would access onboard ROM instead. No problem if they're the same. If they're not the same? Don't use blitter.).

BW

Badwolf wrote: 14 Feb 2025 13:47 Ah, ok. So this is a known variation. I've been mistakenly running both with ROM installed in that case and might explains some of my recent EmuTOS crashes! :oops:

oops.. :lol:

Since blitter can't access TT-RAM I didn't see it not accessing flash as an issue (it would access onboard ROM instead. No problem if they're the same. If they're not the same? Don't use blitter.).

It's why anders did BLTFIX to solve the blitter with TTram issues should they arise. There is so much variation in software and how it can be run, I didn't want to risk any potential compatibility issues, more on a stock configuration, which could make it look like the blitter wasn't working and people start blaming the DFB1X for being "faulty". "swings and roundabouts" I suppose.

I've always said to removed the MB ROM once the user has flashed the flash. Not ideal, as if you wanted to flash again later, you would have to take the falcon to bits and refit the ROM again.. PITA! It's why I did the mod to switch the MB ROM in and out automatically, then is *should* be a win-win really..