User talk:Zecoxao: Difference between revisions

From PS3 Developer wiki
Jump to navigation Jump to search
mNo edit summary
m (correct some info and add additional notes)
Line 24: Line 24:
* The JTAG registers/TAP-controllers need to be bruteforced / reverse engineered
* The JTAG registers/TAP-controllers need to be bruteforced / reverse engineered
* The leaked service manuals present information about the pins connected to the JigPin
* The leaked service manuals present information about the pins connected to the JigPin
* The JigPin contains an object used to diagnose the ps3 using JTAG
* The ObjectiveSuite contains an object (DIAGSERVICE) used to diagnose the ps3 using JTAG
* Using a DIY JigPin would facilitate the task
* Using a DIY JigPin would facilitate the task, but we still need more info about the hardware and software interface used by ObjectiveSuite to handle this.
* This would probably work on ps4 too (provided that the diag pin and the JTAG pins still exist)
* This would probably work on ps4 too (provided that the diag pin and the JTAG pins still exist)

Revision as of 23:43, 5 January 2015

The Last Piece of the Puzzle

How

  • By enabling diagnostic mode on the ps3, we can enable the use of JTAG again (it's temporarily disabled when diag mode isn't set)
  • It is possible to dump the syscon firmware using this method (in unencrypted state)
  • The JTAG registers/TAP-controllers need to be bruteforced / reverse engineered
  • The leaked service manuals present information about the pins connected to the JigPin
  • The ObjectiveSuite contains an object (DIAGSERVICE) used to diagnose the ps3 using JTAG
  • Using a DIY JigPin would facilitate the task, but we still need more info about the hardware and software interface used by ObjectiveSuite to handle this.
  • This would probably work on ps4 too (provided that the diag pin and the JTAG pins still exist)