Improved structure #17
35
README.md
35
README.md
@ -24,11 +24,7 @@ Target systems:
|
||||
The steps in the primary README are related to the main OBC target Q7S.
|
||||
The CMake build system can be used to generate build systems as well (see helper scripts in `cmake/scripts`:
|
||||
|
||||
- Linux (Raspberry Pi): Using the `bsp_rpi` BSP folder, and a very similar cross-compiler.
|
||||
For running the software on a Raspberry Pi, it is recommended to follow the steps specified in
|
||||
[the fsfw example](https://egit.irs.uni-stuttgart.de/fsfw/fsfw_example/src/branch/mueller/master/doc/README-rpi.md#top) and using the TCF agent to have a similar set-up process also required for the Q7S.
|
||||
If you want to use the `gpiod` library, run `sudo apt-get install gpiod libgpiod-dev` on your
|
||||
Raspberry Pi first to install the library before cloning the system root folder.
|
||||
- Linux (Raspberry Pi): See special section below.
|
||||
- Linux Host: Uses the `bsp_hosted` BSP folder and the CMake Unix Makefiles generator.
|
||||
- Windows Host: Uses the `bsp_hosted` BSP folder, the CMake MinGW Makefiles generator and MSYS2.
|
||||
|
||||
@ -150,9 +146,9 @@ The [TCF agent](https://wiki.eclipse.org/TCF) can be used to perform remote debu
|
||||
|
||||
After that, comfortable remote debugging should be possible with the Debug button.
|
||||
|
||||
A build configuration and a shell helper script has been provided to set up the path variables and build the Q7S binary
|
||||
on Windows, but a launch configuration needs to be newly created because the IP address and path settings differ
|
||||
from machine to machine.
|
||||
A build configuration and a shell helper script has been provided to set up the path variables and
|
||||
build the Q7S binary on Windows, but a launch configuration needs to be newly created because the
|
||||
IP address and path settings differ from machine to machine.
|
||||
|
||||
## Building in Xilinx SDK 2018.2
|
||||
|
||||
@ -529,3 +525,26 @@ gpioget <gpiogroup> <offset>
|
||||
````
|
||||
Example to get state:
|
||||
gpioget gpiochip7 14
|
||||
|
||||
## Running the EIVE OBSW on a Raspberry Pi
|
||||
|
||||
Special section for running the EIVE OBSW on the Raspberry Pi
|
||||
It uses the `bsp_rpi` BSP folder, and a very similar cross-compiler.
|
||||
|
||||
For running the software on a Raspberry Pi, it is recommended to follow the steps specified in
|
||||
[the fsfw example](https://egit.irs.uni-stuttgart.de/fsfw/fsfw_example/src/branch/mueller/master/doc/README-rpi.md#top)
|
||||
and using the TCF agent to have a similar set-up process also required for the Q7S.
|
||||
If you want to use the `gpiod` library, run
|
||||
|
||||
```sh
|
||||
sudo apt-get install gpiod libgpiod-dev
|
||||
```
|
||||
|
||||
on your Raspberry Pi first to install the library before cloning the system root folder.
|
||||
|
||||
## Special notes on Eclipse
|
||||
|
||||
When using Eclipse, there are two special build variables in the project properties
|
||||
→ C/C++ Build → Build Variables called `Q7S_SYSROOT` or `RPI_SYSROOT`. You can set
|
||||
the sysroot path in those variables to get any additional includes like `gpiod.h` in the
|
||||
Eclipse indexer.
|
Loading…
Reference in New Issue
Block a user