Gold 2.7 release for the Vampire accelerators

[Sinphaltimus]

Perhaps when my power is restored (March 7th maybe) all of this will be worked out and I can try again. My report May not be needed by then.

[emufan]

Originally Posted by Sinphaltimus

My report May not be needed by then.

I'm sure you will make it work. report your findings, this will help and motivate others

[systmcrsh]

Originally Posted by emufan

can anyone try and report what you get using calculator with fpu disabled?

i tried it with the fpu disabled and got the correct result 6.5

[Seiya]

however, fpu implementation in 2.7 core is needed to run Quake and some Demoscene productions that require fpu also if this one is not very precise or accurate.

[emufan]

Originally Posted by systmcrsh

i tried it with the fpu disabled and got the correct result 6.5

thanks. above Alb42 explained already, how these libraries are working.
this all makes sense (no judging here) - so the vampire fpu needs some tweaking.

Originally Posted by Seiya

however, fpu implementation in 2.7 core is needed to run Quake and some Demoscene productions that require fpu also if this one is not very precise or accurate.

they did an terrific job implementing the fpu, this after all the discussions we had.
just remember the most recent cpu flaws (Meltdown/Spectre) - that should be of more concern.

[emufan]

ALB42 and Chain-Q did help to track down errors in the fpu:

flype  sagt: 
 3. März 2018 um 23:31 Uhr 
Ok, thanks ALB42 and Chain-Q for the inputs.
The Round() issue is now fixed in the next Vampire core.
MUIMapparium runs well now, both CPU and FPU versions are OK.

[emufan]

Originally Posted by Sinphaltimus

Second problem, sdnet doesn't work. That was the dealbreaker. [/url]

Henryk Richter released a new version of the sdnet.device

Henryk Richter - 05 Mar 2018 07:30

For anyone interested, an update to the SDNet package is available
here: EXTERNAL LINK  
I've made some timing adjustments and changed the default SPI clock divider to 2,
so that it works more reliably with x12 and x13 cores.

For x11 cores, I'd recommend to set SPISPEED to 1, as outlined in the README.

[alexh]

I am surprised the SPI core doesn't use a clock enable and a fixed rate tick to make it insensitive to clock speed changes.

[emufan]

I have no idea

#1) I found something useful for V600 V2 owners, those boards need a fix for Gold 2.7

What capasitors do I need to upgrade? What are their numbers on board?

C3 and C6.. NOTE that it's only needed for the V600 V2.

Best way to test if the mod is needed is to flash the 2.7 core.
If it doesn't boot then you need the mod. Alternatively measure
the cap values and if it's less than 22uf then needs to be modded

[TjLaZer]

After updating mine it bricked it with a red screen, but then I use the USB blaster and I got it to boot up! No caps mod needed.

Did they do a up to date registered compile for the 2.7 version? I registered my board last week right before they released the 600 version...

[emufan]

no update for 2.7 yet. nothing i'm aware of. you have that black/white screen now?
IIRC, the problem with V600 V2 may occure under certain circumstances,
disk access or something. screen flicker?! maybe depends on the resolution used.
I cannot remember exactly. so you may do some more tests.

[emufan]

Problem With SFS Partitions With Gold2.7:

The bug causes Workbench to display a second ghosted icon for the SFS partition
with the name "DHx:SFS\0"

This patch fixes a problem with SmartFilesystem 1.279 on a 68k Amiga with an 
exec.library newer than 45.20, such as those found in Cloanto's 45.6x ROMs.

http://www.doobreynet.co.uk/
http://www.doobreynet.co.uk/files/amiga/SFS_Fix.lha

[Sinphaltimus]

OK, so power has returned and there is so much new information out there with so many issues worked around and lot's of people sharing their experience. As promised I published my story of issues in the Apollo forums so rather than repost here, I'll just share the link. I feel lost in a sea of information right now so hopefully I can get the info I need in one place, here:

http://forum.apollo-accelerators.com...php?f=7&t=1872

[emufan]

thanks for the link. i'll follow what will be written over there

#1) yesterday Gunnar gave a link to a Gold 2.7 "SAFE" x10 core V600, which is worth a look too.

#2) above I wrote about a sdnet update.

#3) plipbox problem fix for Gold 2.7:

  It needs to be placed at ENVARC:SANA2/plipbox.config.
 Just add "NOBURST" as the top line of the file.

#4) SAGADriver.v1.1.lha - 2018-03-06

Changelog:
[1.1] (06.03.2018)
* Updated VampireGFX.card to 1.12
    - Adds Scanlines settings
    - Assumes SOFTSPRITE=YES by default if not set in tooltypes 
* Updated SDNet.device to 1.1
    - Fix for x12 cores
* Added VampireGFX tooltypes documentation

[grond]

It may be worth to point out that the project has reached a level of complexity where it is very hard to test and debug everything. The past few days have shown a few bugs that were not found before in a year of development and testing but could be fixed in a relatively short time. This has been very positive for the project.

[Djole501]

So it would be better to release publicly more often pointing out its a beta release.... Testing "in-house" is good but i can imagine, very slow. The users could decide for them self if they want to run the beta release or keep the production one....

[Sinphaltimus]

Originally Posted by grond

It may be worth to point out that the project has reached a level of complexity where it is very hard to test and debug everything. The past few days have shown a few bugs that were not found before in a year of development and testing but could be fixed in a relatively short time. This has been very positive for the project.

Absolutely agree - It's why I'm trying to provide as much detail as possible. I figure the more data the team can collect, the better...

[emufan]

Gunnar just anncounces 2.7.1:

GOLD 2.7.1 JIC is out

This new file gives color to all people which did register since the original 2.7 release.

what other changes are in the 2.7.1?

No changes in the core.

[Sinphaltimus]

Originally Posted by Sinphaltimus

OK, so power has returned and there is so much new information out there with so many issues worked around and lot's of people sharing their experience. As promised I published my story of issues in the Apollo forums so rather than repost here, I'll just share the link. I feel lost in a sea of information right now so hopefully I can get the info I need in one place, here:

http://forum.apollo-accelerators.com...php?f=7&t=1872

So far so good on my round 2 attempt:

http://forum.apollo-accelerators.com...2&p=2819#p2819

[emufan]

Originally Posted by Sinphaltimus

So far so good on my round 2 attempt:

good news. what else is missing/not working?

#1) as a sidenote: if you get a new version of Apollo/CoffinOS,
at least archive the standard folder on your boot partition, such as C: L: S: DEVS: LIBS: ...
so you saved the config files, which you may use on the new Coffin version