[SEARCH] PSP Dev Kit DTP-T1000 firmwares

Hi, Ive got a DTP-T1000 PSP Dev Kit and I need a recent firmware (because my dev kit has been reseted and the only mod avalaible is the debugger mode :/ ).

If someone owns a recent firmware or the SDK, I'm interested!

Thank you for your help

 

5.50 GEN-D3 apparently does install on Testing Tools.

 

This isn't a testing tool though. I still need to dig up the ones that I have, but they only go up to like 2.50.

 

Nobody can help me ? I know some people in this forum have the firmware but they do not want to give it to me for "security" reasons ...

I would really like to run this DTP

 

Yeah, not sure what's up with PSP related stuff.
I've been hoping for someone to share a full PSP SDK, as well as dev firmwares, but nothing has come up, even though the console is not even current gen anymore.
Don't give up hope!

 

If you don't mind me asking, what is the firmware that your DTP is currently on?

 

The original, 1.0.0 :s

 

Just curious, seriously from those 'in the know', what is the reason for not sharing the Dev Tool firmwares at this point?

 

Documents I can understand since sony is pretty strong with marking documents with traceable IDs back to who leaked them. So it on the whole probably makes devs hesitant to leak sony dev software/docs anymore.

For PSP, I believe you need a few firmware files actually and not just one. It's been a long time since I messed with a kit. I will have a better memory/understanding of this when I get my hands on a devkit again (will in a few weeks).

 

I kind of figured there might be a way to trace them.... (Has anyone confirmed for sure that's the case with the PSP Dev software? Or is it just being cautious/paranoid?)
And, at this point, would Sony even care? It is a dead system after all... They didn't even bother to re-collect the devkits after the PSP was killed, many game companies just recycled the hardware. (Thus the flood of Test Kits and Dev Tools hitting the collector market via e-waste companies... )

Yeah the Dev Tool needs several files, especially if you are at 1.0.0. You have to update to 1.5 first, then 4.01, then 6.60. And each one seems to require a kernel update and firmware update, some done through a web browser of a computer connected to the device... It can't all just be done by burned disc or memory card.

 

you don\t need 1.5 and the reason for test tools needing to go to 4.01 first is because thats the firmware that adds the option to update via pbp which the 6.60 TT-A is only in pbp.
there is a ISO version but not sure if anyone tried it.

 

They can't trace firmware updates themselves, they can trace very early tools and they can trace pdf documentation, as for my part, it's more about what could happen to me if I am caught sharing Sony's IP, no matter the source.

 

Well, the documentation says if you are below 1.5 (i.e., at 1.0), to update to 1.5 _first_ before updating to 4.01... That's the only reason I mentioned that little requirement. It might actually not really be required though, just noting their instructions.

 

You need to update to 1.50 first because earlier firmware do not mount the update discs, so the update icon does not show up and you can't update to 1.52 or later.
Obviously EBOOT.PBP updaters will not display either as the game category on earlier firmware earlier than 3.90 is locked/hidden.

1.50 and earlier updates were done directly through an .arc update flashed using a series of custom IPLs (dformati.bin, formati.bin and writei_sys.bin (sometimes just writei.bin depending on the SDK) This initially required a specific set of sdk tools (dstdb, dspcons, and dsxfilesv)
Those need specific instructions to operate, for instance you need to use the following command to run dsxfilesv: dsxfilesv -i -sc -d XX.XX.XX.XX

The IPL is run using the bloadp command from dstdb for instance
dstdb > bloadp /usr/local/psp/devkit/flash/dformati.bin
dstdb > reset

Eventually 2 versions of an all in one 1.50 updater/downgrader tools were released one was called PSP_150Updater-1.0.0.zip released in January 23rd 2006, which is command like and allows updating/downgrading multiple targets to 1.50, the other is called PSPhtool_150downgrader-095.zip released in September 30th 2008 and is a GUI tool allowing to update/downgrade specific targets to 1.50.

Those tools allow to avoid directly using older sdk tools, especially as there is no windows version of dsxfilesv which only ran on Linux.
Eventually a psp-utils-x.x.x.x-windows package released with later sdks that included most (but not all) of the SDK binaries compiled for Win32 including a standalone version of bloadp called dsbloadp.exe (although dstdb was also ported with the name dstdb.exe) dsxfilesv was never ported.

Starting from the 5.00 beta firmware, all firmware were released in PUPK format which included the infamous custom IPLs along with an updater (in PBP format) and a CP update, all in a single binary archive, updates are performed through the network using the PSPhtool_Updater-101.zip tool supplied with the SDK, this allows to perform the update regardless of the firmware flashed on the unit, you can optionally opt to only flash either the "TOOL update" (CP update) or the "SYSTEM update" (the PSP firmware). Likewise any IPL based updates (1.50 and older) can be flashed on a system regardless of the firmware installed on the unit, you should however take note that some early firmware (1.0.3 and older), upon downgrading will BSOD unless you run the rinit.prx to format the registry as the parsing for registry files has changed.

 

I stand corrected and retract my rebuttal

 

Development Tools (DTP-T1000) do not operate the same way at all the Testing Tools (DTP-H1500) they aren't as straightforward to use and require the proper software to operate otherwise you might as well own a fancy paperweight. When someone acquires such a unit, he needs to ensure he actually has the proper software as his disposal to make it work, most of this software is NDAed and thus can't be shared by most who are privy to it. (And even then it technically remains Sony's IP) finally the owner needs to read the proper documentation to ensure he knows what he's doing, otherwise he is just wasting the use of a good unit.

The DTP-T1000, on pre 2.60 firmware will not boot at all without the proper sdk setup, (that is you need the actual kbooti.bin file, dstdb, the whole environment and to use bloadp with load address 0x20000000). Starting 2.60 it will only boot in system software mode (without debugging features) assuming you have the matching CP version (so if you do a system init, unless you have the CP update for it, you psp firmware won't boot!), and will only boot in all modes (including debugger mode) in firmware 5.00+, even then it needs the matching CP version, so if you don't have the PUPK and the sdk tools to update the unit, you still end up with a paperweight when doing a system init.

 

Great information as always mathieulh.

Also thanks for confirmation on what I remembered about the need for multiple updates (i have to admit the last time I used a psp kit was in early 2009). Never realized they simplified the process in later firmwares.

 

Indeed, I still remember our talks from back then

I assume they simplified the process because developers were tired of having to send the kbooti file with the the proper reset mode argument every time they had to boot/reset the device, on 2.60 they put a copy of kbooti so the unit can start on its own in system software mode, in 5.00+ they put kbooti.bin in flash3:/ and have bootdispi.bin stored in the CP firmware to actually verify flash3:/kbooti.bin and reset to it. (Even though they also flash the IPL on nand, it does not seem to be actually used)

All this wasn't really necessary though because by that point, developers were using SNSys ProDG debugger which send kbooti.bin to the unit for you every time you expected a reset. (ProDG eventually became free to all licensees and didn't require a license anymore)

 

How would you update to 5.50 GEN-D3 on a DTP-H1500 unit? It does not have pandora support (you can't really put a battery in, and so far it hasn't been discovered how to trigger service mode on those units) is there a HEN that works on the TestingTool firmware?

 

I actually don't know how it is supported but it apparently IS supported, I say so because when I installed that version on a PSP Slim Mobo TA-85v2 the UPDATE 'app' notified me that That specific GEN version was installable on testing tools, if you need further info on this you'd have to contact PSP GEN developers.