Firmware Update for Industrial Wearable Device
About the Client
Company’s Request
Technology Set
|
|
|
|
Embedded Android
|
A customized version of the Android operating system, tailored to run specifically on embedded systems like wearables. It provides a stable and optimized platform for devices with specific functionality. Used as the core operating system on the wearable devices.
|
|
C
|
A high-performance programming language that is commonly used for developing firmware and system-level software because of its efficiency and control over system resources. Utilized to develop low-level firmware updates that improve system stability.
|
|
WiFi
|
Used for the device connectivity, enabling communication and data transfer within the network.
|
|
wpa_supplicant
|
A software application used to manage wireless connections, which includes capabilities to handle secure network authentication like WPA and WPA2. Updated to enhance WiFi stability, solving prior issues with network integration.
|
|
Netlink
|
A communication protocol between the kernel and user-space processes. Used to interface with new network configurations and for the integration of updated network management tools within the system.
|
The client provides wearable technology to achieve performance optimization in smart warehouses, manufacturing facilities, field services, and in a variety of other rugged work environments. The service coordinates workers and managers and records all data in the cloud for further analytics and workflow improvements.
That’s why the stability of its connection is essential for the system’s smooth functioning. The client’s devices used wpa_supplicant 2.5 and Android marshmallow. We implemented wpa_supplicant 2.7 and combined all source files for the project’s build. The new wpa_supplicant used Android 8.0 which had an updated Hardware Abstraction Layer. Therefore we couldn’t simply update the source files and our engineers were required to uncover all calls that worked with the new HAL and update them one by one. Moreover, we faced a challenge that existed since the firmware’s creation: there was a mistake in the source files – their device parameters didn’t allow them to work with enterprise networks. So we remade the supplicant exactly for the updated devices.
After all corrective and test phases, we not only upgraded the firmware but in fact, created a new version of it.
Value Delivered
