That makes sense now. Assume the mapping of the switch into ROM is done by the GAL/PAL? I only have 256k flash parts on hand anyway so that shouldn't be a problem. I do remember you looking at the AR carts and USB transfer a while back..do you know how hard would it be to implement the contents/map...

Thanks Trimesh, I shall give this a go. The seller of the PSone on eBay mentions running Caetla - by patched would I be able to just flash caetla? Would I be correct in assuming that if I use a supported flash part, and wire up W/E I should be able to flash it using xflash? Thanks My guess is that ...

Electrically, it's pretty simple - most of the pins are identical to the ones used on the boot ROM with the exception that CE/ has to go to pin 98 of the CPU (the boot ROM goes to pin 97) - data, address and OE/ go to the same places as the corresponding signals on the boot ROM. The code you put in ...

damiank94 wrote: ↑

March 8th, 2019, 8:43 pm

So, Mayumi and Multimode also didn't release pin 6? That sucks. I asked some people around with newer motherboard with modchips about that.

I have no proof of this, but based on examination of the code I think the code that supports PU22/PU23/PSone in both MM3 and ONEchip was copied from Mayumi 4

It should work - the boot ROM patch on the ONEchip is separate from the modchip functions and you can use either of them on their own. Having said that, I'm not sure it will actually work any better, since the actual code in the ONEchip that does the modchip function is pretty much identical to the ...

Honestly, my guess is that you have two bad optical pickup assemblies, not least because they are by far the highest failure rate item on these consoles. I would recommend finding someone local that has a working SCPH-9002 (and doesn't mind you taking it apart!) and swapping the parts you have (PSU,...

Did you get these parts, or are you still looking for them?

Net Yaroze is very limited and expensive. Try to setup and install Psy-Q and compile some code . Then just run PS-EXE (.EXE) file with any working emulator. I prefer PCSXR, but you can use EPSXE or NO$PSX (god bless VRAM viewer!) Good luck :> I think the Yaroze is helpful for getting a quick start ...

You don't have to go back that far - a lot of the early P4 machines supported Windows 98SE too. They typically shipped with XP on them, but since during that time frame a lot of business users were still using 98 they still had support (and drivers) for it. More problematic, depending on the develop...

It shouldn't be a problem - I've written lots of stuff with the source split over multiple files. You could try compiling it manually to see if it's a problem with the build system - just use a command like ccpsx -g -Xo$80010000 file1.c file2.c filex.c -otarget.cpe cpe2x target.cpe Someone was worki...

The short answer is that on a PU-18 the modchip shouldn't interfere with reading the disc. On the older boards (PU-7, PU-8, PU-18, PU-20) the output data from the modchip is connected directly to the mechacon MCU as a digital signal and no connection is made to the analog side of the circuit. The on...

No, that's not normal - from the look of it, the chip has already been programmed with something - and since the 12C508 is an OTP device that means it's basically useless.

This approach seems great so far. About that CPU speed: I really don't know much about ROM reading yet but I assumed that OE pin was there to signal that data is ready. Shouldn't this enable us to deliver the data at the speed we want? The signal you want is conventionally called WAIT - but in the ...

It is the wrong install diagram - that's for the "Stealth 2.x" series of chips. On the PU-8, the MM3 does not support full stealth and is normally installed in 4-wire mode with only pins 1, 5, 6 and 8 connected - all of which go to the same places as the corresponding pin numbers on the stealth 2.x ...

I think these are involved in IC706. But this custom chip, datasheet is only in general terms. There is a lot of information on the components of PU-18 with datasheets. There are also descriptions of the pin assignments of the microcircuits. http://wiki.psxdev.ru/index.php/PU-18 Yeah, the problem i...

Ah yeah, I wrote what I remembered. So the C is for center.. Anyway, we know that the wobble on pressed disks creates a pattern that some kind of tracking error circuit converts to the 1's and 0's that form the SCEX string. That error detect circuit is part of any CD DSP, but Sony added another of ...

Yes, it's entirely reasonable what SCEE did. That's why I find it so odd. As I understand it, the LibCrypt option wasn't available until later, but I may be wrong on that. At the time the anti-modchip code came out, libcrypt was something that SCEE had in development in their Cambridge research cen...

Maybe I'm jaded but such a pro consumer decision just sounds odd to me. It is possible though, of course. One other development of the time: The anti region lock modchip. It was much more complicated to pull of, but it replaced just the last letter of the SCEX string, allowing games of all regions ...

If you search this forum (and maybe Assemblergames, I forgot), you will find this most likely explanation: SCEE simply did not want this code to lock out games from other regions. My addition to it: Maybe they didn't fully understand what this code would block and management simply banned the idea ...

OK, that looks like an original Datel PCB for sure - I don't think I've ever seen a gameshark with an AMD flash chip in it, though. See if you can find one of the chips that were used in the Datel carts - my original Datel carts have Atmel AT29C010 chips in them, and they definitely work .