To much of a coincidence!

[bigade1]

Dunno if this will help anyone but luckily I got mine back working. Not sure if I can remember the exact procedure though but I'll try. I'll relate my experience starting from the beginning ( apologies in advance for the long post ). I've been using the lan tool successfully for months to update both my firmware and channel lists on my F5S without any problems. Anyway, 2 days ago after installing my cccam.cfg via the lan tool I experienced the symptoms of the original poster i.e. with the lnb connected the picture and banner would display for approx. ten seconds then freeze - only way for the box to work was disconnecting the lnb. While the lnb was disconnected I restored a backup of the original firmware after factory resetting and deleting ALL files and channel lists, tried 3 different satellite feeds and even tried it at a neighbour's but all to no avail. I was pretty certain it must be a hardware issue and took the box apart to see if I could spot anything obvious such as a dry joint etc but I didn't notice anything out of place. Anyway, I thought I'd give it another go by trying a different firmware and some of my backup files. If I remember correctly this is what I did. I disconnected the lnb and rebooted the box, I deleted the channel list and ALL files including cccam.cfg files and newcamd files and every other one - I also done a factory reset and I then installed the firmware dated 21-08-13 instead of my original backup firmware. I then done another factory reset and for some reason decided to install a backup of my original cccam.cfg file ( which was an empty file incidentally ) and also installed a backup of my original channel list ( which was obviously out of date ) done a factory reset again, altered time settings, switched box off, connected lnb, switched box back on and for some reason the freeze had gone. I then thought I'd take a chance and update the firmware back to the latest one and also updated the channel list and by luck, it's back to normal. All the updates were done by lan btw. In conclusion, the issue must be a firmware one and not a hardware one as I previously thought. I'm not sure if the firmware I used made any difference as I suspect that the issue lies with the lan tool and the cccam.cfg file. I know for a fact that when I do a backup of that particular file and then I open it the backup process has made it become slightly corrupted. I think that installing the file by lan causes the issue and it could be that all is needed to do was to delete all those files and to install a newly made blank cccam.cfg file. I'm not going to try it out as my box is now working again. Anyway, I hope the info included in this post is helpful to someone.

[Sajon]

i tryed siging up on that website but its says
An Error Has Occurred!

[picoman]

Yes, GeorgeAlf, please go to the libertview forum and make a post in the thread entitled "Skybox F5S Crashing Issue"

The more we have complaining there the better, and they may eventually get a fix for us!

[sailsy]

Please make a post at developers forum libertview who reckon they working on it!

[GeorgeAlf]

Same here. Tried all firmware reflashes via rs232 ,different feeds etc even reflash via lan tool again .Same problem

[Sajon]

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

[sailsy]

ok will do

[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]

Hope you do it!

[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.

[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]

@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]

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.

[sailsy]

Thanks will try tomorrow!

[slugworth]

m3601e loader

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