What's new
By:

NAOMI netboot HELP!

G

gigagiga44

Student
Joined
Aug 28, 2024
Messages
32
Reaction score
8
Location
japan
I have a DIMM board with naomi2 and firmware version 3.17.
I would like to use this to create a netboot environment, but when updating from 3.17 to 4.0x, I get a "connection failure".
Also, the NAOMI2 main unit does not proceed beyond the "CHECKING NETWORK" screen.
The jumper settings are as shown in the image, and a PIC with zero key writing is installed.
All DIMM board checks are fine.
image_67223553.JPG
image_67229441.JPG
naomi_net05.jpg
naomi_net02_0000.jpg
naomi_net03_0000.jpg
naomi_net04_0000.jpg


what should i do?
 
3.17 should netboot. 4.01 is for compact flash.
I have had success cleaning the dimm ethernet port with 99% ipa and allowing to dry.
If they werent ever used it could be dirty.
You can also try pinging the dimm to see if it responds on your network.
 
ForestOfDreams said:
3.17 should netboot. 4.01 is for compact flash.
I have had success cleaning the dimm ethernet port with 99% ipa and allowing to dry.
If they werent ever used it could be dirty.
You can also try pinging the dimm to see if it responds on your network.
Click to expand...
naomi_net06.jpg


I tried sending a ping, but there was no problem.
Should I try 4.02?
 
You have to go 4.01 I believe first in the rare chance it bricks it otherwise.
4.02 is unofficial compact flash.
4.03 is burned cd-r in gd-rom.
 
I tried cleaning it with board cleaner, but there was no change.
In any case, why can't I proceed beyond "Checking the network"?
And I don't understand why it "fails to connect"...
 
Checking network means naomi sees the dimm and the dimm sees the network since you can ping it.
Perhaps a firewall issue?
You can also push this update via wipi netboot if you have a raspberry pi 3 or higher on hand.
 
Hmm, I tried turning off the antivirus on my PC, but nothing changed.
Are there any port numbers that need to be opened?
 
The zero key is only needed when starting the game and has nothing to do with network checking, right?
 
I believe a functional netboot 0 key is necessary to push the update.
I know the last time I pushed an update on a 2.06 version it was very specific how I had the file pathed.
I can't remember as it has been some time.
 
Maybe I wrote the wrong zero key data?
When I looked it up on the internet, it was divided into CF boot and net boot.
The one I used is "ABC_BIN_0000000000000000_NET.bin".

Where did you find the zero key you used?
 
so I think there is no problem with the zero key.
Is it because the DIMM cannot reach the net that it does not proceed from "CHECKING NETWORK"?
Or is the problem that it is running on Windows 10?
 
It should be labeled with a number string and a letter under rhe cartridge next to/near the coin cell battery.
 
Hmm, why doesn't it work?
If set the IP address (e.g. 192.168.1.2) and the network test is GOOD, are connected to the network, right?
can actually send and receive pings.
normally,
Do you want to send the firmware with transfargame.exe on the "CHECKING NETWORK" screen?
 
You must log in or register to reply here.
Back
Top