BlueSCSI V2 configuration help

[bobrocks95]

Hi I have an X68000 Expert HD with a stock 50-pin cable and I'm having trouble getting the BlueSCSI to be detected- feels like I'm getting a setting wrong more than anything?

I have the v2.20 image from here on there as "HD30_512 v220.HDF" or whatever the format is- could the name be too long if it needs to be 8.3 formatting?  Multiple guides used SCSI ID 3 though I'm not entirely sure why.  There was also mention in some older threads about a FDD setting switch on the back- was that for a Compact maybe?

Here's my error messages on bootup and Switch.x and bootsel.x settings.  Monitor is looking, uh, a little blue for whatever reason so it'll be fun to look into that as well...

https://photos.app.goo.gl/os66uBFwhtns7Ca79

[bobrocks95]

Here's my latest startup log with debugging enabled.  I changed the image name to "HD30_512.HDF" just in case there was a DOS 8.3 issue and I tried externally powering the BlueSCSI V2 with the Pi's USB port.  I also tried enabling the jumper for termination just in case (BlueSCSI wiki says to leave it disabled for a SASI X68000)

Code Select Expand

Platform: BlueSCSI
FW Version: 2024.05.21-rel May 21 2024 21:21:44
I2C Supported
Flash chip size: 2048 kB
 
=== SD Card Info ===
SD card detected, FAT32 volume size: 29500 MB
SD Name: SD32G, MID: 0x27, OID: 0x50 0x48
[150ms] 
[150ms] === Global Config ===
[150ms] Reading configuration from bluescsi.ini
[150ms] Active configuration (using system preset "X68000"):
[150ms] -- EnableSCSI2 is off
[150ms] -- Debug is enabled
[151ms] -- Parity is disabled
[151ms] DBG -- ReinsertCDOnInquiry is disabled
[174ms] 
[174ms] === Finding images in / ===
[174ms] == Opening /HD30_512.hds for ID: 3 LUN: 0
[660ms] DBG ---- Read prefetch enabled: 8192 bytes
[660ms] ---- Image ready
[661ms]
[661ms] === ROM Drive ===
[661ms] Platform supports ROM drive up to 1692 kB
[661ms] ---- ROM drive image not detected
[661ms] 
[661ms] === Configured SCSI Devices ===
[661ms] * ID: 3, BlockSize: 512, Type: Fixed, Quirks: X68000, Size: 3073024kB
[1469ms] 
[1469ms] Initialization complete!
[1479ms] INFO: Pico Voltage: 3.254V.


[spectreman]

Switch.x settings:

HD_MAX: 0

give it a try.

[bobrocks95]

Switch.x settings:

HD_MAX: 0

give it a try.

Thank you so much, this did the trick!

Don't know how it got to 96 when it is supposed to max at 16... Maybe I needed to do something to reset the SRAM to default values after replacing the battery?

[spectreman]

Removing the battery restores the default values, it is much more likely that a bad loading of the SxSI drivers is the cause of the problem.

On newer systems like the XVI you can reset the SRAM to default values by holding down the CLR key, immediately after turning on the computer, when the confirmation message appears press Y.

On older models like OG/ACE/PRO/Expert, it's more complicated.
The simplest solution is to use the SRAM_CLR.R program to reset the SRAM: http://nfggames.com/X68000/Misc/Sram/SRAMLOAD.Lzh

Alternatively, you can manually reset the default values, with those indicated in the table to your right of the Switch.x menu, except for:

MEMORY: set the sum of the basic + expansion memory, if present.
BOOT: Must remain set to ROM $ED0100
HD_MAX: 0

This should also fix the blue screen issue.

[incrediblehark]

@spectreman after using ROM $ED0100 to boot your bluescsi hdd image once, could you try setting the boot mode to STD and see if it still works? I have tested this in the past to boot from floppy if inserted or the scsi2sd if not but want to see if it works for other people as well.

[spectreman]

@incrediblehark You can boot the HDD image by setting BOOT: STD on SASI computers, but you need to keep HD_MAX: 0 set.

The STD reading order is as follows:

1 Floppy disk (drive 0/drive 1/drive 2/drive 3)
2 SASI or SCSI (integrated interface)
3 ROM (including SCSI expansion card)
4 SRAM
After loading the SxSI driver, the ROM parameter $ED0100 will be in the list of addresses available in the read sequence.

However, it is not a certain rule, as the system in use makes a difference (OG/PRO are the most problematic), version and type of hardware of the emulator installed, and firmware version.

In the worst case you can always use forced startup with the OPT.1 button.