Hello, first of all big thanx to assembler for reuniting me with a good friend of mine, the ps2 tool. great guy.ray: ok well, upon first investigation this tool has no ssh, that is fine, I now use dsnet with the " -d <tool ip> " to control my tool. well I have an HDTV that doesnt support RGB but does support Y/CrCb. upon game start i can express Y/CrCb with reset 0x00000012 0x00000100 (10 at end of ee expresses Y/CrCb) but the first "TOOL" startup screen is RGB, witch my tv just gives purple wavy lines. so how can I get the tool to starup in Y/CrCb.
I know nothing about the PS2 tool or anything, but if it's running linux then you could add the command to the start-up... Only thing is what kind of startup execution it has. Check /etc/ for rc.d and run levels and whatnot. If it's not linux then I'll just smile saying cheese whilst looking like an idiot
It uses red hat for the host side, but on the local machine (im controlling it on a remote fedora box with dsnet), ill look into the start-up conf's see if its in there, I'll have log in localy though, ugh ( i don't have enough key boards). Thanx
Have a look into /usr/local/sony/bin/devtool-opening, which is the top-level script used to display the network information screen. The actual ELF is started via a dsefilesv command in /usr/local/sony/bin/gstitle. Are you sure the TOOL outputs RGB on startup? I'd assume it just obeys the DIP setting on the back, i.e., it outputs either PAL or NTSC. Try to flip DIP switch No. 5 (UP=NTSC, DOWN=PAL), maybe that helps your TV in getting a correct picture. Otherwise, please note that any setting you pass to DSRESET may just be ignored by the application (as there is no hypervisor on the PS2 that could control access to the GS). So even if you get this working with gstitle.elf, chances are it'll not be recognized by other code; although I assume non-Sony/homebrewn code would be more likely to break than anything that uses the official SDK.
I believe ThePinkBunny is correct on the reset flags. I don't have access to the PS2 Dev docs at the moment but I do remember seeing one of these flags controlling the component output setting (as well as to what all of these flags actually mean). In a retail PS2 you can set this setting in the menu and RGB may be the default. Obviously since the Tool doesn't have a retail boot menu so you can't configure this setting through the front door so the reset flags is how this is controlled. Just to clarify we are working with the component cables (Red, Green, Blue for video and Red, White for Audio) not the composite cables (Yellow, Red and White). So this setting only adjusts how the component signal is encoded.
Ok, I checked the devtool-opening, and the gstitle,(was abit disturbed by the "kill-children" file)well I noticed it used a command "eerun" to execute the gstitle.elf. Well i knew about desdb's "run" command to load all my elf's, so I went into desdb then ran "reset 0x00000010 100" then "run /usr/local/sony/bin/gstitle.elf" Well the screen loaded up (yes I'm using red green blue cable) But because the text file in /tmp was not found, It did not have the network info. so I thought maybe if I add dsreset 0x00000010 100 to the gstitle script before it executed it, but as i hate vi and this red hat does not have nano, I didn't attempt it. bit 0 0x00000001 Workaround for the EE memory controller bug 0 Disable workaround for the EE memory controller bug 1 Enable workaround for the EE memory controller bug bit 1 0x00000002 Startup from disk 0 Do not start up from disk 1 Start up from disk bit 2 0x00000004 Reserved bit 0 Fixed bit 3 0x00000008 Reserved bit 0 Fixed bit 4 0x00000010 Component video output 0 RGB 1 Y/CrCb bit 5 0x00000020 Memory size for EE kernel processing 0 128 MB 1 32 MB The user is not prohibited from accessing memory beyond 32 MB. When the EE kernel API LoadExecPS2 function is called, the memory space up to 32MB is cleared to 0. Also, all 128MB are cleared to zero at reset. bit 6 0x00000040 Stack check function for each thread on the EE kernel 0 Disabled 1 Enabled When enabled, the stack is checked to see whether or not it has enough space to switch to another thread. bit 7 0x00000080 TLB trap function 0 No TLB trap 1 Trap memory accesses above 32 MB through the TLB When the EE memory size is set to 32 MB, the TLB trap function is enabled. This allows memory accesses beyond 32 MB to be detected through the TLB. bit 8 0x00000100 ELOADP driver control 0 Include ELOADP during liberx initialization 1 Do not use ELOADP
