help programming a 12f629 wiht ps1 modchip hex?

[wolffangalchemist]

i have been trying everything i can think of, retail disc boot fine but backups that boot fine with tonyhax do not boot.
think it boils down to either bad code that i am using or setting when buring the chip.
figured maybe some here with more experience with pic programming could possibly assist me?
here are some of my install pictures i am pretty sure it isn't my wiring as i have redone it about four times to be sure reflashing each time this being the final result,

Spoiler: chip install

(will add from phone in a min)
everything is as short as i can possibly get it, and i have no bridges to speak of.
i got the hex files for the 12f629 from this site
https://www.backoldgaming.com/conso...ip-mayumi-v4-multimode3-mm3-onechip-psnee-ps1
i used the mayumi v4 hex for a usa console as that is what i have. it is a pm-41 psone model and i used the points on the schematic in the files.
i tried mm3 before but was using 12c508a pic chips and the appropriate hex file,
they where giving me all sorts of write errors so i think they may have been counterfeit,
i still have about 6 of those that are "blank" and i kept the oscal val when burring the ones i used.
i suspect it might be these settings that need changing for either hex files

but i have no idea what these should be and can find zero info on google about them in the little info on making your own modchips i could muster up.
here is the hex dumped from my 12f629

it's in the shit.zip file linked below.
i used both a k150 pic programmer and a tL866ii plus to erase and write to it multiple times with no success in getting a backup to boot,
it seems to match the original except the oscal value which probably isn't needed with mayumi v4 but i tried it with and without the value to no avail.
any advice is welcome, i would like to successfully get this going.

 

[SylverReZ]

Mayumi 4 write protects the chip after you wrote the hex, meaning that it cannot be reprogrammed. Before programming the chip, you must ensure that the OSC (oscillator) value always remains the same, do note it down in case it ever changes, so then you can change it back to the default value afterwards.

I've had success with my TL866II Plus and I didn't need to change anything beforehand.

 

[wolffangalchemist]

Mayumi 4 write protects the chip after you wrote the hex, meaning that it cannot be reprogrammed. Before programming the chip, you must ensure that the OSC (oscillator) value always remains the same, do note it down in case it ever changes, so then you can change it back to the default value afterwards.

I've had success with my TL866II Plus and I didn't need to change anything beforehand.

yeah i figfured it out, deff something up with the mayumi v4 files i got for the 12f629. i tried mm3 for it on the TL866ii plus, same chip i wrote mayumi v4 to, and got it first go. that said after reassembly today game or no game i am stuck on the white sony screen... could be a fuse apparently, gonna check that and my wiring later today. i really like that the tl866ii plus automatically seems to leave the oscal alone and doesn't let it get over written.
Edit: it isn't a fuse gonna have to ohm it out with a multimeter. So for now i have a scph 9001 without a cd drive, frankenstation anyone?
Yeah...

Edit 2: a little less franken station.

 

[SylverReZ]

yeah i figfured it out, deff something up with the mayumi v4 files i got for the 12f629. i tried mm3 for it on the TL866ii plus, same chip i wrote mayumi v4 to, and got it first go. that said after reassembly today game or no game i am stuck on the white sony screen...

Because you wrote Mayumi v4 on the 12F629, it has set the chip to read only. You will need to get a spare 12F629 and program the MultiMode3 code again.

 

[wolffangalchemist]

Because you wrote Mayumi v4 on the 12F629, it has set the chip to read only. You will need to get a spare 12F629 and program the MultiMode3 code again.

Funny enough it wrote mm3 just fine to the 12F629 that had mayumi 4 on it, I think I might have had a messed up hex file for mayumi. That said even if it failed I have like 10 more 12f629 left and afew attiny85 boards, probably gonna flash them, test them, and sell them eventually after i get the other ps1 I have figured out it is having some issues all on it's own.

 

[SylverReZ]

Funny enough it wrote mm3 just fine to the 12F629 that had mayumi 4 on it, I think I might have has a messed up hex file for mayumi.

Might've overwritten the fuses for all I know or that its the wrong chip.

Here are the official MD5 checksums for Mayumi V4 dated from September 27, 2000.
(A=USA, E=EUR, I=JPN)

Supported chips: 12C508, 12C508A, 12C509, 12C509A.

7faf62085304205160319a32b13c870a Mayu4_0A.hex
cbc783f2321164c566e6e8a34be8c8d0 Mayu4_0E.hex
487007b3e5e6d484bef7fa13296dfb35 Mayu4_0I.hex

Download: https://github.com/rolfposchmann/Mayumi_v4/blob/master/doc/mod0927.zip

 

[barronwaffles]

You can't make a PIC18/16F device read only/write protected - the CP and CPD configuration bits exist to prevent you from reading program and/or data (EEPROM) memory back via external tools.

This excludes 'modern' chips with the ability to write their own program memory - those often have a set of configuration bits to prevent firmware from accidentally overwriting segments of its own program.

I'm not 100% sure about this configuration bit (attached)

Try setting it to something that looks like this :
100 = INTOSC oscillator: I/O function on GP4/OSC2/CLKOUT pin, I/O function on GP5/OSC1/CLKIN