|
|
3 years ago | |
|---|---|---|
| include | 3 years ago | |
| lib | 3 years ago | |
| src | 3 years ago | |
| test | 3 years ago | |
| utils | 3 years ago | |
| .gitignore | 3 years ago | |
| LICENSE | 3 years ago | |
| README.md | 3 years ago | |
| platformio.ini | 3 years ago |
AzulSCSI uses the same harddrive image file format as in BlueSCSI instructions.
The image files should be named e.g. HD00_512.hda for ID 0, LUN 0, 512 byte block.
Log messages are stored in azullog.txt, which is cleared on every boot.
Normally only basic initialization information is stored, but turning DIPSW2 on will cause every SCSI command to be logged.
The indicator LED will normally report disk access. It also reports following error conditions:
In crashes the firmware will also attempt to save information into azulerr.txt.
Optional configuration can be stored in azulscsi.ini.
Example format for config file:
[SCSI]
Vendor = "QUANTUM "
Product = "FIREBALL1 "
Version = "1.0 "
Quirks = 0 # 0: Standard, 1: Sharp, 2: NEC PC98
With verbose log messages disabled, expected SCSI performance is 1.7 MB/s read and 1.5 MB/s write. Slow SD card or fragmented filesystem can slow down access.
The AzulSCSI v1 board can be programmed using USB connection in DFU mode. The necessary programmer utility for Windows can be downloaded from GD32 website. On Linux and Mac gd32-dfu-utils can be used.
The DIP switch settings are as follows:
azullog.txt)This codebase uses PlatformIO. To build run the command:
pio run
This firmware is derived from BlueSCSI, which in turn is derived from ArdSCSIno-stm32. The firmware is available under GPL 3 license.
Major changes from BlueSCSI include: