ABSTRACTING INTER- PLATFORM COMMUNICATION IN
ABSTRACTING INTERPLATFORM COMMUNICATION INAUTOMOTIVESTEFAN MALINICIVALENTIN CIOCOICATALIN UDMAAMF-AUT-T2714 JUNE 2017NXP and the NXP logo are trademarks of NXP B.V. All other product or service names are the propertyof their respective owners. 2017 NXP B.V.PUBLIC
Agenda AMP Software Portfolio Motivation Solution Features ConclusionsPUBLIC1
NXP AMP SoftwareADASGPISC&SVDS(Advanced Driver Assistance Systems)(General Purpose & Integrated Solutions)(Connectivity & Security)(Vehicle Dynamics & Safety)Radar, LIDARVisionSensor FusionBody ElectronicsEdge NodesGatewayChassis & SafetyPowertrain & Hybrid/EV Linux BSP QNX SDK Vision, Radar and FusionSoftware ADAS System Tools OpenCL compiler Autosar MCAL Drivers Autosar OS S32 SDK Drivers andMiddleware IPCF S32 SDK Drivers andMiddleware Software Stacks System Tools FreeRTOS Autosar MCAL Drivers Autosar OS Security Linux BSPFreeRTOSQNX SDKAutosar MCAL DriversAutosar OSLLCESoftware StacksS32 SDK Drivers andMiddleware IPCF Autosar MCAL Drivers Autosar OS Configuration and InitializationToolsPUBLIC2
MotivationPUBLIC3
The need for inter-platform communication Multiple homogeneous orheterogeneous processing coresProcessor2xCortex-M44xCortex-A53PUBLIC4
The need for inter-platform communication Multiple homogeneous orheterogeneous processing coresLocated on a single chip or onmultiple chips in a circuit boardProcessor 12xCortex-M4Processor 22xCortex-A534xCortex-A53Processor 32xCortex-R5PUBLIC5
The need for inter-platform communication Multiple homogeneous orheterogeneous processing coresLocated on a single chip or on multiplechips in a circuit boardRunning multiple OSes AutosarOS, QNX,Processor 1Processor QNXFreeRTOS, RTEMSIntegrityProcessor 3 Linux2xCortex-R5Other OSPUBLIC6
The need for inter-platform communication Multiple homogeneous orheterogeneous processing cores Located on a single chip or on multiplechips in a circuit board Running multiple OSes Communicating over variousinterfaces:Processor 1Processor QNXPCIeShared Memory Ethernet PCIeProcessor 3Ethernet2xCortex-R5 USBOther OS UART,SPI Shared memoryPUBLIC7
Concrete Example - GatewayComm CPULINProcessing CPULINApplicationCANCAN IPCSPI IPCSPISPIETH IPCOther data IPCSPIDrivers, StacksETHApplicationSecureMCAPICANLIN IPCEth0EthernetEth0USBUSBUSBSPIUARTSPI, UARTSPIUARTMCAPICANCANData IPCforwardingEth1DataProcessingDrivers, StacksEth1RTOSHigh Level OSPUBLIC8ETH
Concrete Example: Highway Autopilot on Blue Box MiniETHLS2084ANovaTelProPak 6USBBlueBox MiniUSB HubKvaser USBto CANDrive bywireRADARAutonomousStuff ARMv8-based sensor fusion nodes (Highway SW)ROS KineticSMP Linux Ubuntu root file system HAL support packagesPCIe RCS32VAutonomousStuff ARMv8-based camera node (Highway SW)ROS KineticUbuntu LinuxMIPIPCIe BackplaneVirtual EthernetSingleCamera MIPI(replacingMobileEyeNeusoft ADASVirtual EthernetPCIe EPROS multi-machine messaging is usedto share camera node resultsPUBLIC9
Existing solutions MPI (Message Passing Interface) communication protocol for programming parallelcomputers RPC/RMI (Remote Procedure/Method Call) used in distributed computing programming dominant model in high performance computing multilanguage support: C/C , Java, Python, Ruby Implementations: openMPI, MPICH implementations: D-Bus, CORBA, Java-RMI, DCOM,Protocol BuffersRemoteDMA DDS (Data Distribution Service) useful in massively parallel computer clusters need to install a different networking infrastructure publish-subscribe middleware implementations: InfiniBand, iWARP, RoCE simplifies complex network programming fordistributed applications implementations: OpenDDS, Connext DDS, VortexOpenSplicePUBLIC10
Inter Platform Communication FrameworkPUBLIC11
ArchitectureAPIMCAPIVirtual EthernetCORE rEncryptionEndpointsChannelsISO26262OS Abstraction LayerSoC Abstraction LayerCommunication Interface Abstraction LayerARM/PowerPCETHPCIeUSBUARTSPISharedmemPUBLIC12
System Software OverviewApplicationsvSomeIP/ OpenSSLTCP/IP stackVirtual ETHMCAPIIPCFAbstraction LayerARM/PCIePowerPCUSBUARTSPISharedmemETHPUBLIC13
FeaturesPUBLIC14
API: MCAPI What is MCAPI? Standardized API for communication betweenclosely distributed embedded systemsWhy MCAPI? Multicore and Multichip Connection-oriented and Connectionless Simple and efficient Designed for low-latency, high performanceand tiny footprint Portability Standardized programming emberlist.phpPUBLIC15
MCAPI Overview Domains: multiple nodes/routingpurposes Nodes: independent thread/processor OS instance Endpoints: socket-likecommunication ports Communication-Connectionless messages-Connection-oriented packet channels-Connection-oriented scalar channelsEndpoint Attributes:- Quality of Service- Buffers- TimeoutsDomainsConnectionless- Send or receive messageswith one ore moreendpoints elsewhereNode 1Node 2Endpoint 1Endpoint 3Endpoint 2Endpoint 4Connection-oriented- Established using explicithandshake mechanismbetween endpointsPUBLIC16
Virtual Ethernet Standard API: VirtualEthernet Simplify the intercommunication specification Ease of use using standardnetwork socket No difference than standardETH interfaceApplicationsvSomeIP/ OpenSSLTCP/IP stackVirtual ETHMCAPIIPCFData-link abstraction layerARM/PowerPCPCIeUSBUARTSPIPUBLICShared mem17ETH
Virtual Ethernet - Deep Dive ifconfig pcie0 192.168.1.1 ifconfig pcie0 192.168.1.2 ping 192.168.1.2PING 192.168.1.2 56(84) bytes of data.64 bytes from 192.168.1.2: time 0.34 ms64 bytes from 192.168.1.2: time 0.35 msStandard Ethernet Linux interfaceInterfaces in LS2 LinuxInterfaces in S32V Linuxpcie0Virtual Eth InstancesImplementation:- Virtual Ethernet Network Device- PCIe driverpcie0Virtual Eth InstancesvethvethPCIe Driver (RC)PCIe Driver BLIC18
Security1. SW encryption & authenticationGenericapplicationApplications OpenSSL ReuseOpenSSLTime criticalapplicationover Virtual ETHexisting user applications1TCP/IPVirtual ETH2IPCFPlain data2SoCCryptoEngineEncrypted data2212. HW accelerated encryption &authentication fortime critical applicationsCommunicationInterfacesPUBLIC19
Defaults vs FlexibilityDefaultPlatforms Cortex A Cortex M PowerPCCortex e200Default OSes Linux QNX NXPAutosarOS freeRTOS IntegrityOS2DefaultCommunication UBLIC20
DeploymentLinux BSP kernel module user space library deployed by:Makefiles YoctoQNX/Integrity Resourcemanager shared library deployed by:Makefiles QNXmkifsAutosarOS Autosar CDD deployed by:MakefilesS32 SDK Library deployed by:Makefiles/DesignStudioDefault installation through already existing productsIf required, can be delivered as a separate installation packagePUBLIC21
Ease of UseSocket like APIPortability &FlexibilityEase of UsePluggableSamples &TutorialsPUBLIC22
ConclusionsPUBLIC23
bilityIPCFFlexible &pluggableLow latencyTiny footprintPUBLIC24
AvailabilityQ32017NG eEAREARBETApreEARpreEARpreEAREAR2019RTMRTMNG EARpreEARpreEAREARBETARTMPUBLIC25
NXP and the NXP logo are trademarks of NXP B.V. All other product or service names are the property of their respective owners. 2017 NXP B.V.
BACKUP SLIDESPUBLIC27
HeartBeatPUBLIC28
MCAPI overview MCAPI componentsDomains Domains: multiple nodes/routingpurposesNode 1Node 2Node: independent thread/processor OS instancemcapi initialize ()mcapi finalize ()PUBLIC29
MCAPI overviewEndpoints socket-like communicationterminations pointsDomainsIdentified by domain id, node id, port id Endpoint 1mcapi endpoint create ()Node 2Node 1Endpoint 3Endpoint 2mcapi endpoint delete ()mcapi endpoint get/set attribute ()Endpoint Attributes:- Quality of Service- Buffers- TimeoutsError to connect endpoints withincompatible attributesPUBLIC30
MCAPI overviewCommunication-Connectionless messages-Connection-oriented packetchannelsDomains-Connection-oriented scalarchannelsNode 1Connectionless- Send or receive messageswith one ore moreendpoints elsewhereNode 2Endpoint 1Endpoint 3Endpoint 2Endpoint 4Point-to-Point between send and receiveendpointsConnection-oriented- Established using explicithandshake mechanismbetween endpointsPUBLIC31
MCAPI overviewMessages“ i” - non-blockingDomainsmcapi msg send i ()mcapi msg send ()Node 1mcapi msg recv i ()Node 2Endpoint 1Endpoint 3Endpoint 2Endpoint 4mcapi msg recv()PUBLIC32
MCAPI overviewmcapi pktchan send open i ()mcapi pktchan send () send i ()mcapi pktchan recv () recv i ()mcapi pktchan available ()mcapi pktchan release ()mcapi pktchan recv close i ()mcapi pktchan send close i ()Send / ReceiveBuffers managementmcapi pktchan recv open i ()DomainsNode 1Node 2Endpoint 1Endpoint 3Endpoint 2Endpoint 4Connectiontear-downmcapi pktchan connect i ()ConnectionsetupPacket channelsPUBLIC33
MCAPI overviewScalar channels---Same as packet channels, use twophase setup mechanismUsed to transfer 8-, 16-, 32-, 64-bitscalarsProvides only blocking send andreceive metodsDomainsNode 1Node 2Endpoint 1Endpoint 3Endpoint 2Endpoint 4mcapi sclchan send uint8 () uint64 ()mcapi sclchan recv uint8 () uint64 ()PUBLIC34
IPCF Safety Automotive SPICE development process Functional Safety ISO26262 IPFC provided as Safety Element out of Context(ISO 26262 – 10 Clause 8) developedfor different applications and differentcustomers Hazard analysis and risk assessment FMEA - Failure Modes and Effects Analysis Assume safety requirements for ASIL-D Testing Fault injection Error guessingPUBLIC35
NXP and the NXP logo are trademarks of NXP B.V. All other product or service names are the property of their respective owners. 2017 NXP B.V.
Virtual Ethernet - Deep Dive LS2 S32V PCIe Driver (RC) S32V Interfaces in LS2 Linux pcie0 veth Virtual Eth Instances ifconfigpcie0 192.168.1.1 PCIe Driver (EP) RC Interfaces in S32V Linux pcie0 veth Virtual Eth Instances pcie0 192.168.1.2 BlueBox PCIe Communication Standard Ethernet Linux interface Impl
1. assess the processes of indexing and abstracting, and its intellectual implications in the agricultural library. 2. determine patrons levels of awareness and use of the indexed and abstracted resources. 3. identify the problems militating against the efficacy of indexing and abstracting services by patrons of library. Hypothesis
the FLccSC Learning Management System and consider taking the FCDS Abstracting Basics Course to . Always refer to the most current version of the FCDS Data Acquisition Manual when completing an abstract. The CoC STORE Manual may provide slightly different instructions for coding or abstracting of data items. However, the STORE Manual, the .
7. Communication with others inter personal communication skills Unit-III [Introduction to Mass Communication] L-12 1. Mass Communication and Origin of Media -Functions, role & impact of media 2. Meaning of Mass Communication 3. Functions of Mass Communication 4. Elements of Mass Communication 5. Brief introduction to Mass Media 6.
Fig .3 Intra communication Fig.4 Inter communication Fig.4 is used for inter vehicular communication. Data from the RF transmitter of the first vehicle is decoded by the RF receiver in the second vehicle. The decoder converts the serial input to parallel output. Then alerts the driver in the second vehicle. Using IR LED and Photodiode the
Indexing & Abstracting Of Drugs YEAR 2017 Published by LIBRARY & INFORMATION CENTRE INDIAN PHARMACOPOEIA COMMISSION Ministry of Health & Family Welfare Government of India . Efficacy and Safety of Quinolone-Containing Rescue Therapies after the Failure of Non-Bismuth
Abstracting and indexing information Journal of Clinical and Scientific Research is indexed in Index Copernicus, Academic Index, Open J-gate, Directory of Open Access Journals (DOAJ), Journal Seek, Indian Science Abstracts, Geneva Foundation for Medical Education
The Abstract 3 The abstract is usually created via cancer registry software programs, but may also be created as a paper document for later entryyp b into a computer database. Most of the data on an abstract are numerically coded . cancer. course . abstracting . .
Annual Women's Day Celebration Theme: Steadfast and Faithful Women 1993 Bethel African Methodi st Epi scopal Church Champaign, Illinois The Ministry Thi.! Rev. Sleven A. Jackson, Pastor The Rev. O.G. Monroe. Assoc, Minister The Rl. Rev. James Haskell Mayo l1 ishop, f7011rt h Episcop;l) District The Rev. Lewis E. Grady. Jr. Prc. i ding Elder . Cover design taken from: Book of Black Heroes .
