Thread
SCSI2SD Project - anyone interested ?
I just tested a Kingston 2Gb card (unknown class), and it's about 50% faster than the class 10 16Gb I started testing with. Lido7 reports 600kb/sec write.
The first batch of devices has been shipped :b&w: I have one assembled device left.
I've uploaded utilities for updating the firmware over USB, and for setting configuration parameters over USB here. The configuration tool includes the magical "--apple" option, which sets the parameters to fool Apple Drive Setup.
For those who ordered devices, you will need to update the firmware before using the config tool. Run "bootloaderhost /path/to/SCSI2SD.cyacd", wait for the prompt, and then connect the USB cable. Run as root on Linux. Seems to work fine on Windows without running an Administrative Console. I don't have a Mac OSX machine to compile or test on. Al of thel required files are available via the download link above. I'll start working on a basic user manual tomorrow to explain how this works.
I've uploaded utilities for updating the firmware over USB, and for setting configuration parameters over USB here. The configuration tool includes the magical "--apple" option, which sets the parameters to fool Apple Drive Setup.
For those who ordered devices, you will need to update the firmware before using the config tool. Run "bootloaderhost /path/to/SCSI2SD.cyacd", wait for the prompt, and then connect the USB cable. Run as root on Linux. Seems to work fine on Windows without running an Administrative Console. I don't have a Mac OSX machine to compile or test on. Al of thel required files are available via the download link above. I'll start working on a basic user manual tomorrow to explain how this works.
Why not do an SD card raid array.. since you have so many extra pins?
OOOOOOH!!!!!!!!!!! Striping across a few cards ought to increase throughput tremendously. :approve:
That was my plan with my 2 Slot Acard if I can get it working. :-/
That's not going to happen, IMO. Dual slot devices on the Mac SCSI chain appear as a single volume. Mac SCSI doesn't do LUNs; if you want RAID, you need two separate devices.
This is not necessarily a barrier to using two or more SDs on a device for which one is developing new firmware. Either the device stripes the SDs itself, and presents a single volume to the Mac (faster, simpler) or it could present two slots as separate SCSI IDs and let the Mac do software RAID (slower and more complex).
This is not necessarily a barrier to using two or more SDs on a device for which one is developing new firmware. Either the device stripes the SDs itself, and presents a single volume to the Mac (faster, simpler) or it could present two slots as separate SCSI IDs and let the Mac do software RAID (slower and more complex).
I was thinking along the lines of the former, but using the extra I/O lines and consecutive reads of multiple cards to fill the que to the point that the converter is waiting for data to funnel through the Mac's SCSI bottleneck vs. vice-versa.
Guessing a second proc a/o some cache might be necessary, but it's hard for me to describe, imanoob. :-/
Guessing a second proc a/o some cache might be necessary, but it's hard for me to describe, imanoob. :-/
Indeed that is what I meant as well.. "hardware raid" the mac should still only see one drive.
FastSCSI2SCSI2SDFew? ;D
Hard Disk Speedtool from Intech 3.6 support SCSI RAID on Mac's, but I think it has to be a PowerMac. Not sure. You would have to check their site.
Mine arrived last week and it's been great. I've been using it on a Quadra 800 and a Mac II. I know nothing is ever fast enough, but I haven't had any complaints with the speed. I installed 7.1 in a couple minutes, no problems. This has been pretty neat, thanks a bunch mmcmaster!
I got the PCBs I ordered and the parts to build one should be coming from digikey in the next couple days. Hopefully I'll be able to assemble one. The fine pitch of the processor is a bit intimidating, but I figure I'll give it shot.
I got the PCBs I ordered and the parts to build one should be coming from digikey in the next couple days. Hopefully I'll be able to assemble one. The fine pitch of the processor is a bit intimidating, but I figure I'll give it shot.
I might route out some 2.5" versions of these. What do you need to program these processors? Can i build a programmer?
On another note. I think the bases have been covered. Diy scsi. Diy floppy. Diy keyboard/mouse interface. Only thing left now is diy networking. Like localtalk to ethernet. Or a pds ethernet
On another note. I think the bases have been covered. Diy scsi. Diy floppy. Diy keyboard/mouse interface. Only thing left now is diy networking. Like localtalk to ethernet. Or a pds ethernet
DIY Mac :lol:
Any JTAG programmer compatible with the ARM 10-pin 0.05" connector should work.
You've already started working on an'030 PDS ethernet solution.
The Duo modem/power card is the perfect form factor to shoot for and application for prototyping. You can patch wire the necessary signals from a Floppy MicroDock docking connector's solder cones to any convenient interboard connector lashup. Just bolt the connector assembly up to the bottom plastics of your mangled MicroDock and you can hook conveniently sized protoboard up to the connector for testing both direct and bridged '030, '040 and PPC PDS configurations using 230/270c, a 280 or a 2300c Duos. That will cover just about every NuBus architecture Mac and PowerBook. After that's up and running, it will be time to condense your functional ethernet electronics to a size/shape to cover all other PB modem form factors.
PDS slot cards for most desktop will be a piece of cake after that.
Finally, development for Killy Clipped Compact Macs and Luggable PDS 68000 versions can commence . . .
. . . or something to that effect. }
yeah I totally forgot about that thread. and project for that matter
. . . add ROMs and stir. [] ]'>
] ]'>
Well, I assembled a board by hand (no baking, just soldering iron) and aside from possibly inhaling some of those super small capacitors, it looks fine, no observable shorts, and continuity tests seem fine.
I'm trying to use a Segger jlink2 with a 20pin to 10pin adapter to program the USB_bootloader. I've got a jlink2 compatible gdbserver that sees the cypress processor and I can load the USB_Bootloader.elf, but doing so doesn't show up as a USB device on the computer, bootloaderhost and scsi2sd-config don't seem to recognize it.
I'm not sure if 'load' from gdbserver is actually programming the device (it appears to be...), or what exactly is going on. It could be my flashing process or there could be a problem with how I assembled the board, I'm not sure yet.
I'm trying to use a Segger jlink2 with a 20pin to 10pin adapter to program the USB_bootloader. I've got a jlink2 compatible gdbserver that sees the cypress processor and I can load the USB_Bootloader.elf, but doing so doesn't show up as a USB device on the computer, bootloaderhost and scsi2sd-config don't seem to recognize it.
I'm not sure if 'load' from gdbserver is actually programming the device (it appears to be...), or what exactly is going on. It could be my flashing process or there could be a problem with how I assembled the board, I'm not sure yet.
As long as you coughed the capacitors back up, you'll be fine. If they got lodged somewhere, if you ever get a CXR, tell them it's not TB or cancer, just encapsulated capacitors.
The load command does NOT write to the flash at all - I believe it just loads debug symbols etc into memory to allow debugging.
It looks like you need http://www.segger.com/jflash.html for writing the .hex file (not free, Windows only). Or perhaps you could try OpenOCD http://openocd.sourceforge.net/
Thanks. OpenOCD and jflash don't list support for Cypress or the PSoC5, so I ended up ordering the miniprog3. It should arrive in a few days and hopefully I'll be able to tell if I assembled this correctly.
JFYI, your parts.ods file lists the processor as CY8C5268AXI-LP047, and the PSoC creator file has the processor as CY8C5267AXI-LP051. Apparently it cares when it goes to program the device, it checks what is connected and then gets grumpy when they don't match.
I was able to change the device type in both the USB_bootloader and the SCSI2SD projects, rebuild, and theoretically reprogram (PSoC Creator and PSoC Programmer both reported successful erase, program, verify). However, it doesn't show up as a USB device on my machines, and scsi2sd-config doesn't see it. Neither does the bootloaderhost program.
I've verified continuity from the usb cable through the connector all the way to R4 & R5 for D+/D-, and verified the voltages at the decoupling capacitors of the PSoC (3x 4.83V and one 3.3V). Then verified continuity from R4 & R5 to the PSoC. I verified against the working one you built and sent me and it seems to match up.
Given that there's continuity of the D+/D- lines from the usb cable to the chip, and the chip is powered correctly, and the Cypress tools seem to think it has been flashed correctly, I'm not really sure what the trouble could be other than using the wrong processor, or my build of the sources for the different processor is wrong. Or the chip just isn't functioning correctly due to errors in my assembly, but as best I can tell it seems to be working from PSoC Creator's point of view.
I've verified continuity from the usb cable through the connector all the way to R4 & R5 for D+/D-, and verified the voltages at the decoupling capacitors of the PSoC (3x 4.83V and one 3.3V). Then verified continuity from R4 & R5 to the PSoC. I verified against the working one you built and sent me and it seems to match up.
Given that there's continuity of the D+/D- lines from the usb cable to the chip, and the chip is powered correctly, and the Cypress tools seem to think it has been flashed correctly, I'm not really sure what the trouble could be other than using the wrong processor, or my build of the sources for the different processor is wrong. Or the chip just isn't functioning correctly due to errors in my assembly, but as best I can tell it seems to be working from PSoC Creator's point of view.
Does anyone have one of these built for sale? There's no way I could build one myself.
I just received the CY8C5267AXI-LP051 and assembled a second SCSI2SD. Unfortunately, it's exhibiting the same behavior as the first. PSoC Creator and Programmer can both see the mcu, and program it successfully, but no USB device. I can modify the code to toggle the LED, so I know it is getting loaded and running, just no USB for some reason.
Does the cypress chip have anything like the fuses on an AVR, that need to be set separately from the code?
dougg3 had a similar thought. He found these chips have nonvolatile latches, but they don't seem relevant this particular problem, and from what I can tell, should be included in the hex files (which also encode the processor type and other metadata, not just the binary code).
This should make zero difference, except of course needing a recompile within PSoC Creator. The only difference between the two chips is unused resources.
The USB problem is most likely a dry solder joint. I have experienced many similar problems, where connectivity just does not work. Put the soldering iron on the USB pins of the PSoC for a few seconds, and try again. Repeat until it works.