Page 8 of 12

Re: Forced "toggle" to repair bricked TV?

Posted: Sun Dec 16, 2012 9:53 am
by juusso
I can`t find 24C256 Debug Menu on D series. What is exact path to it on your TV?

Re: Forced "toggle" to repair bricked TV?

Posted: Sun Dec 16, 2012 10:28 am
by oga83
E3V3A wrote:It seems that it can be called from TDM, as it contain a TDM style menu
I don't have the eeprom utility on my BD, but I have a similar TDM submenu. However, it is for the config eeprom, not the Micom's one

Re: Forced "toggle" to repair bricked TV?

Posted: Sun Dec 16, 2012 6:40 pm
by juusso
Interesting - eeprom cleaner is specially designed for E series only or it could be "back-used" on D series.

Re: Forced "toggle" to repair bricked TV?

Posted: Sun Dec 16, 2012 7:26 pm
by E3V3A
I don't know what is the TDM path to get to this. If its even possible...
Also the binary is called through a shell script, selecting for X9 and X10, so I don't know what EEPROM they really refer to.

Code: Select all

577fbcc t_ResetSubMicomEEPROM
57802a8 Control Type is [FACTORY_CTRL_EEPROM_COPY_MAIN_TO_DMD]
5782249  <<<< FOR SUB_MCM's EEPROM >>> id: [%d], name: [%s] value: [%d]
57829a4 ReWrite EEprom data!!!!!
57832e0 t_FAnetWriteEEPROM
57832f4 t_FAnetReadEEPROM
Etc etc.. look inside.

Re: Forced "toggle" to repair bricked TV?

Posted: Wed Dec 19, 2012 10:17 pm
by oga83
juuso wrote:Ordered arduino uno + ethernet shield 1.1
Did you receive it ?

Re: Forced "toggle" to repair bricked TV?

Posted: Thu Dec 20, 2012 5:24 am
by juusso
nah. it takes a while i guess...

Re: Forced "toggle" to repair bricked TV?

Posted: Tue Jan 01, 2013 11:43 pm
by E3V3A
ping! ...someone should start importing these things in that country, so you don't have to wait so long...

Re: Forced "toggle" to repair bricked TV?

Posted: Wed Jan 09, 2013 4:00 pm
by juusso
Some first results of bricked board:

Code: Select all

0000: FF FF B0 77 00 FF 00 FF 00 00 02 00 FF 65 6E 67 FF 00 FF FF 01 C2 2B 02 6E FF B2 FF FF FF FF FF ...w.........eng......+.n.......
0020: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................................
0040: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................................
0060: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................................
0080: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................................
00a0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................................
00c0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................................
00e0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................................
Oliver, can be this is wrong chip? I connected to one, which is green marked...

Re: Forced "toggle" to repair bricked TV?

Posted: Wed Jan 09, 2013 4:40 pm
by oga83
juuso wrote:Oliver, can be this is wrong chip? I connected to one, which is green marked...
I'm quite sure it is the good one as it is connected to the micom processor.
Moreover, I think the language is 'eng' in your eeprom as it was 'fre' for me here. Not at the same place but my micom processor is different than yours (Renesas).

Re: Forced "toggle" to repair bricked TV?

Posted: Wed Jan 09, 2013 6:23 pm
by juusso
Compared dumps when made command toggle. Each timetwo bytes change:
(code removed, messed something with logs :))

Have to repeat all tests, completelly lost in logs. They are identic independent of what boot partition is selected. Just two times i got changing between toggling partitions: at address 0x03 (or is it 0x23, because of additional first line in rw mode?) (AD->B0->AD) and 00->02->00 at address 0x18.

Further testing on this Friday.