I’ve raised this on Twitter before, but I want to formally have an issue documented here since it’s been four months and I’ve never seen my ZZ work properly in the machine I bought it for. Here’s what I’ve found through troubleshooting:
- NTSC progressive works with the Denise adapter
- If I switch to Interlaced, the ZZ loses sync and flickers garbage on a black screen every so often
- Usually if I switch back to progressive scan, it works, but sometimes the framebuffer ends up corrupted
- Indivision ECS works flawlessly in the same machine in the same modes, so it’s not because there’s actually a signal problem from Denise
- I’ve tried a wide variety of firmware releases, back to the original one. None work.
- It’s not my monitor (I’ll explain definitively why shortly)
I tried testing with the video slot adapter, and there’s mixed news there:
- If I use the ZZ with the video slot adapter in an A2000 with J300 set to 1-2 (external tick) NTSC laced and progressive both work. Hooray! (This also confirms there’s not a problem with my monitor.)
- If I move J300 to 2-3 (internal tick), the flicker fixer doesn’t work at all, failing to sync and flashing garbage on screen. This is a showstopper for me as well - the A2000 it’s meant to live in uses an ATX power supply, as the original died. That means I can’t use external tick in that machine.
I don’t know if the tick source is related to my interlaced issues with the Denise adapter, as I don’t want to move that adapter into my machine with an original PSU right now, and it’s super difficult to disconnect the A2000 PSU connector from the system board. Plus the A500 doesn’t even have an external tick option, so how could the Denise adapter rely on it?
Lukas mentioned on Twitter the video slot adapter uses HSYNC and VSYNC, and maybe the Denise issues are an issue decoding CSYNC for laced modes. In my opinion, both adapters should use CSYNC, as HSYNC/VSYNC don’t work in genlock video modes. If it is an issue decoding CSYNC, both RGB2HDMI and the Indivision already do this correctly. Perhaps you could look at the timings for the RGB2HDMI and find the mismatch.
I really want to love the ZZ9000, and was so excited to receive it after waiting eight months. But I’m really disillusioned by the most basic functionality still not working. Basic hires video modes are table stakes. I understand and admire the excitement I see around building new things like the ZZ9000AX (which I ordered!), but it hurts for that to be at the expense of the base product fulfilling its basic promises as a product. I can’t use any of that cool stuff if basic functionality doesn’t work.
Again, I’m ready and willing to help investigate and get this fixed however I can. But if there’s still no movement by the end of January, I strongly suspect my ZZ is going in a box, to be replaced by Matzes A1k adapter, an Indivision, an X-Surf, and a RapidRoad. So much more hardware, and less capable RTG graphics, but it works.
- Amiga model: Amiga 2000 Rev6 (I also tested the video slot adapter in a Rev4)
- 680x0 CPU: 68040/68030 (I’ve tested both)
- RAM Configuration: 64MB fast, 2MB chip
- Kickstart, AmigaOS Versions: 3.2
- ZZ9000 Firmware version: 1.9.1
- ZZ9000 Driver version: 1.9.1
- Monitor model: Various; not related to the problem
- Other Zorro cards: I’ve tested various configurations, with as few as just a GVP HC+8; it’s not related to the problem since this is strictly a scan doubler issue.