AMiRo-OS

Alternatively, some Linux distributions provide the tool in their software

repositories. If you do have root permissions on your system, you can install

the tool this way. However, the scripts will always check for a 'local'

installation in `./Host/Source/stm32flash/` first and only try a system-wide

installation afterwards.

further development of AMiRo-BLT, but are useful in both scenarios.

Please note that you will need to recompile the AMiRo-BLT source code after each

project generation, since the generator executes a compiler call.

The AMiRo-BLT project is separated into two major parts: target- and

host-related software. The former comprises the bootloaders for the base modules

of the AMiRo platform. The latter are the `stm32flash` tool as already mentioned

above and the `SerialBoot` tool, which can be used to flash further binaries

(e.g. an operating system) to the microcontrollers without connecting to the

module directly (data is passed through via CAN bus). Since the programming

connector of the lowermost AMiRo module is the only one accessible when the

robot is fully set up, this enables to update the firmware even for other

modules.

Instructions on how to build and intall the tool are given in chapter 1.4 of

this file.

full read and write permissions to the USB ports of your system when a

programming cable is plugged in. To do so, first create a new file by executing

the following command:

indirect flashing using `SerialBoot` is not possible for the bootloader itself) and run the command

*   Did your system apply the new `udev` rules?  

    Re-login (or reboot) and try again!

*   Could make execute the stm32flash tool?  

    Check the stm32flash installation (reinitialize the submodule if required) and try again!

*   Are the permissions for USB ports set correctly?  

*   Are there any other applications using the serial connection?  

*   Is the AMiRo module connected to your system?  

    Use the programming cable to connect the module to your system!

*   Is the AMiRo module powered up?  

    Keep a charger plugged in during flashing!

*   Was there an error when opening the ports?  

    Please read on!

By default, the scripts use the first matching port (i.e. `/dev/ttyAMiRo0` or

`/dev/ttyUSB0`) for flashing. If you have connected multiple AMiRo boards to

your system, those will be listed with increasing numbers in their identifiers.

Furthermore, other USB devices (also internal components) might be listed as

such as well. In those cases, you have to specify the correct port manually when

calling `make`:

    >$ make flash STM32FLASH_PORT=/dev/ttyAMiRo#

where you have to replace the trailing `#` with the according integer.