Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CD-ROM image loading error ZuluSCSI Pico DaynaPORT 2023-11-27 #345

Closed
beezbo opened this issue Dec 1, 2023 · 6 comments
Closed

CD-ROM image loading error ZuluSCSI Pico DaynaPORT 2023-11-27 #345

beezbo opened this issue Dec 1, 2023 · 6 comments
Assignees
@morio

Comments

@beezbo
Copy link

beezbo commented Dec 1, 2023

I am finding that there is an issue where it seems like this firmware is trying to load the bin or iso file as a disk image. If I load the same micro sd card with no changes in another Zulu board with an older firmware, the CD-ROM images load properly. Running system 7.1.1 on a 68k mac. Am I missing something?

In the log file:

[14565ms] -- Opening 'a_CD.bin' for id: 3
[14614ms] ---- Configuring as disk drive drive
[14615ms] ---- WARNING: This image does not appear to be a valid Macintosh disk image.

working version:

[114ms] -- Opening 'a_CD.bin' for id:3, specified in zuluscsi.ini
[169ms] ---- Read prefetch enabled: 8192 bytes
[171ms] ---- Found CD-ROM CUE sheet at a_CD.cue
[173ms] ---- Cue sheet loaded with 19 tracks
@morio
Copy link
Collaborator

morio commented Dec 1, 2023

Hi @beezbo , could you provide your zuluscsi.ini file and the full log that isn't working?
Thanks, I have a guess as to what is going but want to make sure I'm recreating the bug.

@morio morio self-assigned this Dec 1, 2023
@beezbo
Copy link
Author

beezbo commented Dec 2, 2023

@morio Thanks for your response. Here are the files you requested with some PII removed.

zuluscsi.ini.txt
zululog_cd-rom_issue.txt

@aperezbios
Copy link
Collaborator

@beezbo thank you fort this report. We have investigated this, and determined that this is in fact a regression, which occurred after the release of the September 9th release. The only work-around at this point would be to revert to firmware v2023.09.06, which will work for any non-Pico ZuluSCSI RP2040 users, as well as ZuluSCSI V1.1 users.

Unfortunately, reverting to v2023.09.06 is not an option for the Pico hardware, because the above-mentioned release was made prior to the addition of the ZuluSCSI Pico build target. For all ZuluSCSI Pico users, you will need to wait for us to commit a fix, which should happen in a few days time.

morio added a commit that referenced this issue Dec 4, 2023
@morio
Fix device type for IMG0-9
a935a96 
This is for issue #345
The bug was introduced in https://github.com/ZuluSCSI/ZuluSCSI-firmware/releases/tag/v2023.10.20

This fixes an issue when the device specific options in the
`zuluscsi.ini` file `IMG0`-`IMG9` are set along with
`Type` set to anything besides 0. The type would be ignored
and the device would always be set to a fixed device (Type=0).

The underlying fix was to add a new device type `S2S_CFG_NOT_SET`,
which is only used in initialization to determine where the device
type should be overwritten.
@morio
Copy link
Collaborator

morio commented Dec 4, 2023

Hi @beezbo, I'm pretty sure I found the bug and have a fix, try this build:
https://github.com/ZuluSCSI/ZuluSCSI-firmware/actions/runs/7093854145

@morio morio mentioned this issue Dec 4, 2023
Merged
@aperezbios
Copy link
Collaborator

@beezbo for convenience, here are the two Pico-specific firmware blobs, for you to test with. The other link above includes builds for all supported ZuluSCSI platforms, and is quite large, as it includes debug ELF files as well. They're in a small zip file, which is only 632kB in size: ZuluSCSI_Pico_DaynaPORT_2023-12-04_703a752.zip

@beezbo
Copy link
Author

beezbo commented Dec 9, 2023

@morio @aperezbios Thanks for looking into this and providing a fix!! It seems to be working fine now. Appreciate the quick support.

@beezbo beezbo closed this as completed Dec 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@morio morio

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@morio @aperezbios @beezbo