-
Nominations will close December 20th. If you'd like to join the board and influence how TinkerDifferent runs in the next year, put your name in now!
I suspect it is more of a quality issue. Reading posts on various sites of people's experiences, it seems to be hit-and-miss when you order generic SD extender ribbon cables via Amazon, Alibaba, or AliExpress.
The SD extender from Adafruit should work, and Adafruit is more trustworthy.
@Paolo B, where did you order your SD extender from?
The SD extender from Adafruit should work, and Adafruit is more trustworthy.
@Paolo B, where did you order your SD extender from?
It’s a possibility, I put some cores around, but couldn’t notice any difference.
There are still some options to investigate: plain SD to SD Extender, using full size SD.
Cable I have was meant for the SCSI2SD, so micro SD to SD, I am using two adapters (full size > micro) at both ends.
Amazon, to my eye it looks totally identical to the one sold by Arduino.
What is “curious“ is that the original configuration is not seen by BlueSCSI, but works with my camera.
If you remove the resistor, the card is seen at start up, but it immediately crashes the system.
I wonder if BlueSCSI and BlueSCSI v2 expect specific voltage ranges in the data stream that the resistor is pushing down too low. Is a lower resistor needed?
Why do BlueSCSI or BlueSCSI v2 crash without the resistor in the SD extender?
Why do BlueSCSI or BlueSCSI v2 crash without the resistor in the SD extender?
I honestly have no clue, it goes beyond my knowledge, I would need to study the specifications of the SD card standard.
is BlueSCSI-Toolbox wrapped into the latest firmware? I can't seem to locate the transfer utility.
Not yet, there is one thing outside my control before I release it in the mainline firmware - soon!
Hi everybody!
I just installed my BlueSCSI v2 in my Powebook 100 and it works fantastic!
I just have one question: the powerbook version of the BlueSCSI is 40 pins, but the connector inside my PB 100 is 50 pins. I checked the schematic and the first 40 pins correspond to the pinout of the BlueSCSI, moreover the schematic shows the connector as 40pins while the one in the machine counts to 50. Of the remaining 10, three are connected to something and seven unconnected. Is this a particularity of the PB 100 or is this a standard configuration?
Thanks!
I just installed my BlueSCSI v2 in my Powebook 100 and it works fantastic!
I just have one question: the powerbook version of the BlueSCSI is 40 pins, but the connector inside my PB 100 is 50 pins. I checked the schematic and the first 40 pins correspond to the pinout of the BlueSCSI, moreover the schematic shows the connector as 40pins while the one in the machine counts to 50. Of the remaining 10, three are connected to something and seven unconnected. Is this a particularity of the PB 100 or is this a standard configuration?
Thanks!
I do think most or all of the 1x0 series powerbooks will have that 50 pin internal connector. It's for SCSI target disk mode, so the Mac can dynamically assign the SCSI ID of the internal hard drive for use with an external system. These drives use jumpers there at the back to set the SCSI ID, so the computer can just select the ones that are necessary.
BlueSCSI does not support drive ID selection via external pins due to the image-based drive configuration system. Drive ID is set in the filename.
Ahh yes it makes sense, I was thrown off because the schematic just shows the first 40 pins, probably it is split in two different places.
This is an interesting tidbit to learn -- I always assumed that the motherboard did some advanced ROM-level trickery to present a different SCSI ID to the host Mac than what the internal drive is set to. It's maybe even more clever that the motherboard simply changes the actual ID of the drive itself!
Lots of updates!
New release v2023.07.03 - https://github.com/BlueSCSI/BlueSCSI-v2/releases/tag/v2023.07.03
Thats a lot but one really neat thing I worked with @OneGeekArmy on is adding the ability to detect "bad" macintosh disks. If it's not a Mac Device Image or has the LIDO scsi driver it will warn you in the logs.
---
Jamies Hack Shack gets the BlueSCSI v1 and v2 working on Sun
--
US Sellers are running a promotion for your independence from experiences, closed hardware solutions! $5 off kits, $10 off assembled this week! (or build it yourself, we don't mind!)
New release v2023.07.03 - https://github.com/BlueSCSI/BlueSCSI-v2/releases/tag/v2023.07.03
Thats a lot but one really neat thing I worked with @OneGeekArmy on is adding the ability to detect "bad" macintosh disks. If it's not a Mac Device Image or has the LIDO scsi driver it will warn you in the logs.
---
Jamies Hack Shack gets the BlueSCSI v1 and v2 working on Sun
--
US Sellers are running a promotion for your independence from experiences, closed hardware solutions! $5 off kits, $10 off assembled this week! (or build it yourself, we don't mind!)
You spoke and we listened! We're happy to announce a 32% smaller DB25 design for the BlueSCSI v2 DB25!
Many thanks to @JDW (and others) for pushing us a bit harder on the design
Authorized sellers have stock coming or you can always build a few for yourself!
Thanks to @Androda for his skillful PCB design work!
From https://github.com/BlueSCSI/BlueSCSI-v2/pull/58
This is an updated DB25 design, based partially on user feedback.
PCB length has been cut from about 72.2mm to 49mm, a 32% decrease. The TopOfPCB.jpg image was updated to show the new design.
Two things were removed to achieve this new smaller size:
Old vs New:
Actual Picture Of Development Process:
Many thanks to @JDW (and others) for pushing us a bit harder on the design
Authorized sellers have stock coming or you can always build a few for yourself!
Thanks to @Androda for his skillful PCB design work!
From https://github.com/BlueSCSI/BlueSCSI-v2/pull/58
This is an updated DB25 design, based partially on user feedback.
PCB length has been cut from about 72.2mm to 49mm, a 32% decrease. The TopOfPCB.jpg image was updated to show the new design.
Two things were removed to achieve this new smaller size:
- SCSI Bus Reset Button (probably mostly unused)
- Switchable Termination (termination is always on)
Old vs New:
Actual Picture Of Development Process:
Looks like that picture of old and new DB25 side by side has the prototype version of the smaller DB25, oops. The version I pushed to GitHub (and which the sellers will have) includes an activity LED by the microSD slot.
I must say that size reduction is impressive. Your new v2 DB24 seems to be roughly the same size as the v1.1 DB25, as per my observation of Kay Koba's photo here...Many thanks to @JDW (and others) for pushing us a bit harder on the design
Great job!
I look forward to seeing that the 3D printed case designs will look like.
Not as exciting as Wi-Fi but here's a new release with a fix for the ROM drive and a new feature - ability to define a folder full of ISO's (such as `CD3`) and you will be able to cycle through them on eject. No more confusing ini files! (everyone hates ini files!)
github.com
Release v2023.08.10 · BlueSCSI/BlueSCSI-v2
How to update https://github.com/BlueSCSI/BlueSCSI-v2/wiki/Updating-Firmware What's Changed Implicit ImgDir by @erichelgeson in #52 Users no longer have to configure ini files for sets of CD imag...
github.com