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

[eric]

Minor but important bug fixes for HP-715, better SCSI spec compatibility, and fixes an issue that's existed since 2015! Check it out!

• scsi: fix mac vendor page by @erichelgeson in #134
• scsi: include firmware version in vendor section of inquiry by @erichelgeson in #129
• scsi: inquiry response to invalid lun by @erichelgeson in #128

Release v2024.04.02 · BlueSCSI/BlueSCSI-v2

What's Changed This is a small but important update to fix some bugs users were experiencing: scsi: fix mac vendor page by @erichelgeson in #134 scsi: include firmware version in vendor section of...

github.com

 

[eric]

@This Does Not Compute provides some tips for getting the most out of your BlueSCSI on your vintage mac

 

[svenson]

Hey Eric,
I did a little bit of "quick and dirty" coding. I activated the qwiic OLED display and show the firmware version there (I use Robs Amiga firmware source).
Is there a way in the BlueSCSI code to query the ip address from the system? Or have this information send over the device driver from the system to the BlueSCSI?
My goal is to show the ip address in the qwiic display.

Kind regards, Svenson

 

[eric]

Is there a way in the BlueSCSI code to query the ip address from the system? Or have this information send over the device driver from the system to the BlueSCSI?
My goal is to show the ip address in the qwiic display.

BlueSCSI is in target mode when emulating devices so it can never initiate a command. You could use a custom vendor command to set a variable to display from the host. I had started some work on runtime config setting for key/values in the ini, eg you'd send a payload with scsiid\0key\0value\0 and it would set and persist that so you wouldnt have to pull the SD card out to edit config.

Also as you probably know the BlueSCSI in WiFi is a layer 2 device just passing packets to and from, so it doesnt know anything about layer 3 (eg: the ipaddress/etc) so we cant get it at runtime.

We'll be merging robs stuff into mainline soon, just needed to work out some things first as it's not really a daynaport device anymore with these changes.

You're not the only one working on a display - I do have a menuing framework close to ready, where you could build a custom menu into like this.

 

[robin-fo]

Is there a way in the BlueSCSI code to query the ip address from the system?

You can probably read the IP address from ARP packets (or even send your own requests to the Mac)

 

[svenson]

BlueSCSI is in target mode when emulating devices so it can never initiate a command. You could use a custom vendor command to set a variable to display from the host. I had started some work on runtime config setting for key/values in the ini, eg you'd send a payload with scsiid\0key\0value\0 and it would set and persist that so you wouldnt have to pull the SD card out to edit config.

Also as you probably know the BlueSCSI in WiFi is a layer 2 device just passing packets to and from, so it doesnt know anything about layer 3 (eg: the ipaddress/etc) so we cant get it at runtime.

We'll be merging robs stuff into mainline soon, just needed to work out some things first as it's not really a daynaport device anymore with these changes.

You're not the only one working on a display - I do have a menuing framework close to ready, where you could build a custom menu into like this.

Hey Eric, thank you for this detailed informations! That sounds like really valuable features are coming up! Great

 

[ifrit05]

Don't know if this is a good spot for this (also posted in the Discord) but I'm having an issue with my Desktop BlueSCSI v2-2023.10a with a Pico W. It cannot find an SDCard. Tried a Sandisk and Samsung, FAT/ExFAT, both old but verified genuine and working, overwrite format with SD Card Formatter.

Seems to detect if a card is pulled/swapped, the blinking will stop for a moment then blink again. COM port is reporting SdioCard::readSector(0x00000000) failed: 5 and SdioCard::readSector(0x00000001) failed: 5

I verified all SDCard pins are connected to the pico. At a loss on what to do, 100% think my soldering isn't an issue.

EDIT: SD Card socket was a little jankey, tapped some paper to the top of the sd card and it works now. I'm not bothered by it, just happy it works.

 

[eric]

FYI looks like they fixed the issue on discord - the SD card in the SD slot was not making good connection.

 

[eric]

New BlueSCSI v2 release v2024.05.21

Notable changes:

• New DOS Toolbox apps!
  - BlueSCSI Toolbox now on 4 platforms: Classic Mac, Amiga, DOS, and NeXT)
• iomega ZIP100 support (Roland Samplers)
• Update to Centronics Hardware

Thanks to @jokker, @Androda, `Niels M H`, @OneGeekArmy, and @Stinkerton18 for the contributions this release!

Release v2024.05.21 · BlueSCSI/BlueSCSI-v2

In this release New Toolbox Platforms BlueSCSI Toolbox is now on 4 platforms: Classic Mac, Amiga, DOS, and NeXT (in pre-release) See the BlueSCSI Toolbox wiki page for the details. @stinkerton18 al...

github.com

 

[eric]

Lots of new BlueSCSI Toolbox platforms being added by community members - not just Mac anymore!

Can find the full list here: https://bluescsi.com/docs/Toolbox

• Beginnings of BeOS by 0xb1dd1e

• IRIX by SonnyJim

• DOS by nielsmh

And more on the way!

 

[eric]

I've started a retro compatible site for BlueSCSI related links/files/etc here: http://retro.bluescsi.com/

Has a web (http), ftp, gopher (though I need to adjust the layout, mirror the web for now), links to many retro sites (such as this one).

It's just a start for now - let me know if there's any other things I should include or if there's something needing fixing (I'm sure there is)

I'll need to adjust the styling for the docs but it is automatically mirrored now for your http viewing pleasure.

 

[eric]

This afternoon I got BlueSCSI v2 working on the new Pico2 dev board - still work to do yet and using pretty rough around the edges stuff in the framework, but hey, it boots!

(Red wires/switch is so I can flash the pico without having to unplugging it each time)

 

[3lectr1c]

ah yes, the Quantum BlueSCSI.

 

[JDW]

This afternoon I got BlueSCSI v2 working on the new Pico2 dev board...

I see from the Pico2 product page, it offers "a higher core clock speed, double the memory, more powerful Arm cores, optional RISC‑V cores, new security features, and upgraded interfacing capabilities," plus it is backward compatible.

I assume that to the end user, a BSv2 using a Pico2 would operate no differently (performance, WIFI, general features, etc.) than our existing Pico-1 products, correct?

 

[Androda]

Pico 2 uses a new chip, the RP2350A. It has twice the working RAM as its predecessor, and also twice the program storage (this is on an external chip, but 2x is 2x). Overall it will allow for more features, some of which will have to be Pico2-only due to RAM and storage restrictions on the original Pico.

 

[eric]

Announced something big at VCF-MW like we usually do https://tinkerdifferent.com/threads...re-license-bluescsi-hardware-cern-ohl-s.3819/

 

[eric]

Release v2024.09.15 · BlueSCSI/BlueSCSI-v2

How to update https://github.com/BlueSCSI/BlueSCSI-v2/wiki/Updating-Firmware#usb-method What's Changed PIO base file did not match compiled PIO header file by @androda in #160 Re-License BlueSCSI ...

github.com

New release - Fixes those cryptic CRC and SDIO issues - thanks to @Androda for being this releases MVP!

Note this issue mainly effected early PPC macs and Sun systems, was only experienced by a handful of users but was quite annoying!

 

[eric]

Few updates: @jcs released an updated version of the BlueSCSI WiFi DA that allows you to connect to hidden SSID's

BlueSCSI Wi-Fi Desk Accessory - joshua stein

As well as Wallops 2.1 (IRC client for MacOS 6/7) https://jcs.org/wallops - perfect for idling on your PowerBook with BlueSCSI WiFi

After fixing SDIO we're back to feature development and bug fixes - our next release should be pretty beefy Just wrapping up NeXT features and fixes.

Also we've merged in the Amiga WiFi code into main from RobSmithDev - so Amiga users can enjoy WiFi too.

If you want to see what we're up to you can always peruse our github and grab prebuilt "nightly" binaries too.

 

[eric]

This afternoon I got BlueSCSI v2 working on the new Pico2 dev board - still work to do yet and using pretty rough around the edges stuff in the framework, but hey, it boots!

(Red wires/switch is so I can flash the pico without having to unplugging it each time)

View attachment 17589View attachment 17590

If anyone wants to follow along, contribute, test on the Pico 2 you can grab the code or the uf2 files here https://github.com/BlueSCSI/BlueSCSI-v2/pull/198

 

[eric]

This afternoon I got BlueSCSI v2 working on the new Pico2 dev board - still work to do yet and using pretty rough around the edges stuff in the framework, but hey, it boots!

(Red wires/switch is so I can flash the pico without having to unplugging it each time)

View attachment 17589View attachment 17590

Doing testing with patches to address the timing issues applied - no real surprise here as no other code has changed - slight bump in write. Code will be on github tonight or tomorrow under the existing pico2 branch.