If a wrong firmware has been installed on the controller or the firmware upgrade process has been interrupted, the controller will crash and (most probably) will not be able to communicate with Roborun+ through USB. If no USB communication can be achieved, then the controller cannot be reprogramed and restored. Thankfully the RS-232 communication can still work since this is initialized on the bootloader. Although serial communication can work when the controller enters bootloader, having installed a wrong firmware will not allow RS-232 communication to be achieved during controller’s main operation.  


Firmware upgrade sequence

To perform the firmware upgrade by using RS-232 follow the below steps:

1. Plug in to the controller an RS-232 to USB adapter. The Tx of the adapter should be connected to the Rx of the controller, the Rx of the adapter to the Tx of the controller and the two grounds together.

2. Find the COM port that the adapter is connected

 

 

3. On the Roborun+ utility click “Update Firmware through Com port”

 

  

4. On the pop-up window click “Manually select COM port” and configure the port of your adapter

 

 

5. Click “Browse” and load the firmware bin file



6. Click “Program”


 

7.  Power cycle the controller. The Utility Sends a serial command to make the controller restart and enter bootloader. Since the serial communication cannot be achieved except if the controller is already on bootloader, the controller cannot restart on its own. At this point you have a couple of seconds to power cycle the controller (remove power until caps drain and restore it) so the Utility will detect on time the starting string

     

  

8. Firmware update is complete! If the correct file has been loaded the controller should be able to function properly and communicate through USB after reset.