Hi there, I haven't really had much success trying to burn the onechip.hex (downloaded from http://www.eurasia.nu) on to my 12c508A OTP chip for psone 102 41(A). if i read the blank chip it gives me address hex 0000000 FF 0F FF 0F FF 0F FF 0F FF 0F FF 0F FF 0F FF 0F ...down to address 0001FF0 FF 0F FF 0F FF 0F FF 0F FF 0F FF 0F FF 0F FF 0F However 1 address shows this 00003F0 HEX FF 0F FF 0F FF 0F FF 0F FF 0F FF 0F FF 0F 74 0C <-- Last 4 hex digits, would that be the internal osc hex code for that chip? but then when i load up the onechip hex into the G540 programmer the onechip hex is there and on address line 0003F0 it still ends with 74 0C and the onechip hex also adds to data to the last address line 0001FF0 HEX FF 0F FF 0F FF 0F FF 0F FF 0F FF 0F FF 0F EA 0F < last 4 digits changed on address line 0001FF0. on top of that i need to know the config settings are for CP, WDTE , FOSC1, FOSC0....and there's not an option to set MCLR. I have tried to include screen shots to give you some ideas as to what i am working with. Any help would be great.
OK I'm not 100% on this but you should check the 12C508A datasheet for OSC calibration offset first. That will clear any doubt about this. Again in the datasheet, check the bit settings for FOSC0 and FOSC1, a combination of those 2 will instruct the microcontroller to use it's internal oscillator. My guess is that PSX modchips use internal oscillator to generate a clock signal. My guess is that both those FOSC bits must not be set but again check the datasheet. WDTE is most likely watchdog. If the code is well constructed you could leave this set and watchdog would never be triggered. I would not set this bit, you don't want the PIC to reset if it locks up. As long as it does it's job when you insert a disc. I don't know what CP is (ComParator?), check datasheet for it. I don't remember this PIC memory structure but couldn't it be that the data at the last line of the HEX is preprogrammed configuration bits (FOSC, WDTE, etc)? Also as a suggestion I would go out and buy a 12F508 PIC. 12C508A are, like you mentionned, OTP and will be useless if you screw up the programming. With the 12F, you'll have the convenience of retrying without scraping a PIC everytime. I used a 12F508 in my 7501 PSX without any issue.
CP = code protect OSC CAL is set at the factory, you need to read it from the pic, write it down, then insert this before programming. MM3 uses internal osc, Mayumi v4 uses external Last section of pic layout is the osc cal value
Cheers for the replies, i kinda understand the process but my programmer seems a little different than what other people have used which throws me off a little. Anyway, i have done the steps but want to check before i program the chip if i am on the right lines. I have took screen shots of my steps but there are a few things i still don't quite understand with the Value read from the blank chip and then loading up the onechip.hex. If 74 0C is the oscal value from the blank chip, why is it when i set the fuses/caps config, it changes the very last bit of hex to what you see in the screen shot (12 00) and the oscal value is halfway up the hex program if you look at the addresses. if that makes sense? oh and i do have 12F508's but i didn't think you could use them with the onechip.hex as it was written for the 508a was it not?
Ahh, the Genius G540 one of the known programmers to have the worst software lol but I was helping someone out make a chip using that programmer a little over a year ago and it was successful. Though he was programming a mm3 chip and using the 12F629 Im not sure why those last 4 digits would change after, it looks like the oscal value should be entered there ("74 0C")
yeah the software is pretty pants. I can't even expand the data buffer window to view all the code. I do have a pic k150 programmer too which i haven't had any success with. i always get errors during the programming stage and wrecks the chip
I think you might have to take a leap of faith here. I would make sure "74 0C" is in the same spot on the address line "00003F0" after loading the one chip hex. Also make sure you enter the configuation bits after you load the one chip hex. You got it right from what i see in your screenshots above... that's for sure.
yeah the 74 0C always stays in in the same place/address and the config bit changes at the bottom. Its just hard to tell if the chip has been flashed with the correct settings or if i have a short in my wiring
just tried programming it and another dud happened. it wrote the first few lines and put zeros in the rest of the addresses. what would be the correct settings to load the hex file in from the window on the left?
ok the programmer is trashy but surely the onechip.hex works otherwise it wouldnt be posted online would it not? Which programmer would you suggest that is high quality that can program pic and avr atmel chips? something that supports mplab or something? i think the only reason i got the g540 is to program some atmel eeproms but that was it really, i haven't really used it to program anything else till now.
Wow, that software looks really bad. Any decent program should read OSCCAL automatically from the chip before programming it (at least IC-Prog does). Also, I think you should switch file formation to BIN. It seems like now it reads values in 16 bit little endian fashion which is wrong. For programming the chip you need 13 V which you get from stepping up the USBs 5V. If you have a voltage drop maybe there is not enough power to program the chip. Make sure that you don't use USB hub and that you have a short cord. The best thing to do is to connect it to the back of your PC directly and not in front USB ports. Anyway. I'm using the cheapest method ever and it's working without a hitch - JDM Programmer. If you are good with a soldering iron you can easily build one yourself. My ghetto JDM programmer The only downside to it is that I have to use Windows XP as it's driver can't be installed on 64 bit windows. And I have to use a real COM port (no USB adapters). BTW, is it just me or has PS1 modchip craze started again? I see bunch of new threads about PS1 modchips lately.
i will give it a try and see if it makes a change to how it loads up. I dunno i already have an old modded chunky ps1 had it since like '96 yet i dont know what kind of chip/hex was used. all i know is that it doesn't play ntsc, well it might read it but the screen goes blank, might need the ntsc mod. It does play final fantasy stuff so i imagine it has some sort of stealth. Anyway i had 2 small psones i wonna mod to add to the rest of my collection of ps1,psone,ps2 phat, ps2 slim, ps3 super slim. (i did have a ps3 phat 60gb but that gave up in the summer after 7 years of no ylod) was gutted. waiting for decent games to come out for the ps4 and to finish of the rest of my games before i make a move. i will still always come back to the ps1 as they just dont make games they use to. its all just first person shooters, racing and mmorpg stuff that you pay £40-50 and finish it in 3 days. lol
