Closed randaz81 closed 6 months ago
Hi @randaz81,
In the last days @Gandoo installed the new fingertips and replaced the mtb4-eb2
:
- We would like to obtain a clear procedure to easily program the board (we have to switch multiple times between the standard firmware and the devel firmware)
The procedure is described in https://icub-tech-iit.github.io/documentation/icub_firmware/firmware/firmware.
In a nuts, the user have to:
discover
w/ the ETH board selectedSince this operation failed, we tried to understand if the problem was that specific firmware version, and we tried to program the mtb4 with the standard mtb4c firmware downloaded from icub-firmware-build
⚠️ mtb4
is different from mtb4c
, be sure to flash the right FW Application.
Since your feedback are positive, I would consider the issue solved, right?
cc @AntonioConsilvio @Fabrizio69
We can close here, since the relevant discussion was moved to: https://github.com/icub-tech-iit/tickets/issues/3344 https://github.com/icub-tech-iit/tickets/issues/3388
Robot Name 🤖
ergoCub 1.1 S/N:001
Request/Failure description
Detailed context
We did a lot of unsuccessful tests trying to write the Xela firmware on the MTB4 board.
Since this operation failed, we tried to understand if the problem was that specific firmware version, and we tried to program the mtb4 with the standard mtb4c firmware downloaded from icub-firmware-build (https://github.com/robotology/icub-firmware-build/tree/master/CAN/mtb4c). Also in this case the operation failed.
We tried to do this operation:
The board now is still visible from the FirmwareUpdater but I am not sure if it is still working or not.
I was also not able to put it in bootloader mode (resetting the EMS) to recover its status to the standard firmware version.
Additional context
No response
How does it affect you?
No response