• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

Build A SCSI2SD V4.2

babelfisher

New member
I recently decided to try and make my own scsi2sd v4.2 from the project shared on github. I've managed to build 2 boards and flash a hex file to the cypress chip and then upgrade the firmware.
It's at this stage I've come unstuck. I have not been able to get the board to work on a compact mac, having tried several firmware versions and different combinations of both V3 and V4 versions of the software provided on github.
 
Both boards fail the self test on the configuration utility and I've now come to a dead end on where to proceed from here.
 
I was wondering if anyone could point me towards what might be an obvious problem or suggest a way to further troubleshoot the problem.
 
Thanks
IMG_4498.jpg

Log.png

 

saybur

Well-known member
When I had trouble doing this, I had to get into scsi2sd-util and hack in additional debugging to get more than the a terse "things didn't work" message. I don't have the modified versions I made, unfortunately.

To roll your own, in scsi2sd-util.cc there's a (myHID->scsiSelfTest() ? "Passed" : "FAIL") statement. I believe the value returned there is the same integer returned in the firmware's self-test, defined in scsiPhy.c, where certain bits are set if particular tests failed. You could change the line so instead of doing a pass/fail conditional it just writes the results of scsiSelfTest() to the console so you can check which bits are set.

In all cases with me the problems I had were with with bridged / dry pins on the main SoC. The 0.5mm spacing is tight and it's hard to see if there is a problem there, even using a loupe.

 

babelfisher

New member
In all cases with me the problems I had were with with bridged / dry pins on the main SoC. The 0.5mm spacing is tight and it's hard to see if there is a problem there, even using a loupe.


Thankyou that is a huge help. I'm going to go back and very carefully redo the SoC pins. 

Ive been looking for the problem on the software/firmware side. The problem occurred in both boards that I made and my thinking was that it would be difficult to repeat the same problem twice on both boards. 

I agree with you saying the SoC is tight, I might go as far as saying f$&@ing tight. 

 

techknight

Well-known member
Looking at your picture closely, you do have a handful of issues with the soldering of that CPU. 

you should use a flux pen, and then drag soldering with desoldering braid for cleanup. 

the ATMega128A1U is the same package, and I deal with those almost daily and have 0 issues with this method. 

 

babelfisher

New member
I just got both of them working. ;D

I must have removed and re-soldered the SoC 5 times on each board and I still kept getting the same error.

In total frustration I took one of the boards to the kitchen sink and gave it a good scrub with soapy water and a toothbrush.

You would scarcely believe it now worked.....not only that my second board also came good after a good scrub. 

5297246C-020E-4F32-AAD2-0F8F1790D377.jpeg

 

babelfisher

New member
Looking at your picture closely, you do have a handful of issues with the soldering of that CPU. 

you should use a flux pen, and then drag soldering with desoldering braid for cleanup. 

the ATMega128A1U is the same package, and I deal with those almost daily and have 0 issues with this method. 


I followed your advice and tried my flux pen and dragging the iron across the pins. It was definitely much easier and quicker than the solder paste and heat gun I had been using. 

 

techknight

Well-known member
I followed your advice and tried my flux pen and dragging the iron across the pins. It was definitely much easier and quicker than the solder paste and heat gun I had been using. 


Solder paste and heatgun method only works if you have a stencil for the PCB and you can apply the proper even amount of paste. just going willy nilly with the paste without a stencil is asking for a disaster. Something to keep in mind. 

 

cmao

Member
I recently decided to try and make my own scsi2sd v4.2 from the project shared on github. I've managed to build 2 boards and flash a hex file to the cypress chip and then upgrade the firmware.
It's at this stage I've come unstuck. I have not been able to get the board to work on a compact mac, having tried several firmware versions and different combinations of both V3 and V4 versions of the software provided on github.

Both boards fail the self test on the configuration utility and I've now come to a dead end on where to proceed from here.

I was wondering if anyone could point me towards what might be an obvious problem or suggest a way to further troubleshoot the problem.

Thanks
View attachment 30519

View attachment 30520
 
Last edited:

cmao

Member
I recently decided to try and make my own scsi2sd v4.2 from the project shared on github. I've managed to build 2 boards and flash a hex file to the cypress chip and then upgrade the firmware.
It's at this stage I've come unstuck. I have not been able to get the board to work on a compact mac, having tried several firmware versions and different combinations of both V3 and V4 versions of the software provided on github.

Both boards fail the self test on the configuration utility and I've now come to a dead end on where to proceed from here.

I was wondering if anyone could point me towards what might be an obvious problem or suggest a way to further troubleshoot the problem.

Thanks
View attachment 30519

View attachment 30520
As CY8C5267 is hard to find. What could be the alternative ? Thanks
 

cmao

Member
Not hard, impossible. Building SCSI2SD V3/4/5 is impossible. CY8C5267's and ALL other parts in the family are unobtanium, thanks to the global component shortages.
I know it is not hard to find CY8C5267 but the price is too expensive. I was ~$2 USD but is ~$200 USD. Do you know where to find one(s) with affordable price ?
 

Daniël

Well-known member
I know it is not hard to find CY8C5267 but the price is too expensive. I was ~$2 USD but is ~$200 USD. Do you know where to find one(s) with affordable price ?

If Rabbit Hole Computing knew, they would still be selling SCSI2SDs, as they are the main manufacturer of official SCSI2SDs. The fact that they are entirely out of stock, and ZuluSCSI was introduced to fill the gap, should tell you you're not going to find them for a reasonable price anywhere. The supply is dry, while demand is high.
 

rabbitholecomputing

Vendor The First
Not hard, impossible. Building SCSI2SD V3/4/5 is impossible.calc
I know it is not hard to find CY8C5267 but the price is too expensive. I was ~$2 USD but is ~$200 USD. Do you know where to find one(s) with affordable price ?
They're simply not available at any affordable price. Sure, if you want to pay twenty times what the CY8C5267 was historically worth, you can get them, but why?
 

tecneeq

Well-known member
26324543.png
Someone stole that Classics rainbow!

Congrats on washing your electronics into submission and function. :D

I have a SCSI2SD that is broken, once you put the SD card in, it hangs. You can program/update it via USB and all. I guess the socket for the SD card has a short.

In case anyone wants to salvage it for parts or try to repair the SD card socket i would part with it.
I would try myself, but i can barely see my own hands these days. :mad:
 

mg.man

Well-known member
The broken SCSI2SD goes to @mg.man
Arrived today - along with a couple of unexpected goodies - thanks @tecneeq! I'll definitely need to partake of one of the inclusions while wrangling with the SCSI2SD... my initial focus will be dealing with the uSD card connection. Hard to photo, but the two at the top left look a little 'lean' in the solder department...

20221110_151333.jpg
 

Chopsticks

Well-known member
I recently decided to try and make my own scsi2sd v4.2 from the project shared on github. I've managed to build 2 boards and flash a hex file to the cypress chip and then upgrade the firmware.
It's at this stage I've come unstuck. I have not been able to get the board to work on a compact mac, having tried several firmware versions and different combinations of both V3 and V4 versions of the software provided on github.

Both boards fail the self test on the configuration utility and I've now come to a dead end on where to proceed from here.

I was wondering if anyone could point me towards what might be an obvious problem or suggest a way to further troubleshoot the problem.

Thanks
View attachment 30519

View attachment 30520
seeing this post reminded me that I had built up one of these v4.2 boards a couple years ago but never flashed the firmware.
long story short I dug it out today after compiling and flashing and then updating the board to 4.8.4 I get the same scsi self test fail but it appears to work fine on the two mac's I tried it on..
 
Top