PSPLINK

nullp01nter · Post by **nullp01nter** » Fri Jan 20, 2006 8:37 am

I like it. If you were to use something like the FT232R, you could get rid of a bunch of components and have true 2.5v logic output. I think I'll go cancel my order for a bunch of max3319s and make cables like this instead. :)

Wow! That's it! This is what I need to have :)
This chip is rather new, so I did not come across yet. But I'll try to order a few immediately and then hack together a modified (and "minified") layout. I think I'm a bit excited about that now *g*

Thoralt

Post by **TyRaNiD** » Fri Jan 20, 2006 8:39 am

Damn that looks great, might have to build one myself. Few questions though, is the audio passed straight through (I assume it is)? And is it actually bus powered, i.e. would we even need to init the power from the SIO port to use it, if not that would cut 2 seconds off psplink reboot times ;)

Nice work.

nullp01nter · Post by **nullp01nter** » Fri Jan 20, 2006 9:02 am

Damn that looks great, might have to build one myself. Few questions though, is the audio passed straight through (I assume it is)? And is it actually bus powered, i.e. would we even need to init the power from the SIO port to use it, if not that would cut 2 seconds off psplink reboot times ;)

If you have a look at the schematic (http://www.thoralt.de/projects/SIO2USB/SIO2USB.html) you see, that every line except the PSP's RXD is straight through. So headphones and (if needed) the remote is working as usual. and yes, the device is bus powered. so there's no need of the power supply from the PSP (which still seems to be somehow mystic from the sources I read through).

As suggested by jimparis I will include a different USB chip into the design and thus getting rid of almost all additional components, making the device even smaller :) I then also will update the article on my homepage to be a bit more explanative.

Thoralt

Post by **TyRaNiD** » Fri Jan 20, 2006 9:07 am

Have you actually tried to use psplink with the power init removed? If you edit sio.c in pspsdk and remove the last two function calls from pspDebugSioInit does it still work? If it does I'll be even more interested ;P

edit: Oh and what is driver support like for the usb chip? Need anything special?

jimparis · Post by **jimparis** » Fri Jan 20, 2006 9:17 am

TyRaNiD wrote:edit: Oh and what is driver support like for the usb chip? Need anything special?

Might need to download FTDI's driver for Win or Mac. The ftdi_sio module is standard on Linux, as is uftdi on *BSD.

crazyc · Post by **crazyc** » Sat Jan 21, 2006 4:19 am

I just made something similar out of a cell phone data cable from Radio Shack. It uses a Prolific PL2303 and outputs 3.3V on the TX line, seems to work fine with no pulldown. The same cable also works for SIO with a PS2. BTW, the remote connector is ~5 PCI pins wide :).

xflash · Post by **xflash** » Mon Jan 23, 2006 9:14 am

Hello,

A really great thanks for your job! PSPlink is indeed a "must have" for anyone who wants to test/debug those productions.
I'm Wifi powered. (My soldering skills are .... too old :) ), I met some problems with an SDL app I wrote. It's freezing, when I launch it with psplink, but works fine from Vsh.
No traces to give, SDL redirects them, and stdout.txt and stderr.txt are empty ?!?
Any idea?

xFlash

bulb · Post by **bulb** » Fri Jan 27, 2006 4:10 am

I have two issues with PSPLink.

1. Sometimes I can't exec ELF module that I have just copied. Usually I have to disable and reenable USB. Problems with buffer flushing?

2. Problems with file I/O that happen all the time. Whenever I write the file (from ELF module), it occupies size on the stick, but is nowhere to be found.

NoHexPleaseI'mBritish · Sat Jan 28, 2006 2:35 am

Great piece of software, I can really see this speeding my development times up. The fact I can now actually see my printf statements alone is a major time-saver.

I have a couple of issues though, that could be me not doing something right, or maybe its just how PSPLink is.

Firstly, i'm using WiFi mode.

When I copy my .ELF over to the PSP, then type exec myapp.elf, it starts up on the PSP just fine.

If I type exec to re-execute the same file or exec anotherapp.elf then it restarts PSPlink, killing the wifi connection and USB. Then it starts the app while the wifi in PSPLink is still init'ing. In my PSPGL app this means nothing is visible and the psp buttons don't work, but I can still hear my background music playing. Also if I type reset then it goes to a black screen and freezes for about 20 seconds and then the PSP powers off.

I thought it might have been something in my app, so I tried with Hello World and get the same results.

Am I building my ELF's wrong or something?

Post by **TyRaNiD** » Sat Jan 28, 2006 2:46 am

bulb, there are issues with the use of usb and ms at the same time, there is no real way around that, that is just how the psp's drivers work. You are best to umount the usb drive and reset psplink (it will close usb on exit anyway) then rerun.

NoHexPleaseI'mBritish, I rarely use the exec command these days, I almost always use ld myfile.elf when I want to run a different executable once the shell comes up, exec works oki on sio but isn't so good on wifi as you have found out, if you need to pass complex arguments each time then either using pcterm (for a decent history) or create a script will suffice. As for the reset causing the psp to shut down I have seen this error before, it seems to be releated to having a kernel thread still running in user space. Absolutely no idea why it does this, it seems most likely to be a bug in the psp kernel somewhere, it gets itself stuck when resetting the system which then eventually kicks the watchdog off ;( Ensure your applications you are running are user mode only and that will fix the issue (but I know if you are running other apps this isn't always possible).

Post by **TyRaNiD** » Mon Feb 06, 2006 4:30 am

I have now added a version of GDB which runs over WIFI to PSPLINK. At the moment unfortunately it doesn't play nice with the WIFI shell for what ever reason so it is for SIO users only atm :( You will need to update newlib and pspsdk in order to use it (as usual :P)

With previous work from lovely2 the wifi GDB should be far better than previous versions, it is now a separate prx file which loads the debugee for you so you no longer need to use the inbuilt stub or for that matter kernel mode at all. It operates in a similar fashion to gdbserver does on *nix machines, you set it going with the "debug program.elf [args]" command in the shell then connect to it in GDB using the target remote command on port 6999.

Other improvements is it can now debug both ELF and PRX files and will handle the relocations as appropriate. I am going to try and implement threading support as well so you can manage the entire application from the PC which will be nice.

Anyway if you get a chance to test it obvisouly post any bug reports (and I am sure there will be some).

optixx00 · Post by **optixx00** » Fri Feb 17, 2006 6:20 am

Just got my SIO Cable working, but i can't start an elf. Any ideas.

Code: Select all

ms0&#58;/apps/>  e p.elf
Exec 'ms0&#58;/apps/p.elf'
modulemgr.c&#58;ReadFile&#58;sceIoRead&#40;0xf000&#41; failed&#58; 0x8001001c
modulemgr.c&#58;exe_thread&#58;LoadModule failed&#58; 0x8001001c
modulemgr.c&#58;sceKernelLoadModuleWithApitype&#58;sceKernelLoadModule failed 0x8001001c
lsm&#58; Error loading module ms0&#58;/apps/p.elf 8001001C
Failed to Load/Start module 'ms0&#58;/apps/p.elf' Error&#58; 0x8001001C

Post by **TyRaNiD** » Fri Feb 17, 2006 4:37 pm

I have seen this before and it is down to buffering issues between the USB mass storage and the ms driver. Whenever you copy across a new app unmount or disconnect the usb drive and reset PSPLINK. Then it should run fine.

optixx00 · Post by **optixx00** » Fri Feb 17, 2006 9:41 pm

Thx, the reset did it. Oh man wonderful tool. This makes psp dev work like charm. Quick turn around times and give practical debugging support. Great !

Is there a trick to reinit the SIO connection on psp side , as i lost the connection e.g. after plugging the sio cable off. At the moment iam forced to do an hard reset, holding power button for seconds.

Post by **TyRaNiD** » Sat Feb 18, 2006 2:26 am

Unfortunately not, I haven't got around to doing some more reversing of the hprm driver to allow the SIO to reinit. Maybe sometime :)

raf · Post by **raf** » Sun Feb 19, 2006 1:09 pm

TyRaNiD wrote:Unfortunately not, I haven't got around to doing some more reversing of the hprm driver to allow the SIO to reinit. Maybe sometime :)

Thanks so much, TRaNiD, for such a wonderful tool!
I'm ashamed to say that I just discovered it; and it's already making my life so much easier..
Will have to make/get a sio cable now so I can use gdb!

Great job!

Raf

sandberg · Post by **sandberg** » Mon Feb 20, 2006 8:34 am

TyRaNiD, there seems to be problems with compiling psplink against the lastest sdk ? You've made changes to the prototypes in pspusb.h, which requires sceUsbDeactivate to take the product ID for the default USB driver as an argument, like for sceUsbActivate. This causes psplink to give compiler errors.

Works fine when passing 0x168 as in the call to sceUsbActivate.

Orion_ · Post by **Orion_** » Tue Feb 21, 2006 10:28 am

I tried with eboot loader 9 and wifi hack for 2.0 firmware and psplink don't work :/
should I get back to 1.5 firmware ?

Post by **TyRaNiD** » Tue Feb 21, 2006 11:59 am

psplink relies on kernel mode access so it only works on 1.0 and 1.5 firmware, sorry.

Debug · Post by **Debug** » Fri Feb 24, 2006 8:42 am

When I try to compile PSPLINK I get what seems like a pretty bad error:

Code: Select all

psp-gcc -I. -I/usr/local/pspdev/psp/sdk/include -O2 -G0 -Wall -fno-builtin-print
f -I. -I/usr/local/pspdev/psp/sdk/include -O2 -G0 -Wall -fno-builtin-printf   -c
 -o kmode.o kmode.S
kmode.S&#58; Assembler messages&#58;
kmode.S&#58;9&#58; Error&#58; illegal operands `move $v0,$k1'
kmode.S&#58;11&#58; Error&#58; illegal operands `move $k1,$a0'
kmode.S&#58;19&#58; Error&#58; illegal operands `mfc0 $v0,$0'
kmode.S&#58;20&#58; Error&#58; illegal operands `sw $v0,0&#40;$a0&#41;'
kmode.S&#58;21&#58; Error&#58; illegal operands `mfc0 $v0,$1'
kmode.S&#58;22&#58; Error&#58; illegal operands `sw $v0,4&#40;$a0&#41;'
kmode.S&#58;23&#58; Error&#58; illegal operands `mfc0 $v0,$2'
kmode.S&#58;24&#58; Error&#58; illegal operands `sw $v0,8&#40;$a0&#41;'
kmode.S&#58;25&#58; Error&#58; illegal operands `mfc0 $v0,$3'
kmode.S&#58;26&#58; Error&#58; illegal operands `sw $v0,12&#40;$a0&#41;'
kmode.S&#58;27&#58; Error&#58; illegal operands `mfc0 $v0,$4'
kmode.S&#58;28&#58; Error&#58; illegal operands `sw $v0,16&#40;$a0&#41;'
kmode.S&#58;29&#58; Error&#58; illegal operands `mfc0 $v0,$5'
kmode.S&#58;30&#58; Error&#58; illegal operands `sw $v0,20&#40;$a0&#41;'
kmode.S&#58;31&#58; Error&#58; illegal operands `mfc0 $v0,$6'
kmode.S&#58;32&#58; Error&#58; illegal operands `sw $v0,24&#40;$a0&#41;'
kmode.S&#58;33&#58; Error&#58; illegal operands `mfc0 $v0,$7'
kmode.S&#58;34&#58; Error&#58; illegal operands `sw $v0,28&#40;$a0&#41;'
kmode.S&#58;35&#58; Error&#58; illegal operands `mfc0 $v0,$8'
kmode.S&#58;36&#58; Error&#58; illegal operands `sw $v0,32&#40;$a0&#41;'
kmode.S&#58;37&#58; Error&#58; illegal operands `mfc0 $v0,$9'
kmode.S&#58;38&#58; Error&#58; illegal operands `sw $v0,36&#40;$a0&#41;'
kmode.S&#58;39&#58; Error&#58; illegal operands `mfc0 $v0,$10'
kmode.S&#58;40&#58; Error&#58; illegal operands `sw $v0,40&#40;$a0&#41;'
kmode.S&#58;41&#58; Error&#58; illegal operands `mfc0 $v0,$11'
kmode.S&#58;42&#58; Error&#58; illegal operands `sw $v0,44&#40;$a0&#41;'
kmode.S&#58;43&#58; Error&#58; illegal operands `mfc0 $v0,$12'
kmode.S&#58;44&#58; Error&#58; illegal operands `sw $v0,48&#40;$a0&#41;'
kmode.S&#58;45&#58; Error&#58; illegal operands `mfc0 $v0,$13'
kmode.S&#58;46&#58; Error&#58; illegal operands `sw $v0,52&#40;$a0&#41;'
kmode.S&#58;47&#58; Error&#58; illegal operands `mfc0 $v0,$14'
kmode.S&#58;48&#58; Error&#58; illegal operands `sw $v0,56&#40;$a0&#41;'
kmode.S&#58;49&#58; Error&#58; illegal operands `mfc0 $v0,$15'
kmode.S&#58;50&#58; Error&#58; illegal operands `sw $v0,60&#40;$a0&#41;'
kmode.S&#58;51&#58; Error&#58; illegal operands `mfc0 $v0,$16'
kmode.S&#58;52&#58; Error&#58; illegal operands `sw $v0,64&#40;$a0&#41;'
kmode.S&#58;53&#58; Error&#58; illegal operands `mfc0 $v0,$17'
kmode.S&#58;54&#58; Error&#58; illegal operands `sw $v0,68&#40;$a0&#41;'
kmode.S&#58;55&#58; Error&#58; illegal operands `mfc0 $v0,$18'
kmode.S&#58;56&#58; Error&#58; illegal operands `sw $v0,72&#40;$a0&#41;'
kmode.S&#58;57&#58; Error&#58; illegal operands `mfc0 $v0,$19'
kmode.S&#58;58&#58; Error&#58; illegal operands `sw $v0,76&#40;$a0&#41;'
kmode.S&#58;59&#58; Error&#58; illegal operands `mfc0 $v0,$20'
kmode.S&#58;60&#58; Error&#58; illegal operands `sw $v0,80&#40;$a0&#41;'
kmode.S&#58;61&#58; Error&#58; illegal operands `mfc0 $v0,$21'
kmode.S&#58;62&#58; Error&#58; illegal operands `sw $v0,84&#40;$a0&#41;'
kmode.S&#58;63&#58; Error&#58; illegal operands `mfc0 $v0,$22'
kmode.S&#58;64&#58; Error&#58; illegal operands `sw $v0,88&#40;$a0&#41;'
kmode.S&#58;65&#58; Error&#58; illegal operands `mfc0 $v0,$23'
kmode.S&#58;66&#58; Error&#58; illegal operands `sw $v0,92&#40;$a0&#41;'
kmode.S&#58;67&#58; Error&#58; illegal operands `mfc0 $v0,$24'
kmode.S&#58;68&#58; Error&#58; illegal operands `sw $v0,96&#40;$a0&#41;'
kmode.S&#58;69&#58; Error&#58; illegal operands `mfc0 $v0,$25'
kmode.S&#58;70&#58; Error&#58; illegal operands `sw $v0,100&#40;$a0&#41;'
kmode.S&#58;71&#58; Error&#58; illegal operands `mfc0 $v0,$26'
kmode.S&#58;72&#58; Error&#58; illegal operands `sw $v0,104&#40;$a0&#41;'
kmode.S&#58;73&#58; Error&#58; illegal operands `mfc0 $v0,$27'
kmode.S&#58;74&#58; Error&#58; illegal operands `sw $v0,108&#40;$a0&#41;'
kmode.S&#58;75&#58; Error&#58; illegal operands `mfc0 $v0,$28'
kmode.S&#58;76&#58; Error&#58; illegal operands `sw $v0,112&#40;$a0&#41;'
kmode.S&#58;77&#58; Error&#58; illegal operands `mfc0 $v0,$29'
kmode.S&#58;78&#58; Error&#58; illegal operands `sw $v0,116&#40;$a0&#41;'
kmode.S&#58;79&#58; Error&#58; illegal operands `mfc0 $v0,$30'
kmode.S&#58;80&#58; Error&#58; illegal operands `sw $v0,120&#40;$a0&#41;'
kmode.S&#58;81&#58; Error&#58; illegal operands `mfc0 $v0,$31'
kmode.S&#58;82&#58; Error&#58; illegal operands `sw $v0,124&#40;$a0&#41;'
kmode.S&#58;83&#58; Error&#58; illegal operands `addiu $a0,$a0,128'
kmode.S&#58;84&#58; Error&#58; illegal operands `cfc0 $v0,$0'
kmode.S&#58;85&#58; Error&#58; illegal operands `sw $v0,0&#40;$a0&#41;'
kmode.S&#58;86&#58; Error&#58; illegal operands `cfc0 $v0,$1'
kmode.S&#58;87&#58; Error&#58; illegal operands `sw $v0,4&#40;$a0&#41;'
kmode.S&#58;88&#58; Error&#58; illegal operands `cfc0 $v0,$2'
kmode.S&#58;89&#58; Error&#58; illegal operands `sw $v0,8&#40;$a0&#41;'
kmode.S&#58;90&#58; Error&#58; illegal operands `cfc0 $v0,$3'
kmode.S&#58;91&#58; Error&#58; illegal operands `sw $v0,12&#40;$a0&#41;'
kmode.S&#58;92&#58; Error&#58; illegal operands `cfc0 $v0,$4'
kmode.S&#58;93&#58; Error&#58; illegal operands `sw $v0,16&#40;$a0&#41;'
kmode.S&#58;94&#58; Error&#58; illegal operands `cfc0 $v0,$5'
kmode.S&#58;95&#58; Error&#58; illegal operands `sw $v0,20&#40;$a0&#41;'
kmode.S&#58;96&#58; Error&#58; illegal operands `cfc0 $v0,$6'
kmode.S&#58;97&#58; Error&#58; illegal operands `sw $v0,24&#40;$a0&#41;'
kmode.S&#58;98&#58; Error&#58; illegal operands `cfc0 $v0,$7'
kmode.S&#58;99&#58; Error&#58; illegal operands `sw $v0,28&#40;$a0&#41;'
kmode.S&#58;100&#58; Error&#58; illegal operands `cfc0 $v0,$8'
kmode.S&#58;101&#58; Error&#58; illegal operands `sw $v0,32&#40;$a0&#41;'
kmode.S&#58;102&#58; Error&#58; illegal operands `cfc0 $v0,$9'
kmode.S&#58;103&#58; Error&#58; illegal operands `sw $v0,36&#40;$a0&#41;'
kmode.S&#58;104&#58; Error&#58; illegal operands `cfc0 $v0,$10'
kmode.S&#58;105&#58; Error&#58; illegal operands `sw $v0,40&#40;$a0&#41;'
kmode.S&#58;106&#58; Error&#58; illegal operands `cfc0 $v0,$11'
kmode.S&#58;107&#58; Error&#58; illegal operands `sw $v0,44&#40;$a0&#41;'
kmode.S&#58;108&#58; Error&#58; illegal operands `cfc0 $v0,$12'
kmode.S&#58;109&#58; Error&#58; illegal operands `sw $v0,48&#40;$a0&#41;'
kmode.S&#58;110&#58; Error&#58; illegal operands `cfc0 $v0,$13'
kmode.S&#58;111&#58; Error&#58; illegal operands `sw $v0,52&#40;$a0&#41;'
kmode.S&#58;112&#58; Error&#58; illegal operands `cfc0 $v0,$14'
kmode.S&#58;113&#58; Error&#58; illegal operands `sw $v0,56&#40;$a0&#41;'
kmode.S&#58;114&#58; Error&#58; illegal operands `cfc0 $v0,$15'
kmode.S&#58;115&#58; Error&#58; illegal operands `sw $v0,60&#40;$a0&#41;'
kmode.S&#58;116&#58; Error&#58; illegal operands `cfc0 $v0,$16'
kmode.S&#58;117&#58; Error&#58; illegal operands `sw $v0,64&#40;$a0&#41;'
kmode.S&#58;118&#58; Error&#58; illegal operands `cfc0 $v0,$17'
kmode.S&#58;119&#58; Error&#58; illegal operands `sw $v0,68&#40;$a0&#41;'
kmode.S&#58;120&#58; Error&#58; illegal operands `cfc0 $v0,$18'
kmode.S&#58;121&#58; Error&#58; illegal operands `sw $v0,72&#40;$a0&#41;'
kmode.S&#58;122&#58; Error&#58; illegal operands `cfc0 $v0,$19'
kmode.S&#58;123&#58; Error&#58; illegal operands `sw $v0,76&#40;$a0&#41;'
kmode.S&#58;124&#58; Error&#58; illegal operands `cfc0 $v0,$20'
kmode.S&#58;125&#58; Error&#58; illegal operands `sw $v0,80&#40;$a0&#41;'
kmode.S&#58;126&#58; Error&#58; illegal operands `cfc0 $v0,$21'
kmode.S&#58;127&#58; Error&#58; illegal operands `sw $v0,84&#40;$a0&#41;'
kmode.S&#58;128&#58; Error&#58; illegal operands `cfc0 $v0,$22'
kmode.S&#58;129&#58; Error&#58; illegal operands `sw $v0,88&#40;$a0&#41;'
kmode.S&#58;130&#58; Error&#58; illegal operands `cfc0 $v0,$23'
kmode.S&#58;131&#58; Error&#58; illegal operands `sw $v0,92&#40;$a0&#41;'
kmode.S&#58;132&#58; Error&#58; illegal operands `cfc0 $v0,$24'
kmode.S&#58;133&#58; Error&#58; illegal operands `sw $v0,96&#40;$a0&#41;'
kmode.S&#58;134&#58; Error&#58; illegal operands `cfc0 $v0,$25'
kmode.S&#58;135&#58; Error&#58; illegal operands `sw $v0,100&#40;$a0&#41;'
kmode.S&#58;136&#58; Error&#58; illegal operands `cfc0 $v0,$26'
kmode.S&#58;137&#58; Error&#58; illegal operands `sw $v0,104&#40;$a0&#41;'
kmode.S&#58;138&#58; Error&#58; illegal operands `cfc0 $v0,$27'
kmode.S&#58;139&#58; Error&#58; illegal operands `sw $v0,108&#40;$a0&#41;'
kmode.S&#58;140&#58; Error&#58; illegal operands `cfc0 $v0,$28'
kmode.S&#58;141&#58; Error&#58; illegal operands `sw $v0,112&#40;$a0&#41;'
kmode.S&#58;142&#58; Error&#58; illegal operands `cfc0 $v0,$29'
kmode.S&#58;143&#58; Error&#58; illegal operands `sw $v0,116&#40;$a0&#41;'
kmode.S&#58;144&#58; Error&#58; illegal operands `cfc0 $v0,$30'
kmode.S&#58;145&#58; Error&#58; illegal operands `sw $v0,120&#40;$a0&#41;'
kmode.S&#58;146&#58; Error&#58; illegal operands `cfc0 $v0,$31'
kmode.S&#58;147&#58; Error&#58; illegal operands `sw $v0,124&#40;$a0&#41;'
kmode.S&#58;161&#58; Error&#58; illegal operands `sw $a0,4&#40;$sp&#41;'
kmode.S&#58;162&#58; Error&#58; illegal operands `sw $a1,8&#40;$sp&#41;'
kmode.S&#58;163&#58; Error&#58; illegal operands `sw $a2,12&#40;$sp&#41;'
kmode.S&#58;164&#58; Error&#58; illegal operands `sw $a3,16&#40;$sp&#41;'
kmode.S&#58;165&#58; Error&#58; illegal operands `sw $t0,20&#40;$sp&#41;'
kmode.S&#58;166&#58; Error&#58; illegal operands `sw $t1,24&#40;$sp&#41;'
kmode.S&#58;167&#58; Error&#58; illegal operands `move $a0,$v0'
kmode.S&#58;169&#58; Error&#58; illegal operands `addiu $a1,$sp,4'
kmode.S&#58;172&#58; Error&#58; illegal operands `lw $a0,4&#40;$sp&#41;'
kmode.S&#58;173&#58; Error&#58; illegal operands `lw $a1,8&#40;$sp&#41;'
kmode.S&#58;174&#58; Error&#58; illegal operands `lw $a2,12&#40;$sp&#41;'
kmode.S&#58;175&#58; Error&#58; illegal operands `lw $a3,16&#40;$sp&#41;'
kmode.S&#58;176&#58; Error&#58; illegal operands `lw $t0,20&#40;$sp&#41;'
kmode.S&#58;177&#58; Error&#58; illegal operands `lw $t1,24&#40;$sp&#41;'
kmode.S&#58;179&#58; Error&#58; illegal operands `beq $v0,$0,1f'
kmode.S&#58;181&#58; Error&#58; illegal operands `jr $v0'
kmode.S&#58;186&#58; Error&#58; illegal operands `move $v0,$0'
kmode.S&#58;193&#58; Error&#58; illegal operands `li $v0,0'
kmode.S&#58;200&#58; Error&#58; illegal operands `li $v0,1'
kmode.S&#58;207&#58; Error&#58; illegal operands `li $v0,2'
kmode.S&#58;214&#58; Error&#58; illegal operands `li $v0,3'
kmode.S&#58;221&#58; Error&#58; illegal operands `li $v0,4'
kmode.S&#58;228&#58; Error&#58; illegal operands `li $v0,5'
kmode.S&#58;235&#58; Error&#58; illegal operands `li $v0,6'
kmode.S&#58;242&#58; Error&#58; illegal operands `li $v0,7'
kmode.S&#58;249&#58; Error&#58; illegal operands `li $v0,8'
kmode.S&#58;256&#58; Error&#58; illegal operands `li $v0,9'
kmode.S&#58;263&#58; Error&#58; illegal operands `li $v0,10'
kmode.S&#58;270&#58; Error&#58; illegal operands `li $v0,11'
kmode.S&#58;277&#58; Error&#58; illegal operands `li $v0,12'
kmode.S&#58;284&#58; Error&#58; illegal operands `li $v0,13'
kmode.S&#58;291&#58; Error&#58; illegal operands `li $v0,14'
kmode.S&#58;298&#58; Error&#58; illegal operands `li $v0,15'
make&#58; *** &#91;kmode.o&#93; Error 1

Anyone know why this happens?

Post by **TyRaNiD** » Fri Feb 24, 2006 8:51 am

you have got an old old toolchain build, you will need to update it to get it to build correctly.

Debug · Post by **Debug** » Fri Feb 24, 2006 1:42 pm

I see, thanks. Unfortunately, I updated the toolchain from svn to make sure, then I ran ./toolchian.sh -p. It was going fine until here:

Code: Select all

/cygdrive/f/DOCUME~1/Allen/LOCALS~1/Temp/ccNqBoly.s&#58; Assembler messages&#58;
/cygdrive/f/DOCUME~1/Allen/LOCALS~1/Temp/ccNqBoly.s&#58;53&#58; Error&#58; illegal operands
`vmidt.q M300'
/cygdrive/f/DOCUME~1/Allen/LOCALS~1/Temp/ccNqBoly.s&#58;90&#58; Error&#58; illegal operands
`vmidt.q M300'
make&#91;3&#93;&#58; *** &#91;sceGumLoadIdentity_vfpu.o&#93; Error 1
make&#91;3&#93;&#58; Leaving directory `/tmp/pspdev/pspsdk/src/gum'
make&#91;2&#93;&#58; *** &#91;all-recursive&#93; Error 1
make&#91;2&#93;&#58; Leaving directory `/tmp/pspdev/pspsdk/src'
make&#91;1&#93;&#58; *** &#91;all-recursive&#93; Error 1
make&#91;1&#93;&#58; Leaving directory `/tmp/pspdev/pspsdk'
make&#58; *** &#91;all&#93; Error 2
ERROR BUILDING PSPSDK

Should I run the entire toolchain or is that something else?

Post by **Oobles** » Fri Feb 24, 2006 3:28 pm

Yes, you need to run the full toolchain script, not just the SDK. The operands are now part of GCC, so you need to rebuild it.

Post by **TyRaNiD** » Mon Feb 27, 2006 12:27 am

Okay this is going to need testing. I have added a USB based host filing system to PSPLINK, it uses libusb to communicate with the PSP from user mode, it claims to work on most *nix like systems though I have had issues with it before so this is a good time for people to try it ;) For info I run x86 linux on a 2.6 kernel, and it works fine for me. There is a libusb port for windows but lacking an easily accessible windows machine with dev tools on it I haven't yet tested it on that.

Brief description of how it works, you enable hostfs on the PSP by setting usbhost=1 in the psplink.ini file, you then run up a tool on your PC which uses libusb to communicate with the PSP and serve file data. It supports mapping upto 8 directories (and more if you change the PC side code define) so you can access different directories under host0 or host5 for example. All commands are supported, though devctl and ioctl have not been fully implemented yet, got some plans for those.

It wont like you blocking on the PC side read so no blocking sockets yet but for the most part it should do what people need in a host filing system.

I have tested with USB 1.1 and 2.0 and they both seem to work fine, 1.1 gets around 1Mb/s and 2 around 10Mb/s, so best plug it into a 2.0 host port ;)

Oh and final thing, if you are building on a big-endian machine (i.e. a mac) then make the PC side tool with 'make BUILD_BIGENDIAN=1', that will ensure all integer values are swapped around correctly, however I haven't tested it so YMMV.

Report any bugs to /dev/null, thx.

Post by **TyRaNiD** » Mon Feb 27, 2006 7:54 am

Update: I decided to try my hand at getting the hostfs to work on a windows box and I suceeded, so I thought I might as well post the info. You will need to build in cygwin as there are too many unixism for it to build correctly on vanilla win32 or mingw.

Download the latest snapshot of the libusb-win32 driver (not the filter driver) from libusb-win32.sourceforge.net. Extract to a directory.

Start up psplink with the hostfs driver enabled, Windows should try and install a driver, just ignore that for now. In the bin directory of libusb run inf-wizard, follow the instructions, select the PSP Type-B device, and choose the bin directory as your output. This should have produced a *.inf and *.cat file. Complete the windows driver installation but tell it you will specify the directory, point it at the bin directory and it should pick it up and install the driver.

Now copy include/usb.h and lib/gcc/libusb.a from the extracted directory and copy them into the usbhostfs_pc directory in cygwin.

Open up cygwin and navigate to the usbhostfs_pc directory, you will now need to edit a few bits.
Edit Makefile, add -I. to CFLAGS and then add the line LDFLAGS=-L.
Edit main.c, on line 1669 change the final parameter of euid_usb_bulk_read from 0 to INFINITE.
Type make and it should build. Then run as normal.

There is of course a caveat, seems that on linux bulk reads fail with a 0 byte read when the USB device is disconnected, but on Windows it doesn't seem to do anything at all, i can probably get around it by implementing a goodbye command from the USB device to tell the PC side it should shutdown, but then again that'll teach you for using Windows ;) the fix is obviously to shutdown the hostfs app once the psp has rebooted and rerun it.

pspkrazy · Post by **pspkrazy** » Mon Feb 27, 2006 9:11 am

Amazing job.

Everyone can now use your debug tool with ease and power.

Great.

PS : Are you planning to make an usb shell ? It will be great for poeple like me who don't have a SIO cable (cause wifi sucks a little).

Post by **TyRaNiD** » Mon Feb 27, 2006 10:40 am

Probably, I have left in what I think I need to support a shell in the current driver, my main issue is really with implementing on the PC side, libusb doesn't seem the best thing for actually doing what I need it to do. Will look into it later.

psx-frogger · Post by **psx-frogger** » Tue Feb 28, 2006 4:16 am

Hi Tyranid,

Thanks for this great tool.

I saw on the svn that the Pdf documentation is talking abouit version 0.9b.

Have you released the 0.9b version ?

Regards

Psx-frogger

Post by **TyRaNiD** » Tue Feb 28, 2006 4:56 am

Technically the subversion code is 0.9b, will probably not release a 0.9b until I have a USB shell and that will probably be 0.9c, or more depending what I feel like. For now just use the subversion version.

johnmph · Post by **johnmph** » Sat Mar 04, 2006 1:50 am

Hello TyRaNiD, beautiful tool ;-)

In your find_syscall_addr function (apihook.c), you use a u32 pointer to access syscall table (u32 *syscalls) :

Code: Select all

void *find_syscall_addr&#40;u32 addr&#41;
&#123;
	struct SyscallHeader *head;
	u32 *syscalls;
	void **ptr;
	int size;
	int i;

	asm&#40;
			"cfc0 %0, $12\n"
			&#58; "=r"&#40;ptr&#41;
	   &#41;;

	if&#40;!ptr&#41;
	&#123;
		return NULL;
	&#125;

	head = &#40;struct SyscallHeader *&#41; *ptr;
	syscalls = &#40;u32*&#41; &#40;*ptr + 0x10&#41;;
	size = &#40;head->size - 0x10&#41;;

	for&#40;i = 0; i < size; i++&#41;
	&#123;
		if&#40;syscalls&#91;i&#93; == addr&#41;
		&#123;
			return &syscalls&#91;i&#93;;
		&#125;
	&#125;

	return NULL;
&#125;

and you calculate size with : head->size - 0x10

but this size is in bytes, and you use this with a u32 pointer, the size should not be rather :

size = (head->size - 0x10) / sizeof(u32);

(Sorry for my ultra bad english) ;-)

forums.ps2dev.org

PSPLINK

wow