• Hello, Guest! Welcome back, and be sure to check out this post for more info about the recent service interruption and migration.

Converting Acard AEC-7722 to AEC-7726

weedeewee

Member
Well, I somehow managed to make one adapter unresponsive.
It was either by jumpering the SE & RSV.4 jumpers at the same time,
or jumpering RSV.1 .
the behavior afterwards is, the device no longer is detected, yet also does not cause the scsi host to timeout on the detection,ergo it's stuck.
When id.3 is jumpered (device id 8 set), the host still does not find a device, yet the bus detection proceeds without problem.
I'm going to take the eeprom off and verify the contents just to be certain it's not somehow a firmware fault.
 

feipoa

Member
I have definitely run into a non-responsive conditions like that; I think mostly with rev 1.5 PCBs. Were you successful in sourcing the PLCC32 sockets? It should save hassle with soldering/desoldering. I personally think soldering on the socket is easier than soldering on PLCC directly with an iron. There is only one small socket corner which needs to be dremeled down to make clearance.
 

weedeewee

Member
Ok
Forget about the jumpers messing up the adapter,
I just took off the eeprom,
verified the contents,
tested the adapter without eeprom, was identified as "ARC765E3 BadExtRom 16K"
soldered the eeprom back on
and it works again.
much rejoicing !
 

trag

Well-known member
Ok
Forget about the jumpers messing up the adapter,
I just took off the eeprom,
verified the contents,
tested the adapter without eeprom, was identified as "ARC765E3 BadExtRom 16K"
soldered the eeprom back on
and it works again.
much rejoicing !

That's good news.

Are you two finding that after putting the 7726 firmware on the 7222, that the ID8 is stuck on the resulting board?

That is, all SCSI addresses are 8 + settings. And if no SCSI ID jumpers are installed the boards are showing as ID8.
 

weedeewee

Member
That is, all SCSI addresses are 8 + settings. And if no SCSI ID jumpers are installed the boards are showing as ID8.
No, haven't noticed anything like that. and I just did a test with the three adapters, that I have, hooked up to a 2940UW, one hdd, one msata-ide, one sd-ide, ID zero, one and two. able to do simultaneous linear read at 10MB/s each.

Allthough, while the board was somehow unresponsive, once the third id bit (8+) was set it no longer hogged the scsi bus and detection would continue. I found that to be quite odd and the fact that taking the eeprom off, getting the device seen on the scsi bus with the eeprom off, putting the same eeprom without chances back on, (ok I added some solder to the solderpads) and having the device working again...
I would expect the same badextrom device id to be shown if somehow the eeprom had a bad connection and gave bad data to the main chip, yet.. that didn't happen.

you know what, I'm going to do a test with one device on id eight, one on zero, and the other on one.
 

trag

Well-known member
@weedeewee Looking forward to your results.

I'm using 7726 firmware 1.73Q in my tests, mainly. Sometimes 1.69Q.

On both Rev. 1.5 and 1.8 I see SCSI ID 8 stuck after conversion.

I test all board with an optical drive before conversion, and SCSI IDs were proper -- as the jumper settings indicated -- before the conversion.

I'm using an Adaptec PowerDomain 29160

I'm not sure I've tested with the SCSI ID 8 jumper installed. I wonder if that would take it back to ID 0....
 

weedeewee

Member
@weedeewee Looking forward to your results.

I'm using 7726 firmware 1.73Q in my tests, mainly. Sometimes 1.69Q.

On both Rev. 1.5 and 1.8 I see SCSI ID 8 stuck after conversion.

I test all board with an optical drive before conversion, and SCSI IDs were proper -- as the jumper settings indicated -- before the conversion.

I'm using an Adaptec PowerDomain 29160

I'm not sure I've tested with the SCSI ID 8 jumper installed. I wonder if that would take it back to ID 0....
All seems fine, using ID 0,1 & 8 at the same time.

I'm using the same firmware 1.73q. The only thing that maybe is different is that the first read I did of the original eeprom showed me 32K of data, which seemed to be the same 16K firmware twice, so I did the same with the 1.73q and programmed the eeprom with two consecutive copies.
 

weedeewee

Member
I'm also thinking of a mod, that would add a jumper to address line 17 of the eeprom, and thus allow for the base address to be set at either 0 or 256k. This would allow easy switching between firmware as in, set the hard drive firmware at base 0, and the cdrom firmware at base 256k
At the moment I believe that should work.
 

feipoa

Member
trag, I've always had my SCSI ID's set to ID 5 v1.8 and v3.0 have shown a HDD on ID #5. I'm waiting for some Winbond EEPROMs to test v1.5 with HDDs. I don't want to overwrite my CD-ROM flash at this time.

weedeewee, that is really interesting about having the flash data repeat itself. Looking forward to the results from your jumper hack. Wouldn't the checksum get in the way?
 

weedeewee

Member
feipoa,
The data repeating itself was something I saw in the original eeprom.
There being two copies of the same firmware in the eeprom.

The checksum getting in the way depends on what amount of data the checksum is actually calculated on. The firmware download is only 16K.
Testing will have to wait until I get the plcc sockets, since it will involve disconnecting a pin between socket and pcb, routing the pcb pad and socketpin together with a pullup resistor to a three pin jumper, to select either normal pcb-socket or pin pullup, which would translate to either the first firmware image at the beginning of the eeprom, or a secondary image located at another location in the eeprom.
 

MrFahrenheit

Well-known member
Are those the folks that changed their name to just geeks.com later. And then closed up about five or ten years ago? I got lots of great stuff from them back in the day. Sigh.



One wonderful virtue of your adapters is that one knows they're terminated. I hate shopping for SCSI adapters because, who can tell?

I guess one should assume they contain no termination, unless they specifically mention it. But I also remember seeing some SCA-50 pin adapters that claimed they were terminated and had no circuitry on them at all.

Sorry to inject here so late in the game.

In regards to these u160/320 adapters, I have found very few actually work with u160/320 drives on the Mac. The ones made by a member here worked great. If not available, the ones here are also verified to work on my Macs:


Those are SCA80 to 50 but in case someone is looking for a solution, those do work, too. I haven’t tried any 68 to 50 pin adapters with termination because I don’t have any drives that are 68 pin.

When I tried my Acard with a simple 68-50 plug, the device I plugged in (Fujitsu ATAPI Magneto Optical drive) was not seen at all. I abandoned that attempt to get it working on my Macs after that.
 
Top