46 | | {{{ |
47 | | btflash, version 0.2.0 |
48 | | }}} |
49 | | |
50 | | Please note that the version number may be different. |
51 | | |
52 | | To install btflash, follow the installation instructions in the first section from our btflash repository ([[https://git.barrett.com/software/btflash | link]]), but skip the "setting up for development" section. You need to be connected to the internet to install btflash. |
53 | | |
54 | | == Setting up CAN == |
55 | | |
56 | | Before using btflash, you will need to guarantee that the CAN adapter is plugged in and then run the following commands. To configure CAN, type: |
57 | | |
58 | | {{{ |
59 | | sudo ip link set can0 type can bitrate 1000000 |
60 | | sudo ip link set up can0 |
61 | | }}} |
62 | | |
63 | | == Upgrading == |
64 | | |
65 | | To perform an upgrade you will need a .bin file provided by Barrett. You can carry out the upgrade using the following series of commands (see [#Footnote footnote]): |
66 | | |
67 | | {{{ |
68 | | btflash flash 10 path/to/main-board-comm.<version>.bin |
69 | | btflash reset 10 |
70 | | }}} |
71 | | |
72 | | You should follow these instructions for both consoles to upgrade both Main Boards. |
73 | | |
74 | | === Footnote === |
75 | | |
76 | | For some context, the Main Board, which is what runs the control firmware and talks to ROS, has an id of 10. In the above series of commands you are telling btflash to flash, write to the program memory of the device, the firmware from the defined file to the device with id 10. The reset commands provides a soft reset for the firmware on the Main Board. You should not need to power cycle, but if issues occur a power cycle is recommended. |