PAK68/2 PCB Project ...

[frank.lukas]

I have seven PCBs left.

I can also offer a completely built up and testet card, ask for the Price ...

[IRIOS]

The package has arrived. Thank you !!
I would change for 32MHz operation and synchronized with the STE. To be continued ...

[frank.lukas]

Please make your Mods public ...

[IRIOS]

Yes of course !

[exxos]

Can someone benchmark the pak020 at 16mhz and 32mhz with GB6 ? http://www.exxoshost.co.uk/atari/last/GB6/index.htm

[frank.lukas]

PAK68/2 with VOFA ET4000 Graphiccard Adapter and the NOVA Driver (NVDI only as GDOS) ...

PAK_VOFA.gif

Code: Select all

GEMBENCH 6 
 9475
 2885
 3240
 5850
 7275
 9195
 5690
 7630
 32720
 21545
 8525
 12110
 8805
 11725
 64305
 0
 0
 0
 0
TOS 2.06  AES 3.20
BLiTTER NP
LineF FPU inst.
PLANES 8
COLOURS 0
RES 1024*768*256
NVDI 5.03 present
ST 68020
GEMDOS v0.20
CACHE D=OFF  I=ON
Ran from ST-RAM

PAK68/2 on a SM124 with nothing ...

PAK_MONO.gif

Code: Select all

GEMBENCH 6 
 10475
 10530
 11415
 15040
 10715
 6990
 5690
 7635
 32720
 21545
 4275
 6650
 8245
 14440
 0
 0
 0
 0
 0
TOS 2.06  AES 3.20
BLiTTER NP
LineF FPU inst.
PLANES 1
COLOURS 1
RES 640*400*2
NVDI not present
ST 68020
GEMDOS v0.20
CACHE D=OFF  I=ON
Ran from ST-RAM

... what about the FPU Test in GemBench 6 ?

[exxos]

... what about the FPU Test in GemBench 6 ?

Theres no reference files with FPU programmed yet. It will be fixed next release.

Might be better to use a reference file with isn't using the blitter, like one of the STFM files STFM1048.GB6 and run in medium res. Then we can see the 16mhz benchmark vs a stock machine.

The Falcon benchmark IIRC has a FPU benchmark in it, so you could try that also.. FALCON30.GB6

[frank.lukas]

PAKCOLOR.gif

Code: Select all

GEMBENCH 6 
 10415
 15930
 19350
 22180
 12330
 8395
 5690
 7620
 32710
 21540
 7465
 10600
 12160
 14435
 0
 0
 0
 0
 0
TOS 2.06  AES 3.20
BLiTTER NP
LineF FPU inst.
PLANES 2
COLOURS 512
RES 640*200*4
NVDI not present
ST 68020
GEMDOS v0.20
CACHE D=OFF  I=ON
Ran from ST-RAM

I have no Blitter in my Atari Mega ST ...

There was no STFM1048.GB6 File !?!

[exxos]

PAKCOLOR.gif


I have no Blitter in my Atari Mega ST ...

There was no STFM1048.GB6 File !?!

OK my bad, Looks like some files due for next release.. I've uploaded updated files..

http://www.exxoshost.co.uk/atari/last/GB6/GB6B22.zip

[frank.lukas]

PAKCOLO2.gif

Code: Select all

GEMBENCH 6 
 10415
 15930
 19350
 22180
 12330
 8395
 5690
 7620
 32710
 21540
 7465
 10600
 12160
 14435
 0
 0
 0
 0
 0
TOS 2.06  AES 3.20
BLiTTER NP
LineF FPU inst.
PLANES 2
COLOURS 512
RES 640*200*4
NVDI not present
ST 68020
GEMDOS v0.20
CACHE D=OFF  I=ON
Ran from ST-RAM

GemBench 4.03 ...

PSNAP2.gif

[exxos]

Thanks. Interesting results. It only just beats the STE booster at 32MHz, though integer division is a lot faster on the 020. Of course that 020 must access ROM at 32bit to beat 32MHz speeds at 16bit. Also the cache gives a small speed boost.

Will include that benchmark in the next GB6 release

[frank.lukas]

The PAK68/2 need a TOS 1.0x on the Mainboard for startup and uses a 32bit TOS 2.06 in four 27C512 on the PAK Board ...

[joska]

It works ...

Mine doesn't. Atleast I can't get it to boot. I have the same jumper settings as in your picture, and have also tried removing the FPU (and setting JP4). I have verified the ROMs and the GALs, and have confirmed that I have clocks (both 16 and 8MHz) at the 74F86 and the GALs.

I have no ROMs on the motherboard (and no MonSTer installed), just plain 2.06 on the PAK. I see that you also use 2.06 - how did you create the ROM images? Did you use the GFA ROMSPLIT program?

I use the following GAL files: U4_13, U5_14, U6_22 and U12_24. Any tips on what else to check before I dig out the logic analyser?

.. but it needs some patches.

Your picture is missing one patch that's present on mine (between the FPU and 68000 socket). Should it work without this patch too?

[frank.lukas]

You must have a TOS 1.0x on the Mainboard so the PAK68/2 with TOS 2.06 on the PAK can boot up ...

At my Mega ST I have the MonSTer with TOS 1.04 or KAOS TOS running to boot up TOS 2.06 on the PAK68/2.


I use from the Pinatubo package the rommix tool without any problems.

Code: Select all

# Kommandodatei fr ROMMIX:
# erstellen von 4 Eprom-Files fr 27C512
# 1 TOS206-IMG wird auf 4 Eproms aufgeteilt
# von Udo Overath @ KR
# (das geht auch direkt mit Pinatubo --- ms)

# Puffergr”že setzen
bufsize 256k
# Directory setzen
chdir e:\pinatu24\rommix\

load tos206.img 0 256k all -> 0 all
save ee.u11 64k <- 0 ee
save oe.u10 64k <- 0 oe
save eo.u9 64k <- 0 eo
save oo.u8 64k <- 0 oo

Edit the ROMMIX config File for your TOS Version.

I send all PCBs with the patches already done.

Hardware Patches ...

- IC4 /ROMSEL Pin_10 -> IC6 Pin_20
- IC4 A1 Pin_23 -> A1 68000 Pin_29
- IC6 /BERR00 Pin_22 -> 68000 Pin_22
- FPU D23 Pin_44 -> 020 Pin_L5 or 68000 CPU Pin 62

[joska]

You must have a TOS 1.0x on the Mainboard so the PAK68/2 with TOS 2.06 on the PAK can boot up ...

That really does not make sense, but I have tried that too without any success. I have also tried to disable PAK ROM and boot from 2.06 on the MonSTer.

At my Mega ST I have the MonSTer with TOS 1.04 or KAOS TOS running to boot up TOS 2.06 on the PAK68/2.

I really don't understand this. How does the motherboard TOS boot/start TOS 2.06? AFAICS an unpatched TOS 1.04/1.02/1.00 won't even start on the 020 since it's not aware of the 020 stackframe size. Also, it would need to run some program to execute the PAK TOS.

I use from the Pinatubo package the rommix tool without any problems.

Thanks, I will try this and see if the resulting files are different from mine.

'Hardware Patches ...

- IC4 /ROMSEL Pin_10 -> IC6 Pin_20
- IC4 A1 Pin_23 -> A1 68000 Pin_29
- IC6 /BERR00 Pin_22 -> 68000 Pin_22
- FPU D23 Pin_44 -> 020 Pin_L5 or 68000 CPU Pin 62

I will verify these, and also the rest of the components.

[frank.lukas]

Fact is that the PAK68/2 or the PAK68/3 need on the Mainboard a TOS 1.0x to switch to the 32bit TOS 2.06 (TOS 3.06 on the PAK68/3) on the PAK68/2 ...

In my Setup the PAK68/2 do not work with TOS 2.06 on the Mainboard.

With TOS 1.0x or KAOS or TOS 1.0x or KAOS selected on the MonSTer and a 32bit TOS 2.06 on the PAK68/2 all is fine ...


For TOS 2.06 on the PAK you need U12_21

When you program the GALs set unused Bytes to 0

[joska]

Fact is that the PAK68/2 or the PAK68/3 need on the Mainboard a TOS 1.0x to switch to the 32bit TOS 2.06 (TOS 3.06 on the PAK68/3) on the PAK68/2 ...

In my Setup the PAK68/2 do not work with TOS 2.06 on the Mainboard.

That is most likely because both the MonSTer and the PAK decodes the TOS 2 addresses. Does the PAK boot with no TOS installed on the motherboard? I.e. with flash disabled on the MonSTer and no ROMs in the Mega ROM sockets?

For TOS 2.06 on the PAK you need U12_21

Ok, I will try that. The docs say that this is for TOS at FC0000, but 2.06 (and 3 and 4) is at E00000 which the docs say that U12_24 is for.

[frank.lukas]

Ok, I will try that. The docs say that this is for TOS at FC0000, but 2.06 (and 3 and 4) is at E00000 which the docs say that U12_24 is for.

I know that, but U12_24 do not work ...

[frank.lukas]

Does the PAK boot with no TOS installed on the motherboard? I.e. with flash disabled on the MonSTer and no ROMs in the Mega ROM sockets?

No

... 6 or 2 TOS 1.0x Eproms must sit on the Mainboard or a TOS 1.0x must be selected on the MonSTer.

[joska]

Ok, tested so far...

- Generated new TOS split files with ROMMIX, they are identical to the ones I already created (with a simple STOS program). Popped the ROMs out again and verified them. All OK.
- Popped out the GALs again and verified them. OK.
- Tried U12_21 with 1.02 on the motherboard, no success.
- Verified the motherboard patches. OK.

I guess the next step is to dig out the logic analyser. That would probably have to wait a few days.

[frank.lukas]

I have build up three or four cards so far and all boards works very well. I do not know what can be wrong with your Board ?

... if nothing else goes, simple send me the Board !


Are the GALs OK ?

My China Programmer can not handle Header comments in the JED File.

For example I program this for U4 with all unused bytes set to "00" ...

Code: Select all

L0000 1111110111011101111111101111111111111111*
L0040 1111111011111110111111101111111111111111*
L0080 1011110101011011101001101111111111111111*
L0120 1111100101011111101111101111111110111111*
L0160 1011100101011111101111101111111111111111*
L0200 0000000000000000000000000000000000000000*
L0240 0000000000000000000000000000000000000000*
L0280 0000000000000000000000000000000000000000*
L0320 1111110111101111111111011111111111111111*
L0360 1111110111111110101111101111111111111111*
L0400 1111110111111110011111011111111111111111*
L0440 1111111111101110111111011111111111111111*
L0480 1111110111101110111111111111111111111111*
L0520 1111110101111110111111011111111110111111*
L0560 1011110111111110111111011111111111111111*
L0600 1111110111111110111111011111111111111101*
L0640 1111111011101101111111101111111111111111*
L0680 1011101110011110101111101111111111111111*
L0720 1011111110011010101001101111111111111111*
L0760 1111111011011110111111101111111111111111*
L0800 0000000000000000000000000000000000000000*
L0840 0000000000000000000000000000000000000000*
L0880 0000000000000000000000000000000000000000*
L0920 0000000000000000000000000000000000000000*
L0960 1011111111111011111110111111111111111111*
L1000 1111111111111111111010111111111111111111*
L1040 1111111111111011111011111111111111111111*
L1080 0111111111111111111011111111111111111111*
L1120 0000000000000000000000000000000000000000*
L1160 0000000000000000000000000000000000000000*
L1200 0000000000000000000000000000000000000000*
L1240 0000000000000000000000000000000000000000*
L1280 1111110111011101111111101111111111111111*
L1320 1111111011011110111111101111111111111111*
L1360 0111110111011110101111111111111111111110*
L1400 1111110101011110101111111111111110111111*
L1440 1111110111101110111111101111111111111111*
L1480 1111110111111110101111101111111111111111*
L1520 0000000000000000000000000000000000000000*
L1560 0000000000000000000000000000000000000000*
L1600 1111111111111111111111111111111111111111*
L1640 1111110110011111111111101111111111111111*
L1680 1111111101011110111111101111111111111111*
L1720 1111110101111110111111101111111111111111*
L1760 0000000000000000000000000000000000000000*
L1800 0000000000000000000000000000000000000000*
L1840 0000000000000000000000000000000000000000*
L1880 0000000000000000000000000000000000000000*
L1920 1111110101111110111111101111111111111011*
L1960 1111111101011110111111101111111111111011*
L2000 1111110101011110101111111111111110111010*
L2040 0111110101011110101111111111111111111010*
L2080 1111110110011111111111101111111111111011*
L2120 0000000000000000000000000000000000000000*
L2160 0000000000000000000000000000000000000000*
L2200 0000000000000000000000000000000000000000*
L2240 1111111011111111111111111110111111111111*
L2280 1111111111111111111111101110111111111111*
L2320 1111111111111111111111111011011111111011*
L2360 1111111111111111011111111110111111111111*
L2400 1111111111101111111111111110111111111111*
L2440 1111111110111111111111111110111111111111*
L2480 1011111111111111111111111110111101111111*
L2520 1111111111111111111111111111111111111101*
L2560 0110010100000000000000000000000000000000*
L2600 0000000000000000000000000000000000000100*
L2640 1111111111111111111111111111111111111111*
L2680 11111111111111111111111101*
CBEFF*
0000

[joska]

GALs are OK. I have programmed the same GALs for other projects and they work correctly. I will try again with the files you attached.

The only things I haven't checked so far is the CPU (I only have one) and the board itself.

[joska]

I will try again with the files you attached.

They made no difference.

[joska]

Does the PAK boot with no TOS installed on the motherboard? I.e. with flash disabled on the MonSTer and no ROMs in the Mega ROM sockets?

No

... 6 or 2 TOS 1.0x Eproms must sit on the Mainboard or a TOS 1.0x must be selected on the MonSTer.

But does it boot with ROMs on the PAK, no ROMs (or MonSTer) on the motherboard and U12_24?

[frank.lukas]

But does it boot with ROMs on the PAK, no ROMs (or MonSTer) on the motherboard and U12_24?

No

Maybe U12_24 is for KAOS TOS (TOS1.04) in four Eproms on the PAK68/2. I don´t know ...