forums.ps2dev.org

In 3.71, the SendCommand function is located at address (text_addr+0xF8D0). Commands arrive to this function with endianess reversed. Some unknown data is also sent to this function, not only the commands. The ReceiveCommand functions is located at address (text_addr+0xF9E4). After the call to this...

Yeah, we looked into it with D_A, and the reason is what he told before ;) The marvell firmware used in the PSP's chip is limited...

Before anyone starts asking/begging, NO it is NOT POSSIBLE to get the PSP into a promiscuous (monitor) mode with the Marvell commands. :)

Ahem...

I don't think that "a=b & (x | y | z)" is much better than "a= b&x; a|=b&y; a|=b&z;"... I think it's even the opposite... Especially since a and b are assigned registers ;)

Well, you can just see.... The audiorouting setmode function just sets a 0x20 event flag in sub_00000000 and passes some params. This would not be suspicious if the HPRM connect handler in impose.prx didn't do the same ;) So I think something is wrong in the way it is called - maybe it doesn't like ...

Thanks, somehow I missed that thread when searching. Seems that adrahil failed when trying to provide a software solution and chopping off the Tip of the phone jack is the easy hardware solution. That could work out, though I'd have preferred a software solution (gonna ask adrahil when I see him). ...

For the Power LED you should use Syscon call, but for WLAN/MS leds, you can use this: typedef struct{ int oncnt; int offcnt; int endcnt; int endstat; }SceLedParam; #define LED_MODE_OFF 0 #define LED_MODE_ON 1 #define LED_MODE_TIMED 2 #define LED_MODE_DELAY 3 #define LED_TYPE_MS 0 #...

A non-noob would not need to post such a question but would just look at the stuff on the main page of "http://ps2dev.org/"...

The MS Driver works really well -.-
And for FAT support, just look at Tiny-FatFs (http://elm-chan.org/fsw/ff/00index_e.html) where the code was taken from.

You probably need to replace the battery charging circuitry (stuff around IC6001) as well as the power switch.

SPITFIR3 wrote:I've also tried
sceSysconResetDevice(2, 1);
sceSysconResetDevice(1, 1);

This bricks the slim and have to restore with nand dump.

Bricks? Just by doing these two calls?

Make a kernel module...

You know, there is something called the "Search" button....

I think we should make people follow a course in Searching before being allowed to post on this forum...

But since I'm being nice today, look here:
http://forums.ps2dev.org/viewtopic.php? ... dule+flags

:) moonlight: You're right, I didn't see it... I generally try to *solve* my compiler warnings or errors... psp-gcc -I/usr/local/pspdev/psp/sdk/include/libc -Ipsp -Iisa -Ipsx -I. -I/usr/local/pspdev/psp/sdk/include -O2 -G0 -Wall -D_PSP_FW_VERSION=150 -L. -L/usr/local/pspdev/psp/sdk/lib -specs=/usr/l...

You can mess with the hardware, use EDRAM for display, ... :) There ARE possibilities...

Hi all!
Just dropping by to tell you about a curiosity :) PSPSDK fails to compile SCE-function-less modules. If I don't call ANY SCE functions, it refuses to link, because .lib.stub can't be found... Just found it kind of fun ;)

Yeah, there's some sort of magic going on :)
The macro adds the import to .lib.stub, .rodata.scenid, ... sections, which basically give information to the PSP kernel about what functions to import into the application on loading...

sceLearnCAndRTFMEx(void null);

Good job :) And when people ask you to post the code, it is not because they doubt your C capacities, but it happens quite often that some hardware subtility will cause problems if you do things your way. And there are loads of people - who DO know the hardware better than you - around who can help ...

This question is out of bounds here, because of the respect to developers, if not because of the illegality of it as such. Go somewhere else.

How about showing the code where it goes wrong and telling about the context of its execution? ;)

Uhm... and what is this supposed to prove? That there still is backwards compatibility? You don't really need that kind of app, since games are backwards compatible. (And features which are not are beyond your knowledge and skills) Also, please either remove the official SCE PRXs from the downloads,...

Update to latest SVN release of prxtool.

So... tell me, how do you plan to tackle the following problems: - Display drivers have changed on slim, so won't work on 1.50 - 3.x IPL can't load 1.50 files and 1.50 one won't work on SLIM. - Kernel NIDs are mixed in 3.71, thanks to some "leet hacker" - Various file formats changes? (I w...

Don't try to learn on the PSP. Not exactly. All I knew in programming for the pc was printf and scanf. :D Even given your example (which does not really contradict the statement), jim is right :) Deep knowledge of C is vital not to bother other devs with endless "compilation" problems...

The Marvell card the PSP got does :) But of course SCE are too cheap to extend their WLAN FW ;)

Besides, 1.50 wouldn't even understand the extra memory Yes it will... It is built (for devkit) to understand it :) There is only the partitioning of the NAND to change. Has kernel mode been unlocked on 3.60 Yes. Until programs like Bookr run on 3.xx It should probably work after recompilation - as...

Yes, moonlight = D_A.

The function names you see used are not the true ones... They are wild guesses. True function names have to have their first 32bits of SHA1 be equal to the NID.

The SHA1 does not correspond :/
Moreover SCE hide the function names, making them obscure ;)