Mohamed Mourad Hafidhi

1. Needs and requirements analysis: Evaluate needs in terms of communication capabilities, bandwidth, reliability, etc., to define the specifications of the underwater repeater architecture. 2. FPGA architecture design: Design the overall architecture of the underwater repeater using programmable circuits (FPGA). Identify key components, interfaces, and data flows necessary to ensure reliable underwater communications. 3. VHDL coding: Develop and implement the underwater repeater architecture using the VHDL language. Write VHDL code for each component of the repeater, following the required specifications and standards. 4. Testing and simulations: Conduct thorough testing and simulations to validate the underwater repeater architecture. Use simulation tools to evaluate performance, detect potential issues, and optimize system operation. 5. Proof of Concept for architecture validation: Set up a prototype of the underwater repeater to test and demonstrate the viability of the designed architecture. Collaborate with multidisciplinary teams, including optical, software, and hardware engineers, to ensure successful integration. 6. Documentation: Document the designed architecture by creating diagrams, technical specifications, interfaces, and detailed operating procedures. Write comprehensive reports on tests, simulations, and results obtained during architecture validation.

Mission: Prototyping of the audio chain for an ASIC

Task Description:

1. Definition of audio prototyping plans and document writing:

- Analyze system audio function specifications and define prototyping requirements.

- Develop a detailed plan for testing the audio chain.

- Write technical documents, such as user manuals and test reports.

2. Development in C++ for audio functions:

- Implement required audio functions using C++.

- Ensure compatibility and interoperability with other system components.

- Perform unit tests to verify code functionality and quality.

3. Adding VHDL modules and integration into the board:

- Design and develop necessary VHDL modules for audio processing.

- Integrate VHDL modules with existing components.

- Perform simulations to validate the correct operation of VHDL modules.

4. Debug and bug fixing:

- Identify and resolve operational issues, bugs, and errors in the audio chain.

- Use debugging tools, such as logic analyzers, to find and fix problems.

- Collaborate with the team to perform validation and verification tests.

Required technical environment:

- Programming languages: VHDL, C++

- Development tools: Quartus, ALDEC

- Continuous integration tools: Jenkins

- Hardware platform: Arria10

Mission: Development and validation of Ariane 6 flight equipment

1. Definition of system verification plans and document writing:

- Analyze specifications and understand required functionalities.

- Develop a detailed verification plan by identifying necessary tests to validate the FPGA board.

- Write technical documents such as verification specifications, test procedures, and validation reports.

2. Design and development of the test/debug environment:

- Design and implement a complete test environment to verify the correct operation of the flight equipment.

- Develop debugging and testing tools using programming languages like Python.

- Create VHDL testbenches and use the UVM methodology to validate equipment functionalities.

3. Coding in VHDL:

- Implement required functionalities using VHDL.

- Ensure VHDL code complies with industry specifications and standards.

- Collaborate with other team members to ensure interoperability with other system components.

4. Validation and verification:

- Perform unit tests to verify the functionality of flight equipment components.

- Participate in integration tests to ensure all components work harmoniously together.

- Identify and resolve operational issues, bugs, and errors through in-depth debugging activities.

5. Work closely with multidisciplinary teams, including electronic, software, and systems engineers, to ensure successful equipment integration.

6. Document test results, encountered issues, and implemented solutions.