Page 1 of 28
Re: DoG's DFB1 Build
Posted: 17 Oct 2022 09:37
by markus0321
DoG wrote: 28 Aug 2022 17:59
viking272 wrote: 27 Aug 2022 22:06
Is that NetUSBee operational? Maybe grab UIP Tool?
Nope. It's not working. I got PARCPUSB but I still needed a program on the Falcon to get that going. But got it working with a Gotek.
I did a few tests with 50MHz. I also noticed that I'm running with an older jedec programmed on mine. So I have to reflash my Xilinx later on with 220507 and do tests again. The screen goes black when I activate flashROM so something wrong there. Does that depends on the older jedec/bad solder/flashROM chip broken? Since I have no FPU installed I get lower score in FrontBench I suppose? I haven't done a stresstest or run YARTT yet. But otherwise the rest seems as it should.
How did you manage to detect Alt-RAM in EMUTOS? I tried the latest EmuTOS nightly and it does not detect Alt-RAM? :-(
Re: DoG's DFB1 Build
Posted: 17 Oct 2022 10:58
by Badwolf
@DoG Sorry, I didn't see these posts first time around.
DoG wrote: 28 Aug 2022 17:59
The screen goes black when I activate flashROM so something wrong there. Does that depends on the older jedec/bad solder/flashROM chip broken?
Flash wasn't tested in the release version and I'm pretty sure wasn't working. It's actually something I'm still working on -- there seems to be an issue with EmuTOS detecting the TT-RAM. The latest 'not-release' version in the repository should have flash hard-wired to only use the bottom 512k (in case of a 1M chip being fitted) and I think has all the logic in place, but, like I say, I've been having problems with it and EmuTOS.
I think the flash is fine, but the RAM detection is hanging. If you flash TOS404 onto it, you should get ROM speeds over 200% in Gembench.
Since I have no FPU installed I get lower score in FrontBench I suppose?
No, FPU doesn't affect FrontBench, but running in VGA mode will (60Hz v 50Hz -- the intro sequence is shorter: 5/6ths the length!)
BW
Re: DoG's DFB1 Build
Posted: 17 Oct 2022 11:00
by Badwolf
markus0321 wrote: 17 Oct 2022 09:37
How did you manage to detect Alt-RAM in EMUTOS? I tried the latest EmuTOS nightly and it does not detect Alt-RAM? :-(
Are you seeing a problem with EmuTOS in Flash or EmuTOS.PRG?
I'm still trying to identify a problem with EmuTOS in Flash not being able to probe for TT-RAM properly resulting in a black (or white depending on VGA or RGB) screen on a cold boot.
Is that what you're seeing?
BW
Re: DoG's DFB1 Build
Posted: 17 Oct 2022 11:10
by markus0321
Badwolf wrote: 17 Oct 2022 11:00
markus0321 wrote: 17 Oct 2022 09:37
How did you manage to detect Alt-RAM in EMUTOS? I tried the latest EmuTOS nightly and it does not detect Alt-RAM? :-(
Are you seeing a problem with EmuTOS in Flash or EmuTOS.PRG?
I'm still trying to identify a problem with EmuTOS in Flash not being able to probe for TT-RAM properly resulting in a black (or white depending on VGA or RGB) screen on a cold boot.
Is that what you're seeing?
BW
No, that's not how I programmed EmuTOS and replaced the original eprom from TOS4.04 with EmuTOS.
It starts mormally only does not detect Alt-RAM and here I saw that it is detected and I did not guess that it can be loaded from emutos.prg
I have another bigger problem after activating Alt-RAM with maprom, icons on the desktop window disappear or get damaged.
Re: DoG's DFB1 Build
Posted: 17 Oct 2022 11:18
by Badwolf
markus0321 wrote: 17 Oct 2022 11:10
No, that's not how I programmed EmuTOS and replaced the original eprom from TOS4.04 with EmuTOS.
It starts mormally only does not detect Alt-RAM and here I saw that it is detected and I did not guess that it can be loaded from emutos.prg
Hmm, that's meant to work.
Can you try booting normally (assuming no TT-RAM detected), run YAARTTT, choose 'M' from the choice of 'S' or 'T' (I know) and put in a start address of 0x1000000 and and end address of 0x5000000 (for 64MB SDRAM) or 0x9000000 (for 128) does that run successfully?
(@mods: happy to take this to a different thread)
BW
Re: DoG's DFB1 Build
Posted: 17 Oct 2022 11:30
by markus0321
Badwolf wrote: 17 Oct 2022 11:18
markus0321 wrote: 17 Oct 2022 11:10
No, that's not how I programmed EmuTOS and replaced the original eprom from TOS4.04 with EmuTOS.
It starts mormally only does not detect Alt-RAM and here I saw that it is detected and I did not guess that it can be loaded from emutos.prg
Hmm, that's meant to work.
Can you try booting normally (assuming no TT-RAM detected), run YAARTTT, choose 'M' from the choice of 'S' or 'T' (I know) and put in a start address of 0x1000000 and and end address of 0x5000000 (for 64MB SDRAM) or 0x9000000 (for 128) does that run successfully?
(@mods: happy to take this to a different thread)
BW
I'm not at home now. But when I come back, I will check it, although it seems to me that I was running YAART and it showed no errors. I also changed the memory layouts several times for other ones, but it did not make any changes.
I have another bigger problem after activating Alt-RAM with maprom, icons on the desktop window disappear or get damaged.
Re: DoG's DFB1 Build
Posted: 17 Oct 2022 11:34
by Badwolf
markus0321 wrote: 17 Oct 2022 11:30
I have another bigger problem after activating Alt-RAM with maprom, icons on the desktop window disappear or get damaged.
Sounds like you have the blitter enabled -- the Blitter can't talk to TT-RAM. This would normally be disabled by EmuTOS when it detects TT-RAM, but... see problem 1 ;-)
BW
Re: DoG's DFB1 Build
Posted: 17 Oct 2022 11:43
by markus0321
Badwolf wrote: 17 Oct 2022 11:34
markus0321 wrote: 17 Oct 2022 11:30
I have another bigger problem after activating Alt-RAM with maprom, icons on the desktop window disappear or get damaged.
Sounds like you have the blitter enabled -- the Blitter can't talk to TT-RAM. This would normally be disabled by EmuTOS when it detects TT-RAM, but... see problem 1 ;-)
BW
Can you somehow disable the blitter in TOS 4.04?
I tried
https://github.com/agranlund/tftools/bl ... litfix.prg
but it doesn't work for me :-(
Re: DoG's DFB1 Build
Posted: 17 Oct 2022 11:50
by Badwolf
markus0321 wrote: 17 Oct 2022 11:43
Badwolf wrote: 17 Oct 2022 11:34
Sounds like you have the blitter enabled -- the Blitter can't talk to TT-RAM. This would normally be disabled by EmuTOS when it detects TT-RAM, but... see problem 1 ;-)
Can you somehow disable the blitter in TOS 4.04?
Ah, I thought you were using EmuTOS.
EmuTOS: it's a checkbox in the menus -- make sure you save your desktop aftewards.
TOS4: softblitting is not available, you have to use a replacment VDI. NVDI and fVDI are options [1].
BW
[1]
https://github.com/dh219/DFB/blob/main/DFB1/README.md
Re: DoG's DFB1 Build
Posted: 17 Oct 2022 12:08
by markus0321
Badwolf wrote: 17 Oct 2022 11:50
markus0321 wrote: 17 Oct 2022 11:43
Can you somehow disable the blitter in TOS 4.04?
Ah, I thought you were using EmuTOS.
EmuTOS: it's a checkbox in the menus -- make sure you save your desktop aftewards.
TOS4: softblitting is not available, you have to use a replacment VDI. NVDI and fVDI are options [1].
BW
[1]
https://github.com/dh219/DFB/blob/main/DFB1/README.md
Well, sorry but I have not read this before ... :-(
Ok, probably the easiest way is to upload EmuTos. :-)
I have one more question, can I temporarily use 29F400 instead of 29F800? EMU TOS should fit in it, probably?