SPC5 MCAL overview. ZHANG Livia

Transcription

1 SPC5 MCAL overview ZHANG Livia Senior Application Engineer, Micro BU ADG Marketing and Application Greater China & South Asia Region STMicroelectronics

2 AUTOSAR Idea 2 Standardize the software architecture of ECUs Standardize configuration concepts Design the complete vehicle application software over all ECUs HW and SW will be widely independent each other Developed can be de-coupled by horizontal layers. This reduce development time and cost The reuse of software increases at OEM as well as suppliers. This enhances quality and efficiency.

3 AUTOSAR MCAL 3 Basic Software is based on standard Run-Time Environment (RTE) for separation of system into its ECU (plus common infrastructure) ECU I AUTOSAR SW-C 1 RTE Basic Software AUTOSAR SW-C 2 SW Components Application Software Component AUTOSAR Interface Actuator Software Component AUTOSAR Interface Sensor Software Component AUTOSAR Interface Runtime Environment Application Software Component Application Layer AUTOSAR Interface MCAL (Microcontroller Abstraction Layer) the lowest software layer of the Basic Software It contains internal drivers, which are software modules with direct access to the µc and internal peripherals Basic Software Services Layer ECU Abstraction Layer Microcontroller Abstraction Layer Complex Drivers Microcontroller Drivers MCU Driver Watchdog Driver GPT Driver Memory Drivers Flash Driver Fls EEprom Emu SPI Handler Driver Communication Drivers LIN Driver CAN Driver FlexRay Driver Ethernet Drive ICU Driver I/O Drivers DIO Driver ADC Driver PWM Driver PORT Driver ECU Resources Microcontroller

4 AUTOSAR SW Product Offer 4 Body Powertrain Chassis/ Safety Autosar 3.x Autosar 4.0 Autosar 4.2.x MCAL OS BSW MCAL OS BSW MCAL OS BSW Available from 3 rd Parties

5 SPC56 MCAL SW support 5 Andorra ASR2.1 ASR3.0 ASR3.2 ASR4.0.3 SPC564A Monaco SPC563M Leopard SPC56EL Pictus SPC560P Bolero 3M SPC56EC Bolero SPC560C Bolero SPC560D Bolero SPC560B All SW product in full maturity

6 Available MCAL Versions of SPC56 6 Supported MCU Supported AUTOSAR Spec. MCAL Version Andorra (2M/4M) 3.0 ASR3.0 Version ASR4.0 Version Monaco 3.0 ASR 3.0 Version ASR 3.0 Version Bolero (256K/512K/1.5M) 3.2 ASR 3.2 Version ASR 4.0 Version ASR 3.0 Version Bolero 3M 3.2 ASR 3.2 Version ASR 4.0 Version Leopard (1M) 3.0 ASR 3.0 Version ASR 4.0 Version Leopard (2M) 3.0 ASR 3.0 Version ASR 4.0 Version Pictus (1M) 3.0 ASR 3.0 Version ASR 4.0 Version Pictus (256k, 512k) 3.0 ASR 3.0 Version 1.9.0

7 SPC57/SPC58 MCAL SW support 7 Chorus SPC58_4B_EC_NG Chorus 1M SPC582B ASR4.0.3 ASR4.2.2 Eiger-Bernina SPC58_NE_NN Velvety Sphaero K2 SPC570S SPC574S SPC574K Lavaredo SPC572L All SW product in BETA maturity, full maturity is forecasted in 2017 H2 and 2018

8 Available MCAL Versions of SPC57/58 8 Supported MCU Supported AUTOSAR Spec. MCAL Version K2 (SPC574K) 4.0 ASR 4.0 Version Lavaredo (SPC572L) 4.0 ASR 4.0 Version Sphaero (SPC574S) 4.0 ASR 4.0 Version Velvety(SPC570S) 4.0 ASR 4.0 Version Chorus 1M (SPC582B) 4.0 ASR 4.0 Version Chorus_SPC58EG_EC_4B 4.0 ASR 4.0 Version ASR 4.2 Version Chorus 4M (SPC58XC) 4.0 ASR 4.0 Version TRS19 Signed Eiger(SPC58NE) 4.0 ASR 4.0 Version Bernina(SPC58XE-N) 4.0 ASR 4.0 Version Signed

9 AUTOSAR BSW from 3 rd parties 9 Vector, EB, ETAS deliver BSW validated with ST MCAL Joint integration plan review Sharing of defect database Availability in ST of the 3 rd parties development environment to quick reproduce and fix issues during the Acceptance Testing phase

10 Relationship with 3 rd parties 10 ST has a very strong relationship 3 rd parties for AUTOSAR, Safety and Security Periodic management review for delivery plan alignment Periodic technical meeting for technology roadmap review Reciprocal Access to internal and confidential contents/information Shared bug tracking system ST customer engineer assigned to 3 rd parties for ticket analysis Availability in ST of the 3 rd parties environment for a quick analysis of the customer defects

11 SW Download Center & SW License request

12 Team Space Software Download Center 12 The SW product are available through the ST Portal with controlled access. SW defects report is available through the same portal The customer shall register himself in requesting the login and create an account. The Team Space manager will grant the access to SW Download Center Team space. Then customer can access the SW Download Center team space.

13 Team Space Software Download Center 13 Select your SW product After the download of the SW Product a valid license shall be requested to APG tools

14 Team Space Software Download Center 14 Request the license key for the downloaded SW package You have to follow the installation process as shown in the pictures below. Since you don t have yet the key, you will be asked to fill a formulary with your data. This formulary has to be saved on your PC as a text file, and sent afterwards to our Tool team (APGTools-License@st.com) via mail (picture 1 and 2) If you don t have a SW contract in place, you can request only a Demo license. Following the request, in the coming days you will receive the Key, to unlock the package (picture 3) 1 2 3

15 License Product overview 15 REQUEST INSTALLATION 1 3 Specify SW request Start installation Customer Developer 4 2 Deliver SW package Select Licensing model (DEMO*/DEVELOPMENT/PRODUCTION) Accept related Disclaimer Setup and sign SW License Agreement Development Production license * Not needed for Demo license LICENSING Demo Dev Prod 5 Provide LOCK CODE 6 Verify Request Form and License rights Deliver Serial Number # Customer s Action # STMicroelectronics Action

16 Thanks for the attention