I think those are ESD protection diodes.
https://www.infineon.com/dgdl/Infineon- ... 3e3ca97dc0
Probably accidentally took it out with static while changing cards...
I think those are ESD protection diodes.
https://www.infineon.com/dgdl/Infineon- ... 3e3ca97dc0
Probably accidentally took it out with static while changing cards...
Well there are 6 caps and a resistor network (RN14 or RN17), then directly to pins on the FPGA. On the off-chance it's not one of those passive components, I would say you are damaging the FPGA somehow. Maybe power is feeding back into it somehow from your amplifier/speakers.
Thanks for your work!
It would be great if it could be extended to emulate the Model III and/or 4 also. The III might be a good bit easier than the 4.
It's very easy to blow the transistor on the USB board. You can replace it or bypass it.
I thought it was just a specification and anyone can make them? What makes something official vs. clone?
32GB!? I have never made one larger than 4GB, because the file system is FAT32 and generally the Amiga was limited anyway (with original file systems, of course). I guess you are mounting something that large over SMB?
Can you freeze and return indefinitely on real hardware with a real cartridge? I didn't have a SS back then, but I know my ISEPIC did not always freeze properly every time and you had to catch it just right.
It may also be because of the restore key trigger... that is odd.
Also of course test the monitor with something else. I've had several of those Dells, and while they are nice, they do tend to suddenly die. Sometimes you can recap and rescue them, sometimes not.
It's an ESP32 hooked up via parallel, i.e. not just an RS-232 connection, so also not a UART modem.
Yes the RGB output of the GS definitely does simulate the artifact color! The Apple II portion would be black and white without that, and it is not. All games look normal.
It's actually the composite output that is not very useful, since the IIGS colors do not work right on that connection.
I don't know what to tell you. You need the specific C128 ROM file also, I think in the MAME folder (yes, I know). It did work but docs say it's only experimental. I stopped using them and just made custom ROM files to load.
The MRA file requires a copy of the 128 core in a directory called "cores" (inside the computers folder).
That C64 on C128 MRA rigged it so that it came up in C64 mode directly. It had issues with resetting though, so you could not inject PRG files or anything, so it was not useful to me.
Same. They will boot up for me, but you can't reset them.
The simulated Amiga resets, or the whole core?
Set mister.ini to composite sync, then use the black cable (I think). If it doesn't work, try the gray- it won't hurt anything, but I believe it was the black cable.
This is really really neat. I had the idea years back to use some kind of USB device for this, but never did anything with it. This works great!
No, if the port is dead, it's dead. I've seen them killed by static or something pulling too much current. You can check and see if the physical connection is good. You may be lucky and it can be resoldered, if so.
I had a USB game pad that had some issue with the cable and fried one of mine... Painful.
I think the 128 core is more mature. They probably should be merged at some point like the 2600/7800.
There are already MRA files to make the 128 into a 64, but it has issues with reset.
Yeah if you can put it together yourself you can do a complete nice system with metal case for about $400 total.
I guess some people may not have the skills to put it all together or just don't want to.
It definitely does a CLI right before jumping to BASIC.
See $FCFE.
Also, most text output becomes garbled and unreadable just after booting NitroOS9 kernel on most disks. It looks like it switches into a weird semigraphic mode...
Yeah the first maze color glitch happens if you quickly start a game before the attract mode plays very far. Passing through ghosts is a well known bug/feature from Pac-Man.
I verified it. No changes at all other than swapping 32M for 128M and it works fine. Swap back to 32M, no boot. Same exact setup otherwise.
I put it in as an issue in Github.