AV Testing Tool PS3 (DECHS-XXXX) or PSP (DTP-LXXXX)

@mathieulh I haven't forgotten, I'm still waiting for it to arrive at the moment, hopefully it won't be too much longer

 

I noticed something peculiar in video_plugin.prx from the DTP-L1500 vsh
It seems there is an undocumented feature allowing you to fake UMD Video and Audio paths from the memory stick and host0
below are the relevant paths that get checked:
ms0:/psp_umd/UMD_VIDEO/RESOURCE
host0:__fake__/umd/UMD_VIDEO/RESOURCE
ms0:/psp_umd/UMD_AUDIO/RESOURCE
host0:__fake__/umd/UMD_AUDIO/RESOURCE
disc0:/UMD_VIDEO/RESOURCE
disc0:/UMD_AUDIO/RESOURCE
disc0 is the actual UMD/DVD device

I have checked this against the retail 1.50 video_plugin module and all paths except for the disc0: ones are absent these paths are absent so these are exclusive to the DTP-L1500 firmware.
I Will check once I am back home to see if I can mount a UMD Video from ms0 on the DTP-L1500 vsh using those paths.

UPDATE: I just tried the ms0 path, it does not seem to work.

 

Sorry for the delay on getting my hands on a suitable memory stick, plus as you know life can get busy

Anyways here's a full dump http://rapt0r.xyz:8081/nand-dump.bin

Just so you know your tool reported "bad block at page 113632 block 3551" at the end, I'm not sure if that means that block is dead and cannot be recovered or if it's a block that has been remapped in the past but your dumper tried to read it still.

Anyways, let us know what you find!

 

Thanks, I am downloading it now!

My dumper tries to read all blocks and lists the ones it can't read, it is very likely that the bad block is taken into account within your NAND's ECC data so this is nothing to worry about and this is a normal occurrence on a lot of consoles, not all NANDs are perfect after all.

 

Yeah, i knew NAND generally gets bad blocks, so i wasn't too concerned, i was more concerned about how your dumper handles it, good to hear it will probably be fine.

 

Math knows what hes doing and I can personally attest to it.

 

Well, the dumper only reads, it does not write anything to the NAND (it does write to the memory stick though, obviously ), so your NAND is untouched after running it xD

 

I thought that would've been the case.