forums.ps2dev.org

Isn't it sufficient to just unplug then replug the USB cable?

have you tried completely reiniting the SIO (in psplink it was sioInit) and re-setting the baud rate. Cant remember if HPRM contains some suspend code which might reclaim the SIO port after resume.

There is sceIoGetThreadCwd but annoyingly it is kernel mode only from what I remember. This is why the C library maintains its own copy based on argv[0] but as that doesn't have to match where the file really comes from it isn't ideal.

psplink works quite happily on 3+ and has done for many a year. You need to get the latest version of psplinkusb out of subversion (unless you need the wifi or serial versions, then you are stuffed :P)

Those samples really are legacy now, what you want is the prx_template or kprx_template in the samples/template directory. They should work out of the box.

Good to see xorloser back in business, PDX do so little these days ;)

Of course also just as amusing seeing the sticker on the front of the machine saying "Retail" implying he probably has at least one test kit knocking about, ahem ;)

So if the geniuses outside "this" community knew about it the whole time then where is my accelerated graphics? After all it is easy to say that something exists but I have never seen any proof that anyone else has giving out any information on how to use it. And I don't think people here ...

It kind of worked for a while, then something happened and the debug hardware stopped correctly trapping. You can try setting the debug registers to the correct values but it probably isn't worth it :)

Of course if Sony have done their job correctly then breaking into the HV in otheros mode gives you little, but no doubt they haven't done their job ;)

I suggest you run a normal "make" i.e. go to a PSPSDK sample (say gu/sprite) and run 'make BUILD_PRX=1' in what ever you have available and see what psp-gcc lines are run. Then replicate those.

Well there might not be anything you can do about the last problem. Sometimes Sony change shit and psplink can break because of it. It might be running out of memory for example.

Err ms0: is already mapped. You can either do cd ms0: to map the current dir to ms0: or you can just run an app from ms0: if you want. You perhaps should read the manual :) hostX: is for PC stuff only. Any other drive is available, like you normally can access disc0: which is the UMD, or flash0: or ...

Sigh :) Usbhostfs_pc uses the current directory as its default location for mappings. Either push usbhostfs_pc.exe somewhere in your path and run it from the directory you want to access or in usbhostfs_pc's window type something like mount 0 /path/to/my/files you can also map the other 7 host drive...

Well remotejoy would work fine as it is simply a bug in the shell (it is actually a bug in the firmware which was "intentionally" put there from what I can tell :P)

Urm, have you previously used the same version of psplink on that version of the psp firmware? There was a firmware where the shell breaks, but it is still there you just do not see any output. You need to update to the latest psplink from subversion if that is the case, of course maybe it doesn't w...

This is a forum for software development, we do not do game hacking.

Yes those functions can only be used in kernel mode. If you are using psplink you can set user profiling mode (assuming it still works on new firmwares) by using the profmode command (use "profmode t" to set single thread mode, it will context switch the regs, or "profmode g" to ...

You cannot change your stack pointer easily because if your thread context gets switched the thread manager will kill you because it thinks you blew your stack. You might be able to get away with disabling interrupts while running the ipl code, with interrupts off the threads cannot context switch a...

you are possibly running out of kernel memory, not sure how much 5.50 has available, try running the memfree command in psplink before and after and see if you have virtually no memory left. Alas if it is kernel mode memory issues you are stuffed :)

I did consider writing a windows specific version of usbhostfs using MS's WinUSB which would get around all the driver signing problems. Shame I am too lazy ;)

As pointed out if you get psplink running it comes with its own exception handler so you dont need to set up anything else and will help in development and debugging to boot.

have you just tried it and tested if the current definition works? :) I am sure I have seen bitrev used in some code and it matches the definition binutils use but I could be wrong.

I think now Sony have abandoned "homebrew" they are fair game, alas normally once you can get unlicensed code running it tends to end up with piracy as well is not really our fault. Oh and rapso I call bullshit on the CCC presentation, the 360 was hacked for piracy, without that the initia...

That is unfortunate ;)

Urm, what I meant when I said use 64bit ints is to keep the buf as is (leave as 32bit ints) then when doing the calculation cast each element to a 64bit int.

It works fine, you are just hitting a overflowing the integer arithmetic. You need to convert your 3 values to 64bit integers.

When building a program as an ELF it uses _start (for legacy reasons) when building a prx it uses module_start (for crazy reasons)

There is no difference, module_start is just a synonym for _start. The reason you will see module_start being used is that the actual name sony used (based on reversing the hash) and so in certain situations we use that name for ease.

As long as _start is set to the entry point it runs before _init, well in actual fact your _start routine is responsible for calling _init

640K is still quite a sizable increase :)