nfg.forums

I recently purchased a pre-built BlueSCSI v2 kit in hopes of using it as an external SCSI HDD with my 20F. However, nothing I try is working.

I have tried multiple SCSI IDs and have been using proper naming conventions (e.g., HD1.HDA, HD10_512.HDA, etc). I updated my BlueSCSI v2 unit to the latest firmware and have tried multiple INI settings, such as the ones seen below.

[SCSI]
System=Generic
Quirks=0
EnableSCSI2=0
Debug=1
DisableROMDrive=1

Below is a log sample, which also looks good.

Platform: BlueSCSI
FW Version: 2024.12.08-rel Dec  8 2024 22:19:03
Flash chip size: 2048 kB
 
=== SD Card Info ===
SD card detected, exFAT volume size: 121888 MB
SD Name: SD128, MID: 0x03, OID: 0x53 0x44
[131ms] 
[132ms] === Global Config ===
[135ms] Reading configuration from bluescsi.ini
[139ms] Active configuration (using system preset "Generic"):
[144ms] -- EnableSCSI2 is off
[147ms] -- Debug is enabled
[149ms] DBG -- Parity is enabled
[152ms] DBG -- ReinsertCDOnInquiry is disabled
[209ms] 
[209ms] === Finding images in / ===
[211ms] == Opening /HD10_512.hda for ID: 1 LUN: 0
[216ms] DBG ---- Read prefetch enabled: 8192 bytes
[219ms] ---- Image ready
[222ms]
[222ms] === ROM Drive ===
[224ms] Platform supports ROM drive up to 1692 kB
[229ms] ---- ROM drive image not detected
[232ms] 
[233ms] === Configured SCSI Devices ===
[237ms] * ID: 1, BlockSize: 512, Type: Fixed, Quirks: None, Size: 1363148kB
[993ms] 
[993ms] Initialization complete!
[1025ms] INFO: Pico Voltage: 3.276V.

I've also taken this to the BlueSCSI Discord where a mod there shared an experimental firmware for me to try, but with no luck.

I have tried Cyo's image, as well as using CaptainYS bootloader to map drive letters. I cannot boot the HDD, nor browse it in TownsOS. In fact, Cyo spent some time attempting to troubleshoot this with me, but to no avail.

I also tried creating an empty file and placing it on the BlueSCSI's microSD card in hopes of formatting and partitioning it in TownsOS. My plan was to simple install TownsOS myself, along with creating extra partitions. However, I see the same generic error messages as I did when trying Cyo's image. Meanwhile, this same method works fine in Tsugaru.

I can only assume one of the following things is true...

• BlueSCSI v2 is incompatible with the 20F, though a user on the FMT Discord showed me that it does work with their UX20.
• BlueSCSI v2 requires special configuration options for the 20F, though I've yet to uncover them.
• My 20F is broken in some way.
• I am being an idiot and doing something terribly wrong.

All of that being said, I figured I'd make this post in the hopes that someone out there with a v2 unit has been down this road and knows what I need to remedy my problem. It appears the v1 units work perfectly fine with the 20F, though they're no longer being sold as pre-built kits (though of course one can make one themself). However, before exploring alternative devices, I wanted to ensure I did every ounce of due diligence on this v2 unit.

Thank you in advance to all who read this!

Not sure if this is helpful but I am pretty sure a BlueSCSI 2 worked on the external port of my 40H, which is pretty similar to a 20F. My SillyTinySCSI-Centronics50 had some issues. Never really found out what the problem was but my conclusion was it's the physical connection with the plug.
I am now using an internal ZuluSCSI (RP2040-based, with CDDA addon, SD extension and custom bracket for the extension, button and audio jack) in the 40H and a CX20.
The ZuluSCSI is again very similar to BlueSCSI 2.

Quote from: hiker on March 04, 2025, 01:45:12 PMI am now using an internal ZuluSCSI (RP2040-based, with CDDA addon, SD extension and custom bracket for the extension, button and audio jack) in the 40H and a CX20.
The ZuluSCSI is again very similar to BlueSCSI 2.

Thank you for the reply and suggestion.

I've posted another thread where I tried what is supposed to be the known working BlueSCSI V1, but I'm experiencing the same issue.

Before moving on to trying other SCSI HDD emulators, I want to rule out my computer itself as the culprit first.