ps1 one chip problem

@ Bad_Ad84
Do you connect all wires like in this picture:
http://www.fatcat.co.nz/psx/install/102/diagrams/pm41%282%298w.jpg

Or do you tie Pin 2,7,8 to GND ?

Cause I tested both and it made no difference for me.

@ master991
Because one of the codes for PIC12F629 has only the ability to play imports and no backups (lag of anti piracy mod) and the other one can play backups, but no imports.

 

He asked about the 12F508/9 series not the the 12F629.
Why would you bring up the AP chip up?

 

Same as picture, 8 wire install. But like I ha e already said, the colour correction mod isn't anything to do with the modchip. It just forces pal output. If you have graphic issues like the op - its an issue with compatibility with your TV. Use a rgb cable.

And he wasn't talking about the 12f629, he was talking about the 12f50x which uses any of the modchip codes... Onechip, what ever.

 

You don't even know what i was about talking, 12F50X it the replacement of the OBSOLETE 12c50X series.
The only differences are the flash memory (so no OTP anymore) and the, logically, the different metod of flashing
Also, Gary opa ported the oldcrow code to the 12f629, but someone ported also the mm3 code. BUT it's a code limitation, not a PIC limitation
Seems you don't know the difference beetwen CODE and PIC.
But yeah! 12fxxx sucks, right?

 

So then tell me, how do you code PIC12F508 with the codes designed for PIC12C508 or likewise.

They are not ported 1:1 , so yes code limitation due to pic limitation!

 

The old crow port is perfect port since he used the source code ported to the 12F629.
I do agree that the MM3 for 12F629 is not perfect but all you need to do is add 3 lines of code and recompile it.

The 12F508 is as good as the 12C508. Getting the 12F508 to work comes down to the user not the chip.
If you don't have the correct programmer that supports the 12F508 then you won't get a proper flash.

The AP chip was never ported to the 12F629 so I have no idea why you would bring it up.

I think what happen is you have no idea how to properly install a modchip in classic mode. The 7.5k, 9k require an extra connection for it to work properly, you also need that extra wire in the 101/102 but since you are in PAL land than you would use the onechip but even then you have admitted you haven't been able to properly flash or install the onechip.
I know exactly what you are doing wrong but since you are the expert I'm sure you will figure it out in no time.

 

Seriusly, stop. Next time, read at least datasheed first to write those bullshits. But you are the expert... ahahhahahhahahahha

Jinn, i think we must stop here, this guy don't even know what he writes.

 

Hmm, can you tell me more info about this?

EDIT:
Jinn are you referring this?
MM3usa12f629.ASM need to be fixed.

Line 327:
[TABLE="width: 85%"]
[TR]
[TD][SIZE=-1]Code:[/SIZE][HR][/HR][/TD]
[/TR]
[TR]
[TD][SIZE=-1]dt 'S','C','E','A' ;European/PAL[/SIZE][/TD]
[/TR]
[TR]
[TD][HR][/HR][/TD]
[/TR]
[/TABLE]


Should be:
[TABLE="width: 85%"]
[TR]
[TD][SIZE=-1]Code:[/SIZE][HR][/HR][/TD]
[/TR]
[TR]
[TD][SIZE=-1]dt 'S','C','E','A' ;America/NTSC U/C[/SIZE][/TD]
[/TR]
[TR]
[TD][HR][/HR][/TD]
[/TR]
[/TABLE]



I think not, because it's only a comment typo error, not a code fix...

 

I never managed to get the 12F508 working with the onechip code. I have no idea why - it wasn't the programmer, since I had several of them, including a Picstart Plus and an ICD2, both of which were officially supported for that device and according to the datasheet they are basically identical. The only difference I could see was that pin 5 was a Schmitt trigger on the 'C50x devices but a regular input on the 'F508 - but this shouldn't have mattered since it was just being driven by a clean looking square wave (WFCK) with fast rise and fall times.

 

Imagine it like this, you are running Windows on a PC using a normal hard drive. you are also running Windows on a PC using an SDD.

No porting of code was required.

The only major change was the "media" that the code is stored on (flash vs cmos), rather than the "CPU" which actually runs the code.

 

The only thing I see here, are people talking "they know how" but never tell.
And thats why I still keep saying, you talk bullshit.
It is like I told you guys and since you can't prove me wrong, not only tell bullshit, I will never believe you.
C-types use internal OSCAL and since F-types dont have them, they will not function with the code !!!
And if you would know right, PSONE SCPH-102c PM-41 (2) has no "extra wire" to install for classic mode or something likewise !
Don't talk bullshit guys, I have all schematics and codes here.

cheers!

 

OSCCAL is purely to fine tune the internal oscillator. Its not a requirement of the code for it to exist. If the internal oscillator doesnt need tuning (i.e. microchip know its OK) then there is no need for it.

I have ran MM3 on the 12F508/9, so yes, it does work.

 

Just checked, 12F509 does have an osccal value - exactly the same as the c series.


Hell, microchip have a migration document from C to F series on their website listing the minimal differences.

Work done for you:

Here is the migration document from PIC12C50x to PIC12C50xA:
http://ww1.microchip.com/downloads/en/DeviceDoc/41133b.pdf

Notice the osccal register has changed. But code still works fine on both A and non A chip.

Here is side by side comparision with microchip recommending you use the F series now.

http://www.microchip.com/wwwproducts/ProductCompare.aspx?product1=PIC12C509&product2=PIC12F509

 

I have sold/installed over 400 12F508 chips with ever code you can think of. Not a single complaint. I even use them for the Laser Shut Off protection for the V12 PS2 and they work just fine.

Trust me, you don't have every diagram or hex code, even I'm missing a few but I can tell you this, I have more diagrams and hex codes than you. I even have the original sources codes and documentation for several of them.

The Old crow/OPA hex required an extra wire to be installed in the 7.5k, 9k and 101/2 and in some cases the MM3 will need it too.
In cases you don't know what "classic mode" means, it's the standard 4-wire install.

 

Proof are that things called datasheet, do you know it? And please, stop talking about things you don't know, you are creating only confusion and disinformation. Thanks.

BTW TriMesh, it's your problem, because onechip works good on pic 12F50x

 

Can anyone answer that question?

 

Be something to do with the bios patch, as thats what points 3 and 4 do.

Video mode is all software controlled on the PS1, so the bios patch sets it to NTSC for some reason. Soon as you put a PAL game in, it will be PAL again.

Or just use RGB

 

even if u put a pal game in the boot screen is the same but im happy got all working thanks to bad ad with helping me with rgb

 

Game can't change the display until the game starts, of course the boot screen doesn't change. It will be when the licensing part comes up

 

Still wondering why it does that? A mistake?
Or something to do with the PSone video mode checks as a workaround?