Sony PS2 Tool guide update request - help!

I am considering updating the Playstation 2 Tool assembly guide by amending it to contain further information regarding the T15k, T14 card, set-up guide (installation variations), guide to required software (PC side) and also basic Linux command lines to assist with running software etc.

A lot of this information already exists in a number of AG threads and a while ago I began the long haul of putting it all together.

However, assistance is required as it is a bigger job than I thought. Initially I ran out of time as I was studying for my exams (now passed). Also, things are somewhat complicated as I no longer actually own a PS2 Tool thus I cannot attempt any of the listed commands - in short I need someone (some people) to verify. I also need current Tool owners to establish what is useful to be added to such a guide.

So, although I doubt we'll ever have a comprehensive guide that covers everything, it would be good to update and add what constitutes known unknowns. :nod:

For example, I never thought to add a section on the various manuals supplied with the unit or a section on the external HDD. Dumb huh?

Anyone up for assisting? If not, then I will drop the project. This is like a final farewell as I no longer collect - unfinished business!

 

You know you can count on me!

 

Count me in as well!

 

Excellent - many thanks to you both - I shall keenly view both your superior knowledge of all things Sony and in particular PS related. I know UJ well enough to realise he has put in a huge amount of Tool related effort and assisted greatly in the past. Anyone else care to throw their names into the hat? Good start though!

 

I'm happy to test stuff, otherwise not sure how helpful I can be. But yeah, I'll join in

Stone

 

Excellent - thanks folks! I shall start going over what I have here. Can I ask those among you (looks at UJ in particular) who still have access to a Tool that they put together Linux commands / specific for the unit that are invaluable / useful?

I started with a list, but once I handed it out to be proof read it never returned!

Also, did anyone establish precisely how each of the dips at the rear of the unit affected the Tools operation? I remember seeing something a long time ago that gave an outline, but did anyone start testing the theory?

Anyone got any suggestions as to what should go into the new guide?

Any mistakes anyone has spotted?

Let me know

 

Same here bro if you need any help let me know, i'll keep an eye on the thread as well.

 

I did proof read the document you started, but with not having access to my own pc for the last 3 months and being so busy with the 3rd year of uni haven't been able to check it all works etc. Haven't even got the time/space to use my tool anymore

 

Ah, okay - I wasn't sure whether you'd had the time Oli and certainly not pointing any finger of blame!

I know what it's like when you are really busy. We can review that document then. Starting point! :110:

 

Yeah its a shame, I barely get time for gaming or the internet even these days. I'm possibly going to be selling the Tool as its a bit pointless sitting in my cupboard, however if I do when I take pictures of it & check its working etc I'll try and verify some of the commands etc if I get time.

 

Damn it, another one bites the dust! Know where you are coming from.

 

I'll be selling it on here, so hopefully it will go to a regular member who will contribute!

 

Some commands that I find really useful:

(TOOL+PS2 SDK)
dseping/dsiping
Check whether the PS2 side (EE/IOP) of the TOOL is operational. If these commands do not show a successful packet exchange after starting/rebooting/resetting the TOOL, you have either a serious problem or a pretty ~12kg paperweight :icon_toil.

These commands can show packet loss for a perfectly operational TOOL in case the PS2 side is stuck/hung; however, after a reset command, both of them should work without error.

dsreset
Reset PS2 without changing boot parameters. This is equivalent to pressing the Reset button on top of the TOOL.

dsreset 0 0 (dsedb command "reset 0 0")
Start PS2 in DEV mode. Listed for completeness; I think there is no need to use dsreset for this, as one would need dsedb anyway to start a program.

dsreset 2 180
Most important command if you want to start a game without starting the debugger. Start PS2 in TEST mode and boot from optical drive.

dsreset 2 100
Start PS2 in TEST mode and boot from optical drive. In contrast to the previous command, this one boots the IOP in 8MB mode. This should not be needed for retail games, but could convince some early prototypes to boot that need the additional memory. If you don't know what that sentence means, you probably don't need to use this command :110:.

dsedb/dsidb [-nr]
Start EE or IOP kernel debugger ("-nr"="no reset"=do not perform a reset of the PS2 side).
To which detail do you think we should cover these programs in the guide? After all, the TOOL includes over 60 pages of documentation for them...

(TOOL only)
/usr/local/sony/bin/devtool-opening
Display Network Information screen.

(General Linux)
passwd root
Change superuser password.

shutdown -h now
Shutdown the TOOL (without having to go to the website).

setterm -powersave off -blank 0
Disable screen power saving; i.e., prevent the TOOL's PC side screen from turning off.

I remember seeing something, too, but not sure where it was. How safe is it to fiddle with these switches? I assume its not a good idea to toggle them when the TOOL is running, but is there any chance of permanent damage when rebooting after toggling one of them?

Some ideas, unsorted:

• First steps, aka: "Just got my TOOL. What do I do now?". Especially: where to connect the LAN cable, keyboard, PC monitor to.
• How to change/reset the "root" password and TOOL website logon password
• PS2 and TOOL Hardware Overview ("How does a PS2 work" on a very high level, on how is the hardware integrated into the TOOL). There are quite some programs on both the TOOL and in the PS2 SDK that directly relate to the target hardware, so I think it cannot hurt to mention this. Keywords: EE, IOP, DSNET, ...
• How to set up the development PC (PS2 SDK). What do you think of a premade VMWare or VirtualPC image of a base Linux installation? Of course, it wouldn't include the PS2 SDK, but it could be prepared in a way that user's could simply copy the files over (and probably run some installation script) without going through the hassle if installating Linux themselves.

 

Excellent - good start to some useful basic commands to add to the guide. We had a list similar to this put together from a variety of threads written by AG members of many months. That is the document I put out to be reviewed. Once it returns I can add some of those (I think there is some duplication but I could be wrong).

There's been a bit of an update at my end too. Having stated I didn't have access to a PS2 Tool, I suddenly do due to the acquisition of a pile of 3 DOA units. I spent the whole of last night getting one of the 3 units up and running, although I have been unable to test thoroughly - I assume the laser is gone.

Took 11 hours to get one of the three to work. What a fight I had on my hands with blown PSU, damaged cables, cracked PCB, missing bits etc. The units literally turned up in pieces like a jigsaw and it was a case of 'match the DTL number'. Before anyone asks, the controller ports and cables on the other 2 units were damaged beyond repair. Most of the plastics were shattered or missing the clips. 1 PCI card looks viable though if someone were on the hunt for a replacement. However, if someone is looking for a specific part for a DTL-H10k then I may have something, but it would be untested.

They pretty much arrived like this



After 3 hours sorting out parts and finding a motherboard that looked in good shape I had this



I got utterly frustrated and wasted about 2 hours trying to get a PSU to work (1 buzzed and appeared to have reduced voltage output, the other rattled (which I never noticed until I picked up the completed unit and heard something inside it)) the last PSU just needed a good clean up. Wished I had grabbed it first!









As soon as I wake up I can start testing it thoroughly.

Thanks to Kiff for the remarkably economical sale of dead bits of Tool! Frankentool! Fitting for Halloween!

 

Parris, any useful infos in the dtl-t10kh manual?

You can safely shutdown the Tool with the power button.
And if you can't access it, typing init 0 is probably faster.

 

It's been skimmed through, but I'm in the middle of putting a TV on a wall so put the PS2 stuff to one side for the weekend. I did come across a few interesting bits of information, however a man of your calibre probably found the same information by actually reading other manuals elsewhere

I'll PM you

Really wanted to have this finished so I could watch Lewis Hamilton at the Brazilian Grand Prix, however... I'll just watch the highlights!

 

When reading Parris' TOOL disassembly guide, I stumbled across the section that mentions 8 DIP switches underneath some black tape underneath the PCMCIA port. Has anyone noticed that these DIP switches show the same pattern than the "configuration information" message shown in the IOP debugger after a system reset?

Note the beginning of the last line, "SW=b7:^^^^___^:b0". Looks like the default setting of the DIP switches as mentioned in Parris' guide (Step 36/p.55), doesn't it? I would expect that last line to change according to the current state of the switches, which would give some quite interesting configuration options...

Does anybody want to volunteer for checking this out? :evil::evil::evil:

 

I tried the EE/GS self test, the result is interesting, I will try the other ones when (if) I can find the time to dismantle one of the Tools I have.

 

I have a working PS2 Tool - Frankentool lives! Terrible title for it's first outing though!



At least this way I can help test... face it, if I can understand what the hell you guys are banging on about, there is a fair chance everyone else will.

 

Top tip for putting back together a PS2 Tool if you've had to change or remove the PSU. (This should be added to the guide).

1) Ensure you have cable ties
2) lift ALL the cables running down the central core of the unit and attach them to the metal frame at the REAR of the PSU.
3) Ensure that ALL the leads are away from the GPU & CPU fans mounted on the main motherboard.

I have a suspicion that some damaged units that have been 'tinkered' with may be as a result of the 2 fans on the GPU & CPU, and to a lesser extent potentially on the PCI card being obstructed or even slowed down by cables resting on them.