add: post-reset fw
This commit is contained in:
@@ -417,5 +417,20 @@ There is no FW update available.
|
|||||||
|
|
||||||
### Bridge
|
### Bridge
|
||||||
|
|
||||||
|
You can find the firmware after a full reset [here](firmware/bridge/reset_fw.bin).
|
||||||
|
|
||||||
|
I generated a [report](firmware/bridge/reset_fw_report.txt) using the same IoT FW analysis tool.
|
||||||
|
|
||||||
|
These are the differences:
|
||||||
|
- After reset: MD5 a3ae4e32c155426e5a163429fd35ce74
|
||||||
|
- Before: MD5 847d4795ee64714d3b02e2bdb3d20266
|
||||||
|
- Not byte-for-byte identical, firmware itself is unchanged
|
||||||
|
- Only differing string is a single value (`MMNHB<84` vs `LLNHB<84`)
|
||||||
|
|
||||||
|
> Further & deeper analysis of the FW will be done later on as it exceeds a "simple" informartion gathering.
|
||||||
|
|
||||||
## 2.5 Inspection of Device During Normal Usage
|
## 2.5 Inspection of Device During Normal Usage
|
||||||
|
|
||||||
|
The lock works as expected, the only issue seems to be the touch module which is often delayed or doesn't properly react to input.
|
||||||
|
|
||||||
|
Nothing interesting other than that.
|
||||||
Binary file not shown.
File diff suppressed because it is too large
Load Diff
Reference in New Issue
Block a user