System Architecture Design

More documents

Recommendations

Info

pSHIELDSystem Architecture DesignPUThe standard interface to access configuration registers of the FPGA is the JTAG port and it is used towrite on it the binary file produced by the compiler.The Power Node uses a USB-JTAG converter to grant OS the access to HW reconfiguration. Theconverter is integrated on the Power Node board. This solution has been adopted on both release of theprototype to simplify and improve the development and debug process. A second solution, that doesn’trequire the USB-JTAG converter, could be adopted in future versions of the prototype that will be closer toa final product. The current hardware already allows the implementation of this solution that, in terms offunctionalities, is perfectly equivalent to the one adopted. This second solution is based on the directreconfiguration of the FPGA through the PCi Express bus. A software application is capable to store theFPGA binary images into the Flash memory connected to the FPGA, and chooses the most suitableimage depending on the threat identified. In this case, a specific operating system driver must beimplemented to control the PCi Express bus and an engine that acts as a bridge between the bus itselfand the flash memory, must be implemented into the FPGA and added to the FPGA application specificlogic.The reconfigurability features offered by the Power Node can be used in a real application scenario asfollows:1. A threat is identified by proper application logic2. The application, depending on the threat, decides if a reconfiguration of the FPGA is required3. The operating system stops processes that use the current hardware configuration4. The application chooses the new configuration capable to face the threat5. The selected configuration is written via JTAG to the FPGAThe operating system starts new processes associated with the new HW configuration.6.1.3.4 Technical SpecificationsIn terms of technical specifications, the Power Node will feature:• 2 Intel Xeon 5570/5680 CPUs at 2.93/3.33GHz• At least 6GB RAM 1333MHz DDR3• Optional FPGA device, which allows implementation of: Hardware accelerator features (on board co-processing) Synchronization network for multi node mode• Custom processing units• Optional 80GB 1.8” SATA SSD• Independent sensor network and monitoring system• Connectivity via two additional debugging board that will bring the signal on standard connectorsfor an easier access by the user• QDR Infiniband port• LAN 10/100/1000 Interface• VGA Analog Video output• 2x USB 2.0 host interfacePhysical Specifications:PUD2.3.2Issue 5 Page 88 of 122
pSHIELDSystem Architecture DesignPU• Physical dimensions: 166mm h x 25,4mm w x 500mm d• Weight: 2.2 Kg (with cooling system)Power Specifications:• Power consumption: 350W typical (420W Max)• Power Supply Voltage 12V6.2 Network Layer HW/SW6.2.1 pSHIELD Network Layer and pSHIELD Network AdapterIn section 3.3, the terms and definitions of Network Layer were defined, along with the specificimplementation features, which constitute the targeting core networking capabilities of a pSHIELDsystem. Also, throughout section 6.5, the stepped procedure of defining a conceptual architecture isdescribed. Based on and “modifying” OSI model pSHIELD adopts the four layered approach, thoroughlydescribed previously. Abstracting the network layer component, from the general conceptual architecturalFigure 50:Figure 23 - pSHIELD Network Layer: Adapter and Legacy.It can be deduced, that the pSHIELD Network Layer is constituted from a general sum of Legacy NetworkServices and the pSHIELD Network Adapter, responsible for adding innovative SPD functionalities in thesystem and being, practically, the main component implementing this Layer in the overall architecture.Repeating from the reference architecture:The pSHIELD Network Adapter includes a set of Innovative SPD functionalities interoperating with thelegacy ESD network services (through the NS interface) and the pSHIELD Node Adapter (through the pS-NC interface) in order to enhance them with the pSHIELD Network layer SPD enabling technologies (suchas Smart Transmission). This adapter is also in charge to provide (through the pS-NS interface) all theneeded information to the pSHIELD Middleware adapter to enable the SPD composability of the Networklayer legacy and Network pSHIELD-specific functionalities. Moreover, the pSHIELD Network Adaptertranslates the technology independent commands, configurations and decisions coming from the pS-NSinterface into technology dependent ones and enforce them also to the legacy Network functionalitiesthrough the NS interface. The exact list of functionalities and services has to be determined in the processof this study.The Legacy Network Services includes all the legacy network services (protocol stacks, routing,scheduling, Quality of Service, admission control, traffic shaping, etc.) provided by the Legacy EmbeddedPUD2.3.2Issue 5 Page 89 of 122
Page 1 and 2:
Project no: 100204pSHIELDpilot embe
Page 3 and 4:
Contents1 Executive Summary .......
Page 5 and 6:
FiguresFigure 1 - A generic embedde
Page 7 and 8:
Figure 45 - pSHIELD Security Agent
Page 9 and 10:
MGFMIPSMLNeLNFMRFPNMPNMPSNoLNVMOLOS
Page 11 and 12:
Issue 5Page xi
Page 13 and 14:
pSHIELDSystem Architecture DesignPU
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
pSHIELDSystem Architecture Design3.
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
pSHIELDSystem Architecture Design
Page 33 and 34:
Page 35 and 36:
Page 37 and 38: pSHIELDSystem Architecture DesignPU
Page 39 and 40: pSHIELDSystem Architecture Design
Page 47 and 48: pSHIELDSystem Architecture Designen
Page 75: pSHIELDSystem Architecture DesignPU
Page 82: pSHIELDSystem Architecture DesignPU
show all

System Architecture Design

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?