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