[C-200] Firmware 03-04-110530-21-POP-408 (03-04-110520-21-POP-408 Apps) (3.06.2011)

[TeMpL]

(06-07-2011 07:39 AM)werner Wrote:  there won't be issues with later firmwares, because the difference with this build is that it needs to program the key which happens online, for which it needs memory which is used by the LTU package.

(06-07-2011 07:37 AM)tinnef Wrote:  That did the trick. Still I'm curious what exactly the problem was, previously I have updated with LTU installed (might have been an older version, can't remember) , so something, somewhere has changed. I would hate to have to perform this whole routine with every update.

Just Flash firmware without hdd instaled (for a time of flashing) it think it schuld e recommended to do it this way....

[Padavan]

werner
LTU package used small memory size in rootfs
- SSH dropbear binaries and keys (~210KB)
- busybox extension (~220KB)
- several scripts (~1KB)

rootfs (initramfs) extracted in the RAM and memory available more then 90MB.

By default, in LTU disabled all applications, except telnetd with login.

[halfelite]

it could also be they are pulling information out by byte so if LTU shifts were something was located it cannot be found anymore.

[tinnef]

(06-07-2011 07:39 AM)werner Wrote:  there won't be issues with later firmwares, because the difference with this build is that it needs to program the key which happens online, for which it needs memory which is used by the LTU package.

So just every 18 months or so when the key needs to be renewed? I can live with that.

[werner]

correct tinnef

[zwollywood]

Still little confused. As there were problems, I didn't upgrade with this FW. In fact I even did not upgrade with the previous may-FW.

Is it safe now to just upgrade with the standard procedure (as I did already a couple of times since november 2009 ) or do I have to use Werner's 6 steps. To be more clear: are these 6 steps only for people facing the ERR problems, or are they for everyone who wants to upgrade.

I have some CSI apps running, but what's LTU? Can't remember (here @ work) if I have this one.

[werner]

if you wanna be on the safe side then follow the steps

[chris57]

Success, uninstalled LTU and then disconnected my USB stick which is the location of my NMT Apps.

[jiyong]

After I got the email that there is a new FW, I upgraded without disconnecting the HD. Luckily I don't have LTU installed. So far no problems here. On the other hand LPCM 5.1 with a physical BD still not fixed. I know that the release notes don't state they fixed that, but I was hoping the routines were changed with BD PiP audio stream output as multi channel PCM.

Looks like there is some curse on LPCM 5.1 audio, as MakeMKV seems to have a bug with that too.

Any word on the next SDK from Sigma?

[nathan.never]

After the fw upgrade do I just reconnect the HDD again or do I need to reformat it before plugging in again?

Or do I just plug it in and instal fresh NMT apps?

Never did a fw upgrade with HDD unplugged so I am a little confused about it...

[werner]

just plug it in and after that update the NMT Apps, no need to make a fresh installation

[Caelen]

Saw this thread so I quickly turned the c200 on and set it to update firmware. Came back and read this thread and started to get a bit worried, but I didnt want to stop anything midway so I let it go. Luckily it all went fine, updated with no issue. Next time I might read instructions before continuing.
Still Im sure I wont be the only one.
I had no apps installed from CSI and an internal HDD which i didn't disconnect, I also didn't factory reset, but I did clear cache as I always do before an update.

So if anyone else is wondering, it appears that the update can work as normal, unless I was just very lucky.

[werner]

in most cases it worked without a issue thats what we see from the logs, currently the failed one around 20 are getting lower now , i just made this steps to make it as safe as possible.

[Bloodsack]

I didn't update June 3rd because so many people were having problems. I thought I would risk it and dive in and updated with no problems I guess all that talk about everyone having errors freaked me out a little. All that freaking out for nothing I guess I have one of those c-200's that updated fine.

It was werner that made me feel at ease. Thanks

[werner]

its everytime the same , users will come on the forum if they have issues, so a forum will all the time show issues, same with bugs if 20000000 are not affected by a bug but 5 posting here then all are getting scared , anyway at the beginning it was definitely a keyserver issue, where the many users had issues to upgrade, this was fixed on Sunday and since then we saw only a handfull failed updates in our logs, which seems to be now clear that it was/is related to LTU or CSI, so also the 20 failed macs are getting lower now because we see that they have now successfully updated

Regards,
Werner