Revision d8ed8c1c
| Makefile | ||
|---|---|---|
| 48 | 48 |
all: |
| 49 | 49 |
Builds the binaries for all modules. |
| 50 | 50 |
|
| 51 |
flash: |
|
| 52 |
Flashes all binaries to the hardware. |
|
| 53 |
If the binaries do not exist, they are created beforehand. |
|
| 51 |
<module>: |
|
| 52 |
Builds the binary only for the specified module. |
|
| 53 |
|
|
| 54 |
flash_<module>: |
|
| 55 |
Builds the binary for the specified module and flashes it to the hardware. |
|
| 54 | 56 |
|
| 55 | 57 |
clean: |
| 56 | 58 |
Deletes all temporary and binary files of all modules. |
| 57 | 59 |
|
| 58 |
<module>: |
|
| 59 |
Builds the binary only for the specified module.
|
|
| 60 |
clean_<module>:
|
|
| 61 |
Deletes all temporary and binary files of the specified module.
|
|
| 60 | 62 |
|
| 61 | 63 |
|
| 62 | 64 |
EXAMPLES: |
| ... | ... | |
| 69 | 71 |
This command will generate the binary files for the two modules |
| 70 | 72 |
DiWheelDrive (version 1.1) and LightRing (version 1.0). |
| 71 | 73 |
|
| 72 |
>$$ make flash -j
|
|
| 73 |
This command will first build all missing binary files and flash all
|
|
| 74 |
modules as soon as the binaries are ready.
|
|
| 74 |
>$$ make all -j
|
|
| 75 |
This command will first build missing binary files for all modules that
|
|
| 76 |
are found in the 'modules/' folder.
|
|
| 75 | 77 |
By the additional argument '-j' the build process will be parallelized. |
| 76 | 78 |
|
| 77 |
>$$ make clean && make all && make flash |
|
| 78 |
This command will first clean all thee projects. In a second step the |
|
| 79 |
binaries for all modules are build from scratch. Finally all modules are |
|
| 80 |
updated with the latest software. |
|
| 81 |
The following command can be used as a shorter and faster version: |
|
| 82 |
>$$ make clean && make flash -j |
|
| 79 |
>$$ make flash_DiWheelDrive_1-1 |
|
| 80 |
This command will build the binary for the DiWheelDrive module |
|
| 81 |
(version 1.1) only if required, and flash it to the hardware. |
|
| 82 |
|
|
| 83 |
>$$ make clean; make all; make flash_DiWheelDrive_1-1 |
|
| 84 |
This command will first clean all projects. In a second step the binaries |
|
| 85 |
for all modules are build from scratch. Finally the DiWheelDrive module |
|
| 86 |
(version 1.1) is updated with the latest software. |
|
| 83 | 87 |
|
| 84 | 88 |
################################################################################ |
| 85 | 89 |
endef |
| README.txt | ||
|---|---|---|
| 107 | 107 |
copy of it as well. For the sake of compatibility, it is included in AMiRo-OS as |
| 108 | 108 |
a Git submodule. It is highly recommended to use the ./setup.sh script for |
| 109 | 109 |
initialization. Moreover, you have to apply the patches to ChibiOS in order to |
| 110 |
make AMiRo-OS work properly. It is recommended to use the .setup.sh script for this
|
|
| 111 |
purpose. |
|
| 110 |
make AMiRo-OS work properly. It is recommended to use the .setup.sh script for |
|
| 111 |
this purpose.
|
|
| 112 | 112 |
If you would like to use a different kernel, you can add a subfolder in the |
| 113 | 113 |
./kernel/ directory and adapt the scripts and operating system source code. |
| 114 | 114 |
|
| ... | ... | |
| 116 | 116 |
1.4 Low-Level Drivers |
| 117 | 117 |
--------------------- |
| 118 | 118 |
|
| 119 |
Any required low-level drivers for the AMiRo hardware is available in an
|
|
| 119 |
Any required low-level drivers for the AMiRo hardware are available in an
|
|
| 120 | 120 |
additional project: AMiRo-LLD. It is included as a Git subodule and can be |
| 121 | 121 |
initialized via the ./setup.sh script. |
| 122 | 122 |
|
| ... | ... | |
| 125 | 125 |
2 - RECOMMENDED SOFTWARE |
| 126 | 126 |
------------------------ |
| 127 | 127 |
|
| 128 |
AMiRo-OS can take advanatge of an installed bootloader, which is recommended for
|
|
| 128 |
AMiRo-OS can take advantage of an installed bootloader, which is recommended for
|
|
| 129 | 129 |
the best experience. In order to use all features of AMiRo-OS it is also |
| 130 | 130 |
recommended to install either the 'hterm' or 'gtkterm' application for accessing |
| 131 | 131 |
the robot. To ease further development, this project offers support for the |
| ... | ... | |
| 157 | 157 |
can be reset by toggling the RTS signal on and off again, and you can access the |
| 158 | 158 |
system shell of AMiRo-OS. If you need legacy support for older version of |
| 159 | 159 |
AMiRo-BLT, you can replace the port value by '/dev/ttyUSB0'. |
| 160 |
Advanced users can use several connections to multiple modules simultaneously. |
|
| 161 |
Each additional programmer will be available as '/dev/ttyAMiRo<N>' (and |
|
| 162 |
'/dev/USB<N>' respectively) with <N> being an integer number starting from zero. |
|
| 163 |
Please note: Those interfaces are ordered by the time when they have been |
|
| 164 |
detected by the operating system. |
|
| 160 | 165 |
|
| 161 | 166 |
|
| 162 | 167 |
2.2 - QtCreator IDE |
Also available in: Unified diff