1. - Software block schemes & diagrams - Communications protocols & data format - Conclusions EUSO-BALLOON DESIGN REVIEW, 18.12.2012, CNES TOULOUSE F. S. Cafagna I.N.F.N., Sezione di Bari, Bari (Italy) Software CPU status

2. CDR – 18.12.20122 A brief overview & block scheme CDR – 18.12.2012Software CPU status2 User Interfaces Layer. Telemetry, Console & GUI, Remote access, etc. etc. Hardware Interfaces Layer. Drivers, Readout units, etc. etc. Manager Layer. Run Control FSM, Messages, Configurations etc. etc. User Space Kernel Space

3. CDR – 18.12.20123 From the DP block scheme … CDR – 18.12.2012Software CPU status3

4. CDR – 18.12.20124.. CPU has been extracted, interfaces … CDR – 18.12.2012Software CPU status4

5. CDR – 18.12.20125 … & communication factorized CDR – 18.12.2012Software CPU status5

6. CDR – 18.12.20126 CPU software block scheme CDR – 18.12.2012Software CPU status6 Processes Managers layer Hardware Interfaces & drivers layers User Interfaces & Telemetry layer

7. CDR – 18.12.20127 CPU software block scheme Control Manager (Run Control) Implements the Run Control and supervises the whole software operations. Message Manager Marshals and routes messages between software blocks. Data Manager Provides services to efficiently manage the data handling, storage and transmission to ground. Event Builder Merges CCB, CLKB and all other relevant data into an event frame and check for consistency. Configuration Manager Stores, updates and handles configurations for all subsystems and software blocks. Log Manager Provides a log service to all the software blocks that need it. CDR – 18.12.2012Software CPU status7

8. CDR – 18.12.20128 CPU software block scheme Readout Unit Interface (RUI) Communicates with blocks external to the CPU and manages the data & command flows to and from them. Data Unit Interface (DUI) It is a special RUI dedicated to the data I/O. It is directly interfaced to the SATA or the Ethernet interfaces. Telemetry User Interface (TUI) Handles the command and data transmissions between the telemetry system (SIREN) and the CPU. User Interface (UI) Implements the communications with user and controls when the telemetry system is not connected. CDR – 18.12.2012Software CPU status8

9. CDR – 18.12.20129 CPU software blocks scheme CDR – 18.12.2012Software CPU status9 Transfer data to disk &/or telemetry Polling the CLK for triggers Request data from CCB, CLK

10. CDR – 18.12.201210 Run control Finite State Machine (FSM) CDR – 18.12.2012Software CPU status10

11. CDR – 18.12.201211 Run control Finite State Machine (FSM) CDR – 18.12.2012Software CPU status11

12. CDR – 18.12.201212 User Scenario: Normal Data Acquisition CDR – 18.12.2012Software CPU status12

13. CDR – 18.12.201213 User Scenario: Normal Data Acquisition CDR – 18.12.2012Software CPU status13 User changes detector parameters User operates runs and calibrations Quicklook & Telemetry

14. CDR – 18.12.201214 Activity diagram: Normal Data Acquisition CDR – 18.12.2012Software CPU status14

15. CDR – 18.12.201215 Activity diagram: Normal Data Acquisition CDR – 18.12.2012Software CPU status15

16. CDR – 18.12.201216 Activity diagram: Normal Data Acquisition CDR – 18.12.2012Software CPU status16

17. CDR – 18.12.201217 Activity diagram: Normal Data Acquisition CDR – 18.12.2012Software CPU status17

18. CDR – 18.12.201218 Activity diagram: Normal Data Acquisition CDR – 18.12.2012Software CPU status18

19. CDR – 18.12.201219 Activity diagram: Normal Data Acquisition CDR – 18.12.2012Software CPU status19

20. CDR – 18.12.201220 Activity diagram: Normal Data Acquisition CDR – 18.12.2012Software CPU status20

21. CDR – 18.12.201221 Activity diagram: Normal Data Acquisition CDR – 18.12.2012Software CPU status21

22. CDR – 18.12.201222 Activity diagram: Normal Data Acquisition CDR – 18.12.2012Software CPU status22

23. CDR – 18.12.201223 Activity diagram: Normal Data Acquisition CDR – 18.12.2012Software CPU status23

24. CDR – 18.12.201224 Activity diagram: Normal Data Acquisition CDR – 18.12.2012Software CPU status24

25. CDR – 18.12.201225 Activity diagram: Normal Data Acquisition CDR – 18.12.2012Software CPU status25

26. CDR – 18.12.201226 Activity diagram: Normal Data Acquisition CDR – 18.12.2012Software CPU status26

27. CDR – 18.12.201227 Activity diagram: Normal Data Acquisition CDR – 18.12.2012Software CPU status27

28. CDR – 18.12.201228 Activity diagram: Normal Data Acquisition CDR – 18.12.2012Software CPU status28

29. CDR – 18.12.201229 Communications with HK Communication between CPU and HK. Low level protocol: RS422; serial point to point, master-slave protocol. HK is the slave and respond only upon CPU request. CRC16 will be used to check for data corruption during transmission from and to HK. HK data format Data are 16 bit words while commands are encoded into a 8 bit word. The packet size range from a minimum of 5 Bytes to a maximum of 8 Bytes. CDR – 18.12.2012Software CPU status29

30. CDR – 18.12.201230 Communications with CCB (PDM) Communications between CPU and CCB Low level protocol: SpaceWire; full-duplex. Messages transmitted by the CCB to the CPU includes a CRC-32 (IEEE 802.3, Ethernet). CCB interfaces the CPU with the PDM and the SPACIROCs attached to the latter. Both command and data packets must be exchanged to configure the boards and chips, and readout physics data (~330kB/event). CCB (PDM) data format Commands are simple actions on the boards or write/read register requests on boards and chips. Different commands may have different associate parameters (data). CDR – 18.12.2012Software CPU status30

31. CDR – 18.12.201231 Communications with CLKB Communications between CPU and CLKB Low level protocol: SpaceWire; full-duplex. Messages transmitted by the CLKB to the CPU includes a CRC-32 (IEEE 802.3, Ethernet). CLKB interfaces the CPU with the GPS board. Both command and data packets must be exchanged to configure the boards, and readout GPS and trigger data (~800B/event). CLKB data format Both trigger status and GPS data are transmitted by the CLKB to the CPU. Trigger status data can be transmitted standalone: Or togheter with the GPS ones: CDR – 18.12.2012Software CPU status31

32. CDR – 18.12.201232 Conclusions −Hardware interface backbone layer developed (Spacewire, RS422) and extensive performance tests, to monitor failure rates and spot bottlenecks, are in progress. −The low level drivers and communication protocols have been tested on the flight CPU and the data acquisition chain proven to work. −The most critical part was related to the SpaceWire driver that is in charge for the bulk data exchange between the CPU and CCB. This driver is actually understood and the data transfer rate between the CCB and the CPU is almost the maximum one reachable with the SpaceWire protocol. −The low level packet formats of both commands and data have been defined for all DP components. −Continuous feedback to and from the developers to define hardware block working modes, configuration parameters, command lists etc. etc., and debug and fine tune the firmware of the HK, CCB and CLKB. CDR – 18.12.2012Software CPU status32