forums.ps2dev.org

32bit symbol ID is actually the first 4 bytes of SHA1 of the symbol name. Someone on IRC figured this out the otehr day and there is code to calculate it on the ftp server. Right, what nem is saying (and as demonstrated by his code) -- the relocation is done only by the NID, the name is irrelevant....

Use the search function; there's a decent amount known about the format that was used in the old "broken" update, but the new 1.5-format is much more opaque.

ooPo wrote:Leaked firmware, eh? How did you manage that? :)

Is this the leaked breaks-your-PSP firmware? Or another? If it's the leaked one, it certainly seems like someone packaged together a 1.0 firmware... perhaps it's the firmware for the PSP development boxen?

On loading an ELF or PRX, the PSP's loader has the ability to dynamically link in other prx modules. There's a couple of structures that are relevant to this; this is what i've deduced so far. nem has much of this in the startup.s in the HelloPSP source zip. typedef struct { // 0, 0, 1, 1 ?...

Ok, I did some research I guess the dev units dont have a UMD drive but a unit in place of it that has a parallel cable to stream the data. So I still dont see how Paradox would rip a UMD with a dev unit. They would have to have the stolen code, or some way to export the data from a standard PSP. I...

I have to say, this is really touching the edge of the rules and I'm left wondering what kind of development-based topics will arise from this list. One topic is exploration of file structure in /PSP/GAME -- it might be (probably is) feasable to put a set of files there in the right directory struc...

I thought I had a copy of the original will-break-your-PSP update PBP somewhere, but I don't seem to.. anyone have this sitting around? Been trying to find it for a few days without much success.

In theory it could be done, with a MMU, and with tight kernel control over what pages get the executable bit and where they came from -- but that doesn't make it "physically impossible". As far as I know, it's a modified R4k with 32mb dram and 32 mb flash. They do mention a hardware securi...

I've tried doing exactly this, but my PSP was 1.5 out of the box. I couldn't repeat the blank screen error either though; I'll try again, as perhaps there was something that I missed.

I don't own a copy of Namco Museum (yet, I think; fry's had a jp import last time I was there, I'll have to pick it up), but I attempted to repeat some of the findings. If I send my PSP the 0x0103 packet that was in ooPo's namco gameshare capture, it responds with a 0x0104 packet; same packet each t...