To much of a coincidence!

[picoman]

I've just found this thread.
I'm yet another one with a Libertview F3s with exactly the same problem. ie after changing a cfg file with the LAN tool, the box crashes after a few seconds when the LNB cable is connected. I've also tried every possible combination of fixes with no result. BTW, as others have already stated, there is nothing wrong at all with the LNB cable.

There must be some way to fix this?

[sailsy]

As of yet still not fixed haven't tried at another house yet because not convinced but will do had plenty of f5s connected here no problem!

There must be a fix???

[picoman]

I've been studying how the eromupgrade tool works. The config.bat needs to be run to copy the correct data into the sdram.ini and eromclient.abs files.

To do this the cmd line must be

config.bat [platform_type]

where [platform_type] defines the processor and the memory size

eg "64M_SF_M3602" or "128M_SF_M3606" etc

The problem is, the F3s is a 3601 with 128M DDR. [Is the F5s the same?]
There are no configuration files that match this in all the "rs232 upgrade" packages I've downloaded.

The nearest is "ddram_128M_32bit_M3602.ini"

I believe 3602 is not compatible with 3601

I'll keep looking!

[picoman]

@sailsy
I'm certain another house/LNB/dish/cable will make NO difference whatsoever for you.
I've already tried it.

[sailsy]

Yeah I know was working fine before im sure there must be a fix for this it's as if there something left in system that messing it up!

[slugworth]

m3601e loader

m3601e loader I found.
notice the eromclient.abs and sdram.ini files are different than the usual ones.

[sailsy]

Thanks will try tomorrow!

[slugworth]

that was the only one that mentioned the m3601e for the sdram.ini file batch file,but it was for 64m and not 128m size ram.

[picoman]

@slugworth
Thanks for the files. They load fine but unfortunately with the same result. I get a picture for about 30s, the remote is unresponsive and then there is a complete crash.

In the upgrade packages I've seen the 3601E looks like it has 64M DDRAM
"For 64M 16bit DDRAM,Serial Flash Platform M3601E: config.bat 64M_SF_M3601E"

and the F3s has 128M.

However, as you stated, in the package you uploaded the eromclient.abs is different from the usual eromclient_M3601E.abs, but the sdram.ini is identical to ddr_M3601E_64M.ini.


I think perhaps what we need is the correct configuration for "ddr_M3601E_128M.ini" which I've not seen anywhere.

Having said that, the only difference betweeen the 128M and 64M ini files is this line (respectively).

Cmd36=ww 0xb8001000 0x569A40c3
Cmd36=ww 0xb8001000 0x569A40c2

I guess this is the address and data.

I'll patch the 64M ini file to the 128M data and have another try.

EDIT
@slugworth
You posted re the 64/128M ram size issue whilst I was composing my post!

EDIT2
Patching the 128m data to the ini file does not work. Exactly, the same result.

[slugworth]

but the 128m data size ini is based on the m3606 processor,if you trace the history of the original ini files.
I saw more differences than what you posted.
A moot point unless you have a receiver that is bricked and won't load any firmware.

[picoman]

Yes, I used the ddr_128M_M3606.ini as the comparison as that is the one that works for the F3s boxes.

However, no matter. Whatever is causing the crash in these affected boxes, is certainly not fixed by uploading new firmware.

Another mode of attack needs to be found.

[sailsy]

Hope you do it!

[picoman]

A thread about this problem has been started on the LibertView support forum.

It may help if those with the same problem post there too.

.......................

[sailsy]

ok will do

[Sajon]

any updates i am sitting with a dead box cant watch tv :/