through my network setup i can acess my ps2 and add some comfiguration but for the package, it's doesn't do anything by cliking on get package information button.
Can you help me ?
Can you help me ?
hello again, can you give me some details on this operation.When I did it, I used the SDK instructions and I was using Linux. I don't know about how you can do it on Windows, but since you were able to run dsedb, it seems like it may be possible. It may be possible to do with Codewarrior, but I don't know how.
In the same folder as the dsedb program there should be a tool called "dsflash". When I flashed mine, I used this command:
dsflash -d 10.0.0.10 /usr/local/sce/t10000-rel300.bin
You should replace the 10.0.0.10 with the IP address of your TOOL. When I used dsedb, I ran it like "dsedb -d 10.0.0.10". When you run dsflash, you should have the switch TOOL/WS switch in the "TOOL" position.
This takes a few minutes. After its done, you have to reboot the entire TOOL.
If this does not work for you, maybe try reading through the CodeWarrior documentation to see if can do this.
yes it's seem to be a good way to, but unfortunately when i do that it's return me this error.What you could do is to transfer the t10000-rel300.bin file to the Tool via ftp and run dsflash locally following the guidelines from the setup.pdf
Can't remember if there is a function in ProDG to flash the Tool firmware, but it's probably worth installing on your Windows computer anyway.
ok I'm at the stage to connect but it marks me this (see pictures).You don't need to use the Tool's web interface.
Run a ftp server on your windows machine, set a user account and a directory, put the t10000-rel300.bin in that directory, on the Tool, got to /home, run the ftp client "ftp"
And use the "open" command to connect to your server, "bin" to switch to binary mode, "get t10000-rel300.bin" to download the file you need.
Also to avoid any problems with the firmware file, make a md5 hash on your computer and check the file you received with "md5sum t10000-rel300.bin" to make sure it's identical.
ok so i've done what you've requested on the linux side, and it's done me this.(see pictures).127.0.0.1 is the local ip address, not the one on the network, if you don't know it or if the network info screen doesn't show it on the Tool video composite out, run ifconfig -a on the Tool
can you confirm me it's ok, and to do next ?The ftp client should be able to connect to 192.168.1.113 now.
On your Tool, go to the /home directory before running the ftp client, or it will download the firmware file to your location by default...