Skip to content
Aditya90 edited this page Apr 3, 2012 · 9 revisions

These steps have to be followed to update the motor firmware using Linux.

  1. Download the latest drivers from http://sourceforge.net/projects/darwinop/files/Software/Main%20Controller/Source%20Code/.

  2. Copy the zip folder which was downloaded, onto the Darwin.

  3. Extract the files into a new folder on the Darwin.

  4. Open the "build" folder, and edit the Makefile to remove the "LinuxCamera.o" line

  5. Execute "make clean" and then "make" to compile the files.

  6. Go to the "project/firmware_installer/" folder and "make" there.

  7. An executable file, "firmware_installer" should now be present in this folder. Run "./firmware_installer".

  8. Select the first option, "CM-730 firmware installation" and proceed to update. But to reflash the motor with the old firmware (this file exists in the latest update itself,i.e in v1.4.0), you have to select the second option provided it is showing the older firmware and not the latest one (mx1080 I think!). If not, do the following to get the second option as the older firmware file: Type in: ./firmware_installer -a --> That should do it. Now you can choose the second option and it should flash the motors one by one stating 'successful' at the end of each step. (If you have doubts about the above line, just put it ./firmware_installer --help for details of firmware versions contained in the v1.4.0 zip file)

  9. Then run, "Dynamixel firmware installation" and proceed to update.

NOTE:

If there is an issue getting the downloaded v1.4.0 zip file on to the bot, try the following (WIRELESS):

  • Note ip addr of the bot

  • from your laptop/system, SCP the v1.4.0 zip file to the bot. How? eg:- scp (file location on your system) darwin@(above obtained ip addr of the bot)

-Now you should be able to see the copied zip file on the darwin. Then Run steps 3 - 9!

-PLEASE ENSURE THAT THE USB2DYNAMIXEL CONVERTER IS IN THE TTL MODE.


Troubleshooting

  • If you get errors at the end of step 9, it could be due to baud rate differences in the motors. Ensure that all motors are at a baud rate of 1MHz.

  • THE BAUD RATES ALWAYS CHANGE!!!! More specifically, when you update the firmware. But more often than not, all errors are due to baud rate differences.

Clone this wiki locally