Certain ports would fail to recognize peripherals until a hard power cycle was performed.
Resolved an issue where the tripod arms could experience delayed locking/unlocking cycles under high traffic. ts1022 firmware fixed
If you’ve been holding off on buying a TS1022 or have one sitting in a drawer due to frustration, now is the time to update and get back to work. Certain ports would fail to recognize peripherals until
Fixed a loop where users could occasionally re-enter without a valid exit log. Firmware Flashing: Fixed a loop where users could occasionally re-enter
If you are experiencing issues, checking your Zigbee2MQTT OTA updates for the latest manufacturer-released version is the most common resolution.
add_watchdog=setenv bootargs $bootargs watchdog=gpio_wdt
Diagnosis and Root Cause Engineers reproduced the failures in lab conditions by simulating high-frequency I/O bursts and synchronous peripheral accesses. Instrumentation revealed that the race arose when two interrupts—one for data-ready signaling and another for DMA completion—occurred in close succession. The firmware’s locking scheme assumed interrupt latency that modern variants of the TS1022 silicon no longer guaranteed. Additionally, the bootloader lacked an atomic swap or rollback capability, so interrupted updates could leave devices with partially written firmware images.
Certain ports would fail to recognize peripherals until a hard power cycle was performed.
Resolved an issue where the tripod arms could experience delayed locking/unlocking cycles under high traffic.
If you’ve been holding off on buying a TS1022 or have one sitting in a drawer due to frustration, now is the time to update and get back to work.
Fixed a loop where users could occasionally re-enter without a valid exit log. Firmware Flashing:
If you are experiencing issues, checking your Zigbee2MQTT OTA updates for the latest manufacturer-released version is the most common resolution.
add_watchdog=setenv bootargs $bootargs watchdog=gpio_wdt
Diagnosis and Root Cause Engineers reproduced the failures in lab conditions by simulating high-frequency I/O bursts and synchronous peripheral accesses. Instrumentation revealed that the race arose when two interrupts—one for data-ready signaling and another for DMA completion—occurred in close succession. The firmware’s locking scheme assumed interrupt latency that modern variants of the TS1022 silicon no longer guaranteed. Additionally, the bootloader lacked an atomic swap or rollback capability, so interrupted updates could leave devices with partially written firmware images.