[00:10:51] *** Quits: n1s (~n1s@rockbox/developer/n1s) (Quit: Ex-Chat) [01:04:30] *** Joins: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) [01:04:30] *** Quits: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) (Remote host closed the connection) [01:08:42] *** Joins: alberthrocks (~alberthro@pool-71-179-91-89.bltmmd.fios.verizon.net) [01:08:43] *** Quits: alberthrocks (~alberthro@pool-71-179-91-89.bltmmd.fios.verizon.net) (Changing host) [01:08:43] *** Joins: alberthrocks (~alberthro@unaffiliated/alberthrocks) [03:32:36] *** Joins: [Saint] (~saint@rockbox/user/saint) [03:50:00] *** Joins: [Saint_] (~saint@rockbox/user/saint) [03:50:33] *** Quits: [Saint] (~saint@rockbox/user/saint) (Ping timeout: 245 seconds) [04:00:37] *** [Saint_] is now known as [Saint] [06:41:46] *** Quits: TheSeven (~quassel@rockbox/developer/TheSeven) (Read error: Operation timed out) [06:42:35] *** Joins: TheSeven (~quassel@rockbox/developer/TheSeven) [07:05:09] *** Joins: clustur (~logger@68.53.250.91) [07:05:09] *** Quits: clustur (~logger@68.53.250.91) (Remote host closed the connection) [13:10:00] *** Joins: clustur (~logger@68.53.250.91) [13:10:04] *** Quits: clustur (~logger@68.53.250.91) (Read error: Connection reset by peer) [14:53:47] *** Parts: [Saint] (~saint@rockbox/user/saint) ("Part") [17:52:14] *** Joins: n1s (~n1s@nl118-168-30.student.uu.se) [17:52:14] *** Quits: n1s (~n1s@nl118-168-30.student.uu.se) (Changing host) [17:52:14] *** Joins: n1s (~n1s@rockbox/developer/n1s) [19:07:55] *** Joins: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) [19:07:55] *** Quits: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) (Remote host closed the connection) [20:10:43] *** Joins: liar (~liar@clnet-p09-185.ikbnet.co.at) [21:05:37] TheSeven: can you briefly explain what do i need in order to debug the OF booting issue on the classics? [22:53:52] user890104: edit the OF with a hex editor while looking at the disassembly, place crash/reboot and hang stubs somewhere at a safe memory location, probe various places for whether they're being reached [22:54:06] that's how I tracked it down to an I2C IRQ not arriving for some reason [22:54:56] might make sense to somehow capture the state of the i2c core during OF execution (if that's at all possible), and compare to the state when leaving emcore [22:55:09] could also be in the register space of the clock and power controller