host build note
This commit is contained in:
parent
1aa7636151
commit
16e8e9829a
23
README.md
23
README.md
@ -41,7 +41,7 @@ npm install --global xpm
|
|||||||
xpm install --global @xpack-dev-tools/windows-build-tools@latest
|
xpm install --global @xpack-dev-tools/windows-build-tools@latest
|
||||||
```
|
```
|
||||||
|
|
||||||
### Building the software
|
## Building the software
|
||||||
|
|
||||||
1. Clone the repository with
|
1. Clone the repository with
|
||||||
```sh
|
```sh
|
||||||
@ -69,7 +69,7 @@ git submodule update
|
|||||||
* As build command type: <path to make>\make -j all WINDOWS=1
|
* As build command type: <path to make>\make -j all WINDOWS=1
|
||||||
7. Run build command (double click the generated target)
|
7. Run build command (double click the generated target)
|
||||||
|
|
||||||
### Debugging the software (when workstation is directly conncected to Q7S)
|
## Debugging the software (when workstation is directly conncected to Q7S)
|
||||||
1. Assign static IP address to Q7S
|
1. Assign static IP address to Q7S
|
||||||
* Open serial console of Q7S (Accessible via the micro-USB of the PIM, see also Q7S user maunal chapter 10.3)
|
* Open serial console of Q7S (Accessible via the micro-USB of the PIM, see also Q7S user maunal chapter 10.3)
|
||||||
* Baudrate 115200
|
* Baudrate 115200
|
||||||
@ -118,7 +118,7 @@ git submodule update
|
|||||||
* Local File Path: Path to eiveobsw-linux.elf (in _bin\linux\devel)
|
* Local File Path: Path to eiveobsw-linux.elf (in _bin\linux\devel)
|
||||||
* Remote File Path: /tmp/eive_obsw.elf
|
* Remote File Path: /tmp/eive_obsw.elf
|
||||||
|
|
||||||
### Debugging the software via Flatsat PC
|
## Debugging the software via Flatsat PC
|
||||||
Open SSH connection to flatsat PC:
|
Open SSH connection to flatsat PC:
|
||||||
````
|
````
|
||||||
ssh eive@2001:7c0:2018:1099:babe:0:e1fe:f1a5
|
ssh eive@2001:7c0:2018:1099:babe:0:e1fe:f1a5
|
||||||
@ -146,7 +146,7 @@ Note: When now setting up a debug session in the Xilinx SDK, the host must be se
|
|||||||
of the Q7S.
|
of the Q7S.
|
||||||
|
|
||||||
|
|
||||||
### Launching an application after boot
|
## Launching an application after boot
|
||||||
Load the root partiton from the flash memory (there are to nor-flash memories and each flash holds two xdi images).
|
Load the root partiton from the flash memory (there are to nor-flash memories and each flash holds two xdi images).
|
||||||
Note: It is not possible to modify the current loaded root partition.
|
Note: It is not possible to modify the current loaded root partition.
|
||||||
1. Disable write protection of the desired root partition
|
1. Disable write protection of the desired root partition
|
||||||
@ -205,7 +205,7 @@ More detailed information about the used q7s commands can be found in the Q7S us
|
|||||||
writeprotect 0 0 0 # qspi0 nom unlock (see also Q7S user manual)
|
writeprotect 0 0 0 # qspi0 nom unlock (see also Q7S user manual)
|
||||||
````
|
````
|
||||||
|
|
||||||
### Setting up UNIX environment for real-time functionalities
|
## Setting up UNIX environment for real-time functionalities
|
||||||
Please note that on most UNIX environments (e.g. Ubuntu), the real time functionalities
|
Please note that on most UNIX environments (e.g. Ubuntu), the real time functionalities
|
||||||
used by the UNIX pthread module are restricted, which will lead to permission errors when creating these tasks
|
used by the UNIX pthread module are restricted, which will lead to permission errors when creating these tasks
|
||||||
and configuring real-time properites like scheduling priorities.
|
and configuring real-time properites like scheduling priorities.
|
||||||
@ -264,7 +264,18 @@ a permanent solution). If running the script before executing the binary does
|
|||||||
not help or an warning is issue that the soft real time value is invalid,
|
not help or an warning is issue that the soft real time value is invalid,
|
||||||
the hard real-time limit of the system might not be high enough (see step 1).
|
the hard real-time limit of the system might not be high enough (see step 1).
|
||||||
|
|
||||||
### Flight Software Framework (FSFW)
|
## Building and running the software on a host system
|
||||||
|
|
||||||
|
The host build can be built with following command
|
||||||
|
|
||||||
|
```sh
|
||||||
|
make all -j
|
||||||
|
```
|
||||||
|
|
||||||
|
If compiling on Windows, it is recommended to supply `WINDOWS=1` .
|
||||||
|
A release build can be built by using the `mission` target.
|
||||||
|
|
||||||
|
## Flight Software Framework (FSFW)
|
||||||
|
|
||||||
An EIVE fork of the FSFW is submodules into this repository.
|
An EIVE fork of the FSFW is submodules into this repository.
|
||||||
To add the master upstream branch and merge changes and updates from it
|
To add the master upstream branch and merge changes and updates from it
|
||||||
|
Loading…
Reference in New Issue
Block a user