The above video goes away if you are a member and logged in, so log in now!
Have no luck on Progskeet unbricking the PS3
Have no luck on Progskeet unbricking the PS3 –
Hi, anyone can help me?
I updated my progskeet v1.1 with the latest bitstream file 111126.
After that my progstream can't be detected by computer anymore.
Seems that the progskeet with latest bitstream will lose its USB when it was connected to PS3.
Its USB works fine if it gets the power from computer side.
Anyone knows what is happening?
And anyone has progskeet's old bitstreams, I would like to program my progskeet back to the old version for getting its USB back to work when power is supplied by PS3. NOR Dump and erase looks working fine but the NOR writing does not work, so I would like to have a try to see any luck on the previous versions.
[ ] R7 Open
[ ] R7 Closed
[X] R7 Switch Installed
[ ] R8 Shorted by 0-Ohm Resistor (Stock)
[ ] R8 Shorted
 R8 Switch Installed
[ ] NAND
Length of Wires: Roughly 15cm
NAND/NOR Model: Spansion S29GL128P90TFIR2
Description of Task: Attempting to write the NOR chip of a Sony Playstion 3 slim console after the Progskeet updated.
Description of Methodology: Updated the Progskeet with bitstream 111126 and attempted to flash back resulting image.
Problem: Progskeet cannot be detected by computer on USB after updated with power supplied from PS3 and NOR writing error.
I can help you with this one. Since you got yourself switch on R7, i suggest you put one at R8 as well. So figure this - when R7 is shorted, Progskeet takes power from console, and when R8 is shorted - it takes power from PC. Whatever you do - make sure they never shorted both at one time - it can burn your mobo in case when console is powered on.
Then again, step by step workout.
Make sure R7 and R8 are opened. (from now on, forget about R8)
Plug the power cord, power up your console.
Wait around 15 secs or so and short R7 (by simply pushing the switch in your case).
Plug USB from PC to progskeet.
Profit. Progskeet is detected by Windows, and console is not RLOD'ed. The rest is up to you.
Good luck in any case.
BTW, R8 is very handy when you wish to flash your console without actually powering it up. Just keep in mind that for this case you'll have to find shortest USB cord, since current is terribly harmed by long wire.
And dont forget to check your dumps all the time in accordance with PS3DevWiki's information regarding dumps - this will save you greatly.
Have fun anyway
Also, for the Spansion (the most inadequate NOR I've ever seen), use following settings - Single word programming, Static Timing. After it flashes, check out verification errors - I can assure you there will be lots of them. And here is a trick - before progskeet write something to NOR, it reads memory contents and flash only those blocks that mismatch the desired BIN file. So, go ahead and flash it again and again (and again, up to more than 16 times in a row), until he says "nothing to flash!".
But, if there's still a few blocks left that don't pass verification no matter how hard you try - switch to USB Transfer Timing and flash again. It's too damn slow to start flashing with these settings, it takes around 2 minutes to flash one block => around 4 hours to flash complete NOR, so that's where the trick I explained above comes in handy - it's just saves your time and nerve.
Just saw your post back at Progskeet's forum, but for some strange reason I couldn't register in there - confirmation mail just won't come.
And did you verified your NOR dump? Is it good, containing 0FACEOFF & DEADBEEF magic headers, as well as other nessesary parts? I suggest you to check it out immideately.
Finally , the Progskeet stopped flashing the PS3 (over 6 hours I guess) but a lot of verification failed there. lol
Now the proskeet can be powered by the PS3, the USB is back after used a shorter usb cable (1.5feet) and moved to a laptop.
I tried the trick but the progskeet/its program often halt itself which causing the problem.
I was using ps3devwiki's Hardware_flashing#.27NOR.27_Interface_Testpoints_o n_NAND_consoles as a guideline to connect the Nor and progskeet. Is that correct for the connection? I think I will shorten the length of the wires, hope that would have some help on it.
Seriously though, it definitely has something to do with latest bitstreams, if it takes 6 hours to flash full NOR... Progskeet that I've got flashes it within 15 minutes or so.
Anyway, I'm using 12 cm. long wires to connect Progskeet to mainboard. Which length have yours?
Aslo, don't you mixed up about timing? I personally use Static timing at preliminary flashing, and write hard blocks under USB Transfer Timing. Check it out too.
But AFAIK USB Timing never misses the data. It's too damn long to wait, but there will be no verification errors in the end. So, give it a try.
And I want to ask you for report back all of your struggles, since it can greatly help out for guys facing same obstacles.
Good luck on your quest!
Hold it right there!!!
Hold it right there!!! –
Wait! Have you got a FAT model? You mentioned NOR testpoints on NAND console, which is direct access to Starship2. Correct me if I'm wrong.
If it is NOR console, then I suggest you using an official diagrams from Progskeet's download section - I never had any problems with them.
Hmm...my PS3 is a slim model. I remember its mother board is the JTP-001. The length of the wires should be around 15cm~20cm I guess. I used the picture from the Hardware_flashing#Progskeet_notes of ps3devwiki (sorry, can't post the link) as it looks bigger and clear enough, it shows the pads the same as the official one. From the past experiments, except using the default setting, any setting with "single word program" would take long on flashing.
I double checked the diagrams, have you used the gp3 to connect the WP# pin of the NOR chip? I have not connected that pin to progskeet as it is not shown on the picture.
But I found that the gp3 is used for the DIA-001 board, should I connect it to the progskeet as well?