I'll throw this out there even though I'm not 100% positive it's still relevant:
I would be willing to at least loan out my nonfunctional Q700 board (the one that spawned this thread) or would outright donate it to science to help further this cause. It's not doing anything for me right now and may never work. It (and I!) would benefit if there's even a hint of what caused the ADB issue I'm having. PM me if there is any interest.
Well, CUDA as well as its predecessors (Bit-bang, Egret) is basically a multipurpose MCU that emulates some peripheral bus protocol using the bit banging approach. In other words, all required functionality is implemented in software.
To recreate the chip, we thus need to download and understand its firmware.
IIRC, Arbee from MAME project may have already obtained a dump of CUDA Lite as he did for other CUDA versions. I'm going to ask him...
I've just started uploading a commented assembly for the Cuda Firmware v2.37, see this Github repository. To my knowledge, that's the latest firmware available but we need to re-check it. In the next days, I'm going to put even more docs on Cuda - so stay tuned!
Thanks for the commented disassembly! Is that the whole thing, or just a part? I didn't see anything in there for how CUDA monitors the power button and asserts or de-asserts /PFW to turn on/off the power supply.
Did anyone manage to dump the contents of an Egret? My understanding is that it's got custom Apple ROM contents to handle RTC/ADB.
My understanding of how most of this works is limited beyond "there's stuff on a chip there and we want to grab that and program a replacement chip", so what are the main blockers to achieiving this?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.