Hi,

It appears that the source code for the beta firmware version that supports the BlueSCSI Transfer Utility / Toolbox is completely missing. As the BlueSCSI firmware source code is distributed under the GPL 3.0, and the copyright is not entirely owned by the BlueSCSI team (as BlueSCSI is forked from and depends on code written by others), it is necessary for this source code to be available to comply with the terms of the GPL.

The binary firmware packages can be found at
https://github.com/erichelgeson/BlueSCSI-Toolbox/releases/tag/v20220927-BETA1 for BlueSCSI v1
and https://github.com/erichelgeson/BlueSCSI-Toolbox/releases/tag/beta2 for BlueSCSI v2.

While there are apparent links to source code on those release pages, they only contain a README.md file.

This is probably best resolved by uploading snapshots of the source code used to make those builds to the above release pages. This could also be resolved by including license text, attribution, and an offer for the source code in the release zips (which is already required per the terms of the GPL); and ideally on the release page as well.

Hi,
Trying to update from version 2023.01.25 to v2023.07.03 and got the file "err.txt":

[10ms] Platform: BlueSCSI Pico
[10ms] FW Version: 2023.01.25-release Jan 25 2023 08:22:29
Flash chip size: 2048 kB
[10ms] Bootloader version: Jan 25 2023 08:22:29 BlueSCSI Pico
[201ms] Found firmware file: BlueSCSI_Pico_2023-07-03_46af79d1.bin
[202ms] DBG Writing flash at offset 0x00020000 data 0x00 0xC0 0x03 0x20

++ MbedOS Fault Handler ++

FaultType: HardFault

err.txt
log.txt

Same error with version "v2023.04.10".

Then I tried to rollback to version "v2023.01.25" and seems to work again, see the log file with debug enabled.

Cheers,
Daniel

PS: Hardware version 2022.12a

On bluescsi.com this hardware is referred to as "open hardware" in several places, however the hardware license you are using is not considered an open hardware license because of the non-commercial clause. Please see the OSHWA definition here: https://www.oshwa.org/definition/ specifically criteria number five.

This requirement that commercial use is allowed is not specific to hardware. In fact the Open Source Definition and Free Software Definition both agree on this: https://opensource.org/osd and https://www.gnu.org/philosophy/free-sw.html#fs-definition

See also "Why isn’t a license that restricts commercial use considered a free culture license?" at the Creative Commons website: https://creativecommons.org/share-your-work/public-domain/freeworks/

and the definition of Free Cultural Works: https://freedomdefined.org/Definition

Some of the resistors for Desktop 50pin are missing values. The affected resistors are:
R1
R2
R3
R4
R5
R6
R7
R8
R9
R10
R33
R34
R35
R36
R37
R38
R39
R40

hi,
forgot to flash the pico before soldered it to the bluescsi v2 board. But now I can't get it to go into flashing mode by holding down the boot_sel. Is there any work around? or do I have to desolder the pico?

thanks in advance
eddie

Unlike v1, a 2Gb micro SD card is nolonger detected as valid - 5 flashes.
I have treied half a dozen different low capacity devices including: SanDisk 2 Gb, unmarked 2Gb, unmarked 1 Gb. It also fails to recognise a FujiFilm 128 Mb SD card.

The micro SD cards are detected as valid in V1 board.

I have tried 2 x 16 Gbmicro SD,: Kingston 16 Gb, and Sandisk 16 Gb both seem to work.

Peter

Generally when a BlueSCSI (v1 or v2) is connected internally and PiSCSI externally on the same machine I run into issues with behavior of the two together.

Q700 - BlueSCSI v2 + PiSCSI - Bad

Using the two devices together in this configuration and booting from the BlueSCSI results in very slow boot times and corruption of data on the BlueSCSI disk image. This blueSCSI I believe is running the latest firmware (v2023.07.03).

SE - BlueSCSI v1 + PiSCSI - Bad

In this case I was booting from the PiSCSI to install an OS on the BlueSCSI v1 images. The machine boots up fine from the PiSCSI but the BlueSCSI is completely inaccessible and doesn't show up. Running Apple SD HC to see the drives is very slow and only finds the PiSCSI devices. BlueSCSI log file reports it's seeing the images and operating normally. The BlueSCSI v1 is an earlier model and running an older firmware because it requires a programmer to upgrade (which I don't have).

Molar G3 - BlueSCSI v2 + PiSCSI - Fine?

Out of curiosity, I tossed one of the BluSCSI v2s in a gossamer Molar G3 and connected the PiSCSI up. I was booting from my IDE CF card, but I was able to see and interact with both devices in that case for whatever reason.

IIsi - SCSI2SD 5.1 + PiSCSI - Good

No issues in this case, only including to note that I've tested this as well.

PiSCSI Info for reference

• Which version of Pi are you using: 2b
• Which github revision of software: v23.04.01
• Which board version: 2.4a
• Which computer is the PiSCSI connected to: Mac SE, Quadra 700

Crosslinking the PiSCSI issue since I'm not sure which device is the cause: PiSCSI/piscsi#1202

EnableParity option is totally ignored.

EnableParity = 0

or

EnableParity = 1

Both have the same effect. Parity checking is permanently enabled.

RM kit is an 8 bit SCSI controller whaich does not support parity. There Parity checking needs disabling.

WIKI for V2 is very sparse - no information on BLUESCSI.INI configuration options. Nor details on what the various System types do.

Peter

I just got an external DB25 BlueScsi V2, and I found the 3D-printed case available in this repo a little too thin for my liking. I made a sturdier version based on the original stl files which works for me. This version keeps the idea of clickable buttons (which I found very neat), and also added little holes so you can see LED status. It is sturdier than the original, and is generally a little more polished. Happy to make a PR if you like it.

https://www.youtube.com/watch?v=jpjAizllZkU

Hi,
Firmware v2023.08.10, created the CD2 directory when it placed the ISO images. macOS created Spotlight index files.

When change the image in a vintage Mac, an index file is inserted.

Of course, Mac OS can't read such a "image" of the disk

After upgrading to firmware v2023.10.12 (https://github.com/BlueSCSI/BlueSCSI-v2/releases/tag/v2023.10.12) using the USB method, it is no longer possible to ping any other machines on the network from my Atari TT030.

Besides updating the firmware nothing else has changed in the setup, so I'm guessing one of the firmware changes that was introduced between the release of the Wifi beta and v2023.10.12 broke something that prevents the Wifi setup on the BlueSCSIv2 from working correctly.

Looking at the log.txt I've noticed that with firmware v2023.10.12 the entry showing that the connection to the WiFi network was successful is missing (with the beta it prints "Successfully connected to Wi-Fi SSID... " after the information about the voltage):

[1000ms] === Network Initialization ===
[1000ms] Unique board id: e6 61 38 52  83 81 86 35
[1863ms] Wi-Fi MAC: 00:80:19:52:83:81
[1863ms] Connecting to Wi-Fi SSID "<SSID>" with WPA/WPA2 PSK
[1880ms]  
[1880ms] Initialization complete!
[1895ms] INFO: Pico Voltage: 3.243V.
[21860ms] DBG BUS RESET

The bluescsi.ini only contains the settings required to enable WiFi Access (I've also added "Debug=1" as requested in the Troubleshooting section of the Wiki to get the debug output in the log.txt):

[SCSI]
Debug=1
WiFiSSID=<SSID>
WiFiPassword=<password>
# Optional - Each Pico-W will generate its own MAC address, so normally not needed.
# WiFiMACAddress=00:80:19:C0:FF:EE

I'm using the fully assembled BlueSCSIv2 DB25, Smaller Design from One Geek Army (https://shop.onegeekarmy.eu/index.php/product/bluescsi-v2-db25-smaller-design/) in case this makes any difference.

Attached are the log.txt from the working Wifi beta firmware, the log from the non working v2023-10-12
LOG_Wifi_Beta.txt
LOG_2023-10-23.txt

I'm trying to get a latest release v2 working with a SGI Indigo R4400.

For installing operating system 2 CDs are required so I need disk set. However the block size of SGI CDROM is 512, so it cannot boot from the CD. For Indigo and older SGIs 512 block size is hard requirement, they don't set the blocksize as newer systems do.

Is there any undocumented way to set block size for a set?

Congrats on your release - I think it is good to have a hobbyist-buildable design available. The support for Pico-W also opens up interesting possibilities.

You mention "Keeping the lineage of a project is important - who wrote what code, what changed when and where. We've restored the missing attribution and history for SCSI2SD, as well as kept the entire history of ArdSCSIno and BlueSCSI all in one repository."

I agree that I should probably have added SCSI2SD with full version history in the first place.

However, I think there may have been some mistake with this merge commit:
d789904

It seems to mix together a lot of unrelated commits:

• Hundreds of lines of code related to RP2040 acceleration developed by me
• Update of SdFat library, removed by the next commit
• Several smaller changes by @morio.

It is probably difficult to directly merge changes between the projects due to different file paths.
Maybe it would be possible to develop a script using git-filter-branch for the purpose?

At the very least, it would be helpful if the merge commit message could include attribution of where it is merging from and what commits are included.

Hello colleagues.

Have some Problems connecting BlueSCSIv2 (Pico W) with WifiBeta Firmware.

My Network is normal Router (AVM FritzBox 6490 Router, WLAN is 2,4 GHz 802.11b/g/n + 5 GHz 802.11ac )

Here is my bluescsi.ini:

`[SCSI]
WiFiSSID=CiTKA
WiFiPassword=secretcode

[SCSI1]
Type=0 ; Fixed
IMG0=HD10_512_PB180_MacOS761_RU.hda
IMG1=HD20_PB180_MacOS71.hda

[SCSI3]
Type=2 # CD-ROM
Dir2="/CD3"
IMG0=CD3_StuffIt_Dlx_551.toast

DisableROMDrive=1`

I always get Wi-Fi connection failed: -4 Error in the log.txt
log.txt

Can someone help me whats wrong?

The release notes for the latest firmware (https://github.com/BlueSCSI/BlueSCSI-v2/releases/tag/v2023.10.12) mention that "Initiator mode" is now supported, but there is no clear documentation on how to actually use this feature.

On the linked page (https://androda.work/bluescsi-initiator-mode-and-stock-update/) it mentions that two jumpers have to be set, but it doesn't mention anything about which jumpers those are.

Since that page also mentions "The first production versions of Desktop BlueSCSI which support Initiator mode are in manufacturing now.", does that mean that this feature will only work with new versions ofthe BlueSCSIv2 Desktop boards which will be available sometime in the future? Or will it also be possible to use it with the already existing BlueSCSIv2 boards?

Would be great if some information could be added in the Wiki (https://github.com/BlueSCSI/BlueSCSI-v2/wiki) describing the requirements and how to use this feature.

I am getting occasional write errors when I copy a number of files.

log.txt

[10ms] Platform: BlueSCSI Pico
[10ms] FW Version: 2023.04.10-dev Apr 30 2023 15:09:12
Flash chip size: 2048 kB

=== SD Card Info ===
SD card detected, FAT32 volume size: 7615 MB
SD Name: ASTC, MID: 0xFE, OID: 0x34 0x56

=== Global Config ===
Reading configuration from bluescsi.ini
Active configuration (using system preset "Generic"):
-- SelectionDelay: 150
-- EnableSCSI2 is off
-- Parity is disabled

=== Finding images in / ===
== Opening /HD10_512.hda for ID: 1 LUN: 0
---- Image ready
== Opening /HD20_512.hda for ID: 2 LUN: 0
---- Image ready

=== ROM Drive ===
Platform supports ROM drive up to 1692 kB
---- ROM drive SCSI id 1 is already in use, not enabling

=== Configured SCSI Devices ===

• ID: 1, BlockSize: 512, Type: Fixed, Quirks: None, Size: 31980kB
• ID: 2, BlockSize: 512, Type: Fixed, Quirks: None, Size: 63960kB

Initialization complete!
SDIO SD card error on line 413, error code 2
SDIO SD card error on line 413, error code 2
SDIO SD card error on line 413, error code 2
SDIO SD card error on line 413, error code 2
SDIO SD card error on line 413, error code 2
SdioCard::stopTransmission() timeout
SD card write failed: 0x00
SDIO SD card error on line 413, error code 2
SDIO SD card error on line 413, error code 2
SdioCard::stopTransmission() timeout
SD card write failed: 0x00
SDIO SD card error on line 413, error code 2

Thoughts / ideas please

Peter

I have a Wi-Fi extender on my network and when I connect one machine to that access point and another to my main router AP the two devices cannot see eachother over AppleTalk.

Once both are connected to the same SSID then file sharing works properly.

• Tried Timbuktu as well. Same result.
• Tested two separate Wi-Fi extenders. Same result.

Config example:
• IIcx on system 7.1 with MacTCP connected to "Living Room" SSID (Wi-Fi extender)

• Powebook on system 7.1 with OT connected to "Main" SSID (main router)

Devices cannot see eachother. Switch one to the same SSID and issue is resolved.

Hi,

I am currently trying to get the Ethernet functionality of the latest firmware (v2023.08.10) to work with the following configuration file:

BlueSCSI.ini

[SCSI]
WiFiSSID=france2
WiFiPassword=********
# Optional: If you have more than one BlueSCSI WiFi connected to
# the same network you will have to change your MAC address:
 
# WiFiMACAddress=01:23:45:67:89 # Default is 00:80:19:C0:FF:EE
WiFiMACAddress=00:01:45:89:67:20

After starting, MacOS 7.6.1 french + Opentrasport 1.3 can see the network interface, but the Mac (IIsi) can't communicate on the network (DHCP or static IP).
The log file from BlueSCSI is:

log.txt

[12ms] Platform: BlueSCSI Pico
[12ms] FW Version: 2023.07.08-dev Aug 10 2023 17:49:40
Flash chip size: 2048 kB

=== SD Card Info ===
SD card detected, exFAT volume size: 15189 MB
SD Name: SC16G, MID: 0x03, OID: 0x53 0x44

=== Global Config ===
Reading configuration from bluescsi.ini
Active configuration:

=== Finding images in / ===
== Opening /HD60-1GB-exchange.dsk for ID: 6 LUN: 0
---- WARNING: This drive contains the LIDO driver and may cause issues.
---- Image ready
== Opening /HD10-2GB.hda for ID: 1 LUN: 0
---- WARNING: This drive contains the LIDO driver and may cause issues.
---- Image ready
== Opening /HD00 - System-7.1-mini.dsk for ID: 0 LUN: 0
---- WARNING: This drive contains the LIDO driver and may cause issues.
---- Image ready
== Opening /HD20 - Sytem-753FR.dsk for ID: 2 LUN: 0
---- WARNING: This drive contains the LIDO driver and may cause issues.
---- Image ready
== Opening /NE4.hda for ID: 4 LUN: 0
---- Configuring as network based on image name
---- Image ready

=== ROM Drive ===
Platform supports ROM drive up to 1692 kB
---- ROM drive image not detected

=== Configured SCSI Devices ===
* ID: 0, BlockSize: 512, Type: Fixed, Quirks: Apple, Size: 102400kB
* ID: 1, BlockSize: 512, Type: Fixed, Quirks: Apple, Size: 2097216kB
* ID: 2, BlockSize: 512, Type: Fixed, Quirks: Apple, Size: 512000kB
* ID: 4, Type: Network, Quirks: Apple
* ID: 6, BlockSize: 512, Type: Fixed, Quirks: Apple, Size: 1048576kB

=== Network Initialization
Wi-Fi MAC: 00:00:00:00:01:45
WARNING: Wi-Fi MAC is not what was requested (%02x:%02x:%02x:%02x:%02x:%02x), is libpico not compiled with CYW43_USE_OTP_MAC=0?016913710332
Connecting to Wi-Fi SSID "france2" with WPA/WPA2 PSK

Initialization complete!
INFO: Pico Voltage: 3.265V.
Successfully connected to Wi-Fi SSID "france2"

On the computer, viewed TattleTech, the MAC address is good ($000145896720).

Same issue (same log.txt replace just "Wi-Fi MAC: 00:00:00:00:01:45" by "Wi-Fi MAC: 00:00:00:00::80:19") with the default MAC address.

Something to do on my side or is it a bug ?

Thank for help

Patrice

PiSCSI can emulate a Dynaport SCSI Network Card.

If BlueSCSI is used with Pico W, something similar could also work for BlueSCSI.

I have been fighting (literally) for days to get the POS Blue Scummy to work on a Macintosh Plus. Compared to just about anything else, this is the ultimate in half assed garbage.
Funny how you can plug in a Floppy Emu and it just works...
This isa high profit low quality joke,
Just to answer the "I'm stupid and we who made it are smart" questions.

Yes, I purchased from an authorized scammer.
eBay ID: jwg1 - It is a very crappy POS and has no return policy. A waste of $65.00

I downloaded ever single piece of shovelware listed on every page and updated the pico. This isn't my first rodeo.

I attempted to use the Blue Scummy v2 with 1MB, 2 MB, and two different sets of 4MB of ram just to see if it made a difference.
I also used two motherboards, an early 1986 board and a board from 1989 which was a factory 4MB version.

yes, I created the scummy ini file.

Anyone remember the old Mac commercial where they show an IBM and say "In order to use this, you'll need to read this" and a stack of three ring binders hit the table. Then they show the Macintosh and drop a little pamphlet,
Sad how the Blue Scummy idiots complicated the most simple machine.

I know I have no right to be angry, and should join the discord for tech support and a plethora of dick and fart jokes.
You shouldn't have to join a social media cult site to get answers. They all should be available and accessible to everyone who buys this POS.
ALONG WITH A TROUBLESHOOTING SECTION THAT DOESN'T TELL YOU TO FORMAT YOUR MEMORY CARD USING A SHOVELWARE PROGRAM OR BUY A FASTER MEMORY CARD!
I currently have seven NEW SD cards PNY, Sandisk, etc. with varying sizes and speeds, All formatted using the slow shovelware program several times after each failure.

Even the hda files I have used boot nicely on emulators.

what do we get? Sometimes its blinking oncesometimes twice, sometimes three times and so on.
Would it kill anyone to tell us what each of these blinking LED codes mean?
I guess it would.
In the you can add a rom file to your Pico section., it tells you where blanks are, and tells you you can include start up files in the rom, but it is locked once it is copied to the pico...
soooooooo...
how the hell do you put accessible files on there and what files will actually work or even boot the system?

ANYONE WANT TO ANSWER THAT?

No?

I opened an empty one without proper instruction from this github page using ciderpress and copied an System disk in. I can see it once I boot up using a floppy disk but it says it can't boot from the rom!!!!!
HAHAHAHAHAHAHAHAHA!
Did I mention that the Macintosh was the easiest computer? So why have people like you ruined it with shovelware, files that don't work and vague instructions?
I just want a SCSI hard drive to boot from and store files on. Not to be laughed at while I swear and struggle with this POS.

Oh well,.
Delete this and banish me from github for hurting your feels if you like. The truth is that Shit creating shit is still shit. Enjoy my $60 and the good laugh at my utter hopeless frustration, After all, it's funny isn't it!
"SOMEONE ACTUALLY BOUGHT THIS CRAP AND THOUGHT IT WOULD WORK! HA HA HA HA HA!"

I look at my Macintosh Plus and seriously consider smashing it with a hammer and chucking it in the dumpster, I no longer find retro computing fun thanks to Blue Scummy and this whole ordeal.

Hi same SD card, Same hdd image works in on the old BlueSCSI board but not on the V2 with the pico. The STE crashes after it has loaded the harddisk driver during booting. Got four bombs on the display :-) I have termination off. If i put termination on the systems does not recognize the bluescsi device at all.

Is there anything i can try? Can i do some debugging to provide more information?

Cheers!

Hi good morning, I'm silvano from italy. I have an iBook 520C running system 7.5. The hard disk image on the sd card works but I can't activate the internet wifi connection. I ve been installed daynaport application, create an empty NE4.hda file, and a BlueSCSI.ini file wich contains wifi's name and password.I've been installed openTransport and set "Alternate Ethernet" and "Using DHCP Server". But if try to open an internet browser like icab, f.e, I can't navigate because there's no Internet connection. I put the log.txt file.
Someone can help me please?? thanks bye!!
Platform: BlueSCSI Pico
FW Version: 2023.11.16-release Nov 17 2023 03:26:27
Flash chip size: 2048 kB

=== SD Card Info ===
SD card detected, FAT32 volume size: 30436 MB
SD Name: SD32G, MID: 0x03, OID: 0x53 0x44

=== Global Config ===
Reading configuration from bluescsi.ini
Active configuration:

=== Finding images in / ===
== Opening /NE4.hda for ID: 4 LUN: 0
---- Configuring as network based on image name
---- Image ready
== Opening /HD10_512 PowerBook 520c 240MB.hda for ID: 1 LUN: 0
---- Image ready

=== ROM Drive ===
Platform supports ROM drive up to 1692 kB
---- Activating ROM drive, SCSI id 0 size 1692 kB
---- WARNING: This image does not appear to be a valid Macintosh Device image. See: https://github.com/BlueSCSI/BlueSCSI-v2/wiki/Disk-Images
---- Activated ROM drive, SCSI id 0 size 1692 kB

=== Configured SCSI Devices ===

• ID: 0, BlockSize: 512, Type: Fixed, Quirks: Apple, Size: 1692kB
• ID: 1, BlockSize: 512, Type: Fixed, Quirks: Apple, Size: 245824kB
• ID: 4, Type: Network, Quirks: Apple

=== Network Initialization ===
Wi-Fi MAC: 00:80:19:07:E3:38
Connecting to Wi-Fi SSID "" with no authentication
Wi-Fi connection failed: -4

Initialization complete!
INFO: Pico Voltage: 3.276V.

Hi! I'm using the "Image Set" feature, where you can rotate through different CD images in a single SCSI ID, which is really neat. I would like to be able to have more than 10 though, and the current implementation handles IMG0 to IMG9. I guess I could just another SCSI channel and have 10 more, but that feels a little sloppy.

I looked at the source, and it seems it would be reasonably straightforward to change the way the CONFIG is handled into double digits, so that it allows setting CD images from IMG00 to IMG99, which should be enough. I would be happy to give that a try, but then I also remembered that you already have an utility that allows file transfer between the mac side and the sdcard. I couldn't find the source for it, but its existence must imply that you already have a "communication channel" in place between the mac os side and the BlueSCSI-v2.

With that in mind, maybe it would be cooler to develop a native 68k app that allows the user to choose what CD to mount next, straight from the sdcard? This way there's no need to edit tedious config files etc, just drop all CD images you want to be able to mount into a directory, and choose which one to mount. And of course you avoid the process of ejecting multiple CDs until you get to the one you want...

Is there a published list of SCSI Common Command Set (CCS) comands as implemented by BlueSCSI?

Or in particular those which are not implemented and those with only a partial implementation.

This would be far more use to those of us trying to get BlueSCSI running on non-MAC hardware.

Peter

Hello, i have a problem with Transfer Utility.

When i open blue transfer utility on Macintosh SE FDHD i get only: No compatibibile BlueSCSIs Found...

I have image created in Disk Jockey.
I have BlueSCSI-V2 Desktop version.
fimware from log: [10ms] FW Version: 2023.04.10-dev May 11 2023 02:01:14

Can someone please tell me what I am doing wrong?

I have a couple particular Toast images that mount in a strange way when used through BlueScsi V2 (v2023.04.10). The same exact file mounts ok when copied into the hard drive and mounted through the OS (either with toast, Virtual CD/DVD, etc). When mounted this way, the OS gives a read error when trying to access the files. It seems to be an issue with the particular file; it always happens with the same files.

This is an example of one such files: https://macintoshgarden.org/sites/macintoshgarden.org/files/games/TheDig_1_0.sit

You can tell right away, when mounted through blueSCSI the mounted CD shows no icons, but when mounted directly through the OS, app icons show correctly. The issue happens on macos 7.5.3, 7.6, 8.1, 8.6 and 9.1 on my machine (a color classic with a takky 5300/100 applied).

There's nothing relevant I can see on the log.txt file, and no error file is created.

Have not tried Blue yet on RS3 console. (Old DCS HMI) I have tried SCSI2SD, and it really makes the console unusable and actually somehow damaged some of the (graphic) hardware. As replacements parts are not made, I would like to not do this again with trying Blue. Debugging on the console side is very difficult as it's proprietary software. To continually support this system, we have use old 2.1GB Apple drive pulls to run. I was wondering if there is any information, I can provide to potentially mitigate damaging the hardware again. We are upgrading to SCSI2CF, currently being sold for the replacement on the RS3 consoles. However, I would like to have other options, and also offer those options to community members. I'm not a big fan of putting all my eggs in 1 basket as it limits resources and being held to the limitations of 1 company's resources. I currently use 2 of their SCSI2CF mad for RS3 and they work great, So based on a software/firmware side I know it is a possible venture. Again if there is anything I can provide to bring RS3 into the compatibility list, I would greatly do so. I hope anyone understands my reservations of just trying the device as I have already had to replace a $5k video generation OI card and that was a few years ago. (The RS3 name for the GPU)

Hi,

thanks for this nice project (I have built myself and using a few BlueSCSI v1).

I was considering building a BlueSCSI v2, but unless I missed something, there are issues in the schematics. For example if I consider the C50p version:

• R values are missing around CBTD3384 chips,
• Circuits around LVT245's are very weird. If I'm not mistaken, LVT245 is an octal bus transceiver, so A1 <-> B1 (etc) with DIR pin setting the direction of the buffer. In this schematics, we have:
  • DB0T <-> DB0 (ok could make sense)
  • GND-R11 <-> R45-GND : what is this supposed to do?
  • etc.
• The SCSI termination circuit does only link SCSI lines to the +2.8v via an unknown resistor, while the usual SCSI termination should be a pair of 220/330 Ω linked to vcc and GND. How does this schematics match the SCSI specs?
• The DB25 version seems not finished.

Are there improved/updated versions of these schematics that are waiting to be merged or something?

David

I have a Power Macintosh 7600 with an 800MHz G4 CPU upgrade. When attempting to install OS X 10.2 using XPostfacto, the machine will not boot. It works perfectly fine with the stock 200MHz 604e CPU and will also work with a 400MHz G3 upgrade I have if I set the CPU throttling option in XPosfacto to "8". No level of throttling seems to let the machine boot with the 800MHz CPU. When booting, I just see an OpenFirmware screen with the message "Can't LOAD from this device". It loops on this forever, with the light on the BlueSCSI turning solid blue for several seconds, then going off again. The debug logs show "scsi_accel_rp2040_finishRead timeout" with some repeating commands. I have tried using the fastest SD card I have (Samsung PRO Plus) freshly formatted with the recommended SD formatting tool as suggested by the help docs, but this didn't change the behavior. I have attached a full log of letting it attempt to boot for a few cycles. This was attempted with the latest v2023.10.12 firmware.
log.txt

I have 2x BlueSCSIv2, One PowerBook Version, and one DB25 (Short).
Both devices just ignore the Firmware .bin File, when i put them to the root of the MicroSD-Card.

Can i somehow force the Firmware Update with a statement in the bluescsi.ini ?

While DB25-Version is quickly disassembled to update via the USB-Method, for PowerBook Version its more complicated.
I already extended the MicroSD-Card, so it is accessible from the outside of the PowerBook, and i really don't want also extend the MicroUSB :)

Hi ,

First of all thank you very much for all the amazing work you did!

The BOM file BlueSCSI-v2/cc-nc-hardware/Desktop_50_Pin/ProductionFiles_JLCPCB/ cannot be uploaded on JLCPCB.COM. There must be a column "Footprint" in the table.

When using the CDX folder with a set of disk images, initialization fails with the following error (3x):

WARNING: Host attempted read at sector 16+1, exceeding image size 2 sectors (2048B/sector)

This is on an LCIII w/ 7.6.1 installed. I also am using the Pico W with the binary from pull 59.

It should just log a warning but instead it crashes.

Work around:

Use a different quirks mode setting in bluescsi.ini

Found by Mått#3016 on discord.

Currently I have data losses at PowerBook 170.

I will try to have a fix for this issue.

1. I'm preparing to add additional capacitors to 5V (2x 6.3V/1000uF), 3.3V (3x 6.3V/1000uF) and 2.8V (1x 6.3V/1000uF).
2. Raspberry Pi Pico can detect via GPIO24 if a voltage is present, GPIO29 (ADC3) can measure the voltage via ADC. If the VSYS voltage drops below 3V, the SD-Card should be synced and read/write should be stopped to prevent data losses.

At least as of 20231012, the ROM drive function seems to overwrite at least part of the firmware, causing the BlueSCSI to become non-functional until firmware is re-flashed through USB.

1. flash firmware to Pico over USB
2. use known-working HD1.hda as test (ensure booting is successful)
3. rename working HD1.hda to HD1.rom
4. power up Pico and wait for writing
5. ... no more function

It may be coincidence (or not) but it seems that the Pico goes into an extremely high-pitched whine during HD1.rom writing, and this high-pitched whine continues after any successive reboots.

Config is parsed all over the place which leads to bugs and duplicated code. It is hard coded to one file which makes it inflexible.

We should be able to:

• Abstract away the file it's reading the config from
• Allow updates to config values
  • This is more complex now that there's a caching layer
• Have one way to get the most correct value for a key (See #47)
  • ini scsi id section - take this no matter what, user must know more than we do
  • ini scsi global section - take this if not set in the id section.
  • File name - take this if not set in the ini
  • Runtime detection if applicable
  • Sane default
• Move config keys to own file and document there
  • Have process parse this file and update ini.bluescsi.com and the wiki automatically

I have the Bluescsiv2 working on SS10 however it throws a few SCSI Bus DATA IN phase parity Error.s on the console. and the transfer speed is lowered to 5MB/S .. apart from that the drives work fine. I have parity enabled as per the SpacSS10 documentation.

bluescsiv2ss10.txt

I just tested out Androda's 2023 10a PowerBook hardware with the wake from sleep fix and it looks like it has resolved the HD connection issue. I was able to remove my 5v power jumper wire bandaid.

Sleep/wake and the drive "spins up" and resumes within seconds now. No more freeze for several minutes. 👍

The only issue now is resuming the tcp/ip connection.

Upon wake up if you try to connect to something (telnet/Netscape etc) the system will freeze for a few minutes and then show an error that the connection has broken.

Using the Wi-Fi D/A I can re-establish the Wi-Fi connection and I can change between access points but telnet, Netscape etc. connection is broken so it looks like it's also the tcp/ip to Daynaport scsi link.

With open transport I am able to turn tcp/ip off and back on again but have not been able to reliably recover the connection.

If I wait for a timeout and then do a warm reboot the tcp connection re-established. No need to power down and back up.

First of all thanks for all the hard work on the BlueSCSI v2.
Long story short what ever you did with the latest update BlueSCSI V2 now works flawlessly on SASI x68000's. I did find one quirk however is when you power cycle the machine you get a "Chk.Conn." error then "So Low SCSI Level". Hitting the reset button works fine.
I'm using the 50 Pin Centronics version on a OG x68000 SASI Machine powered by an external PSU. I do also have the desktop version I planned to use in my Expert HD but I had the same read issues from the previous firmware so ended up going with a PiSCSI.
I'm sure if I wired the Bluescsi to use the internal x68000 psu the issue would be resolved due to the Bluescsi power cycling with the machine instead of being on all the time, however not everybody would have the know how to do this.
bluescsi.ini is as follows

[SCSI]
System="X68000"
Debug=1

Log
log.txt

Keep up the great work guys!

I am attempting to create an MSDOS ROM disk.

I have an image of a 720k floppy which I have loaded onto the Pico. However, when I set 'Type = 3', it is reported as Floppy1.4 in the log file.

How do I generate / support a 720k disk?

Thanks

Peter

How do I specify CHS parameters in Bluescsi.ini?

The example comments:

number of heads: 'HeadsPerCylinder=4'
sectors per track: 'SectorsPerTrack=33'

but omits details on number of cylinders!

Peter

Hi, I have assembled 4 pieces of BlueSCSI V2 devices and only two of them work without problems.
On the other two devices, there is a problem when trying to initialize the hard drive.
When trying to initialize BlueSCSI on the Pico, the LED lights up for a few seconds, after which it goes out and a message appears on the screen that SCSI disks have not been found.
I have an assumption that the problem is in one of the chips on the board and some signal does not pass through to Pico
Is there any program for testing chips on the board, or maybe there is a way to determine which chip is the problem from the logs?

Log:
"[10ms] Platform: BlueSCSI Pico
[10ms] FW Version: 2023.04.10-release Apr 10 2023 19:08:58
Flash chip size: 2048 kB

=== SD Card Info ===
SD card detected, FAT32 volume size: 3832 MB
SD Name: SD16G, MID: 0xFE, OID: 0x34 0x32

=== Global Config ===
Reading configuration from bluescsi.ini
Active configuration (using system preset "Generic"):
-- SelectionDelay: 0
-- ReinsertCDOnInquiry is enabled

=== Finding images in / ===
== Opening /HD00_512-1GB.hda for ID: 0 LUN: 0
---- Image ready

=== ROM Drive ===
Platform supports ROM drive up to 1692 kB
---- ROM drive image not detected

=== Configured SCSI Devices ===

• ID: 0, BlockSize: 512, Type: Fixed, Quirks: None, Size: 1048576kB

Initialization complete!
SCSI ID 0 negotiated synchronous mode 5 MB/s (period 4x50 ns, offset 8 bytes)
scsi_accel_rp2040_stopWrite() timeout, FIFO levels 0 2 PC 17"

Log with debugging enabled:
"[10ms] Platform: BlueSCSI Pico
[10ms] FW Version: 2023.04.10-release Apr 10 2023 19:08:58
Flash chip size: 2048 kB

=== SD Card Info ===
SD card detected, FAT32 volume size: 3832 MB
SD Name: SD16G, MID: 0xFE, OID: 0x34 0x32
[22ms]
[22ms] === Global Config ===
[23ms] Reading configuration from bluescsi.ini
[24ms] Active configuration (using system preset "Generic"):
[25ms] DBG -- SelectionDelay: 255
[25ms] DBG -- EnableUnitAttention is off
[26ms] DBG -- EnableSCSI2 is on
[27ms] DBG -- EnableSelLatch is off
[27ms] DBG -- MapLunsToIDs is off
[28ms] -- Debug is enabled
[29ms] DBG -- Parity is enabled
[29ms] -- ReinsertCDOnInquiry is enabled
[108ms]
[108ms] === Finding images in / ===
[108ms] == Opening /HD00_512-1GB.hda for ID: 0 LUN: 0
[386ms] DBG ---- Read prefetch enabled: 8192 bytes
[387ms] ---- Image ready
[392ms]
[392ms] === ROM Drive ===
[393ms] Platform supports ROM drive up to 1692 kB
[393ms] ---- ROM drive image not detected
[393ms]
[394ms] === Configured SCSI Devices ===
[394ms] * ID: 0, BlockSize: 512, Type: Fixed, Quirks: None, Size: 1048576kB
[496ms]
[496ms] Initialization complete!
[16279ms] DBG BUS RESET
[23529ms] DBG ---- SELECTION: 0
[23530ms] DBG ---- MESSAGE_OUT
[23531ms] DBG ------ OUT: 0xC0
[23532ms] DBG ------ OUT: 0x01
[23532ms] DBG ------ OUT: 0x03
[23533ms] DBG ------ OUT: 0x01
[23533ms] DBG ------ OUT: 0x32
[23534ms] DBG ------ OUT: 0x08
[23534ms] SCSI ID 0 negotiated synchronous mode 5 MB/s (period 4x50 ns, offset 8 bytes)
[23535ms] DBG ---- MESSAGE_IN
[23535ms] DBG ------ IN: 0x01 0x03 0x01 0x32 0x08
[23538ms] DBG ---- COMMAND: Inquiry
[23538ms] DBG ------ OUT: 0x12 0x00 0x00 0x00 0x02 0x00
[23539ms] DBG ---- DATA_IN, syncOffset 8 syncPeriod 50
[28540ms] scsi_accel_rp2040_stopWrite() timeout, FIFO levels 0 2 PC 17
[28540ms] DBG ---- Total IN: 2 OUT: 0 CHECKSUM: 0
[28541ms] DBG ---- STATUS: 0 GOOD"

The Desktop files and PNG were updated to the 2022.12a revision and blue PNG file, but the DS25 and Powerbook versions are still green and showing the 2022_11b, I'm guessing these are not the latest?

Also, the Desktop folder has a zip file of the gerber files for it, the Powerbook and DS25 versions do not have a zip file of the gerber files.

Thanks, what an exciting day!

Similar to how DietSCSI (BlueSCSI v1 fork) is doing USB pass through we could use TinyUSB to present the drive images as usb mass storage devices. Since HFS Fuse has been updated and things like CiderPress/etc can open volumes it would be handy to just be able to plug in your BlueSCSI to your modern or slightly less retro computer and have the HFS/etc volumes mounted.

I've done some work on this and will push a branch soon.

When setting up a BOM on LCSC site, I stumbled upon a "discontinued" part which is affecting C2290 (power led).
Could you please share some details of the led used so we could pick up an alternative?

Also, would you be accepting alternatively some other distributors (Mouser for example) part numbers as well? (Or how/where are the BOM referenced maintained?)

I upgraded a DB25 BlueSCSI v2-2022.12ato the 0223-07-03 firmware using BlueSCSI_Pico_2023-07-03_46af79d1.uf2. After drag & dropping the .uf2 file the PICOBOOT drive disappeared as expected but the USB device didn't reconnect and I got a continuous stream of flashes of the Pico's green LED. Eventually Windows complained that the USB device wasn't recognized. If there was a pattern to the blinking I didn't recognize it.
Pulling the SD card to the Windows machine I did the flashing from shows the attached err.txt. Disabling the ROM disk using DisableROMDrive=1 in the INI file go it working again, as well as creating a CLEAR_ROM file to delete the ROM disk.
err.txt

Recreating the ROM drive from the same image brings back the crash:
== Loading ROM drive from /HD5.rom for ID: 5 ---- SCSI ID: 5 blocksize 512 type 0 ---- ROM drive maximum size is 1732608 bytes, image file is 1732608 bytes ---- ROM drive programming successful, image file renamed to /HD5.rom_loaded

Hi,
Is it supported to boot from bootable images?
I have several images that work fine if burned out to disk, but they don't boot into BlueSCSI.
The universal image of Mac OS 9.2.2 from the MacOS9Lives community is booted, but I can work with it, because this Power Mac 9600 does not have native support for 9.2.2.

I named the boot image like "CD2-Name.iso"
I don't see anything in the BlueSCSIv2 log that says errors or problems.

After the OS is loaded, the specified ISO is mounted on the system and works normally.
If you specify this image in the Startup disk, the boot is also not performed.

Hello,

I'm trying to use a BlueSCSI card to emulate my NED Synclavier II hard-disk.

The only "special" need from the Synclavier, is to have SCSI drives with Parity Disable Checking.

I have upgraded my BlueSCSI module with the last firmware available (11th august 2023).

Here is my bluescsi.ini file content :

Debug=1

[SCSI5]
BlockSize=512
EnableParity=0
Parity=0
EnableSCSI2=0
Type=0

========================================================================================

Here is the log.txt output :

[10ms] Platform: BlueSCSI Pico
[10ms] FW Version: 2023.08.10-release Aug 11 2023 01:25:40
Flash chip size: 2048 kB

=== SD Card Info ===
SD card detected, exFAT volume size: 29503 MB
SD Name: SD32G, MID: 0x27, OID: 0x50 0x48

=== Global Config ===
Reading configuration from bluescsi.ini
Active configuration:

=== Finding images in / ===
== Opening /HD50_512 Ramon.hda for ID: 5 LUN: 0
---- WARNING: This image does not appear to be a valid Macintosh Device image. See: https://github.com/BlueSCSI/BlueSCSI-v2/wiki/Disk-Images
---- Image ready

=== ROM Drive ===
Platform supports ROM drive up to 1692 kB
---- ROM drive image not detected

=== Configured SCSI Devices ===

ID: 5, BlockSize: 512, Type: Fixed, Quirks: Apple, Size: 81920kB
Initialization complete!
INFO: Pico Voltage: 3.185V.

========================================================================================

I have two questions...

Why don't I see the debug informations in the log.txt file ? do I need a special firmware version ?
The Synclavier make an error when booting on the BlueSCSI drive, which refers to a problem with the parity check ...
I'm not sure my bluescsi.ini file is taken into consideration.... how can I be sure it is read and all the options taken into account ?

By the way, the BlueSCSI card is recognized and works fine when connected to a Mac using a RATOC FR1SX adapter and using Synclavier InterchangeX software to read the image disk.

Thanks in advance for your help !

Best regards.

Laurent.