thanks for the quick response i have a cechj system and i also have a slim so not really worth trying to fix the nec/tokins for me might just keep it in the closet and one day if i get bored ill have a go at fixing it.. thanks for the help
Yeah, non-BC models are cheap. No sense spending more to fix it than to replace it.
becount
Bringup : 1776 times
Shutdown: 1760 times
Power-on: 70day 19hour 07min 26sec
Well this still doesn't replace the proper serial connection with the adapter as you say... Not just because of requiring CFW but mostly because it requires the system to be powered on and working properly in the first place hehe.
The E model was released in August of 2007 in NA, so you're mixed up on the date. Maybe you got it in 2008?
The PS3 firmware starts counting the time at 1st January 1970, the Syscon at 1st January 2000. I just add a fixed offsets to it. I didn't add any time zone handling to it, that's why some values might be off. Doing that would require much more work and I don't think it's worth the time. Syscon is doing some weird stuff with the RTC. For some errors Syscon sets the time to -1 which then corresponds to the last second in 1999.
Prototype consoles still have the "diag rtc_set YYMMDDhhmmssddHHS" command but that was removed before the retail release.
It says CokB10 so it's at least based on a COK-002. (see https://www.psdevwiki.com/ps3/Chassis_ID)
Ahh, to be honest I didn't even notice that haha.
Yes, the translation between the data shown to you via UART and the one which Syscon gives to CELL is also different, so it's hard to replicate the UART output 1:1.
It actually resets to 2000 and Syscon adds the 6 year offset - weird since they used the same syscon since 2004 which means they had to change the offset 2 times. I guess they did that because the PS2 Mechacon is based on the same architecture.
The official RTC set procedure which is done at the factory is part of the Syscon Remarry process. You can also do that if you skip the "First blank the complete SPCR with hex FF. Then for the first 0x30 bytes write this:" step of "Case #2" on the https://www.psdevwiki.com/ps3/Remarry_Syscon guide.
), from the thermal sensor to the SYSCON chip are of different values(one for 3000ohm and the other is 2400ohm), which is weird but should be okay if they're just pull ups? From the service manual they should be both 3300ohm(R4083 & R4084)
You can't trust the multimeter reading for resistors in circuit. You'd have to remove them first. Parasitic resistance from other components in the line can make it appear off. However, you can compare the relative resistance from a working board to know if it's ballpark. It it's just a pull up resistor, the all that matters is it's higher than the threshold voltage (which we don't really know). 2400ohms isn't far off from 3300. I suspect it's fine. I would be more worried about shorts or open lines.For now, the only thing I can tell is the two pull up resistors of the SMBus/I2C SCL/SDA line(THR_I2C_SCL and THR_I2C_SDA from the service manual of SEM-001, I know it's of different model
You'd need an oscilloscope to see the I2C data signal from the RSX. If there's no data, there could be a break in the line. However, a multimeter would just see a voltage, it's not fast enough to see the pulses. A lack of voltage might be meaningful, I'm not sure. I imagine if it can't send data, it'd be low all the time. So that might be a way to see it.
Do you mean the schematics and voltage pictures stored on @vyktormvmpay25's share drive? Sometimes I get an HTTPS isn't available error, but it's fine if I ignore that. At least from the USA. IDK, maybe his share drive is blocked in your region. If so, VPN is your friend.
Oh, that'll go away once you hit like 10 or so posts. It's some new user rule. You'll also be able to directly attach pictures then.
Here's something wierd. The SYSCON just keeps spitting out 2006 dates for me when the clock on console is set by the internet and correct. They should be reading 2021 on the errors I was getting in the last couple days and was talking about in my previous post.
errlog
ofst[ 20]:err_code:0xffffffff, clock:0xffffffff
ofst[ 24]:err_code:0xffffffff, clock:0xffffffff
ofst[ 28]:err_code:0xffffffff, clock:0xffffffff
ofst[ 32]:err_code:0xffffffff, clock:0xffffffff
ofst[ 36]:err_code:0xffffffff, clock:0xffffffff
ofst[ 40]:err_code:0xffffffff, clock:0xffffffff
ofst[ 44]:err_code:0xffffffff, clock:0xffffffff
ofst[ 48]:err_code:0xffffffff, clock:0xffffffff
ofst[ 52]:err_code:0xffffffff, clock:0xffffffff
ofst[ 56]:err_code:0xffffffff, clock:0xffffffff
ofst[ 60]:err_code:0xffffffff, clock:0xffffffff
ofst[ 64]:err_code:0xffffffff, clock:0xffffffff
ofst[ 68]:err_code:0xffffffff, clock:0xffffffff
ofst[ 72]:err_code:0xffffffff, clock:0xffffffff
ofst[ 76]:err_code:0xffffffff, clock:0xffffffff
ofst[ 80]:err_code:0xffffffff, clock:0xffffffff
ofst[ 84]:err_code:0xffffffff, clock:0xffffffff
ofst[ 88]:err_code:0xffffffff, clock:0xffffffff
ofst[ 92]:err_code:0xffffffff, clock:0xffffffff
ofst[ 96]:err_code:0xffffffff, clock:0xffffffff
ofst[100]:err_code:0xffffffff, clock:0xffffffff
ofst[104]:err_code:0xffffffff, clock:0xffffffff
ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xffffffff, clock:0xffffffff
ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xffffffff, clock:0xffffffff
ofst[124]:err_code:0xffffffff, clock:0xffffffff
ofst[ 0]:err_code:0xa0801001, clock:0x0be47303 2006/04/28 06:30:27
ofst[ 4]:err_code:0xa0801001, clock:0x0be47416 2006/04/28 06:35:02
ofst[ 8]:err_code:0xa0801001, clock:0x0be47bc1 2006/04/28 07:07:45
ofst[ 12]:err_code:0xa0801001, clock:0x0be47cc3 2006/04/28 07:12:03
ofst[ 16]:err_code:0xa0801001, clock:0x0be4a0af 2006/04/28 09:45:19
[mullion]$
>$Firmware Version: 4.88 (50731)
Platform ID: Cok14
Hardware Config: 00000000FFFFFFFF
Syscon Fimware Version: 0B8E.0001000000000006 (0001000000000006)
Bringup Count: 1755, Shutdown Count: 714
Runtime: 11 Days, 15 Hours, 20 Minutes, 26 Seconds
Error Log
01: A0801001 Fri Apr 28 09:45:19 2006
02: A0801001 Fri Apr 28 07:12:03 2006
03: A0801001 Fri Apr 28 07:07:45 2006
04: A0801001 Fri Apr 28 06:35:02 2006
05: A0801001 Fri Apr 28 06:30:27 2006
06: FFFFFFFF Fri Dec 31 23:59:59 1999
07: FFFFFFFF Fri Dec 31 23:59:59 1999
08: FFFFFFFF Fri Dec 31 23:59:59 1999
09: FFFFFFFF Fri Dec 31 23:59:59 1999
10: FFFFFFFF Fri Dec 31 23:59:59 1999
11: FFFFFFFF Fri Dec 31 23:59:59 1999
12: FFFFFFFF Fri Dec 31 23:59:59 1999
13: FFFFFFFF Fri Dec 31 23:59:59 1999
14: FFFFFFFF Fri Dec 31 23:59:59 1999
15: FFFFFFFF Fri Dec 31 23:59:59 1999
16: FFFFFFFF Fri Dec 31 23:59:59 1999
17: FFFFFFFF Fri Dec 31 23:59:59 1999
18: FFFFFFFF Fri Dec 31 23:59:59 1999
19: FFFFFFFF Fri Dec 31 23:59:59 1999
20: FFFFFFFF Fri Dec 31 23:59:59 1999
21: FFFFFFFF Fri Dec 31 23:59:59 1999
22: FFFFFFFF Fri Dec 31 23:59:59 1999
23: FFFFFFFF Fri Dec 31 23:59:59 1999
24: FFFFFFFF Fri Dec 31 23:59:59 1999
25: FFFFFFFF Fri Dec 31 23:59:59 1999
26: FFFFFFFF Fri Dec 31 23:59:59 1999
27: FFFFFFFF Fri Dec 31 23:59:59 1999
28: FFFFFFFF Fri Dec 31 23:59:59 1999
29: FFFFFFFF Fri Dec 31 23:59:59 1999
30: FFFFFFFF Fri Dec 31 23:59:59 1999
31: FFFFFFFF Fri Dec 31 23:59:59 1999
32: FFFFFFFF Fri Dec 31 23:59:59 1999
