basically my problem is that the pspsh doesn't get the prompt.
usbhostfs_pc seems to connect as "Connected do device" appears.
(when psplink is idle and the screen is black it would light up when usbhostfs_pc is connecting).
when i run pspsh "Accepting async connection ([0,2,3]) from 127.." appears but if i press enter host0:/ won't appear as it should.
strange is that when i enter reset (or poweroff) in pspsh nothing happens but once the usbhostfs_pc is closed (exit, or ctrl^c) the psplinkusb will restart (or the psp shut down).
i've compiled psplinkusb from a recent svn copy and tried on 1.5, 3.03, and 3.40 where all produced the same so it's not really fw related.
anyone experienced something similar?
chrs
[EDIT]
did some testing with usbhostfs_pc in vverbose mode and it turned out that only "Bulk Write" happens on the USB after a command is entered in pspsh. (there is also Read when the device is connected).
this can explain the turn off on exit.
now i'd like to see what happens in the psp but putting pspDebugScreenPrintf in shell.c is not obvious to me.
maybe PSPSDK_LIBC should be used instead of KERNEL_LIBS?
other solution to get printout on the screen?
psplinkusb pspsh no prompt
-
- Posts: 107
- Joined: Sat Jan 13, 2007 11:50 am
Re: psplinkusb pspsh no prompt
I experienced the same problem while partially upgrading pspsh in the ps and not the psplink in the psp. Get the lastest version from everything from the svn, recompile and use the new psplink and pspsh and it will work.
-
- Posts: 51
- Joined: Sun Feb 24, 2008 3:36 am
This happens to me, after the first reset of psplink. Are you in linux, and are you running 64bit? I am, and I know of atleast one other person having the problem who also happens to be on 64bit linux. If you don't know, just give me the output of uname -a.
I don't know if the bug is in psplink pc tools, or in libusb, but googling doesn't seem to show any 'known issues' with libusb and 64bit...
~S
I don't know if the bug is in psplink pc tools, or in libusb, but googling doesn't seem to show any 'known issues' with libusb and 64bit...
~S