You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently had to update the firmware on the iCub3 robot. After the update (it was not updated for a year more or less), the yarprobotinterface was complaining about a wrong firmware version. So I tried to update the robot with the latest firmware in master, but the FirmwareUpdater printed in the terminal the following errors
EthMaintainer::cmdProgram() is about to program the APP partition of 13 boards: 10.0.1.1 (candoit) 10.0.1.2 (candoit) 10.0.1.3 (candoit) 10.0.1.4 (candoit) 10.0.1.5 (candoit) 10.0.1.6 (candoit) 10.0.1.7 (candoit) 10.0.1.8 (candoit) 10.0.1.9 (candoit) 10.0.1.10 (candoit) 10.0.1.11 (candoit) 10.0.1.12 (candoit) 10.0.1.13 (candoit)
ERROR: EthMaintainer::program() could not program board none @ 0.0.0.0: 10.0.1.1: APP NOK
10.0.1.2: APP NOK
10.0.1.3: APP NOK
10.0.1.4: APP NOK
10.0.1.5: APP NOK
10.0.1.6: APP NOK
10.0.1.7: APP NOK
10.0.1.8: APP NOK
10.0.1.9: APP NOK
10.0.1.10: APP NOK
10.0.1.11: APP NOK
10.0.1.12: APP NOK
10.0.1.13: APP NOK
.
I tried multiple times and I always had the same result. @julijenv told me he noticed a similar issue also while updating iCubGenova04.
Nevertheless, I tried to relaunch the yarprobotinterface and it started correctly, so I am wondering whether those errors are false positives.
I recently had to update the firmware on the iCub3 robot. After the update (it was not updated for a year more or less), the
yarprobotinterface
was complaining about a wrong firmware version. So I tried to update the robot with the latest firmware inmaster
, but theFirmwareUpdater
printed in the terminal the following errorsI tried multiple times and I always had the same result. @julijenv told me he noticed a similar issue also while updating iCubGenova04.
Nevertheless, I tried to relaunch the
yarprobotinterface
and it started correctly, so I am wondering whether those errors are false positives.@marcoaccame
The text was updated successfully, but these errors were encountered: