I was hoping to get a little bit of guidance here. I am receiving a hopefully functional PS2 Tool in the mail in about a week or so and I have the SDK 3.0 with Codewarrior already and I was hoping to setup a dev unit before the device arrived so that I can break it in. This is my first development console and I'm a bit confused with the included instructions. 1.) Does the SDK get installed on the dev PC or directly onto Tool? The instructions seem to assume Linux and don't seem to mention one compiler or the other which almost leads me to believe that it needs to be setup on Tool and when I setup Codewarrior to communicate to Tool, then it will somehow work out. 2.) The docs recommend Red Hat Linux 6.2 for my dev PC, Codewarrior appears to install just fine under Xp Pro... is it a simple recommondation due to Sony's competition with MS or will I start hitting a bunch of issues when I go to actually compile something? If running XP is ok, any guides/tips I could use to ensure proper connection through XP and Codewarrior? 3.) Also, my research seems to indicate that Tool is setup to be a one stop shop for developing/compiling/debugging PS2 games, the Tool I'm getting simply comes with the unit and nothing else. From what I can tell, there is no periphials that I need other than a basic power cord and PS2 controller to get this working... is that correct or do I need something else to get started? Thanks in advanced, I hope to be more active here once I get my hands on this.
Hi, Sony's SDK includes its own compilers (separate ones for EE and IOP) and does not depend on CodeWarrior to work. It is installed onto a development PC running Linux, which is then connected to the TOOL via Ethernet. I've never used CodeWarrior (or, for that matter, anything not running on Linux for PS2 development), so I cannot comment on whether it is really standalone or requires parts of the official SDK. That's correct, provided the unit is working as expected . You'll just need a standard ethernet cable to connect the TOOL to your development PC; and, obviously, a TV to play your games on ;-). A TOOL basically contains a (heavily modified) PS2 and a Linux-based PC in the same enclosure sharing the same power supply. The PS2 is connected like a retail unit (controllers, memory cards, TV). The Linux system, in a standard configuration, is used for communication with the development PC, and requires just a single ethernet cable. It has its own internal connection to the PS2 side, which allows the development PC to control it (like debugging or uploading programs for execution). Although the TOOL's Linux side has its own connectors for monitor and keyboard, Sony does not expect you to use them; by default, they are hidden behind metal covers on the back of the unit. However, if you want to, you can connect regular PC peripherals and use the Linux side like a regular PC. TOOLs typically have some parts of the official SDK (like the debuggers DSEDB/DSIDB) installed on their Linux side, so you don't even need to set up a development PC to perform some initial tests.
Ok, just got my TOOL in today, unfortunately I haven't been able to do anything but unbox it and set it aside as it's getting late here. I do have one quick question before the fun begins... If you look at this pick on this site: http://gamerhistory.com/images/TOOL/TOOL3.jpg Coming from the left hand side of the unit, right before the video card is an empty slot on my unit. It has a punch release type latch(reminds me of a PCMCIA card slot button)... anyone know what I'm missing and is it curcial to developmental needs?
Can't see that image for some reason, but I think what you're describing is indeed, a PCMCIA card slot - the original PS2 network/HDD adapter (as intended for the the early Japanese retail PS2 SCPH-10000/15000/18000 models) was a PCMCIA card based design. It's not vital, unless you want to play with software that uses the PS2 side network/HDD. The TOOL had an adapter card made specifically for it (DTL-H10010), though the retail equivalent (SCPH-10190) should work too - the only difference I could see was that the DTL version has a small cable extension on the network port, presumably to make it a little more accessible from behind the rear of the TOOL. (Side note: I remember that there was some discussion that only DTL-T10000H TOOLs supported PS2 networking & that DTL-T10000's didn't - did anyone ever prove/disprove that? Just curious.)
Thanks for the quick replies, I do believe you guys are right about the HDD. I spent my time this evening resetting the root password, access TOOL via the web browser and installing the SDK with VS 6 and Prodg on my laptop. Now on to my next issue, which I'm not sure if it's Prodg specific, but... When I go to compile any sample code from the 3.0 SDK, I get this link error: C:/usr/local/sce/ee/lib/crt0.s(1) : error: L0039:Reference to undefined symbol _init in file C:\USR\LOCAL\SCE\EE\SAMPLE\VU1\hako\crt0.o I tried 'group libraries' from the VS Intergration Control Panel which was recommended by the included guide to eliminate these types of errors, but it didn't correct the issue. Anyone seen this before?
