What's new
Got a new zero key from mitsu and played around with my old netdimm for a while. Still seems flaky, but the zero key works. I used transfergame.exe to test. I like how that gives you a status as it loads. so my other zero key was definitely bad. I still have an issue where a game will sometimes load a bit then fail. Then I just have to try again. What usually works is if I go to test and clear backup data, see if I can ping the netdimm and if I can try from there. Sometimes I can’t seem to ping it but resetting gets it back to “checking network” and I can usually ping it then. So this netdimm seems to work but it’s a bit of a pain. The other one I got recently works great and I just got a cf kit for another regular dimm from mitsu. So with 3 ways to boot any game I figure I’ll be covered when some of this stuff inevitably gives me more issues later.
 
Same, had problems with my Naomi setup too. It was the pic - the file I was burning on it was just bad. Eventually found one that worked.
 
Just checking in because I have the same Error 33 issue with my setup.

Did this issue only occur for people only when trying WiPi? I can load games one at a time via USB just fine, but whenever I switch over to the WiPi setup, the system will run a game for maybe 30 secs before resetting into Error 33. Based on skimming over this thread, my guess is that I need to replace my pic, but I'm just making sure since the problem seems to be specific to WiPi.
 
You can remove the pic all together and turn on the time hack in the settings menu. This will eliminate the need for the PIC. Not sure if it works 100% with all games though.

If nothing else, it will let you test to see if the PIC is the issue.
Finally had some time to try this out, and it seemed to do the trick. I didn't even remove the PIC yet, but I haven't run into Error 33 since enabling Time Hack for the few games I tried (Hotuko, Tetris K, MBAA, Puyo Fever). I will have the chip redone at some point, thanks for for the help on this!
 
Pretty good indication your PIC, or something to do with it is faulty.

I could be wrong, but playing without the PIC and time hack should work perfectly fine....
Yep, sounds like a bad PIC.

And you're not wrong, a NAOMI will run fine with a time limit hack running, as long as the computer running the hack stays online and running. You only need a PIC to be able to disconnect the host PC (or Pi) while a game is running. Generally though I use a PIC so I can shut down my computer after netbooting.
 
What PSU you using? My naomi net boot setup is very temperamental when I try to use the blast city psu and is way better when I use a Sun psu
 
What PSU you using? My naomi net boot setup is very temperamental when I try to use the blast city psu and is way better when I use a Sun psu
1630362293465.png
 
Naomi universal cab.

and blast city.

and now that I have a working pic, works fine everywhere, including the blast
 
Last edited:
I'm having this same error, but only with one specific network only daughter board. The 0-pic works fine with other boards, and I've been able to update the firmware through the network daughter board so I know that communication is OK. But I get "error 33 network gateway not found" after a game loads. Game loads, the Naomi reboots, runs the RAM check and then errors out.

Anyone have any ideas? I have another 0-pic I can pry out of another system to test with...

Edit: figured it out... problem was that the cabinet type was set to 1 player. Changed it to 2 player to match my JVS controller and presto it works.
Bah, spoke too soon. Looks like it works sometimes now...

When it fails, it drops off the network (ethernet port shows no connection)
 
Last edited:
Check PIC socket for cold joints and try lifting the 0 pic like 1/2mm out of the socket after pushing it down.
 
Honestly you could always try the time limit hack that eliminates the need for a PIC.
 
Thanks, I've got a wipi-netbooter setup here somewhere. Will give that a try.
Good deal. It's pretty straightforward, the function existed in the netboot .py script forever, it's just usually diabled. If you need / if wipi doesn't work easily I can provide you the netboot .py script (good ol triforcetools iirc) in 2 forms, one with and one without the hack enabled.

The only limitation of the hack is the dimm and pi/computer have to stay connected. But, at least that's better than a non working dimm.
 
OK... so solder joints and traces look fine (checked with multimeter and inspection scope). I couldn't get it to be recognised by the wipi-netbooter, it's doing it's "I refuse to acknowledge the network" thing (sometimes I can get TX/RX LEDs to light, but it cant be seen). Tried with a known good "standard" network board and it's working as expected, so I the main board would seem to be OK as is the raspberry-pi.

Thinking it's something with this "network only" variant. There are some jumpers and connectors that are not found on the standard boards.

(board in question)
IMG_1044.jpg


(trace check)
Quick Camera Image 2021-10-26 at 7.07.03 AM.png


(working test with known good network board)
IMG_1045.jpg


Update: Thinking this ethernet board is bjorked.
 
Last edited:
I am getting this error when I use the WiPi on an ethernet switch. I am connecting to the WiPi through the wireless, but have it hooked up to a ethernet switch that runs to the 2 cabinets I have setup right now. I can load games just fine, but then it will default to Error 33. Now if I hook the WiPi up directly to the machine or I run one of them with my older dedicated Raspberry Pi 1 running NaoPi it will run fine. So I do not think it is a Zero Pic issue.
The netdimm's are upgraded to 4.02
I did not want to run the cabinets on my home network necessarily - I was just hoping to run them on this small network.
Is there something I am missing?
 
Back
Top