User talk:Sandungas
.jpg)
My To Do wiki pages
To fill (by me :P)... list of pages i started or i helped improving them but are not finished yet, with a temporal layout, needs a cleanup, or abandoned temporally for some reason.
PARAM.SFO
Neverending oddisey
PARAM.PFD
Dunno how
ETC...
I will make a better list when i find some time, sorry
- About changes in CXML decompiler: yes, correct.
--Flatz (talk) 16:26, 17 November 2014 (EST)
Dev_flash\vsh\resource\sysconf\calibration
| Filename | Version | Size | MD5 | Remarks |
|---|---|---|---|---|
 01.png |
3.40-4.91 | 46611 | c08832aa1fdeecf8bf95986d22766a31 | |
 02.png |
3.40-4.91 | 10766 | 35859247d2b3548c879d805e6d2b80e8 | |
 03.png |
3.40-4.91 | 45806 | 9e0b454ee894bfe9052279f08e2c68c4 | |
 04.png |
3.40-4.91 | 12972 | 098ee01d7a75c454349e649e954078b5 | |
 05.png |
3.40-4.91 | 20260 | 0ab33e75f1bc9effdf9afbcfc0dee048 | |
 06.png |
3.40-4.91 | 10045 | d02dfdb83292014ac3a0fab819f3ef8d | |
 07.png |
3.40-4.91 | 21912 | c7130cf54ccd5ec99c48923f60899f91 | |
 08.png |
3.40-4.91 | 13720 | b3615e8f13f1e8982508d53b07a1a4b6 | |
 09.png |
3.40-4.91 | 21264 | e536ea25f671416ba8863d7f5931c601 | |
 10.png |
3.40-4.91 | 14383 | 14d88c0a31dd1247485d31885f60345b | |
 11.png |
3.40-4.91 | 21600 | 31d8666d65f21f96c47327a9ee8ecf96 | |
 line.png |
3.40-4.91 | 12793 | f8c8a41f6a1d751fb017dce627ea8383 |
Note: no variants
is not yet on an article page?
Dev_flash\vsh\resource\explore\user
| Filename | Version | Size | MD5 | Remarks |
|---|---|---|---|---|
 000.png |
1.00-4.91 | 8732 | 782383150fe84e4860d26114bc84eac6 | |
 001.png |
1.00-4.91 | 8692 | 89c5f403c53f58599c99b3fa8c09f0c5 | |
 002.png |
1.00-4.91 | 8314 | 5e4d7d44fa2ac8f1467abdd01680beb5 | |
 003.png |
1.00-4.91 | 7599 | eb32cd2ec540958a809186e1dae626e8 | |
 004.png |
1.00-4.91 | 9590 | 0dda6f66eb49006dda8d8b5f64721fd7 | |
 005.png |
1.00-4.91 | 10141 | a682913b618dfa18fa858e3220096189 | |
 006.png |
1.00-4.91 | 9761 | 08d2e916bb6c3cf1131f5dc0db8bd873 | |
 007.png |
1.00-4.91 | 10818 | 8c3fd52c7060cb9b7f1630e7a8244452 | |
 008.png |
1.00-4.91 | 10013 | ad647ab5f7a3a7654d69073d57e2df19 | |
 009.png |
1.00-4.91 | 2297 | 2979b1a3f321453f8dd32b87d6af26ae | |
 010.png |
1.00-4.91 | 2784 | 97b1383a45b127f4b961a41e46725763 | |
 011.png |
1.00-4.91 | 4138 | 3bbbf0ab68a1f6319a802f9c4413c3b8 | |
 012.png |
1.00-4.91 | 3063 | 4c2a7f17c0ec6d5919168591a6ea6116 | |
 013.png |
1.00-4.91 | 3489 | e2a625b8e3229b4fd3d8cf98a4bd164b | |
 014.png |
1.00-4.91 | 3162 | 28ff7495ce9da4026766d88e9a9105da | |
 015.png |
1.00-4.91 | 3388 | 1cfac53ebec607ba2b559203f6d79eea | |
 016.png |
1.00-4.91 | 4305 | 3b7642247edcc4a1bc3ac999f20be729 | |
 017.png |
1.00-4.91 | 3920 | 72ed5f6e7ad644fc26865dd589b71fa7 | |
 018.png |
1.00-4.91 | 16597 | 267fc9f686987fb329c5494907941d8f | |
 019.png |
1.00-4.91 | 17617 | 0f9efaef8626de4baac4e850ff43e494 | |
 020.png |
1.00-4.91 | 16912 | 91304828046ef81a769911417ef8de27 | |
 021.png |
1.00-4.91 | 16595 | 37ca85996c2f0c3d9d4310882fb9f9bb | |
 022.png |
1.00-4.91 | 18742 | 0e801b22adc8e7e4262490c6f1a1eda4 | |
 023.png |
1.00-4.91 | 18387 | 115cd081bea9622f1105210bf4857124 | |
 024.png |
1.00-4.91 | 18016 | 9a2597dee82c144375ae95630c554fc3 | |
 025.png |
1.00-4.91 | 18551 | 5d729a8ac9f052135393434cf5d16b70 | |
 026.png |
1.00-4.91 | 17346 | d72fd0c1a810ce6138e314010f15795b |
Note: no variants
is not yet on an article page
Users suggestions, brainstormings, help, etc...
HDD regions table
ps3dd HDD region is between 8 sectors of padding, in the space leaved empty by resizing ps3da, see how: http://gitorious.ps3dev.net/ps3otheros/scripts/blobs/master/create_hdd_region.sh
The script is a facility to create a next region on free (from regions) space on HDD, with GameOS rights: same script for ALL models, it needs new drivers and new ps3sed.
ps3disk sb_03: accessible region 0 start 0 size 1250263728 //ps3da ps3disk sb_03: accessible region 1 start 32 size 1212515008 //ps3db ps3disk sb_03: accessible region 2 start 1212515040 size 4194296 //ps3dc ps3disk sb_03: accessible region 3 start 1216709344 size 33554376 //ps3dd ps3disk sb_03: ps3stor_probe_access:132: 4 accessible regions found 32 + 1212515008 = 1212515040 //ps3db end sector 1212515040 + 4194296 = 1216709336 //ps3dc end sector 1216709344 - 1216709336 = 8 //ps3dd begin pad 1216709344 + 33554376 = 1250263720 //ps3dd end sector 1250263728 - 1250263720 = 8 //ps3dd ending pad note: no gap between GameOS regions
- I added the padding you point of 0x8 sectors at the end of the table, and i also added some notes out of the table about the differences of padding between official layout and other methods (and maybe differences between NAND/NOR models)... is hard to know or represent in the table because there are differeces in the info people posted (included your displacement of 0x20 sectors before ps3db in your NAND console, that doesnt seems to match the total displacement of 0x18 sectors in graf NOR notes). By now for me this "small" problem with innacurate paddings in the table is fine (no idea if can be solved by modding an script of driver config), overall it looks the whole hdd is mapped so i finished with the table by now, the most important think to know about this areas out of the regions was to be sure if are padding (not other important data) --Sandungas (talk) 19:00, 1 April 2014 (EDT)
This table is copyed from: Hypervisor_Reverse_Engineering#HDD_device (i added the grey rows and usage column). The console was a NOR model (because it has vflash region) and in a firmware under 3.21 (because it has otheros region)
| Region Index | Start sector | Number of sectors | Usage |
|---|---|---|---|
| 0 | 0x0 | 0x950F8B0 | whole hdd |
| 0x8 | HDD Partition table | ||
| 1 | 0x8 | 0x80000 | vflash |
| 0x10 | Padding ? (0x80018 - 0x80000 - 0x8 = 0x10) | ||
| 2 | 0x80018 | 0x7C8F898 | gameos |
| 0x8 | Padding (0x7D0F8B8 - 0x7C8F898 - 0x80018 = 0x8) | ||
| 3 | 0x7D0F8B8 | 0x3FFFF8 | gameos cache |
| 0x8 | Padding (0x810F8B8 - 0x3FFFF8 - 0x7D0F8B8 = 0x8) | ||
| 4 | 0x810F8B8 | 0x13FFFF8 | otheros |
| 5 | - | - | - |
| 6 | - | - | - |
| 7 | - | - | - |
HSW-001 pinout
please check this if you have a chance Zer0Tolerance, on CECH-25xx the BD controller is integrated and it seems the blue eject led is connected to it --Sandungas (talk) 15:55, 20 June 2015 (UTC)
Verifyed, pin36 @CXD5131R-1 is correct pin. Now we need to trace it on JTP-001 (@Renesas chip)
I cant check a JTP-001 at this moment, by now im assuming the CXD5131R-1 and the renesas R8J32830FPV1 has the same pinout and internally are exactly the same, actually i have a partial theory about why there are renesas BD controllers used in some PS3 models. It seems when sony is going to redesign the BD controller they uses renesas for the first prototype (though renesas chip reaches production line). Or maybe is the opposite, first sony redesigns the BD controller and then they passes the manufacturing license to renesas for building it cheaper, to reduce taxes or something like that. One way or the other it seems renesas BD controllers works exactly the same as sony BD controllers --Sandungas (talk) 15:55, 20 June 2015 (UTC)
Components
D35653 0S25
Next to NOR, on top of the board JSD-001, responsible of the NOR VCC
| Pin | Signal | Description |
|---|---|---|
| 1 | V_OUT | NOR VCC 3.3v |
| 2 | GROUND | |
| 3 | GROUND | |
| 4 | Goes to capacitor (4nf ?), then to ground | |
| 5 | To a sinkhole, hidden trace in inner layers (control pin ?) | |
| 6 | GROUND | |
| 7 | GROUND | |
| 8 | V_IN | to BD3527 0A95 pin 11, to BD3525 0938 pin 11 |
BD3525
| Pin | Signal | Description |
|---|---|---|
| 1 | GROUND | |
| 2 | GROUND | |
| 3 | GROUND | |
| 4 | GROUND | |
| 5 | GROUND | |
| 6 | GROUND | |
| 7 | control pin ? | |
| 8 | ? | capacitor to ground |
| 9 | GROUND | |
| 10 | GROUND | |
| 11 | V_IN | to D35653 0S25 pin 8, to BD3527 0A95 pin 11 |
| 12 | ? | to resistor 46Kohm to ground |
| 13 | ? | to capacitor 0.500nf to ground |
| 14 | GROUND | |
| 15 | GROUND | |
| 16 | GROUND | |
| 17 | GROUND | |
| 18 | GROUND | |
| 19 | GROUND | |
| 20 | GROUND |
BD3527
| Pin | Signal | Description |
|---|---|---|
| 1 | GROUND | |
| 2 | GROUND | |
| 3 | GROUND | |
| 4 | GROUND | |
| 5 | GROUND | |
| 6 | GROUND | |
| 7 | control pin ? | |
| 8 | ? | power |
| 9 | ? | dissapears under package |
| 10 | ? | dissapears under package |
| 11 | V_IN | to D35653 0S25 pin 8, to BD3525 0938 pin 11 |
| 12 | ? | dissapears in a sinkhole (resistor 23Kohm to ground in the other side) |
| 13 | ? | dissapears in a sinkhole (capacitor 915nf to ground in the other side) |
| 14 | GROUND | |
| 15 | GROUND | |
| 16 | GROUND | |
| 17 | GROUND | |
| 18 | GROUND | |
| 19 | GROUND | |
| 20 | GROUND |
BD9684 0906
| Pin | Signal | Description |
|---|---|---|
| 1 | ? | sealed coil... then ? |
| 2 | ? | dissapears under package |
| 3 | V_IN | ------------- connected to the common rail with the previous ones |
| 4 | ? | to a sinkhole |
| 5 | GROUND | |
| 6 | GROUND | |
| 7 | dissapears under package | |
| 8 | V_IN | ----------- connected to the common rail with the previous ones |
| 9 | ? | dissapears under package |
| 10 | ? | sealed coil... then ? |
| 11 | ? | to other side of sealed coil at pin 10... then... ??? (power rail) |
| 12 | ? | tied to pin 13... missing in a 4x-sinkhole (power rail) |
| 13 | ? | tied to pin 12... missing in a 4x-sinkhole (power rail) |
| 14 | GROUND | |
| 15 | ? | to a sinkhole |
| 16 | ? | dissapears under package |
| 17 | V_IN | ----------- connected to the common rail with the previous ones |
| 18 | ? | towards blu ray laser connector |
| 19 | ? | dissapears under package |
| 20 | ? | to a sinkhole |