BlueSCSI v2 Pico - Low cost, open hardware, fast SCSI device!

François

Tinkerer
Aug 9, 2022
79
37
18
France
Maybe it’s just because the (too long?) ribbon câble of the SD extender is unshielded and thus picking up all sorts of interferences?
 

retr01

Senior Tinkerer
Jun 6, 2022
2,469
1
778
113
Utah, USA
retr01.com
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?
 

Paolo B

Tinkerer
Nov 27, 2021
242
137
43
Nagoya, Japan
Maybe it’s just because the (too long?) ribbon câble of the SD extender is unshielded and thus picking up all sorts of interferences?
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.
 

Paolo B

Tinkerer
Nov 27, 2021
242
137
43
Nagoya, Japan
where did you order your SD extender from?

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.
 

retr01

Senior Tinkerer
Jun 6, 2022
2,469
1
778
113
Utah, USA
retr01.com
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?
 

Paolo B

Tinkerer
Nov 27, 2021
242
137
43
Nagoya, Japan
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?
I honestly have no clue, it goes beyond my knowledge, I would need to study the specifications of the SD card standard.
 

fourteentones14

New Tinkerer
Oct 6, 2022
9
4
3
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!
 

Androda

TinkerDifferent Board Secretary 2023
Staff member
Sep 25, 2021
455
496
63
USA, Western
androda.work
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 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.
 
  • Like
Reactions: Fizzbinn and retr01

fourteentones14

New Tinkerer
Oct 6, 2022
9
4
3
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 Does Not Compute

Active Tinkerer
Oct 27, 2021
212
341
63
www.youtube.com
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.
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!
 

RetroTheory

Tinkerer
Oct 17, 2021
77
118
33
Some cool things are possible with SCSI target mode and bluescsi, here I have no drive at all in IIsi, both the HD and the CD image are mounted over target mode from my powerbook 180.
VideoCapture_20230608-234912.jpg
 

Attachments

  • 20230324_143952.jpg
    20230324_143952.jpg
    1.4 MB · Views: 55
  • Like
Reactions: eric and Androda

eric

Administrator
Staff member
Sep 2, 2021
822
1,305
93
MN
scsi.blue
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.

**Full Changelog**: https://github.com/BlueSCSI/BlueSCSI-v2/compare/v2023.04.10...v2023.07.03
**Discussion**: https://github.com/BlueSCSI/BlueSCSI-v2/discussions/48
**How to Update**: https://github.com/BlueSCSI/BlueSCSI-v2/wiki/Updating-Firmware

# Highlights

## New!

* Hardware: 2023_03a version of Centronics 50 Pin #24 - @androda
* Support for Atari ST ICD extensions #36 - @mynameistroy
* Validate Macintosh Disks #43 - @erichelgeson
* .bin/.cue support - @PetteriAimonen @saybur [CUEParser](https://github.com/BlueSCSI/BlueSCSI-v2/tree/main/lib/CUEParser)
* Various CD and Image Set fixes - @saybur @PetteriAimonen (see full changelog)
* Various CD SCSI commands and fixes - @saybur @PetteriAimonen (see full changelog)
* Monitor board supply voltage and warn if voltage drops too low. @PetteriAimonen https://github.com/BlueSCSI/BlueSCSI-v2/commit/6dd37e3f42a09aee0778ecb39ed306d422af8d22
* Log voltage when booting for troubleshooting - @erichelgeson https://github.com/BlueSCSI/BlueSCSI-v2/commit/ba4b5012ab53d15401dc7bdbc53fc4e436f7b8b9
* Improved OMTI support @Kars-de-Jong https://github.com/BlueSCSI/BlueSCSI-v2/commit/d7ccb9048036036c627a8c0972ffee7ee154e4df
* Add X68000 preset @erichelgeson https://github.com/BlueSCSI/BlueSCSI-v2/commit/be6d1adbbd64fb7de436efdb82d0d95c823124e8
* Add rudimentary support for tapes - @Kars-de-Jong https://github.com/BlueSCSI/BlueSCSI-v2/commit/cc3587d96af4e73f0f55a8c30d6d716e80e30f02
* More tape command implementations: Erase, Seek, ReadPosition, Write, ReadBlockLimits, WriteFilemarks (dummy result), Verify (dummy result) - @PetteriAimonen https://github.com/BlueSCSI/BlueSCSI-v2/commit/a75508c93da2d0ca1290a83be1580aec5bfefeb3, https://github.com/BlueSCSI/BlueSCSI-v2/commit/ea15cd2f25ad9021d4d4404948e4bb090deb12d4

## Fixes!

* Parity is properly ignored when Parity=0 #30 @mynameistroy
* Fix crash when using ID7 @erichelgeson https://github.com/BlueSCSI/BlueSCSI-v2/pull/43/commits/c26d4841df43d6040afc07ff6a81024a2194573a
* Set Inquiry standard version based on EnableSCSI2 setting @PetteriAimonen https://github.com/BlueSCSI/BlueSCSI-v2/commit/6b13c942f17393b71e6308479677768b6499e82a
* Fix crash when switching between FAT and exFAT formatted cards. @PetteriAimonen https://github.com/BlueSCSI/BlueSCSI-v2/commit/65a4566e0dcdff51ce4814fa5f007d08b2e5a0c8
* Add support for 2GB SD cards @PetteriAimonen https://github.com/BlueSCSI/BlueSCSI-v2/commit/66c1e47d298c273faec8458317ec60f7f0bb889c
* Fixes hard coded block sizes in multiple locations. #47 - @erichelgeson

## Chore!

* Update to [email protected] platform https://github.com/BlueSCSI/BlueSCSI-v2/pull/43/commits/ccb2295a13ec9d82def564160c408112cfb8b855 @erichelgeson

## New or changed config params

* `Parity` is now `EnableParity`
* `BlockSize` - allow block size to be overridden at the ini level
* `DisableConfigHook` - skip any defined Configuration Hooks

---

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!)
 

eric

Administrator
Staff member
Sep 2, 2021
822
1,305
93
MN
scsi.blue
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:

  • SCSI Bus Reset Button (probably mostly unused)
  • Switchable Termination (termination is always on)
This DB25 model must be placed at the end of your SCSI bus, but that's probably where people were putting them anyway.

Old vs New:
image

Actual Picture Of Development Process:
image
 

Androda

TinkerDifferent Board Secretary 2023
Staff member
Sep 25, 2021
455
496
63
USA, Western
androda.work
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.
 

JDW

Administrator
Staff member
Founder
Sep 2, 2021
1,285
1,136
113
53
Japan
youtube.com
Many thanks to @JDW (and others) for pushing us a bit harder on the design :)
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...

1691194799652.png

Great job!

I look forward to seeing that the 3D printed case designs will look like.
 

eric

Administrator
Staff member
Sep 2, 2021
822
1,305
93
MN
scsi.blue
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!)