- Messages
- 5,013
- Points
- 113
Another quick Post with an explanation of how Milesight's cameras manage firmware storage & upgrades.
We learned this only yesterday based upon what seemed to us to be rather odd behaviour:
When we reset a camera to its factory defaults using the pushbutton reset, not only were the parameter settings restored to default, but also the camera's firmware version reverted to the 'as shipped' firmware version.
Milesight have explained that their cameras use what they term a dual kernel system for firmware upgrades:
For instance, you receive a new Milesight camera - it is running File system 1 in Kernel 1.
You update the firmware; it will create a new File system 2 in Kernel 2.
It then runs from this new File system 2.
Subsequently, if you upgrade the firmware again, it update the older version (File system 1 in Kernel 1) and switch to using that.
It always retains the 'Last Good' File system in the kernel not currently being used.
If you encounter a problem and use the hard reset pushbutton, it will reset and revert to that other kernel / File system and 'Last Good' firmware.
This makes for a more durable / recoverable system.
I have come across similar solutions for PC motherboards e.g. dual BIOS, but have never come across this functionality in IP cameras before.
I have asked if they have a fuller explanation or description such as a White paper, but there's nothing available at the moment so hopefully this explanation will suffice for the time being.
We learned this only yesterday based upon what seemed to us to be rather odd behaviour:
When we reset a camera to its factory defaults using the pushbutton reset, not only were the parameter settings restored to default, but also the camera's firmware version reverted to the 'as shipped' firmware version.
Milesight have explained that their cameras use what they term a dual kernel system for firmware upgrades:
For instance, you receive a new Milesight camera - it is running File system 1 in Kernel 1.
You update the firmware; it will create a new File system 2 in Kernel 2.
It then runs from this new File system 2.
Subsequently, if you upgrade the firmware again, it update the older version (File system 1 in Kernel 1) and switch to using that.
It always retains the 'Last Good' File system in the kernel not currently being used.
If you encounter a problem and use the hard reset pushbutton, it will reset and revert to that other kernel / File system and 'Last Good' firmware.
This makes for a more durable / recoverable system.
I have come across similar solutions for PC motherboards e.g. dual BIOS, but have never come across this functionality in IP cameras before.
I have asked if they have a fuller explanation or description such as a White paper, but there's nothing available at the moment so hopefully this explanation will suffice for the time being.
