Jump to content


  • Content Count

  • Joined

  • Last visited


About inertialcomputing

  • Rank
    Vendor The First

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

716 profile views
  1. Great question. We've contemplated how to possibly make this work, and the only safe way I can think of would be to provide pre-flashed SPI NOR on a separate PCB, which would then plug in/be soldered to P301/P302. Then, you'd just need to update your firmware. We have hardware here to be able to bulk flash SPI NOR at ~320 kilobytes per second, which is the maximum speed allowed for by the SPI NOR flash. With inexpensive, USD $30 equipment, you can flash blank SPI NOR at about ~125 kilobytes per second, but only once it's successfully been laid down on the PCB, and you've connected
  2. Unfortunately not, simply because the pin assignments between V5.0 and V5.2 are different, since the boards have different signal routing requirements. There's also nowhere to physically put the SPI NOR on V5.0. That said, it's entirely possible to make a version of V5.2 that's smaller form factor, much similar to V5.0, but no such thing is in development as of now.
  3. The pre-assembled ENC28J60 modules we have sourced are not 12 pin modules They look like this:
  4. You'd daisy chain them just as you would any two SCSI HDDs. The last one in the chain must have termination enabled (which is the default), the other must not, and they obviously must have unique/non-conflicting SCSI IDs. All that is accomplished with scsi2sd-util.
  5. The current testing I've done with DMA-enabled firmware read speeds show things maxing out between ~1.7 to ~1.8 megabytes per second, which is comparable to throughput of a 12X CD-ROM drive. The SPI interface to the SD card is in addition to that of the one that is used for the SD card. That's with the SPI interface clocked at about 50MHz.
  6. We've been working on the firmware to enable this for a while, and I'm happy to be able to lift back the curtain and show a working demo of it. Using yet-unreleased firmware, which is still under testing, we're able to boot from a pre-built image (any Apple-partitioned, HFS volume, up to 32 megabytes in size), flashed to serial/SPI NOR flash, which is directly laid down on the SCSI2SD V5.2 PCB. and use this as a read-only recovery/bootstrap environment. The SPI flash component itself is a Cypress (formerly Spansion) S25FL256SDPNFB000, which is a 32 megabyte (256 megabit) SPI NOR flash chip. Th
  7. SCSI2SD V5 firmware is very mature at this point, having been iterated and improved upon since ~2014. Around ten thousand V5.x boards are in use in the wild, and V5.2 uses that same firmware, so to somehow twist that in to "it's not ready yet, I should wait" is a bit laughable. V5.2 can do everything the previous V5 boards can, so judging it purely on the basis of future functionality seems...odd, at best. You shouldn't ever buy a product for features that don't exist when you make the purchase. That said, the pins on the Cypress PSoC 5LP microcontroller that is used in SCSI2SD V5
  8. It's soldered to the bottom of the board. That makes it one piece in my book, and to most rational people, I'd imagine.
  9. It definitely reduces versatility, but that versatility had unintended consequences when it came to noise immunity. V5.5 is way, way more portable, and most people are happy to use that.
  10. The number one requested feature, when V5.1 was designed by Michael McMaster, was a full sized SD card. LOTS of people hate hate hate microSD with a passion. We don't have anything against the form factor, personally, and find it a lot more environmentally friendly, given that more than half of a modern SD card is pure ABS plastic. While it's trivial to adapt from full sized SD to micro, it's not to go the other way around. I've considered making a variant of V5.5 in the V5.0b form factor. Would that be of interest?
  11. We are actually working on securing a Canadian distributor. While we can't do anything about the cost of shipping from the US, this is how we can improve the experience for Canadian customers. More to follow.
  12. Last week we took delivery of the first mass-production batch of SCSI2SD V5.2's, all of which are now assembled in Canada (with foreign components), with a new Markham, Ontario-based contract manufacturer. They produce a far-superior quality product, and the quality of their Printed Circuit Boards is a cut above what we've come to expect. We are very pleased with the results. From a user's perspective, on day one, the V5.2 isn't much different, functionally speaking, to that of SCSI2SD V5.1. It's a derivative design, and anything that works with V5.1 will work fine with V5.2. The m
  13. Please don't purchase SCSI2SD clones from Artmix; They are non GPL compliant, unlicensed clones of SCSI2SD, and Artmix is and has been distributing modified firmware without providing their changes. They've been approached multiple times, and all they are willing to provide is the compiled, binary blob for the board, which in no way makes them compliant with the GPL. In response, they claim _we_ are violating the GPL, which is 100% wrong. Buyer beware. Don't believe me? Ask Michael McMaster, the creator. Regardless of your opinions of Artmix, below is the prototype interposer we de
  14. Apologies, It's been a long month for us, with fallout from local wildfire, and an overall lack of time to do anything but fulfill orders. New employee starts Monday, which will shed an immense burden. We're have developed a SCSI2SD V5.5-based/derived solution, to replace the legacy V5.0 Powerbook Edition. Stay tuned.
  • Create New...