[Lizard360]

Hello guys,

i have been trying to downgrade my ps3 for about two days now and still no success. It's a slim and the mobo is dyn-001. My flasher is progskeet 1.2 and I soldered the wires. I don't think soldering is the problem because i have successfully soldered a lot of XBOXes in the past. In addition to that i already did the wiring twice to find out whether this is my problem. The CFI check in Winskeet says it's invalid and the dumps extracted are almost everytime the same but faulty ones. This is clear to me because for example the offset value 0x200 is IBI instead of IFI or the header doesn't show FACEOFF DEADBEEF.
I looked at the page for validating dumps on ps3devwiki and there is a point called repetitions. I have such a repetition, it's 0x1000 and that would mean my adress line A11 is faulty, is that correct? I am not sure because they speak of 30 adress lines though my board just has 22.

I also tried a new usb cable. At first i used one with a length of 1m, now it's 30 cm, about 13-14 inch. That didn't work out.

The next step was to increase the amount of ground points. Didn't help either.

As wires i use AWG 28 ones because i still have those from a nand ps3. Is that a problem?

What about the point WP on the progskeet? Does it stay unsoldered?

If this could help i attached one of my dumps.

I am powering the nor with my progskeet. That means i soldered the 3.3v from progskeet to the 3.3v on the ps3 mobo.

[ps3333]

http://www.ps3devwiki.com/wiki/Validating_flash_dumps

[thelamacmdr]

AFAIK, you shouldn't be powering the NOR with your progskeet. Either use an external power supply or use the PS3's power supply. Now while this applies to the Progskeet 1.1 PS3DevWiki R7/R8 Explanation You'll see that it's actually the progskeet on its own isn't really enough to power that nor. So I suggest dumping with the PS3 on and 3.3V disconnected from the progskeet.

This is for the 1.1/1.0 as well but it's worth looking through here to get a lot more information first: http://www.ps3devwiki.com/wiki/Talk:Progskeet_1.0_/_1.1

[Lizard360]

Thanks for those first replies. Any help is welcome.

@ thelamacmdr
That sounds logic to me. So i will desolder my 3.3v pin from progskeet to the ps3 mobo and instead power on the console and thereby powering the nor. Do I have to care for anything on the progskeet itself then? Like bridging some contacts? At the moment R8 is closed and R7 is open. Is it the same like on PS 1.1?

Anymore suggestions how to fix this?

[thelamacmdr]

I've asked around but I honestly haven't gotten any definitive answers regarding whether the R7 and R8 points are the same on both. I've tried both and dumping dumps fine with both configurations and no 3.3V soldered but writing is still an issue for many as you may have noticed so I'd be cautious.

[underwurlde]

This is how the resistors appear to be wired on the ProgSkeet v1.2 PCB:



R17: If fitted, then power from the 15 way cable from either an InJeCtuS JTAG programmer or from the ProgSkeet USB interface is used to provide 3.3V to the ProgSkeet v1.2 main PCB. The power source ultimately being 5.0V from the computer via USB.

Hence if R17 is not fitted, then 3.3V must be sourced from elsewhere to power the ProgSkeet v1.2 main PCB.

Fit either R13 & R15 OR R14 & R16 to provide either 3.3V (R13 & R15 fitted as supplied by default) OR 1.5V (R14 & R16 fitted) to the VMV0 VMV1 voltages to the Actel A3P125 FPGA chip.

R7: If the ProgSkeet is used to program / read a NAND or Dual NAND setup, fit this resistor.
OR
R8: If the ProgSkeet is used to program / read a NOR setup, fit this resistor.

As can be seen in the diagram, the fitting of R7 enables two 10K resistor pull-ups (R9 & R10) for the Ready /Busy line for NAND flash chip(s). The fitting of R8 enables a 10K resistor pull-up (R11) for the Ready /Busy line for a NOR flash chip.

Hope that makes sense.

-------------

Although not shown on the ProgSkeet web-site manual, I think P05 (apart from being NAND1 /CEa primary control signal) is also the TRISTATE control signal when reading / programming NOR chips when the ProgSkeet v1.2 is connected to in-circuit NOR chips soldered to the motherboard of say a PS3. Hence in order to prevent the PS3's Southbridge chip from placing signals on the memory bus (and hence ****ing everything up for the ProgSkeet), this signal too must be connected perhaps?

I think that NOR /WP appears on P04 and NOR /RESET appears on P06.

Please double check as I have not tried this, I have just gleamed this from reading from what is 'out there'.

Good luck

A

[Lizard360]

@underwurlde
Thanks for this great explanation. As I said in my first post my R8 is soldered whereas my R7 is open. All other resistors are unchanged. So this seems to be right.

I now tried using the ps3 as power source for the nor. Thereby I found out that I must have a short between two or more lines because when I tried to turn on the ps3 the led turned yellow for a millisec and beeped three times. Afterwards it was blinking red. I was afraid that I might have f*cked up my console so I desoldered all wires and cleaned up the test points. Now the console boots up normally and no problems.

What I have learned:
Using the PS3 as power source is a good way to find out whether you have a short in your soldering

I just ordered some AWG26 wire and this will be my next try. I hope this will work then I will tell you if this worked out.

[OGzxFTW]

Use 26awg for NOR
Nand is 28-30

[underwurlde]

I now tried using the ps3 as power source for the nor.

So for PS3 in-circuit programming of NOR type flash memory devices hence:
Remove R17, therefore have to connect ProgSkeet's GND & 3V3 to power source of PS3 (Get this right!!!)
Remove R7 and solder it to R8 position instead.
Leave R13 & R15 alone.
Correctly connect P04, P05 & P06.

Thereby I found out that I must have a short between two or more lines because when I tried to turn on the ps3 the led turned yellow for a millisec and beeped three times. Afterwards it was blinking red. I was afraid that I might have f*cked up my console so I desoldered all wires and cleaned up the test points. Now the console boots up normally and no problems.

Now you have me thinking... If the ProgSkeet programmer is ALSO connected to the Address, Data & Control bus of a PS3, when the PS3 is then turned on wouldn't one expect it to appear faulty? Having said this, if the TRISTATE connection is made and the ProgSkeet is not being used to read / program flash then perhaps the ProgSkeets outputs go tristate thereby allowing the PS3 to do it's stuff and IF some wires you've connected are indeed wrong then yes, the PS3 will show a fault. When the ProgSkeet goes into read / program mode then it will change the state of the TRISTATE connection which will disable the PS3 SouthBridge chip effectively disconnecting the PS3 from the NOR chip and allowing the ProgSkeet control and access to it.

Not tried this so just second guessing things really!

A

[ozz387]

Hi, im a noob, would someone be able to check my dump plz, i followed bailyscreams tutorial but in the stats on the left line its 18.54 and my bootldr is 00 00 2F 13 F5 A2 21 B5 C0 5F 21 42 01 97 9D AA.

Heres the link: https://rapidshare.com/files/2476029...pps30.swap.bin
************* [ - Post Merged - ] *************

Originally Posted by ozz387 Hi, im a noob, would someone be able to check my dump plz, i followed bailyscreams tutorial but in the stats on the left line its 18.54 and my bootldr at offset 00FC0000 is 00 00 2F 13 F5 A2 21 B5 C0 5F 21 42 01 97 9D AA. Heres the link: https://rapidshare.com/files/2476029...pps30.swap.bin

Also can i use any downgrade dongle with e3 flasher to downgrade from ofw4.25? because all the dongles i can find say they only work on fw's around 3.55, or is that only to use it for playing bk ups?