Comfort Home Automation/ Security System Forums Home
Home Search search Menu menu Not logged in - Login | Register

UCM 7.054, 7.056 (beta)
 Moderated by: ident Page:    1  2  Next Page Last Page  
 New Topic   Reply   Printer Friendly 
 Rate Topic 
AuthorPost
 Posted: Sunday Aug 24th, 2014 06:10 am
   PM  Quote  Reply 
1st Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

The beta firmware 7 .054 has the following changes
  1. Added new command "cc" to echo everything after "cc" eg "cc1234abcd" command will echo back "cc1234abcd" for testing purposes
  2. Allow F!ffSS Flag change command where ss = 3  for toggle, eg F!0103 will toggle the state of flag 1
  3. UCM/ETH03 SNTP feature for internet Time sync will not give OK reply when it is not logged in

BUG
UCM 7.054 will not be able tp upgrade its own firmware. Please do NOT upgrade to UCM 7.054 and if you have done so, do not try to upgrade (or downgrade) the firmware until further instrutions

Last edited on Wednesday Aug 27th, 2014 04:32 pm by ident



 Posted: Wednesday Aug 27th, 2014 04:31 pm
   PM  Quote  Reply 
2nd Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

We have just detected a serious bug in UCM 7.054 (beta)

If the UCM is upgraded to this firmware, the UCM will NOT be able to upgrade its own firmware again

Do NOT upgrade to UCM 7.054 and if you have done so, Do NOT try to upgrade firmware any further

We will check if it is OK to upgrade the UCM firmware via another UCM. More information will be provided

The beta firmware has been removed from the server


Last edited on Wednesday Aug 27th, 2014 04:33 pm by ident



 Posted: Wednesday Aug 27th, 2014 05:56 pm
   PM  Quote  Reply 
3rd Post
juwi_uk
Advanced Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1243
Status: 
Offline

  back to top

Yep I trashed the UCM/Eth3 on my test rig!

Presume it cant connect anymore it the issue right?

Julian

 

 

 

 



 Posted: Wednesday Aug 27th, 2014 06:04 pm
   PM  Quote  Reply 
4th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 4307
Status: 
Offline

  back to top

The ucm with 7.054 will work until you try to upgrade it again, so do not upgrade it by the normal method
You can use another ucm with the firmware upgrade cable to upgrade the ucm 7.054



 Posted: Wednesday Aug 27th, 2014 06:35 pm
   PM  Quote  Reply 
5th Post
juwi_uk
Advanced Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1243
Status: 
Offline

  back to top

Unless that other UCM is also on 7.054?

What happens then?



 Posted: Wednesday Aug 27th, 2014 06:44 pm
   PM  Quote  Reply 
6th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 4307
Status: 
Offline

  back to top

No problem
The 7.054 only has a problem when it has to upgrade its own firmware

It has no problem with uograding another ucm



 Posted: Wednesday Aug 27th, 2014 06:44 pm
   PM  Quote  Reply 
7th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 4307
Status: 
Offline

  back to top

No problem
The 7.054 only has a problem when it has to upgrade its own firmware

It has no problem with uograding another ucm



 Posted: Wednesday Aug 27th, 2014 07:24 pm
   PM  Quote  Reply 
8th Post
juwi_uk
Advanced Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1243
Status: 
Offline

  back to top

Yes I just reverted both my 7.054 UCMs back to 7.049 using the programme cable method without a hitch!  Phew!

I guess you have to slip in these problematic upgrades if only just to remind us once, every so often, as to how lucky we are normally not to have to faff with the programming method anymore.  I even had to read the manual as so long since I've done one! 

:D

 

Julian



 Posted: Friday Aug 29th, 2014 12:48 am
   PM  Quote  Reply 
9th Post
cc_uk
Member
 

Joined: Friday Mar 28th, 2014
Location:  
Posts: 64
Status: 
Offline

  back to top

Is there likely to be a recovery for those of us with one UCM only on 7.054?



 Posted: Friday Aug 29th, 2014 07:46 am
   PM  Quote  Reply 
10th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

Do you have another UCM by any chance?

We are looking at how to solve it. but do not try to upgrade the ucm firmware using the same UCM. Using another UCM should be no problem



 Posted: Friday Aug 29th, 2014 09:41 am
   PM  Quote  Reply 
11th Post
juwi_uk
Advanced Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1243
Status: 
Offline

  back to top

Whilst it wont help the scenario this time around,  could you make use of the U3 eeprom in the future and change the  upgrade process so it saves a copy to there somehow and use this like a, what would be in PC terms, crash-free bios and be able to recover from in these type scenarios.

Maybe just save the previous firmware to there before it upgrades and any issues if can be reverted back somehow?

Julian

 



 Posted: Friday Aug 29th, 2014 09:51 am
   PM  Quote  Reply 
12th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

Saving firmware to eeprom will not help if the firmware is corrupted, as you need  working firmware to read the eeprom

For UCM 7.054, once you try to self upgrade, the firmware is corrupted



 Posted: Friday Aug 29th, 2014 10:05 am
   PM  Quote  Reply 
13th Post
juwi_uk
Advanced Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1243
Status: 
Offline

  back to top

Save the previous version to the U3 chip before the new upgrade download starts.   If it fails for any reason then restore from the U3 chip previous version.

Maybe the firmware upgrade cant always do the auto recovery as it doesn't necessarily know it is broke; this actual use case in this thread is a good example of that.

But to recover then you could have some ring-fenced code that could recover from U3.  then to initiate the restore retrospectively you just set a Boolean at a memory address X and reset the system and it auto recovers.

That's my suggestion anyway.

Julian

 



 Posted: Friday Aug 29th, 2014 06:04 pm
   PM  Quote  Reply 
14th Post
tman
Comfort Distributors
 

Joined: Wednesday Sep 22nd, 2010
Location: United Kingdom
Posts: 22
Status: 
Offline

  back to top

juwi_uk wrote: Save the previous version to the U3 chip before the new upgrade download starts.   If it fails for any reason then restore from the U3 chip previous version.

Maybe the firmware upgrade cant always do the auto recovery as it doesn't necessarily know it is broke; this actual use case in this thread is a good example of that.

But to recover then you could have some ring-fenced code that could recover from U3.  then to initiate the restore retrospectively you just set a Boolean at a memory address X and reset the system and it auto recovers.

That's my suggestion anyway.

Julian

 

The EEPROM fitted is only 32KB.



 Posted: Friday Aug 29th, 2014 06:07 pm
   PM  Quote  Reply 
15th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

Yes, there is also that little problem



 Posted: Friday Aug 29th, 2014 06:16 pm
   PM  Quote  Reply 
16th Post
juwi_uk
Advanced Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1243
Status: 
Offline

  back to top

The UCM/GSM4 baseboard has a 256K eeprom (24LC256) in U2 for a start so 32K cannot be the max even if you have in your specific UCM 

That said I've no idea what it would need to be anyway.

J

 

 

 



 Posted: Saturday Aug 30th, 2014 04:44 am
   PM  Quote  Reply 
17th Post
tman
Comfort Distributors
 

Joined: Wednesday Sep 22nd, 2010
Location: United Kingdom
Posts: 22
Status: 
Offline

  back to top

juwi_uk wrote: The UCM/GSM4 baseboard has a 256K eeprom (24LC256) in U2 for a start so 32K cannot be the max even if you have in your specific UCM 

That said I've no idea what it would need to be anyway.

J

24LC256 is a 256Kbit EEPROM which is 32KB. The UCM firmware file is 256KB.



 Posted: Saturday Aug 30th, 2014 09:32 am
   PM  Quote  Reply 
18th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

UCM 7.056 (beta) fixes the bug in 7.054 (corrupted by self upgrade)


Bugs Fixed
  1. UCM 7.054 cannot be upgraded except  by another UCM

New Features
  1. Implement new UCM command r?TTxxNN query sequential registers where TT = type 0 for Counter, 1 for sensor, xx= starting register no, NN is no of registers. Reply from UCM is r?TTxxNNaaaabbbbccccdddd...... Requires Comfort firmware 7.062
  2. Allows all RS485 modules to be upgraded if the firmware is version 6 including future KP04



 Posted: Saturday Aug 30th, 2014 11:01 am
   PM  Quote  Reply 
19th Post
juwi_uk
Advanced Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1243
Status: 
Offline

  back to top

So where does that leave users on 7.054 with just the one UCM as was asked by one user?



 Posted: Saturday Aug 30th, 2014 12:10 pm
   PM  Quote  Reply 
20th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

we are still considering the best solution. If there is anyone else who has upgraded to UCM 7.054 please send email to support@cytech.biz or send a PM



 Current time is 07:58 amPage:    1  2  Next Page Last Page  
Top




UltraBB 1.172 Copyright © 2007-2014 Data 1 Systems