Closed WJG6260 closed 2 years ago
There have been some reliability problems with RP2040 bootloader. They should be resolved by the next firmware release.
To upgrade the bootloader or to recover from bad flashing on RP2040 platform:
.uf2
format of the firmware.BOOTLOADER
DIP switch on the ZuluSCSI RP2040 PCB..uf2
file to the USB drive.Remove safely
or wait at least 30 seconds before disconnecting USB.@WJG6260 here's a direct link to the .uf2 file https://github.com/ZuluSCSI/ZuluSCSI-firmware/releases/download/v1.0.9/ZuluSCSI_RP2040-1.0.9-4e2112b.uf2
As per @PetteriAimonen's comment, this is a known issue. The only way to work around it is to update the firmware via copying the .uf2 file to the ZuluSCSI RP2040 in bootloader mode. The BOOTLDR DIP switch must be on before you power on the board, and I recommend switching it off as soon as you plug it in. If you don't upon successful completion of the firmware flash (by copying the .uf2 to file to the virtual drive it exposes), it will immediately do the same thing again, when it re-starts, after re-flashing itself, which can appear as if it didn't flash successfully, even though it /did/ flash successfully.
@WJG6260 no response in over a week, so I'm going to close this as resolved, since we've provided the only workaround. Feel free to re-open this if need be.
Platform: ZuluSCSI RP2040 FW Version: 1.0.9-release Sep 30 2022 18:19:23
Earlier tonight, I attempted to upgrade my ZuluSCSI RP2040 from firmware 1.0.8 to 1.0.9 using the methods described. I renamed the v1.0.9 RP2040-specific bin file to ZuluSCSI.bin, inserted the SD card with such file at the root directory, and booted the device.
The light on the device flashed numerous times (more than the five described as a failure), and I am now unable to boot from the device.
The following zuluerr.txt was generated:
At this point, I cannot seem to access the device via Mac/Windows and cannot boot the device on an Adaptec AHA-2842W, as I had done before.
I attempted another flash, this time to the nightly build and received the same exact error.
Any thoughts would be appreciated greatly.
EDIT: As of 11:59 P.M., I have managed to boot the device by swapping from an exFAT-formatted SD card to a new FAT32 formatted one. I am not sure if this is perhaps related, but the device seems just fine now.