exxos's Atari, Amiga & retro forum

Atarian Computing wrote: 07 Dec 2020 08:51 With the latest firmware, everything works except for CosmosEx. CosmosEx ACSI SD works so the ACSI part seems fine. However, loading the CosmosEx driver results in the actual CosmosEx not being found. @derkom Did you encounter issues like this with your setup?

I haven't tested extensively, since I only recently got my CosmosEx, and to be honest, I'm not even sure if I've tested it at all in 68030 mode. I wasn't paying attention to how the switch was set at the time.

What are you referring to when you say "loading the CosmosEx driver"? Are you referring to the configuration program CF_CONF.PRG? It was certainly working fine in my setup, but my data are useless since I don't know which CPU I was using. ;-)

Atarian Computing wrote: 07 Dec 2020 08:51 With the latest firmware, everything works except for CosmosEx. CosmosEx ACSI SD works so the ACSI part seems fine. However, loading the CosmosEx driver results in the actual CosmosEx not being found. @derkom Did you encounter issues like this with your setup?

Now that I am finally getting pieces assembled, I've run into this problem as well. HDDRIVER sees the CosmosEx, but CE_DD.PRG just sits there scanning and can't find it. Flip the switch back over to 68000 mode, and everything is working fine.

Due to the Stacy having the MegaSTE-style ACSI connection internally, I lack the hardware to plug in any other ACSI devices and see if there is any strange behaviour.

Did you ever figure anything out here? Any thoughts on this from @agranlund or @terriblefire?

Does this change if you revert to previous firmware versions?

I know that my TF536 was more tetchy (and slower) with the latest firmware relative to the one it came with (which would have been from August).

stephen_usher wrote: 13 Jan 2021 09:53 Does this change if you revert to previous firmware versions?

Checking that out is somewhere on my roadmap (trying to track down an unrelated random reboot issue at the moment). Simply switching back to an older firmware could be good for troubleshooting, but not necessarily for a permanent solution, as I'm running a custom build from @agranlund on my TF, which moves on the onboard IDE over to secondary, so that it won't conflict with the Lightning ST IDE.

Oh, I see.