Is the PPS 2000 040 accelerator compatible with AmigaOS 3.2

[amigamania]

I recently purchased one of this cards but I am having a difficult time having it boot to 3.2 Workbench.

I am using the MMULibs method and configured MMU-Configuration with:

"SetCacheMode from 0x08000000 size 0x01C00000 Copyback Valid
AddMem from 0x08000000 size 0x01C00000".

MemModes displays 0x01C00000 instead of 0x01E00000 as some folks have mentioned that works for them but not for me for 30mb and it does not display in MemModes.

I have tried the first 2 memory statements mentioning 0x08000000 range and 0x08400000 ranges but at boot it throws out a software error regarding ENVARC: so I combined the two first statement from 0x08000000 to 0x01C00000 and at least it displays a PFS-III Error Requester message regarding SetPatch (suspend/reboot)with a blank Workbench screen that never loads.

I know the PPS 2000 040 card is recognized in the Early Boot Menu under Expansion Board Diagnostics provided 2mb is auto-configured. If I set Auto-Configure Disabled with a full 32mb the A2091 is not recognized in the Expansion Board Diagnostics. I have 32MB or 4MB x 8 non-parity installed. Any insight on what works with 3.2 is appreciated. I really do not want to downgrade to 3.1 or 3.1.4 if that's what it will take.

The PPS 040 manual states it does work with A2091 so I'm not understanding where the problem is unless its 3.2 or the BetterWB overlay.

My A2630 BigRam never has had an issue with A2091 regarding 3.2 BetterWB.

Amiga B2000 Rev. 6.2
3.2 Kickstart rom
AmigaOS 3.2 / BetterWB
ACE2b - 2MB chipmem
A2091 (7.0 roms, set to 0 mem) w/ SCSI2SD v6 32MB SD card
ZZ9000/ZZ9000AX


The PPS 2000 040 is to replace my A2630 BigRAM 112MB (works great but wanted my 2000 faster)

[amigamania]

Update: I tried 3.1 rom and AmigaOS 3.1 to no avail. Same result. Been reading some blogs and and one comment from TheBajaGuy stated , and I'm paraphrasing from my bad memory, that a GuruRom provides a a full mask within a partition of 0x7FFFFFFF. And that when AddMem is used there are potential for problems when anything other than GuruRom is used on your SCSI controller. I believe he stated the A2630 works around the masking issue because its completely autoconfiged. So sounds like I need a GuruRom for my A2091 for the PPS 2000 040 to work with SCSI and replace my v7.0 roms.

[SpeedGeek]

The A2091 with v7.0 ROMs should use the same mask as the Guru ROM. Mask was a kludge for old SCSI drivers which did not restrict DMA to MEMF_24BIT memory. It only affects the filesystem unless the filesystem doesn't support mask. So it was never a complete solution because SCSI direct (HD_SCSI CMD) will bypass the filesystem.

[SpeedGeek]

Originally Posted by amigamania

I know the PPS 2000 040 card is recognized in the Early Boot Menu under Expansion Board Diagnostics provided 2mb is auto-configured. If I set Auto-Configure Disabled with a full 32mb the A2091 is not recognized in the Expansion Board Diagnostics.

This is a hardware bug. Auto-Config disabled on the PP&S040 should not prevent the A2091 from working.

[Thomas Richter]

Originally Posted by amigamania

I recently purchased one of this cards but I am having a difficult time having it boot to 3.2 Workbench.

I am using the MMULibs method and configured MMU-Configuration with:

"SetCacheMode from 0x08000000 size 0x01C00000 Copyback Valid
AddMem from 0x08000000 size 0x01C00000".

MemModes displays 0x01C00000 instead of 0x01E00000 as some folks have mentioned that works for them but not for me for 30mb and it does not display in MemModes.

First, let us check what exactly we have here. So, please provide an output of "ShowConfig" from the operating system once the memory has been added.
Then, please post an output of "MuScan" (from the Mulib distribution on Aminet) to see whether the memory is correctly added.

Originally Posted by amigamania

I have tried the first 2 memory statements mentioning 0x08000000 range and 0x08400000 ranges but at boot it throws out a software error regarding ENVARC:

That is not precise enough unfortunately to say anything. Could be that the memory is somewhere different, or could be that loading failed.

Originally Posted by amigamania

so I combined the two first statement from 0x08000000 to 0x01C00000 and at least it displays a PFS-III Error Requester message regarding SetPatch (suspend/reboot)with a blank Workbench screen that never loads.

Are you sure that this is memory that is on the board, and that it is not autoconfiguring? The entire range I mean? Please only add memory were the board really has memory, and not for memory that is already in the system. Again, ENVARC: is probably requested after setpatch being run, thus, this does not look like an improvement.

Originally Posted by amigamania

A2091 (7.0 roms, set to 0 mem) w/ SCSI2SD v6 32MB SD card

Which ROM is on this board? If it is the original bootROM, it may not work as the 32-bit RAM on the accelerator is not reachable through DMA, and the 2091 is a DMA device. The original ROM is not aware of 32-bit RAM. In such a case, you can get away by installing the harddisk properly: Add a mask of 0x00ffffff and a BufMemType of 513. This requests
single-block transfer outside of the Zorro-II area, and will request Zorro-II 24-bit DMA capable memory. HDToolBox in the file-system settings allows such modifications.

[amigamania]

Originally Posted by SpeedGeek

This is a hardware bug. Auto-Config disabled on the PP&S040 should not prevent the A2091 from working.

That sounds horrible ):

[SpeedGeek]

Originally Posted by amigamania

That sounds horrible ):

Since, you already tried using a 3.1 ROM then you have eliminated OS3.2 as the cause of your Auto-Config problem. You can try re-seating any chips in sockets. Cleaning the edge connector. Recheck your jumper settings, etc.

[amigamania]

Originally Posted by Thomas Richter

First, let us check what exactly we have here. So, please provide an output of &amp;quot;ShowConfig&amp;quot; from the operating system once the memory has been added.&lt;br /&gt;<br />
Then, please post an output of &amp;quot;MuScan&amp;quot; (from the Mulib distribution on Aminet) to see whether the memory is correctly added.&lt;br /&gt;<br />
&lt;br /&gt;<br />
&lt;br /&gt;<br />
That is not precise enough unfortunately to say anything. Could be that the memory is somewhere different, or could be that loading failed.&lt;br /&gt;<br />
&lt;br /&gt;<br />
&lt;br /&gt;<br />
Are you sure that this is memory that is on the board, and that it is not autoconfiguring? The entire range I mean? Please only add memory were the board really has memory, and not for memory that is already in the system. Again, ENVARC: is probably requested after setpatch being run, thus, this does not look like an improvement.&lt;br /&gt;<br />
&lt;br /&gt;<br />
&lt;br /&gt;<br />
Which ROM is on this board? If it is the original bootROM, it may not work as the 32-bit RAM on the accelerator is not reachable through DMA, and the 2091 is a DMA device. The original ROM is not aware of 32-bit RAM. In such a case, you can get away by installing the harddisk properly: Add a mask of 0x00ffffff and a BufMemType of 513. This requests&lt;br /&gt;<br />
single-block transfer outside of the Zorro-II area, and will request Zorro-II 24-bit DMA capable memory. HDToolBox in the file-system settings allows such modifications.

&lt;br /&gt;<br />
&lt;br /&gt;<br />
&lt;br /&gt;<br />
Thomas,&lt;br /&gt;<br />
I'm uncertain at this time on the rom version of the PPS 040 board at this time. I made the HDToolBox changes you suggested changing mask to 0x00ffffff and BuffMemType to 24BitDMA (I hope that's what 513 refers too). These changes do get me a little further but i still have an instability issue at boot without startup-config. However when I am able to get to the AmigaDOS prompt i still get a Write-Protected DH0 or No Disk Present prompt after reboot when I am able to run the BuildMMUConfig.rexx. In some instances after MMU-Configuration file is created and I do an "Ed" to review the file it errors and states the file contains Binary and I am not able to view its configuration. I have the PPS 040 board jumpered for 32mb. Is it possible that there is a conflict between the PPS board and the SCSI2SD? Unfortunately I do not have another storage method such as IDE for testing with the PPS 040 board and MuLibs. Attached are showconfig, muscan, and memmodes Prep.

[amigamania]

I have re-imaged my SD card multiple times starting from scratch to configure the memory. I have tried 30mb (2mb ZII) and 32mb ram I keep getting "No Disk" errors making the sd card useless. Is it possible the PPS 2000 040 Accelerator card is defective and some how corrupts the image. Has anyone had a defective accelerator that is non-auto-configured? Is there anyway to test an accelerator card? I have tried to boot to my Diagrom v1.3 when both my PPS 2000 and my 2630 BigRam is inserted into the slot. But the PPS only boots to a yellow screen. The 2630 boots to a cyan/red screen (I've been using my 2630 for 1 year so I know it functions when inserted). When I remove any of the two accelerators it boots to the Diagrom test selection screen. I'm at a loss regarding my PPS 2000 040 accelerator. Any troubleshooting tips are appreciated. I do not have a second B2000 for testing.


Is it possible the PPS does not like SCSI2SD. I've tried v5 and v6 with same no disk error. I wouldn't think the accelerator would detect storage type as long as it accepts the A2091, in which the user manual states it is compatible with the A2091. I always configure the SCSI2SD with the SCSI2SD Utility v5 or v6 application prior to booting the Amiga.

I use SanDisk 32mb cards. Are there better "more reliable" or Amiga approved SD cards?

[Jope]

The SD cards would need to be SCSI2SD approved, if there was an approval like that. The Amiga doesn't come into it at that point, as the SD interface is not really exposed to the Amiga.

You mention using both the V5 and V6 SCSI2SD utilities. Do you have both versions of the SCSI2SD hardware also?

[amigamania]

Originally Posted by Jope

The SD cards would need to be SCSI2SD approved, if there was an approval like that. The Amiga doesn't come into it at that point, as the SD interface is not really exposed to the Amiga.

You mention using both the V5 and V6 SCSI2SD utilities. Do you have both versions of the SCSI2SD hardware also?

Yes I have both hardware versions. I use the V5 app on the V5 hardware and V6 app on the V6 hardware. I realize the amiga is unaware of the scsi2sd and only detects the A2091 scsi card. I guess Im asking is 040 hardware more sensitive to scsi2sd somehow i dont have issues with 030 accelerators and scsi2sd. I'm grasping at strawa at this point. Its just odd that trying to configure memory on the PPS would trigger a No Disk error after reboot. Or it could be coincidence and the SD card is to blame.

[Kin Hell]

Wasn't there a DMA patch for the A2091 cards? - needed at least 6.6 ROM or something like that...

http://aminet.net/search?query=2091+patch

There were speed ups of 50% & something to do with A2091's only addressing the first 16Mb of fast ram. I know the patches above are all before OS3.2 launch & these may not be of use.

RE SanDisk media.... Is yours genuine or from China? - Lots of anomalies if so. - Samsung Evo Media is more reliable if sourced reputably. - Have you tried other media?

[amigamania]

I haven't tried any patches yet as you mentioned but i may as a next step.i have pdone the following since my last post: I have tried three sets of 32mb ram (4mb×8 60ms non-parity, 4mb×9 60ms parity, 4mbx8mb 80ms non-parity). I purchased both an 060 adapter and an 060 processor and installed them on the card using the 060 mulibs library (currently still installed). I have tried 32mb, 30mb+2mb auto. I have tried romtagmem. The only thing i have not tried is downgrading to 2.04 as i do not have the ROM. Both 040 and 060 processors act the same as it never successfully loads to workbench as it freezes and crashes at the workbench screen but 99% of the time it displays memory errors and reboots itself until it displays No Disk error.