Skip to content

Commit

Permalink
Update to 2.1.0.
Browse files Browse the repository at this point in the history
  • Loading branch information
the-other-james committed Dec 4, 2017
1 parent df2f813 commit a82fb73
Show file tree
Hide file tree
Showing 269 changed files with 83,295 additions and 91,264 deletions.
10 changes: 10 additions & 0 deletions CMakeLists.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
cmake_minimum_required(VERSION 2.6.4)
project(CFS_LC C)

include_directories(fsw/mission_inc)
include_directories(fsw/platform_inc)

aux_source_directory(fsw/src APP_SRC_FILES)

# Create the app module
add_cfe_app(lc ${APP_SRC_FILES})
20 changes: 10 additions & 10 deletions cfs-lc-app-OSS-readme.txt
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
core Flight System (cFS) Limit Checker Application (LC)
Open Source Release Readme

LC Release 2.0.0
LC Release 2.1.0

Date:
February 27, 2015
August 29, 2017

Introduction:
The Limit Checker application (LC) is a core Flight System (cFS) application
Expand All @@ -24,12 +24,12 @@ Introduction:
The LC application is written in C and depends on the cFS Operating System
Abstraction Layer (OSAL) and cFE components. To build and run the LC
application, follow the cFS Deployment Guide instructions contained in
cFE-6.4.1-OSS-release/docs. There is additional LC application specific
cFE-6.5.0a-OSS-release/docs. There is additional LC application specific
configuration information contained in the application user's guide
available in cfs-lc-2.0.0-OSS-release/docs/users_guide
available in cfs-lc-2.1.0-OSS-release/docs/users_guide

There are also "Quick start" instructions provided in
cFE-6.4.1-OSS-release/cfe-OSS-readme.txt
cFE-6.5.0a-OSS-release/cfe-OSS-readme.txt

The OSAL is available at http://sourceforge.net/projects/osal/ and
github.com/nasa/
Expand All @@ -41,23 +41,23 @@ Introduction:


Software Included:
Limit Checker application (LC) 2.0.0
Limit Checker application (LC) 2.1.0


Software Required:

Operating System Abstraction Layer 4.1.1 or higher can be
Operating System Abstraction Layer 4.2.0 or higher can be
obtained at http://sourceforge.net/projects/osal or
github.com/nasa/osal

core Flight Executive 6.4.1 or higher can be obtained at
core Flight Executive 6.5.0 or higher can be obtained at
http://sorceforge.net/projects/coreflightexec


Runtime Targets Supported:
The "out of the box" targets in the cFE 6.4.1 distribution include:
The "out of the box" targets in the cFE 6.5.0 distribution include:
1. 32 bit x86 Linux ( CentOS 6.x )
2. Motorola MCP750 PowerPC vxWorks 6.4
2. Motorola MCP750 PowerPC vxWorks 6.9

Other targets:
Other targets are included, but may take additional work to
Expand Down
Binary file removed docs/CFS LCX Requirements Document V1_0 090512.docx
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file added docs/cFS LC RequirementsDocumentV1_2-082517.docx
Binary file not shown.
Binary file added docs/cFS LC RequirementsDocumentV1_2-082517.pdf
Binary file not shown.
1,849 changes: 926 additions & 923 deletions docs/dox_src/detailed_design/cfs_lc.dox

Large diffs are not rendered by default.

50 changes: 25 additions & 25 deletions docs/dox_src/mnem_maps/cfs_lc_cmd_mnem_map
Original file line number Diff line number Diff line change
@@ -1,25 +1,25 @@
#---------------------------------------------------------------------------
# Each of the following assignment statements should have the documentation
# mnemonic on the left followed by the mission specific command mnemonic
# on the right of the equals operator.
#
# FORMATTING DETAILS TO REMEMBER!
# 1) ALIASES line MUST have "+=" as the operator
# 2) There CANNOT be spaces around the "=" operator on assignment statements
# 3) Each line, EXCEPT the last, MUST have the line continuation character "\"
# at the end
# 4) NO comments, such as these, can be interspersed within the assignment
# statements
# 5) If there are multiple mnemonics for a particular data point, they should
# be separated by the following ", \b \c " and enclosed in double quotes to
# maintain proper formatting in the documentation. For example:
# ES_RESET="$sc_$cpu_ES_ProcessorReset, \b \c $sc_$cpu_ES_PowerOnReset"
#---------------------------------------------------------------------------
ALIASES += \
LC_NOOP=$sc_$cpu_LC_NOOP \
LC_RESETCTRS=$sc_$cpu_LC_ResetCtrs \
LC_SETLCSTATE=$sc_$cpu_LC_SetLCState \
LC_SETAPSTATE=$sc_$cpu_LC_SetAPState \
LC_SETAPPERMOFF=$sc_$cpu_LC_SetAPPermOff \
LC_RESETAPSTATS=$sc_$cpu_LC_ResetAPStats \
LC_RESETWPSTATS=$sc_$cpu_LC_ResetWPStats
#---------------------------------------------------------------------------
# Each of the following assignment statements should have the documentation
# mnemonic on the left followed by the mission specific command mnemonic
# on the right of the equals operator.
#
# FORMATTING DETAILS TO REMEMBER!
# 1) ALIASES line MUST have "+=" as the operator
# 2) There CANNOT be spaces around the "=" operator on assignment statements
# 3) Each line, EXCEPT the last, MUST have the line continuation character "\"
# at the end
# 4) NO comments, such as these, can be interspersed within the assignment
# statements
# 5) If there are multiple mnemonics for a particular data point, they should
# be separated by the following ", \b \c " and enclosed in double quotes to
# maintain proper formatting in the documentation. For example:
# ES_RESET="$sc_$cpu_ES_ProcessorReset, \b \c $sc_$cpu_ES_PowerOnReset"
#---------------------------------------------------------------------------
ALIASES += \
LC_NOOP=$sc_$cpu_LC_NOOP \
LC_RESETCTRS=$sc_$cpu_LC_ResetCtrs \
LC_SETLCSTATE=$sc_$cpu_LC_SetLCState \
LC_SETAPSTATE=$sc_$cpu_LC_SetAPState \
LC_SETAPPERMOFF=$sc_$cpu_LC_SetAPPermOff \
LC_RESETAPSTATS=$sc_$cpu_LC_ResetAPStats \
LC_RESETWPSTATS=$sc_$cpu_LC_ResetWPStats
58 changes: 29 additions & 29 deletions docs/dox_src/mnem_maps/cfs_lc_tlm_mnem_map
Original file line number Diff line number Diff line change
@@ -1,29 +1,29 @@
#---------------------------------------------------------------------------
# Each of the following assignment statements should have the documentation
# mnemonic on the left followed by the mission specific telemetry mnemonic
# on the right of the equals operator.
#
# FORMATTING DETAILS TO REMEMBER!
# 1) ALIASES line MUST have "+=" as the operator
# 2) There CANNOT be spaces around the "=" operator on assignment statements
# 3) Each line, EXCEPT the last, MUST have the line continuation character "\"
# at the end
# 4) NO comments, such as these, can be interspersed within the assignment
# statements
# 5) If there are multiple mnemonics for a particular data point, they should
# be separated by the following ", \b \c " and enclosed in double quotes to
# maintain proper formatting in the documentation. For example:
# ES_RESET="$sc_$cpu_ES_ProcessorReset, \b \c $sc_$cpu_ES_PowerOnReset"
#---------------------------------------------------------------------------
ALIASES += \
LC_CMDPC=$sc_$cpu_LC_CMDPC \
LC_CMDEC=$sc_$cpu_LC_CMDEC \
LC_APSAMPLECNT=$sc_$cpu_LC_APSampleCnt \
LC_MONMSGCNT=$sc_$cpu_LC_MonMsgCnt \
LC_RTSCNT=$sc_$cpu_LC_RTSCnt \
LC_PASSRTSCNT=$sc_$cpu_LC_PassRTSCnt \
LC_WPSINUSE=$sc_$cpu_LC_WPsInUse \
LC_ACTIVEAPS=$sc_$cpu_LC_ActiveAPs \
LC_CURLCSTATE=$sc_$cpu_LC_CurrentLCState \
LC_WPRESULTS=$sc_$cpu_LC_WPResults \
LC_APRESULTS=$sc_$cpu_LC_APResults
#---------------------------------------------------------------------------
# Each of the following assignment statements should have the documentation
# mnemonic on the left followed by the mission specific telemetry mnemonic
# on the right of the equals operator.
#
# FORMATTING DETAILS TO REMEMBER!
# 1) ALIASES line MUST have "+=" as the operator
# 2) There CANNOT be spaces around the "=" operator on assignment statements
# 3) Each line, EXCEPT the last, MUST have the line continuation character "\"
# at the end
# 4) NO comments, such as these, can be interspersed within the assignment
# statements
# 5) If there are multiple mnemonics for a particular data point, they should
# be separated by the following ", \b \c " and enclosed in double quotes to
# maintain proper formatting in the documentation. For example:
# ES_RESET="$sc_$cpu_ES_ProcessorReset, \b \c $sc_$cpu_ES_PowerOnReset"
#---------------------------------------------------------------------------
ALIASES += \
LC_CMDPC=$sc_$cpu_LC_CMDPC \
LC_CMDEC=$sc_$cpu_LC_CMDEC \
LC_APSAMPLECNT=$sc_$cpu_LC_APSampleCnt \
LC_MONMSGCNT=$sc_$cpu_LC_MonMsgCnt \
LC_RTSCNT=$sc_$cpu_LC_RTSCnt \
LC_PASSRTSCNT=$sc_$cpu_LC_PassRTSCnt \
LC_WPSINUSE=$sc_$cpu_LC_WPsInUse \
LC_ACTIVEAPS=$sc_$cpu_LC_ActiveAPs \
LC_CURLCSTATE=$sc_$cpu_LC_CurrentLCState \
LC_WPRESULTS=$sc_$cpu_LC_WPResults \
LC_APRESULTS=$sc_$cpu_LC_APResults
Loading

0 comments on commit a82fb73

Please sign in to comment.