Editing Talk:Syscon Error Codes

== UART Samples ==
https://www.psx-place.com/threads/fault-finding-ylod-with-the-syscon-first-steps-and-error-reporting.30100/page-127#post-324377

*In the sample below:
**The oldest errorcode is located at offset 112
**The newest errorcode is located at offset 104
**The errorcode FFFFFFFF at offset 108 is a mark indicating the errorlog has been looped (is not an error, and the associated timestamp is not valid, the timestamp 2013/02/23 05:54:19 is garbage)
**The next errorcode will be stored at offset 108, and the loop mark will be moved to 112 overwriting the oldest errorcode but not overwriting the oldest timestamp (so it will inherit the timestamp 2013/06/09 06:43:04 as garbage)
**When the errorcodes from offsets 112, 116, 120, 124, 0, 4, 8, 12 was triggered (orderd from old to new) the battery was present and the date and time was correctly configured under GameOS
**When the errorcodes from offsets 16, 20, 24, 28, 32, 36, 40, 44, 48 was triggered (orderd from old to new) the battery was not present
**When the errorcodes from offsets 52, 56, 60, 64, 68, 72, 76, 80, 84, 88, 92, 96, 100 was triggered (orderd from old to new) the battery was present, but the date and time was not correctly configured under GameOS
**When the errorcode from offset 104 was triggered the battery was not present
**This errorlog was close to complete his second loop (the second loop is completed after the loop mark overwrites a valid errorcode at offset 124), it had at least 59 errorcodes and is missing 5 more to complete 2 loops
<pre>
>$ errlog
errlog
ofst[108]:err_code:0xffffffff, clock:0x18bb160b  2013/02/23 05:54:19 <-- loop mark with a garbage timestamp
ofst[112]:err_code:0xa0801701, clock:0x1946e078  2013/06/09 06:43:04 <-- battery was present and date and time configured (oldest errorcode)
ofst[116]:err_code:0xa0801601, clock:0x1946e078  2013/06/09 06:43:04 <-- battery was present and date and time configured
ofst[120]:err_code:0xa0404412, clock:0x19496d29  2013/06/11 05:07:53 <-- battery was present and date and time configured
ofst[124]:err_code:0xa0403034, clock:0x19496d29  2013/06/11 05:07:53 <-- battery was present and date and time configured
ofst[  0]:err_code:0xa0404412, clock:0x19496d40  2013/06/11 05:08:16 <-- battery was present and date and time configured
ofst[  4]:err_code:0xa0403034, clock:0x19496d40  2013/06/11 05:08:16 <-- battery was present and date and time configured
ofst[  8]:err_code:0xa0801701, clock:0x194be6c6  2013/06/13 02:11:18 <-- battery was present and date and time configured
ofst[ 12]:err_code:0xa0801601, clock:0x194be6c6  2013/06/13 02:11:18 <-- battery was present and date and time configured
ofst[ 16]:err_code:0xa0404412, clock:0xffffffff                      <-- battery was removed, invalid timestamp
ofst[ 20]:err_code:0xa0403034, clock:0xffffffff                      <-- battery was removed, invalid timestamp
ofst[ 24]:err_code:0xa0902120, clock:0xffffffff                      <-- battery was removed, invalid timestamp
ofst[ 28]:err_code:0xa0404412, clock:0xffffffff                      <-- battery was removed, invalid timestamp
ofst[ 32]:err_code:0xa0403034, clock:0xffffffff                      <-- battery was removed, invalid timestamp
ofst[ 36]:err_code:0xa0404412, clock:0xffffffff                      <-- battery was removed, invalid timestamp
ofst[ 40]:err_code:0xa0403034, clock:0xffffffff                      <-- battery was removed, invalid timestamp
ofst[ 44]:err_code:0xa0404412, clock:0xffffffff                      <-- battery was removed, invalid timestamp
ofst[ 48]:err_code:0xa0403034, clock:0xffffffff                      <-- battery was removed, invalid timestamp
ofst[ 52]:err_code:0xa0801701, clock:0x0b48869c  2005/12/31 00:00:28 <-- battery was present, but date and time was not configured, error triggered 28 seconds after inserting the battery
ofst[ 56]:err_code:0xa0801601, clock:0x0b48869c  2005/12/31 00:00:28 <-- battery was present, but date and time was not configured, error triggered 28 seconds after inserting the battery
ofst[ 60]:err_code:0xa0404412, clock:0x0b4888cd  2005/12/31 00:09:49 <-- battery was present, but date and time was not configured
ofst[ 64]:err_code:0xa0403034, clock:0x0b4888cd  2005/12/31 00:09:49 <-- battery was present, but date and time was not configured
ofst[ 68]:err_code:0xa0404412, clock:0x0b97ec4c  2006/03/01 05:23:24 <-- battery was present, but date and time was not configured
ofst[ 72]:err_code:0xa0403034, clock:0x0b97ec4c  2006/03/01 05:23:24 <-- battery was present, but date and time was not configured
ofst[ 76]:err_code:0xa0404412, clock:0x0b9812ad  2006/03/01 08:07:09 <-- battery was present, but date and time was not configured
ofst[ 80]:err_code:0xa0403034, clock:0x0b9812ad  2006/03/01 08:07:09 <-- battery was present, but date and time was not configured
ofst[ 84]:err_code:0xa0404412, clock:0x0b9a653d  2006/03/03 02:23:57 <-- battery was present, but date and time was not configured
ofst[ 88]:err_code:0xa0403034, clock:0x0b9a653d  2006/03/03 02:23:57 <-- battery was present, but date and time was not configured
ofst[ 92]:err_code:0xa0404412, clock:0x0b9a654e  2006/03/03 02:24:14 <-- battery was present, but date and time was not configured
ofst[ 96]:err_code:0xa0403034, clock:0x0b9a654e  2006/03/03 02:24:14 <-- battery was present, but date and time was not configured
ofst[100]:err_code:0xa0902120, clock:0x0b9a654e  2006/03/03 02:24:14 <-- battery was present, but date and time was not configured
ofst[104]:err_code:0xa0901001, clock:0xffffffff                      <-- battery was removed, invalid timestamp (newest errorcode)
</pre>

*In the sample below:
**After using the command '''clearerrlog''' the errolog is emptyed (completly filled with FF), and the newest error is stored at relative offset 0 (at most top of the errorlog structure, but displayed at bottom by the comand errlog)
**There is no loop mark because there is only 1 errorcode, but syscon considers the first errorcode found with value FFFFFFFF while reading the errorlog structure from top to bottom is the loop mark (so the next errorcode at offset 8 is considered the oldest)
**The next errorcode will be stored at offset 4, and the loop mark will be considered the errorcode FFFFFFFF at offset 8
**When the errorcode from offset 0 was triggered the battery was present, but the date and time was not correctly configured under GameOS (so the date and time is automatically configured around 2005/12/31 00:00:00)
<pre>
>$ errlog
errlog
ofst[  4]:err_code:0xffffffff, clock:0xffffffff
ofst[  8]:err_code:0xffffffff, clock:0xffffffff
ofst[ 12]:err_code:0xffffffff, clock:0xffffffff
ofst[ 16]:err_code:0xffffffff, clock:0xffffffff
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:0xa0801200, clock:0x0b488687  2005/12/31 00:00:07 <-- it seems the error was triggered 7 seconds after inserting the battery :D
</pre>