Сбой обновления прошивки на WB-MR6LV/I после которого устройство окирпичелось

Добрый день,

При попытке обновить WB-MR6LV/I произошла ошибка timeout, после нее повторные обновления не проходят, устройство перестало реагировать на Входы.

Ниже лог попытки обновить:

wb-mcu-fw-updater update-fw /dev/ttyRS485-1 -a34
Will find serial port settings for (/dev/ttyRS485-1 : 34; response_timeout: 0.20)... (elapsed: 00:00)
2025-07-30 13:46:42,497 Has found serial port settings: SerialSettings(baudrate=9600, parity='N', stopbits=1)
2025-07-30 13:46:46,783 fw (mr6G 34 on /dev/ttyRS485-1):
2025-07-30 13:46:46,786 Update: 1.21.2 -> 1.21.7 (mr6G 34 /dev/ttyRS485-1)
2025-07-30 13:46:47,677 
2025-07-30 13:46:47,678 Bootloader update (v1.4.1 -> v1.4.9) for mr6G /dev/ttyRS485-1:34 is available! (bootloader updates are highly recommended to install) Do a bootloader update? [Y/N]
y
2025-07-30 13:46:51,889 Flashing /var/lib/wb-mcu-fw-updater/bootloader/wb-bootloader-updater_mr6G__1.4.9_master_4617288.wbfw (36 data chunks)
  3%|####3                                                                                                                                                        |1/36
2025-07-30 13:46:52,935 Flashing fw to (/dev/ttyRS485-1 34; response_timeout: 0.20s) has failed!
2025-07-30 13:46:52,936 

При повторном запуске обновления ошибка:

wb-mcu-fw-updater update-fw /dev/ttyRS485-1 -a34
Will find serial port settings for (/dev/ttyRS485-1 : 34; response_timeout: 0.20)... (elapsed: 00:00)
2025-07-30 13:50:43,008 Has found serial port settings: SerialSettings(baudrate=9600, parity='N', stopbits=2)
2025-07-30 13:50:43,430 Flashing fw to (/dev/ttyRS485-1 34; response_timeout: 0.20s) has failed!
2025-07-30 13:50:43,431 Checksum error in rtu mode: 'òé' instead of 'üå' . The response is: '"\x03|`o`Û`~`7ؽ`e`g``````````òé' (plain response: '"\x03|`o`Û`~`7ؽ`e`g``````````òé')

Для наглядности с учетом расцветки ошибки прикладываю скриншот.

Что делать? Как восстановить?

Добрый день.
Для начала - рекомендую (несколько раз) прочитать сигнатуру устройства.
Убедившись что ошибок на шине нет - использовать wb-mcu-fw-flasher для обновления загрузчика и загрузки прошивки.

get-device-info возвращает данные, но не всегда.
Если возвращает, то в осномном “Invalid CRC” как для бутлоадера, так и для прошивки, но один раз вернулись реальные данные:
Bootloader version: 1.1.14
Firmware version: 2.3.7
Firmware signature (fw-sig): map12eG
Download firmwares: S3 Bucket Listing Generator

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Bootloader version read error: Invalid CRC
Firmware version: 2.3.7
Firmware signature (fw-sig) read error: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Connection timed out

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Bootloader version: 1.1.14
Firmware version: 2.3.7
Firmware signature (fw-sig): map12eG
Download firmwares: S3 Bucket Listing Generator

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Invalid CRC

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Response not from requested slave

root@a-wboard02:~# wb-mcu-fw-flasher -d /dev/ttyRS485-1 -a34 --get-device-info
/dev/ttyRS485-1 opened successfully.
Trying to probe (34 /dev/ttyRS485-1) at bootloader params…
Failed to connect (34 /dev/ttyRS485-1) at bootloader settings: Response not from requested slave

Так а точно остановлен wb-mqtt-serial?
Если он остановлен и такое количество ошибок - ну, прошивать не очень хорошо, скорре всего неудачно пройдет.
Проверьте, точно его остановив.

Добрый день,

Все оказалось проще, чем думали :).

По ошибке к шине было подключено другое устройство с таким же адресом, которое при том не было добавлено в wb-mqtt-serial.conf и получается при опросах они оба отвечали.
Смена адреса помогла запросить данные с устройства, оно оказалось переведенным в режим буллоадера, далее по инструкции Сервисная утилита wb-mcu-fw-flasher — Wiren Board все получилось прошить.

Спасибо за помощь в изучении проблемы!

Да, подобное предположить сложно.
Ну отлично, рад что получилось.