chapter15 - PacoReinaCampo/gnumig GitHub Wiki

IMPLEMENTATION

.. ....... ........ ........ ....... .. ........... ...... .... .. ...... ..... .. ..... .... ........ ... ...... . ... .... .. ......... ........... .... .... ........ .. .... . ..... ....... .... ... ........ .... ............ .. ... ... ....... .. ...... .... ... .... ....... .. ..... ... .... ....... ... ....... ......... ..... .......... ....... ..... ....... ... ....... ... ....... ..... ..... .... . ........ .. ... ..... ......... .. ........ ..... ....... .......... .......... ... ........ .. ... ..... .. ........ ..... .......... .... ... ...... .. .....

IMPLEMENTATION PROCESS

The implementation process uses the detailed design data to produce the hardware item that is an input to the testing activity.

Implementation Objectives

The objectives of the implementation process are:

A hardware item is produced which implements the hardware detailed design using representative manufacturing processes.
The hardware item implementation, assembly and installation data is complete.
Derived requirements are fed back to the detailed design process or other appropriate processes.
Requirement omissions and errors are provided to the appropriate processes for resolution.

Implementation Activities

Guidance for the implementation activities includes:

A hardware item should be produced using the design data and, where practical, the resources intended for the production product. This may include procurement, kitting, build, inspection and test.
Derived requirements generated by the implementation process should be fed back to the detailed design process or other appropriate processes.
Omissions and errors discovered during the implementation process should be provided to the appropriate process for resolution.

PRODUCTION TRANSITION PROCESS

In this process, manufacturing data, test facilities and general resources should be examined to ensure availability and suitability for production. The production transition process uses the outputs from the implementation and verification processes to move the product into production.

Production Transition Objectives

The objectives of this process are:

A baseline is established that includes all design and manufacturing data needed to support the consistent replication of the hardware item.
Manufacturing requirements related to safety are identified and documented and manufacturing controls are established.
Derived requirements are fed back to the implementation process or other appropriate processes.
Errors and omissions are provided to the appropriate processes for resolution.

Production Transition Activities

Guidance for the production transition activities includes:

Manufacturing data should be prepared from configured design data.
Manufacturing data should be checked for completeness and consistency with the configured design data.

Note: It is beyond the scope of this document to impose any conditions on the nature of the manufacturing build documentation.
Any changes or improvements that are incorporated during the production transition process should be evaluated to ensure they adhere to all product requirements, especially safety requirements. Any changes not compliant with customer or certification requirements should be approved by the relevant parties.
Manufacturing requirements pertaining to safety should be explicitly defined so they can be controlled during the production process.
Data required to develop acceptance test criteria should be determined.
Omissions or errors that are identified should be provided to the appropriate process for resolution.

ACCEPTANCE TEST

An acceptance test demonstrates that the manufactured, modified or repaired product performs in compliance with the key attributes of the unit on which certification is based. These key attributes are chosen using engineering judgement and are indicative that the product is capable of meeting the requirements to which the unit was developed.

Note 1: Configuration control of the "as built" product is not a function to be performed by the acceptance test activity. The configuration management plan, as described in Section 7 of this document, should describe how the applicant plans to perform this activity.

The scope of this document does include the determination of the acceptance test criteria, including pass/fail conditions. Production activities, including acceptance testing, are considered to be outside the scope of this document

Note 2: An acceptance test is not intended to verify all requirements on each production unit.

Subitem testing may be used as a part of the acceptance test.

Acceptance test criteria should ensure that:

Electrical tests are identified.
Environmental screening tests are identified when necessary.
The acceptance test provides coverage of those design aspects necessary to meet the safety requirements. Safety related item or subitems that are not covered by the test should be identified and other assurance means provided. These means may include analysis, design control, statistical process control or other means as appropriate.

SERIES PRODUCTION

This process is not within the scope of this document, but elements impacting design assurance are briefly described to complete the life cycle.

This process reproduces the hardware item on a routine basis that complies with the production data and requirements.

Considerations include:

Management of change of the production processes or the design provides assurance that change does not adversely impact existing safety or certification or compliance to the requirements.

Note: In addition to the guidance proposed by the body of the document, Section 11.1.1 covers Modifications to Previously Developed Hardware. When addressing component obsolescence, refer to Section 11.2.
Updating of all documentation related to changes is performed in compliance with approved configuration management plans.

Advanced Workflow {width=8cm}

MODEL

State Space Model {width=8cm}

${\dot {x} (t) = {A} (t) {x} (t) + {B} (t) {u} (t)}$

${ {y} (t) = {C} (t) {x} (t) + {D} (t) {u} (t)}$

Feedback State Space Model {width=8cm}

HARDWARE/SOFTWARE DESIGN

IMPLEMENTATION

Architecture

FRONT-END OPEN SOURCE TOOLS

4004

Hardware Engineers Compiler

Software Engineers Compiler

MSP430

Hardware Engineers Compiler

Software Engineers Compiler

OpenRISC

Hardware Engineers Compiler

Building OR1KSIM

type:

export PATH=/opt/or1k-elf-gcc/bin:${PATH}

git clone --recursive https://github.com/openrisc/or1ksim

mkdir build
cd build
../configure --target=or1k --prefix=/opt/or1k-elf-gcc
make
sudo make install

Software Engineers Compiler

Building OR1KSIM

type:

export PATH=/opt/or1k-app-gcc/bin:${PATH}

git clone --recursive https://github.com/openrisc/or1ksim

mkdir build
cd build
../configure --target=or1k --prefix=/opt/or1k-app-gcc
make
sudo make install

RISC-V

type:

sudo apt -y install device-tree-compiler
sudo apt -y install libboost-all-dev
sudo apt -y install libglib2.0-dev
sudo apt -y install libpixman-1-dev
sudo apt -y install pkg-config

Hardware Engineers Compiler: Spike

Building Proxy Kernel

type:

export PATH=/opt/riscv-elf-gcc/bin:${PATH}

git clone --recursive https://github.com/riscv/riscv-pk

cd riscv-pk
mkdir build
cd build
../configure --prefix=/opt/riscv-elf-gcc --host=riscv64-unknown-elf --with-arch=rv64gc_zifencei
make
sudo make install

Building Spike

type:

export PATH=/opt/riscv-elf-gcc/bin:${PATH}

git clone --recursive https://github.com/riscv/riscv-isa-sim

cd riscv-isa-sim
mkdir build
cd build
../configure --prefix=/opt/riscv-elf-gcc
make
sudo make install

Software Engineers Compiler: QEMU

type:

export PATH=/opt/riscv-app-gcc/bin:${PATH}

git clone --recursive https://github.com/qemu/qemu

cd qemu
./configure --prefix=/opt/riscv-app-gcc --target-list=riscv64-softmmu,riscv32-softmmu,riscv64-linux-user,riscv32-linux-user
make
sudo make install

BACK-END OPEN SOURCE TOOLS

type:

sudo apt -y install autoconf
sudo apt -y install automake
sudo apt -y install autotools-dev
sudo apt -y install curl
sudo apt -y install python3
sudo apt -y install libmpc-dev
sudo apt -y install libmpfr-dev
sudo apt -y install libgmp-dev
sudo apt -y install gawk
sudo apt -y install build-essential
sudo apt -y install bison
sudo apt -y install flex
sudo apt -y install texinfo
sudo apt -y install gperf
sudo apt -y install libtool
sudo apt -y install patchutils
sudo apt -y install bc
sudo apt -y install zlib1g-dev
sudo apt -y install libexpat-dev

4004

4004 GNU C

4004 GNU C++

4004 GNU Go

4004 GNU Rust

MSP430

MSP430 GNU C

MSP430 GNU C++

MSP430 GNU Go

MSP430 GNU Rust

OpenRISC

OpenRISC GNU C

OpenRISC GNU C++

OpenRISC GNU Go

OpenRISC GNU Rust

RISC-V

RISC-V GNU C

type:

git clone --recursive https://github.com/riscv/riscv-gnu-toolchain

cd riscv-gnu-toolchain

./configure --prefix=/opt/riscv-elf-gcc
sudo make clean
sudo make

./configure --prefix=/opt/riscv-app-gcc --enable-multilib
sudo make clean
sudo make linux

RISC-V GNU C++

type:

git clone --recursive https://github.com/riscv/riscv-gnu-toolchain

cd riscv-gnu-toolchain

./configure --prefix=/opt/riscv-elf-g++
sudo make clean
sudo make

./configure --prefix=/opt/riscv-app-g++ --enable-multilib
sudo make clean
sudo make linux

RISC-V GNU Go

type:

git clone --recursive https://go.googlesource.com/go riscv-go
cd riscv-go/src
./all.bash
cd ../..
sudo mv riscv-go /opt

chapter15 - PacoReinaCampo/gnumig GitHub Wiki

IMPLEMENTATION

IMPLEMENTATION PROCESS

Implementation Objectives

Implementation Activities

PRODUCTION TRANSITION PROCESS

Production Transition Objectives

Production Transition Activities

ACCEPTANCE TEST

SERIES PRODUCTION

FRONT-END OPEN SOURCE TOOLS

4004

Hardware Engineers Compiler

Software Engineers Compiler

MSP430

Hardware Engineers Compiler

Software Engineers Compiler

OpenRISC

Hardware Engineers Compiler

Software Engineers Compiler

RISC-V

Hardware Engineers Compiler: Spike

Software Engineers Compiler: QEMU

BACK-END OPEN SOURCE TOOLS

4004

4004 GNU C

4004 GNU C++

4004 GNU Go

4004 GNU Rust

MSP430

MSP430 GNU C

MSP430 GNU C++

MSP430 GNU Go

MSP430 GNU Rust

OpenRISC

OpenRISC GNU C

OpenRISC GNU C++

OpenRISC GNU Go

OpenRISC GNU Rust

RISC-V

RISC-V GNU C

RISC-V GNU C++

RISC-V GNU Go

RISC-V GNU Rust