SamyGO

Sorry, can`t see what`s is written on chips. Could you mark chip, labeled "Weltrend" ? And next to it - 8 pin chip, labeled ATML...(any letters/digits). Is that those? (check photo). The big one is Weltrend, i can see on other photos found on google, now that about small one? Label? Here is no visble pads on the back side right under those chips, but i see really similar to mine 3 pins (red marked): I wonder if those can have connection to small 8-pin chip, it is far enough, but what if?

p.s. seems three pads on second photo are right under SPD1005. Anyway, take multimeter and check pls.

juuso wrote:Sorry, can`t see what`s is written on chips. Could you mark chip, labeled "Weltrend" ? And next to it - 8 pin chip, labeled ATML...(any letters/digits). Is that those? (check photo). The big one is Weltrend, i can see on other photos found on google, now that about small one? Label?

you are right, the small one is the ATML chip (ATMLH046)

Here is no visble pads on the back side right under those chips, but i see really similar to mine 3 pins (red marked):
I wonder if those can have connection to small 8-pin chip, it is far enough, but what if?

p.s. seems three pads on second photo are right under SPD1005. Anyway, take multimeter and check pls.

yes, those pads are for the SPD1005 and they are labeled A_SYNC, B_SYNC, C_SYNC so not related to micom. I will check some others with multimeter. I did find an SDA_NXC, and SDL_NXC right under this chip, any use?

No doubts ATMLH046 is required micom eeprom config. So now you just need to solder wires to i`ts pads 5-4-6 (SDA-SCL-WP) and get GND from some other place (or from pin 4 of that chip if you want, but there are much better places to get GND from ).

oh, arduino is needed as well.

p.s. duno about that chip and pads...

juuso wrote:No doubts ATMLH046 is required micom eeprom config. So now you just need to solder wires to i`ts pads 5-4-6 (SDA-SCL-WP) and get GND from some other place (or from pin 4 of that chip if you want, but there are much better places to get GND from ).

oh, arduino is needed as well.

p.s. duno about that chip and pads...

good, I will order the arduino-ethernet combo and give it a try.

prairie wrote:I did find an SDA_NXC, and SDL_NXC right under this chip,

SpoilerShow

This is Nexell chip (hardware video encoder, for Dual View/Smart View)

any use?

No, not really.

Micom EEPROM should read ATMLH046*02*; those three pads marked red by juuso are connected to it, most likely.

However, I'm not quite sure forced partition switching will have any useful impact for your bricked mainboard. Unless I'm very much mistaken, it will probably not help at all..

Looks like what you need is mtd_rwarea partition clean-up/reformat - but I don't have any useful ideas how to do it by any simple hardware hack[s].
In theory (just maybe): if you'll be somehow able to disrupt OneNAND <-> SoC communication in the VERY precise moment (to prevent initial /mtd_rwarea mounting in startup script), it may then get erased/reformated.

sbav1 wrote: However, I'm not quite sure forced partition switching will have any useful impact for your bricked mainboard.

Agree. This is other kind of brick. But AFAIK there is patched firmware on its bricked boards alternative partition and (must ask arris) hotplug is enabled. or not enabled?

juuso wrote:

sbav1 wrote: However, I'm not quite sure forced partition switching will have any useful impact for your bricked mainboard.

Agree. This is other kind of brick. But AFAIK there is patched firmware on its bricked boards alternative partition and (must ask arris) hotplug is enabled. or not enabled?

No, this was an early board and I think another stock FW is on alternate partition, but I will test just for fun. I already tried hotplug trick on active partition and no luck.

Full # of atmel chip is ATMLH046 02C M Y
065003A

sbav1 wrote:

prairie wrote:I did find an SDA_NXC, and SDL_NXC right under this chip,

SpoilerShow

This is Nexell chip (hardware video encoder, for Dual View/Smart View)

any use?

No, not really.

Micom EEPROM should read ATMLH046*02*; those three pads marked red by juuso are connected to it, most likely.

However, I'm not quite sure forced partition switching will have any useful impact for your bricked mainboard. Unless I'm very much mistaken, it will probably not help at all..

Looks like what you need is mtd_rwarea partition clean-up/reformat - but I don't have any useful ideas how to do it by any simple hardware hack[s].
In theory (just maybe): if you'll be somehow able to disrupt OneNAND <-> SoC communication in the VERY precise moment (to prevent initial /mtd_rwarea mounting in startup script), it may then get erased/reformated.

Probably this is right, the system remains on for only ~3 seconds before power cycle. Could the SoC I2C pads be used to do this kind of glitch?

Why are you sure your problem is some flag on mtd_rwarea? You`ll lose nothing (oh, exept arduino price..) if you check what happen if youtoggle partitions. Can be flash error or so dives your tv in bootloop.

I am sure it's the flag, I added it manually (stupid idea) to see what would happen. I will still try toggling though, as you say no loss.