Command Module Prototype Board 2 prototype boards produced

  • Slides: 6
Download presentation
Command Module – Prototype Board • 2 prototype boards produced: See webpage: https: //mdttp.

Command Module – Prototype Board • 2 prototype boards produced: See webpage: https: //mdttp. docs. cern. ch/Hardware/Command%20 Module/Demonstrator/dem/ https: //www. mpp. mpg. de/~fras/projects/ATLAS/MDT_II/Trigger/MDT_TP/docs/Hardware/CM/Demonstrator/Prototype_1/

Command Module – Test Plan • Two engineers from Pro. Design and MPI sharing

Command Module – Test Plan • Two engineers from Pro. Design and MPI sharing work for testing the board: – Mr. Kohl: Board bring-up, power, et cetera – Mr. Stacheter: MCU and software – MPI: MCU, software, et cetera • Documents: – L 0 MDT CM Demonstrator Testing (MPI) https: //nextcloud. mpp. mpg. de/nextcloud/index. php/s/As. Z 4 Zy. L JMF 6 Zm. A 4 – MPIP 001 Bring-up Test List (Pro. Design) https: //mdttp-files. web. cern. ch/mdttpfiles/L 0 MDT/Demonstrator/CM/doc/Testing/MPIP 001_bringup_test_list. xlsx • Regular meetings once or twice a week.

Command Module – Test Preparation • KU 15 P firmware projects done by Mr.

Command Module – Test Preparation • KU 15 P firmware projects done by Mr. Kohl. • MCU firmware and software done by MPI: – https: //github. com/mppmu/mdt-tp-cm-mcu – All GPIOs, I 2 C busses and UARTs implemented. – Simple user interface. – Python 3 classes: • Serial user interface. • I 2 C busses and devices: muxes, clock generators, temp. sensors, I/O expanders. • UARTs. – First simple HW test script and module for running MCU command batch files: • Python 3, compatible with test environment of Pro. Design. • Optional simulated HW access.

Command Module – Test Preparation Next Steps: • Firmware: – FPGA: • ZU 11

Command Module – Test Preparation Next Steps: • Firmware: – FPGA: • ZU 11 EG test firmware projects. • Unified test FW for KU 15 P and ZU 11 EG (long term, with help of FW-developers). – MCU: • • Automatic checks of power and temperatures. Power-up sequences. Switching of UARTs. QSPI support for flash memory. • Software: – Libraries for all HW components. – Full test script probing the complete chain of slow-control devices. – Automated board configuration and monitoring. • HW tests: – – – Program and verify all power supplies. Program and test all clock devices. MCU firmware download and debugging, user interface and peripheral devices. FPGA boot (JTAG, QSPI, µSD card). FPGA features (IOs, Ser. Des, Zynq PS, DDR 4 memory, power/cooling). Etc. : Fire. Flys, communication with SM, SMA and expansion connectors, … … …

Command Module – Test Results • Issues found so far: – Switch-off / oscillation

Command Module – Test Results • Issues found so far: – Switch-off / oscillation in main +12 V supply => Fixed by additional filter circuit. – Cross-flow on 1. 8 V supply of Fire. Flys from I 2 C => Ignored for now, as it is high-ohmic. => Use isolator ICs in 2 nd-step protoype. – Access to program connector of MCU blocked by jumpers. => Stand-off adapter built at MPI and sent to Pro. Design. – Light guides for LEDs not available. => Under investigation by Mr. Kohl.

Command Module – Conclusions • Basic test plan available. => Test report for every

Command Module – Conclusions • Basic test plan available. => Test report for every module. • A lot of firmware and software required. => Good investment for later operation. • Complex test scenario. => Delivery may be delayed. • Critical mistakes found on 1 rst-step Prototype. => 2 nd-Step prototype required.