Updating Debug firmware for PS3

Hey everyone


I tried updating my firmware, but is there like a specific name to name the folder containing the firmware? Can't seem to get my TeST ro cecognize the Instal Package Files. Thanks!

 

I think it is the same folder name as when updating a retail console. Folder \PS3\UPDATE on a USB thumb drive, file PS3UPDAT.PUP. At least it works this way on the reference tool...

 

very cool, thanks man, thanks a bunch!

 

Craps, didn't seem to recognize the update..........

 

what fw is it currently on?

Maybe try it on a sd card or burn it on a cd.

 

3.30 to 3.41, hahaha, Ill try a CD next, I was being ghetto and just snagged my sony picture cam and used it as a volume with the folders and firmware, thanks again guys

 

it should work from a usb drive. you're sure your not trying to flash with devkit/retail firmware?

 

I got two files "descriptor.h" and "psgroove.c"

 

psgroove isnt going to help you install debug firmware, not yet anyway.

 

Wait what? Those files have nothing to do with the debug firmware. Do you even have a debug kit?

 

Ummm...

Now I'm thinking you're running jailbreak and trying to update... you know jailbreak disables updates right???


:edit:
shit now i re-read your first post and you mention package files... so what the hell are you really trying to do? Re-reading this entire thread and you make 0 sense...
package files, jailbreak, updating ur debug.. maybe try to explain in detail what info you really need so that we can help you.

 

Sure sorry guys, I read recently that Debug FW 3.40 was available for my DECH PS3 TEST slim, i'm currently running Debug 3.30 which was not a problem updating before, but now I'm wondering if this "leak" is some hack firmware for retail systems to run the debug menu:
http://www.nextgenupdate.com/forums...leases-psgroove-debug-consoles-fw-3-40-a.html
I don't own a retail PS3 so hacking isn't the issue, but this "payload" apparently should only apply to to debugs, I do appreciate the advice guys and thanks as usual, I am a bit of a noob since none of the old TEST PS1 nor PS2 ever needed firmware updates like this complex kit.

 

I'll totally buy your debug kit, since you're clueless

 

That site is hardly readable for me because of all those "Only registered and activated users can see links. CLICK HERE TO REGISTER" fragments, but from what I can see, this is about PSGroove payloads for the debug firmware. This is not a firmware update for a debug PS3, but a modified version of psgroove suitable for debugs. Which means: if [1] you have a TEST PS3 running one of the mentioned firmware versions, and [2] you want to run the USB exploit (aka jailbreak, psgroove and so on) on it, that stuff is for you. In that case, you would update your USB stick, AVR development board or whatever device you are using with the specified USB descriptor, then use it to exploit the debug console as you would exploit a retail machine.

No problem, we all started as noobs ;-).
And because you mentioned it: those good old consoles were using MASK ROMs, so they could not be updated at all without soldering new chips in. The development kits used flash, though, so they could be updated if needed. Applies to the PS2 TOOL and the PS1 dev cards minus the DTL-H2000, which also has non-electrically-erasable ROM as well (could be an EPROM, but I'm not sure).

Anyway, OS updates had to be performed as well sometimes, and Sony came up with some interesting ideas. On the H2000, you had to run a special updater application before starting your own code. That updater exchanged parts of the kernel in RAM, so any code started afterwards would run as if it was on a retail console. Funny side note: the first versions of the updater were bugged as hell, so they would randomly fail and leave the card in an inoperable state. The updater got an update itself some time later, and all was well until the newer cards arrived (H2500, H2700). These featured flash memory instead of a ROM, and came with a bunch of BIOS images, depending on what you wanted to do with them. You usually had to use a matching PC-side driver and flash version, or the card would not work at all. Ask Jackhead (or search for his posts) if you want to know more; getting a H2500 to work must have given him a lot of gray hairs ;-).

The situation was better for the PS2. The TOOLs had flash, and each SDK version came with an image you had to install prior to running code compiled with that specific SDK (or better: libraries). If the version did not match, certain calls would just fail. The interesting question now was to get the "correct" (from the viewpoint of the application) version of the kernel loaded, independent of whether it was running on a retail, TEST or TOOL. Remember: you can run any retail game (minus those it doesn't work for, but that is mainly due to some bad programming of the early TOOL's drive controllers) on a TOOL, even if the versions do not match.
For this, Sony thought of a special update reboot sequence: when a PS2 program starts, it usually tells the system "please load the following kernel image". The system then resets the second processor (IOP) to the default kernel (mainly to terminate resident drivers and free as much memory as possible), then executes a special file from ROM named UDNL. UDNL uses the default CDVD driver to load the update file into memory, then performs a warm restart of the IOP to execute it. If everything works, the application can continue and use the updated kernel; if not, it hangs indefinitely while waiting for the IOP to acknowledge the reboot request. There are interesting ways to interfere with the reboot requests to get various effects; think of programs like HDL or ESR (as well as my own IOP DECI2 Bridge and ODEM ;-)).

Leave something for me. :drool:

 

Real interesting deep insight on the inner workings and boot notes! I am running several TEST PS2 and a DTL-T10000H, nice clear up about the software libraries, I had always wondered what could cause failure. Well, at this point coming across a TEST PS3 is still not easy, thus I wont even quote anyone how much I would let it go for since I can't imagine selling it.......... but trading my slim for the fat gloss is a more likely scenario.

 

ok.. so saying that you have a real test kit and the correct firmware, there should be no problem updating from a usb drive.

 

Yes, pretty sure my Sony systems are Debug and Dev, I am a noob and no longer able to attain my softwares through "the man" so it's the hard way for me

 

there's also alternative methods of updating using the http update method (consult your manual for this.. don't remember the instructions on how to setup and through target manager (or maybe this was only for dev kits?)

 

You have a slim PS3 TEST?

 

Yeah, she's a slim, I had never seen one other than mine