DFB1 Support thread

[markus0321]

Awesome. Could you post the binary please? I’ve not got a compiler set up on my Falcon yet. Is vbcc the one to use?

I compiled on windows under cygwin.
I can't compile it on my Falcon :oops:

[markus0321]

With HDDRIVER 11.13 it loads and freezes on screen as attached.


IMG_20221125_203709.jpg


Version 9.0 similarly only 4 bombs appear...


IMG_20221125_204430.jpg

You can’t also run MAPROM!

This will only work if HDDriver recognises TTRAM and adds the FRB. It’s an experiment, but it does MAPROM/FASTRAM’s job.

BW

I tested without MAPROM.
The system starts up but even with NVDI running there are graphic corruptions and when I move the mouse cursor to an item in the menu, bombs appear and the system freezes, other times it resets when hovering over the menu. :(

IMG_20221128_202237.jpg

[Badwolf]

I changed from 5 to 10 compiled and it works.
Now I have MX29F800 programmed with EmuTOS. :D :thumbup:

Lovely! Thanks for that. I'll get that updated.

Now I only need to try to figure out how to flash the top half of the chip!

BW

[Badwolf]

I tested without MAPROM.
The system starts up but even with NVDI running there are graphic corruptions and when I move the mouse cursor to an item in the menu, bombs appear and the system freezes, other times it resets when hovering over the menu. :(

That looks like blitter corruption, which would imply NVDI failed to start properly.

I've got NVDI + TOS404TT booted up here without that corruption.

IMG_6051.jpg

EDIT: here's the same boot but without NVDI. Looks familiar.

IMG_6052.jpg

BW

[markus0321]

I tested without MAPROM.
The system starts up but even with NVDI running there are graphic corruptions and when I move the mouse cursor to an item in the menu, bombs appear and the system freezes, other times it resets when hovering over the menu. :(

That looks like blitter corruption, which would imply NVDI failed to start properly.

I've got NVDI + TOS404TT booted up here without that corruption.


IMG_6051.jpg

EDIT: here's the same boot but without NVDI. Looks familiar.

IMG_6052.jpg

BW

Hmm.. I'll try with the second DFB1...

[Badwolf]

Hmm.. I'll try with the second DFB1...

Probably easiest to check if the NVDI cookie is set with SYSINFO.

BW

[markus0321]

Hmm.. I'll try with the second DFB1...

Probably easiest to check if the NVDI cookie is set with SYSINFO.

BW

I checked botting with ide and then it's ok. Apparently, even NVDI in this configuration can't boot properly from a SCSI disk.

IMG_20221128_211948.jpg

IMG_20221128_212139.jpg

[Badwolf]

Probably easiest to check if the NVDI cookie is set with SYSINFO.

I checked botting with ide and then it's ok. Apparently, even NVDI in this configuration can't boot properly from a SCSI disk.

Hold on, are you trying to solve the blitter issue or the SCSI issue ATM?

The blitter issue is because NVDI wasn't running (it's not in the first cookie list).

The SCSI issue, well that we need to get to but I don't see an _FRB cookie -- so can we conclude HDDriver isn't setting one up when it finds TT-RAM?

If we can, well we've proved the point. When _FRB is set up (by FASTRAM/MAPROM), then it's ignored anyway.

So: HDDriver bug report.

BW

[markus0321]

I checked botting with ide and then it's ok. Apparently, even NVDI in this configuration can't boot properly from a SCSI disk.

Hold on, are you trying to solve the blitter issue or the SCSI issue ATM?

The blitter issue is because NVDI wasn't running (it's not in the first cookie list).

The SCSI issue, well that we need to get to but I don't see an _FRB cookie -- so can we conclude HDDriver isn't setting one up when it finds TT-RAM?

If we can, well we've proved the point. When _FRB is set up (by FASTRAM/MAPROM), then it's ignored anyway.

So: HDDriver bug report.

BW

"The blitter issue is because NVDI wasn't running (it's not in the first cookie list)." >> Yes. NVDI won't boot from SCSI drive when Alt-RAM is active.

"The SCSI issue, well that we need to get to but I don't see an _FRB cookie -- so can we conclude HDDriver isn't setting one up when it finds TT-RAM?" >>
Yes indeed when I use TOS4.04 and hddriver it is missing _FRB

IMG_20221128_222244.jpg

EDIT:
But when I use the original TOS4.04 together with the MAPROM, the _FRB is visible in Sysinfo and there are still problems with the SCSI disk

[Badwolf]

Yes indeed when I use TOS4.04 and hddriver it is missing _FRB
But when I use the original TOS4.04 together with the MAPROM, the _FRB is visible in Sysinfo and there are still problems with the SCSI disk

I think this sums it up nicely. HDDriver is neither setting or observing an _FRB cookie. Good investigation. I'm afraid it's not in our hands now.

BW