What's new
By:
Filters

Zero PIC issue (I think)

Nimmers

Nimmers

Grand Master
Joined
Oct 25, 2016
Messages
620
Reaction score
579
Location
NSW, Australia
Hey guys,

I have been slowly collecting the parts to put a NetBoot setup together for a while.

Naomi.jpg

-I've replaced all the fans
-Burned the multi BIOS
-Got a power supply sorted
-I don't think my NULL PIC works though

I think I'm almost there just this last issue.

Using TransferGame.exe results in:

D:\TransferGame>TransferGame.exe 192.168.199.75 SNKGD_SL.BIN


-----------------------------------------------------
Transfer Game PROGRAM
æèÄÞɵIPâAâhâîâX:192.168.199.75 port
ô]æùâtâ@âCâï:SNKGD_SL.BIN
-----------------------------------------------------
Now Connecting...
DIMMâtâ@ü[âÇâoü[âWâçâôüF0x0317
DIMMâTâCâYüF256MB
DIMMÅÒé╠CRCÆlüF0xfcb4eacc
CRCâXâeü[â^âXĵô¥èJÄn
CRCâXâeü[â^âXĵô¥ÅIù╣
CRCâXâeü[â^âXüF3
CRCîvÄZÆå...
CRCîvÄZÅIù╣üB
CRCé¬êÛÆvéÁé▄éÁé¢üB
CRCâXâeü[â^âXé¬ê┘ÅÝé╚é╠é┼özÉMéÁé▄éÀüB
âoâCâiâèâtâ@âCâïô]æùèJÄn
File size: 159383552 bytes
rate: 33149.5 bytes/sec (262080/159383552)byte
rate: 4062755.9 bytes/sec (4389840/159383552)byte
rate: 4324965.5 bytes/sec (8779680/159383552)byte
rate: 4256220.5 bytes/sec (13104000/159383552)byte
rate: 4583172.4 bytes/sec (17755920/159383552)byte
rate: 4571162.8 bytes/sec (22473360/159383552)byte
rate: 4518620.7 bytes/sec (27059760/159383552)byte
rate: 4514173.2 bytes/sec (31646160/159383552)byte
rate: 4256220.5 bytes/sec (35970480/159383552)byte
rate: 4841379.3 bytes/sec (40884480/159383552)byte
rate: 4191732.3 bytes/sec (45143280/159383552)byte
rate: 4389517.2 bytes/sec (49598640/159383552)byte
rate: 4385196.9 bytes/sec (54054000/159383552)byte
rate: 4127244.1 bytes/sec (58247280/159383552)byte
rate: 4324965.5 bytes/sec (62637120/159383552)byte
rate: 4772126.0 bytes/sec (67485600/159383552)byte
rate: 4578661.4 bytes/sec (72137520/159383552)byte
rate: 4066758.6 bytes/sec (76265280/159383552)byte
rate: 4578661.4 bytes/sec (80917200/159383552)byte
rate: 4776827.6 bytes/sec (85765680/159383552)byte
rate: 4127244.1 bytes/sec (89958960/159383552)byte
rate: 4578661.4 bytes/sec (94610880/159383552)byte
rate: 4324965.5 bytes/sec (99000720/159383552)byte
rate: 4320708.7 bytes/sec (103390560/159383552)byte
rate: 4320708.7 bytes/sec (107780400/159383552)byte
rate: 4389517.2 bytes/sec (112235760/159383552)byte
rate: 4256220.5 bytes/sec (116560080/159383552)byte
rate: 4389517.2 bytes/sec (121015440/159383552)byte
rate: 4256220.5 bytes/sec (125339760/159383552)byte
rate: 4514173.2 bytes/sec (129926160/159383552)byte
rate: 4324965.5 bytes/sec (134316000/159383552)byte
rate: 4449685.0 bytes/sec (138836880/159383552)byte
rate: 4449685.0 bytes/sec (143357760/159383552)byte
rate: 4131310.3 bytes/sec (147551040/159383552)byte
rate: 4191732.3 bytes/sec (151809840/159383552)byte
rate: 4066758.6 bytes/sec (155937600/159383552)byte
TOTAL TIME: 44218 ms
CRCô]æù ü¿ énéjüiCRC:0xfcb4eaccüj
NAOMIâèâZâbâg ü¿ énéj
âtâ@âCâïözÉMé¬ÅIù╣éÁé▄éÁé¢üB

Then game boots to error 31

Error.jpg



Using the python script:

evan@Omega:/mnt/d/TransferGame$ python naomi_boot.py SNKGD_SL.BIN
connecting...
ok!
length: 09800000
time limit hack looping...


This title boots fine!


Not all games work with the python script though. When I use the python script, some games do the Error 31 thing, for example Street Fighter Zero3 Upper.

For the PIC:

Have used the code I got from @werejag

I burned it with a Wellon VP-280 - have attached screenshots of my settings. It looks to have burned correctly. I must have missed something but not sure what.

Anyone have any ideas?


Compare.PNG
Settings2.PNG
 

Attachments

  • PIC_Chips.jpg
    PIC_Chips.jpg
    133.5 KB · Views: 174
  • Settings1.PNG
    Settings1.PNG
    335.7 KB · Views: 159
Error 33 is the one I'd always get with zero pic issues. I think 31 has to do with the game data, the region, encryption, corrupted transfer, or wrong bios/region setting. Are you using the newest bios? What game/region are the jumpers set to?

Are you saying the same game/data works when you transfer it one way, but not with another?
 
ekorz said:
Error 33 is the one I'd always get with zero pic issues. I think 31 has to do with the game data, the region, encryption, corrupted transfer, or wrong bios/region setting. Are you using the newest bios? What game/region are the jumpers set to?

Are you saying the same game/data works when you transfer it one way, but not with another?
Click to expand...
Hi mate,

Yep so the game does not work with TransferGame.exe but it does work if I use the python script. But some games don't even work with the Python script.

I burned the revision H multi-bios and I've got it set to USA. Bios came from here.

Could definitely be user error on my part. Just not sure where to start.
 
Hm ok. Might be the PIC then.. If I recall, the pi script keeps the connection open, so you don't need a zero pic. Transfergame doesn't do that, so the PIC needs to be good.

That PIC is a pain in the butt and still a bit of a mystery to me, even though a working PIC has emerged from my own programmer: Programming zero-key pic

Ill PM you a couple things that may help
 
If you get stuck - I can burn you another zero PIC and send it to you, the settings need to be correct or it won't function

Could also be a power issue, bad BIOS, bad anything. NAOMI netbooting is so fickle it's scary :/
 
xodaraP said:
If you get stuck - I can burn you another zero PIC and send it to you, the settings need to be correct or it won't function

Could also be a power issue, bad BIOS, bad anything. NAOMI netbooting is so fickle it's scary :/
Click to expand...
yeah. Super fickle. Like... could be your plastic casing is causing the DIMM to not be seated correctly (they do bolt it down, stock) and it might work if you just seat the pcb outside the shell. I assume since you get it working sometimes that you solved a lot of that stuff already!

Someone should make a multi cart...
 
ekorz said:
Hm ok. Might be the PIC then.. If I recall, the pi script keeps the connection open, so you don't need a zero pic. Transfergame doesn't do that, so the PIC needs to be good.
Click to expand...
i had errors for some games with the Pi script (31,32,33, don’t remember which one), those errors where solved with a new PIC.
 
Mitsurugi-w said:
Oscillator type needs to be HS and your security fuses are all wrong.
Click to expand...
Thanks Mitsu,

I see the Oscillator setting, what are the fuse settings? Sorry mate, I'm a noob :(
 

Attachments

  • Mistake.PNG
    Mistake.PNG
    77 KB · Views: 155
It says right there in the source. :)

HS Oscillator
CP = off
Data CP = off
LVP = on
BODEN = off
MCLRE = on
PWRTE = on
WDT = off
 
Nimmers said:
Mitsurugi-w said:
It says right there in the source. :)

HS Oscillator
CP = off
Data CP = off
LVP = on
BODEN = off
MCLRE = on
PWRTE = on
WDT = off
Click to expand...
*facepalm*
I assume CP = the "Secure" option?
Click to expand...
No, Code Protection, you have it there, you have it disabled in your picture :)

edit: scratch that, data code protection is also listed, so yes I'd say it's secure
 
Hey man, silly question but since that looks like an Atomiswave conversion rom? Do you get the same error with a regular Naomi rom? Some of us have trouble booting Atomiswave conversions at all.
 
xodaraP said:
Nimmers said:
Mitsurugi-w said:
It says right there in the source. :)

HS Oscillator
CP = off
Data CP = off
LVP = on
BODEN = off
MCLRE = on
PWRTE = on
WDT = off
Click to expand...
*facepalm*I assume CP = the "Secure" option?
Click to expand...
No, Code Protection, you have it there, you have it disabled in your picture :)

edit: scratch that, data code protection is also listed, so yes I'd say it's secure
Click to expand...
You are a legend mate!

Here's the settings that worked, my game just booted using only TransferGame.exe

Works.PNG

I'll do some more testing.
 
The CP and DataCP flags are not that important.
If they are set, the code and data can't be read out from the chip, but the program doesn't use or check them.
The oscillator and some of the other flags like the WDT are very important.
It was a wrong oscillator setting that made some of those pics work on a chihiro 1 but not on a chihiro 3.

The python script does not only keep the connection open, it also resets a timer value regulary so that no timeout is generated.
Due to that, the system can run, even without pic installed.

If your pic doesn't work due to wrong flag settings, you will likely have the same issues if you try to run the games without pic as well.
 
obcd said:
The CP and DataCP flags are not that important.
If they are set, the code and data can't be read out from the chip, but the program doesn't use or check them.
The oscillator and some of the other flags like the WDT are very important.
It was a wrong oscillator setting that made some of those pics work on a chihiro 1 but not on a chihiro 3.

The python script does not only keep the connection open, it also resets a timer value regulary so that no timeout is generated.
Due to that, the system can run, even without pic installed.

If your pic doesn't work due to wrong flag settings, you will likely have the same issues if you try to run the games without pic as well.
Click to expand...
Yeah I think all my problems were probably due to having the incorrectly written PIC inserted.

Done a bunch of testing and it works awesome now :) Thanks all!
 
You must log in or register to reply here.
Back
Top