Сделано.
Возникли проблемы с обновлением до bullseye. Через сброс установил стабильную версию 2207.
Welcome to Wiren Board 6.7.2 (s/n ACTCUFPH), release wb-2207 (as stable)
Linux wirenboard-ACTCUFPH 5.10.35-wb120+wb101 #2 Tue Nov 22 12:48:20 UTC 2022 ar mv7l GNU/Linux
Попробовал обновить, выяснилось, что есть еще проблемы. Обновились 3 устройства из 7, лог:
root@wirenboard-ACTCUFPH:~# wb-mcu-fw-updater update-all
2023-03-04 09:19:01,960 Will probe all devices on enabled serial ports of /etc/w b-mqtt-serial.conf:
2023-03-04 09:19:01,976 Probing WB-MRGBW-D (port: /dev/ttyRS485-2, slaveid: 198, uart_params: 9600N2, response_timeout: 0.50)...
2023-03-04 09:19:02,369 Probing WB-MR6C (port: /dev/ttyRS485-2, slaveid: 144, ua rt_params: 9600N2, response_timeout: 0.50)...
2023-03-04 09:19:02,812 Probing WB-MRGBW-D (port: /dev/ttyRS485-2, slaveid: 27, uart_params: 9600N2, response_timeout: 0.50)...
2023-03-04 09:19:03,244 Probing WB-MWAC (port: /dev/ttyRS485-2, slaveid: 127, ua rt_params: 9600N2, response_timeout: 0.50)...
2023-03-04 09:19:10,987 Probing WB-MDM3 (port: /dev/ttyRS485-2, slaveid: 133, ua rt_params: 9600N2, response_timeout: 0.50)...
2023-03-04 09:19:11,433 Probing WB-MR6C (port: /dev/ttyRS485-2, slaveid: 190, ua rt_params: 9600N2, response_timeout: 0.50)...
2023-03-04 09:19:18,364 Probing WB-MDM3 (port: /dev/ttyRS485-2, slaveid: 8, uart _params: 9600N2, response_timeout: 0.50)...
2023-03-04 09:19:22,444 Update: 1.3.1 -> 3.3.4 (WB-MRGBW-D (198, /dev/ttyRS485-2 ))
2023-03-04 09:19:22,454
2023-03-04 09:19:22,460 Major version has changed (v1 -> v3);
2023-03-04 09:19:22,466 Backward compatibility will be broken. Are you s ure? [Y/N]
Y
2023-03-04 09:19:40,222 Released FW not found for " "
Release info:
{
"REPO_PREFIX": "",
"TARGET": "wb6/stretch",
"RELEASE_NAME": "wb-2207",
"SUITE": "stable"
}
2023-03-04 09:19:43,392 Update: 1.3.1 -> 3.3.4 (WB-MRGBW-D (27, /dev/ttyRS485-2) )
2023-03-04 09:19:43,400
2023-03-04 09:19:43,408 Major version has changed (v1 -> v3);
2023-03-04 09:19:43,416 Backward compatibility will be broken. Are you s ure? [Y/N]
Y
2023-03-04 09:20:10,777 Update: 2.2.1 -> 2.5.3 (WB-MDM3 (133, /dev/ttyRS485-2))
2023-03-04 09:20:13,868 Released FW not found for " E "
Release info:
{
"REPO_PREFIX": "",
"TARGET": "wb6/stretch",
"RELEASE_NAME": "wb-2207",
"SUITE": "stable"
}
2023-03-04 09:20:13,878 Flashing firmware to WB-MRGBW-D (198, /dev/ttyRS485-2)
2023-03-04 09:20:21,162 Flashing /var/lib/wb-mcu-fw-updater/mrgbw__3.3.4_master_ 128db7a.wbfw
100%|###################################################################|193/193
2023-03-04 09:21:13,669 Flashing firmware to WB-MRGBW-D (27, /dev/ttyRS485-2)
2023-03-04 09:21:34,975 Flashing /var/lib/wb-mcu-fw-updater/mrgbw__3.3.4_master_ 128db7a.wbfw
100%|###################################################################|193/193
2023-03-04 09:22:27,252 Flashing firmware to WB-MDM3 (133, /dev/ttyRS485-2)
2023-03-04 09:22:47,086 Flashing /var/lib/wb-mcu-fw-updater/mdm3__2.5.3_master_3 8ac9f0.wbfw
100%|###################################################################|137/137
2023-03-04 09:23:24,300 Not supported in current wb-2207 release:
2023-03-04 09:23:24,308 WB-MR6C (144, /dev/ttyRS485-2); WB-MDM3 (8, /dev /ttyRS485-2)
2023-03-04 09:23:24,316 You may try to switch to newer release
2023-03-04 09:23:24,323 No answer from:
2023-03-04 09:23:24,329 WB-MWAC (127, /dev/ttyRS485-2); WB-MR6C (190, /d ev/ttyRS485-2)
2023-03-04 09:23:24,336 Devices are possibly disconnected
2023-03-04 09:23:24,343 3 upgraded, 0 skipped upgrade, 0 stuck in bootloader, 2 disconnected and 0 too old for any updates.
Ниже запросы сигнатуры, версии прошивки и серийного номера для WB-MR6C (144, /dev/ttyRS485-2); WB-MDM3 (8, /dev /ttyRS485-2):
root@wirenboard-ACTCUFPH:~# modbus_client -mrtu -pnone -s2 /dev/ttyRS485-2 -a144 -t3 -r 290 -c 12 SUCCESS: read 12 of elements:
Data: 0x0008 0x00f9 0x000a 0x0000 0x0008 0x00f9 0x000a 0x0000 0x0000 0x0000 0x0000 0x0000
root@wirenboard-ACTCUFPH:~# modbus_client -mrtu -pnone -s2 /dev/ttyRS485-2 -a144 -t3 -r 330 -c 8 SUCCESS: read 8 of elements:
Data: 0x0031 0x002e 0x0031 0x002e 0x0037 0x0000 0x0000 0x0002
root@wirenboard-ACTCUFPH:~# modbus_client -mrtu -pnone -s2 /dev/ttyRS485-2 -a144 -t3 -r270 -c2 SUCCESS: read 2 of elements:
Data: 0xfed2 0x4129
root@wirenboard-ACTCUFPH:~# modbus_client -mrtu -pnone -s2 /dev/ttyRS485-2 -a8 - t3 -r 290 -c 12
SUCCESS: read 12 of elements:
Data: 0x0000 0x00d9 0x000a 0x0000 0x0008 0x00d9 0x000a 0x0000 0x0008 0x0 045 0x0002 0x0000
root@wirenboard-ACTCUFPH:~# modbus_client -mrtu -pnone -s2 /dev/ttyRS485-2 -a8 - t3 -r 330 -c 8
SUCCESS: read 8 of elements:
root@wirenboard-ACTCUFPH:~# modbus_client -mrtu -pnone -s2 /dev/ttyRS485-2 -a8 - t3 -r270 -c2
SUCCESS: read 2 of elements:
Data: 0xfe82 0x85f7
Вобщем, у них проблема с сигнатурой. Попробовал через wb-mcu-fw-flasher для устройства WB-MDM3 (8, /dev /ttyRS485-2) залить ту же прошивку, которая успешно встала на WB-MDM3 (133, /dev/ttyRS485-2), но получил ошибку:
root@wirenboard-ACTCUFPH:/var/tmp# wb-mcu-fw-flasher -d /dev/ttyRS485-2 -a 8 -f ./2.5.3.wbfw
/dev/ttyRS485-2 opened successfully.
./2.5.3.wbfw opened successfully, size 18664 bytes
Sending info block...
Error while sending info block: Slave device or server failure
Data format is invalid or firmware signature doesn't match the device
Судя по всему этой опции нет в stable. Выполнил через команду, найдено 5 из 7 (тут без изменений, 2 не найдены):
root@wirenboard-ACTCUFPH:/var/tmp# for i in {1..247}; do echo -n "$i - "; D=`modbus_client -mrtu /dev/ttyRS485-2 --debug -b9600 -pnone -s2 -a$i -t3 -o100 -r200 -c6 2>/dev/null | grep Data: | awk 'gsub("Data:","")' | sed -e 's/0x00/\\\x/g' -e 's/\s//g'`; echo -e $D; done
1 -
2 -
3 -
4 -
5 -
6 -
7 -
8 - WBMD3
9 -
10 -
11 -
12 -
13 -
14 -
15 -
16 -
17 -
18 -
19 -
20 -
21 -
22 -
23 -
24 -
25 -
26 -
27 - WB-MRG
28 -
29 -
30 -
31 -
32 -
33 -
34 -
35 -
36 -
37 -
38 -
39 -
40 -
41 -
42 -
43 -
44 -
45 -
46 -
47 -
48 -
49 -
50 -
51 -
52 -
53 -
54 -
55 -
56 -
57 -
58 -
59 -
60 -
61 -
62 -
63 -
64 -
65 -
66 -
67 -
68 -
69 -
70 -
71 -
72 -
73 -
74 -
75 -
76 -
77 -
78 -
79 -
80 -
81 -
82 -
83 -
84 -
85 -
86 -
87 -
88 -
89 -
90 -
91 -
92 -
93 -
94 -
95 -
96 -
97 -
98 -
99 -
100 -
101 -
102 -
103 -
104 -
105 -
106 -
107 -
108 -
109 -
110 -
111 -
112 -
113 -
114 -
115 -
116 -
117 -
118 -
119 -
120 -
121 -
122 -
123 -
124 -
125 -
126 -
127 -
128 -
129 -
130 -
131 -
132 -
133 - WBMD3
134 -
135 -
136 -
137 -
138 -
139 -
140 -
141 -
142 -
143 -
144 - WBMR6C
145 -
146 -
147 -
148 -
149 -
150 -
151 -
152 -
153 -
154 -
155 -
156 -
157 -
158 -
159 -
160 -
161 -
162 -
163 -
164 -
165 -
166 -
167 -
168 -
169 -
170 -
171 -
172 -
173 -
174 -
175 -
176 -
177 -
178 -
179 -
180 -
181 -
182 -
183 -
184 -
185 -
186 -
187 -
188 -
189 -
190 -
191 -
192 -
193 -
194 -
195 -
196 -
197 -
198 - WB-MRG
199 -
200 -
201 -
202 -
203 -
204 -
205 -
206 -
207 -
208 -
209 -
210 -
211 -
212 -
213 -
214 -
215 -
216 -
217 -
218 -
219 -
220 -
221 -
222 -
223 -
224 -
225 -
226 -
227 -
228 -
229 -
230 -
231 -
232 -
233 -
234 -
235 -
236 -
237 -
238 -
239 -
240 -
241 -
242 -
243 -
244 -
245 -
246 -
247 -
ИТОГ: 2 устройства с битой сигнатурой, 2 устройства не отвечают. Если нужно все-таки обновиться до testing 2210, напишите, пожалуйста, но кажется, что это ничего не поменяет, и дело в устройствах.
p.s.: Приложил на всякий случай свежий файл диагностики
diag_output_ACTCUFPH_2023-03-14-13.25.38.zip (98.4 КБ)