Skip to content

ZuluSCSI/daynaport-amiga

 
 

Repository files navigation

Amiga DaynaPORT Driver for BlueSCSI V2 and ZuluSCSI Pico OSHW

Created by RobSmithDev Based on the MNT ZZ9000 Network Driver by Lukas F. Hartmann and uses bits I learnt from reading how PlipBox works.

This is an implementation of a SANA-II driver for the Amiga, which allows you to use either a Pico-W enabled BlueSCSI V2 or ZuluSCSI Pico OSHW board to give internet access to the machine!

This code is based on the MNT ZZ9000Net driver by Lukas F. Hartmann (which is based on work by Henryk Richter) and also borrows a little from the PlipBox device driver, which has several contributors.

For a step-by-step guide on installing, check out (this video by Retronaut)[https://www.youtube.com/watch?v=FDtqd04bq-k]

This requires the updates in https://github.com/RobSmithDev/BlueSCSI-v2 in order to work.
A Compiled Version Is Included With The Downloadable Release

I've tested it with the following setups:

Amiga 500+ (2M Chip)

  • A590 HDD (2M fast ram, 7.0 ROM)
  • BlueSCSI Pico (V2) Wi-fi version, or
  • ZuluSCSI Pico OSHW board with Pico W, running stock/unmodified ZuluSCSI Pico firmware version v2024.03.07, or later.
  • Kickstart 3.2

Amiga 2000 (2M Chip)

  • Impact A2000-HC+8 Series II (8M Fast Ram)
  • BlueSCSI Pico (V2) Wi-Fi version or ZuluSCSI Pico OSHW board with Pico W.
  • Kickstart 3.1

Side effects

With BlueSCSI V2 hardware, the HDD light constantly flashes while the driver is in use. The driver needs to be copied to the Devs:Networks folder and then setup your TCP/IP stack as normal.

Notes

If you find your data transfer is very slow, like less than 5k/s then check you've turned the debug log off within BlueSCSI!

Config File (IMPORTANT)

scsidayna.prefs contains an example config file for the device. This needs to be copied to ENVARC on the Amiga and rebooted The format of that file is:

DEVICE=scsi.device
DEVICEID=-1
PRIORITY=0
MODE=1
AUTOCONNECT=0
SSID=
KEY=\

where:

  • DEVICE is the name of the SCSI driver, eg: scsi.device or gvpscsi.device
  • DEVICEID is the SCSI device index the DaynaPORT is on, or -1 for Auto Detect
  • PRIORITY -128 to 127, sets the I/O task priority, see below
  • MODE see below
  • AUTOCONNECT 0/1 if 1, the driver will attempt to connect to the WIFI device (you can configure BlueSCSI to do this)
  • SSID The SSID/Wifi name to connect to if autoconnect=1
  • KEY the wifi key/password

Mode

This patches around weirdness in the various SCSI drivers. Mode should be:

  • 0: This runs in normal mode
  • 1: Runs in 24-byte pad mode (required for scsi.device - A590/A2091)
  • 2: Runs in 'single transfer' mode (required for gvpscsi.device)

Task Priority

A small note about task priority. If left at 0 the device will function perfectly fine, however the throughput of data is somewhat all over the place. If you want a really stable throughput, then set this to '1', but also expect this will possibly slow down some of the other applications running on your system.

About

daynaPORT SCSI Sana-II Device Driver

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • C 89.5%
  • Makefile 7.7%
  • Assembly 2.4%
  • Other 0.4%