Changes between Version 372 and Version 373 of Developer/OpenProjects


Ignore:
Timestamp:
Feb 10, 2015, 1:15:48 AM (5 years ago)
Author:
Joel Sherrill
Comment:

Update

Legend:

Unmodified
Added
Removed
Modified
  • Developer/OpenProjects

    v372 v373  
    2929  *  [wiki:Developer/Testing/Specifications RTEMS Test Specification] - Need a formal test specification.  Ideally, inspired by http://softwaretestingstandard.org/ some notes about existing test specifications can be found http://www.rtems.org/wiki/index.php/GoogleCodeInProjects#Test_Documentation_Files_update .
    3030  *  [wiki:RTEMS_Test_Screen_Validation RTEMS Test Screen Validation] - This requires expertise in a unit testing framework, probably DejaGnu, and will probably need to be tied into [http://git.rtems.org/rtems-testing/ rtems-testing].
    31  *  '''[wiki:TBR/UserManual/RTEMS_Coverage_Analysis  Test Coverage Analysis]''' - Improve coverage by adding more test cases. Eliminating dead code and reaching 100% coverage helps reduce the likelihood of new and recurrent bugs. (SOCIS)
    32   *  Test the [wiki:Projects/POSIXFIFOs  POSIX FIFO Implementation].
    33   *  [wiki:GSoC/2011/gprof  Add support for gprof output to covoar]
    34   *  ''Add [wiki:GSoC/2011/gcov  support for gcov output] to covoar so tools like gcov and lcov can be used with RTEMS ([wiki:Projects/GCOVSupport another page here])'' GCOV support could use work and generation of gcov reports as part of our output.
    35   * Complete conversion of coverage reporting to Python and integration into RTEMS Tools. SOCIS 2014 code works but is not production worthy.
     31 *  '''[wiki:TBR/UserManual/RTEMS_Coverage_Analysis  Test Coverage Analysis]''' - In general, there are specific areas that need actual tests written and areas in which the RTEMS Project tools need work to improve our testing ability. Look until Tools and Development Environment for those projects. This section focuses on improvements to coverage by adding more test cases, reworking code to eliminate the need for additional test cases, etc.. Eliminating dead code and reaching 100% coverage helps reduce the likelihood of new and recurrent bugs.
     32 *  [wiki:Projects/Open/SimulatorUpdates Simulator Updates] - Test BSPs that target simulators to find and fix problems. It is important to ensure that BSPs which run on simulators pass all tests possible.
     33 *  Test the [wiki:Projects/POSIXFIFOs  POSIX FIFO Implementation].
     34
     35 *  Improve [wiki:Projects/GNUToolsTesting  Testing of the GNU Tools] on RTEMS targets
     36 *  ''[wiki:TBR/Delete/POSIXTimingTests  POSIX Timing Tests]'' - Many have been implemented but there should be more cases worth timing. Precise status is stored in a .csv file in the psxtmtests directory in the source tree.
     37 *  ''[wiki:Projects/POSIXComplianceTestSuite  POSIX Compliance Test Suite]'' There are multiple aspects to this project. One aspect is the addition of interface compliance tests for rest of POSIX API. Another part is running third party C Library and POSIX API tests (e.g. from glibc, *BSD, or the older Intel POSIX suite)  against RTEMS and newlib. Ultimately, we would like functional coverage test results on newlib as well as RTEMS. Results of third party existing tests would have to be carefully evaluated to ensure appropriateness and results.
    3638 *  [wiki:TBR/Delete/Fault_injection Fault tolerance]: get a fault injection tool to work with RTEMS and create tutorials and examples.
    37  *  Improve [wiki:Projects/GNUToolsTesting  Testing of the GNU Tools] on RTEMS targets
    38  *  ''[wiki:TBR/Delete/POSIXTimingTests  POSIX Timing Tests]''
    39  *  ''[wiki:Projects/POSIXComplianceTestSuite  POSIX Compliance Test Suite]'' Add interface compliance tests for rest of POSIX API.
    40  *  [wiki:Projects/Open/SimulatorUpdates Simulator Updates] - Test BSPs that target simulators to find and fix problems. (SOCIS)
    41  * '''RTEMS Tester - rtems-test improvements''' - Add simulator recipes for more simulators. Many more are supported by older simscripts.
    4239
    4340= Tools and Development Environment =
     
    4643
    4744The following areas have been identified for projects related to improving RTEMS development:
     45
     46 *  Develop a tool for static analysis of stack usage. GCC can produce a ".su" file when used with the -fstack-use option. cflow can be used to produce the control flow to analyze a call stack. The goal of this analysis is for a user to be able to specify a user thread entry point and see the stack usage for each method that thread calls as well as a total usage. This should include application code, RTEMS, and newlib. The scripting will be in Python. cflow will need to be added as an RSB recipe.
     47 *  Improvements in RTEMS Tools for execution and analysis of both functional test results and coverage analysis.
     48   * Complete conversion of coverage reporting to Python and integration into RTEMS Tools. SOCIS 2014 code works but is not production worthy.
     49   * '''RTEMS Tester - rtems-test improvements''' - Add simulator recipes for more simulators. Many more are supported by older sim-scripts.
     50   *  Use gcov output as generated by covoar to generate useful reports.  This leverages work by [wiki:GSoC/2011/gcov  support for gcov output] to so tools like gcov and lcov can be used to generate standard coverage reports for RTEMS ([wiki:Projects/GCOVSupport another page here])'' This type of reporting is important for safety certification reviews.
     51   *  Use gprof output as generated by covoar to generate useful reports.  This is based on the previous project [wiki:GSoC/2011/gprof  Add support for gprof output to covoar]
     52 *  [wiki:TBR/UserManual/RTEMS_Source_Builder RTEMS Source Builder] improvements such as building host tools, building a GUI, and improving configuration management and creation.   
    4853 *  Improvements in the [wiki:Developer/Eclipse/Information RTEMS Eclipse Integration].
    4954 *  Compiling RTEMS with [wiki:Projects/CLANG CLANG].
    50  *  [wiki:Projects/Leon_rtems_merge  Merge Leon RTEMS and mainstream RTEMS] merge the Leon [wiki:TBR/UserManual/DriverManager DriverManager], [http://gaisler.com/anonftp/rcc/src/ samples], and [https://github.com/daniel-hellstrom/leon-rtems/tree/master/c/src/lib LEON-RTEMS] into mainstream RTEMS. (SOCIS)
     55 *  [wiki:Projects/Leon_rtems_merge  Merge Leon RTEMS and mainstream RTEMS] merge the Leon [wiki:TBR/UserManual/DriverManager DriverManager], [http://gaisler.com/anonftp/rcc/src/ samples], and [https://github.com/daniel-hellstrom/leon-rtems/tree/master/c/src/lib LEON-RTEMS] into mainstream RTEMS.
    5156 *  Integration of RTEMS cross development environment into [wiki:Projects/EVisualStudio  eVisual Studio]
    5257 *  [wiki:Projects/ArgoUML  ArgoUML RTEMS Support]
    5358 *  [wiki:Projects/GDB_Python GDB Python] Script support for RTEMS
    54  *  [wiki:TBR/UserManual/RTEMS_Source_Builder RTEMS Source Builder] improvements such as building host tools, building a GUI, and improving configuration management and creation.
     59
    5560
    5661= RTEMS Run-Time Oriented =
     
    7378
    7479 *  '''[wiki:Projects/TraceTool  Run-Time Tracing]''' - includes gathering, capturing, and displaying information to the user.  We are looking for more trace improvements and visualization.
    75  *  [wiki:Projects/CPU_Statistics CPU Statistics] - Improvements to CPU Usage Statistics. (SOCIS)
    76  *  [wiki:Projects/Open/StackChecker Stack Checker] - Improvements to Stack Bounds Checker. (SOCIS)
     80 *  [wiki:Projects/CPU_Statistics CPU Statistics] - Improvements to CPU Usage Statistics.
     81 *  [wiki:Projects/Open/StackChecker Stack Checker] - Improvements to Stack Bounds Checker.
    7782
    7883= Board Support Package (BSP) =
     
    8489 *  ''[wiki:Projects/GSoC/Beagle Beagle BSP improvements]'' - More peripherals for the Beagleboard / Beaglebone BSP and other improvements
    8590 * VESA x86 BIOS - This is Pavel Pisa's idea.
    86  * x86 Edison
     91 * Raspberry Pi2 - on hold due to unavailability of open information
     92 * x86 Edison - on hold due to unavailability of open information
    8793
    8894= API Layers (POSIX, Classic, SAPI) =
     
    97103= rtems-libbsd =
    98104
    99  *  ''[wiki:Projects/TCP/IP_update  Update the RTEMS TCP/IP stack]'' - The networking stack is old and showing it. This project is actively underway.  At a high level, this effort requires porting the TCP/IP stack and providing support functional equivalents of multiple BSD kernel constructs.  This project has many subprojects many of which are appropriate for SOC.
    100  *  ''[wiki:TBR/UserManual/USBStack  port BSD USB stack]''
     105 *  ''[wiki:Projects/TCP/IP_update  Update the RTEMS TCP/IP stack]'' - The networking stack in the main source tree is old and showing it. This project is actively underway.  At a high level, this effort requires porting the TCP/IP stack and providing support functional equivalents of multiple BSD kernel constructs.  This project has many subprojects many of which may be appropriate for SOC. Given that the stack is working now along with USB, ask about possibilities about Ethernet over USB and Wifi support.
     106 *  ''[wiki:TBR/UserManual/USBStack  port BSD USB stack]'' - This project is complete for some device types. Needs documentation and possible addition of other device types.
    101107
    102108= Languages =