spc5 mcal overview - stmicroelectronics · spc5 mcal overview zhang livia senior application...
TRANSCRIPT
SPC5 MCAL overviewZHANG Livia
Senior Application Engineer, Micro BUADG Marketing and ApplicationGreater China & South Asia RegionSTMicroelectronics
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.
AUTOSAR MCAL• Basic Software is based on standard
• Run-Time Environment (RTE) for separation of system into its ECU (plus common infrastructure)
3
ECU I
AUTOSAR SW-C 1
AUTOSAR SW-C 2
RTEBasic
Software
Bas
ic S
oftw
are
SWC
ompo
nent
sEC
U
Res
ourc
es
Com-plex
Drivers
Microcontroller
Microcontroller Abstraction Layer
Services Layer
Application Layer
Runtime Environment
ECU Abstraction Layer
ActuatorSoftware
Component
SensorSoftware
Component
ApplicationSoftware
Component
AUTOSARInterface
AUTOSARInterface
AUTOSARInterface
ApplicationSoftware
Component
AUTOSARInterface
I/O Drivers
AD
C D
river
DIO
Driver
PW
M D
river
ICU
Driver
Microcontroller Drivers Communication Drivers
Memory Drivers
Flash Driver
Watchdog D
river
MC
U D
river
GP
T Driver
CA
N D
river
LIN D
river
FlexRay D
river
SP
I Handler D
river
Ethernet D
rive
PO
RT D
river
• 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
FlsE
Eprom
Em
u
AUTOSAR SW Product Offer 4
Autosar 3.xAutosar 4.0Autosar 4.2.x
Body Powertrain Chassis/Safety
MCAL
OS
BSW
MCAL
OS
BSW
MCAL
OS
BSW
Available from 3rd Parties
SPC56 MCAL SW support 5
ASR2.1 ASR3.0Andorra
SPC564A
Monaco
SPC563M
Leopard
SPC56EL
Pictus
SPC560P
Bolero 3M
SPC56EC
Bolero
SPC560C
Bolero
SPC560D
Bolero
SPC560B
ASR3.2 ASR4.0.3
All SW product in full maturity
Available MCAL Versions of SPC56 6
Supported MCU Supported AUTOSAR Spec. MCAL Version
Andorra (2M/4M)3.0 ASR3.0 Version 2.0.1
4.0 ASR4.0 Version 1.0.0
Monaco 3.0 ASR 3.0 Version 2.0.0
Bolero (256K/512K/1.5M)
3.0 ASR 3.0 Version 3.0.6
3.2 ASR 3.2 Version 1.0.2
4.0 ASR 4.0 Version 1.0.1
Bolero 3M
3.0 ASR 3.0 Version 1.0.2
3.2 ASR 3.2 Version 1.0.0
4.0 ASR 4.0 Version 1.0.1
Leopard (1M)3.0 ASR 3.0 Version 1.0.3
4.0 ASR 4.0 Version 1.0.1
Leopard (2M)3.0 ASR 3.0 Version 1.0.0
4.0 ASR 4.0 Version 1.0.1
Pictus (1M)3.0 ASR 3.0 Version 3.0.1
4.0 ASR 4.0 Version 1.0.1
Pictus (256k, 512k) 3.0 ASR 3.0 Version 1.9.0
SPC57/SPC58 MCAL SW support 7
All SW product in BETA maturity, full maturity is forecasted in 2017 H2 and 2018
ASR4.0.3Chorus
SPC58_4B_EC_NG
Chorus 1M
SPC582B
Eiger-Bernina
SPC58_NE_NN
Velvety
SPC570S
Sphaero
SPC574S
K2
SPC574K
Lavaredo
SPC572L
ASR4.2.2
Available MCAL Versions of SPC57/58 8
Supported MCU Supported AUTOSAR Spec. MCAL Version
K2 (SPC574K) 4.0 ASR 4.0 Version 0.9.0
Lavaredo (SPC572L) 4.0 ASR 4.0 Version 0.8.0
Sphaero (SPC574S) 4.0 ASR 4.0 Version 0.9.1
Velvety(SPC570S) 4.0 ASR 4.0 Version 0.8.0
Chorus 1M (SPC582B) 4.0 ASR 4.0 Version 0.8.1
Chorus_SPC58EG_EC_4B 4.0 ASR 4.0 Version 0.9.1
4.2 ASR 4.2 Version 0.8.0
Chorus 4M (SPC58XC) 4.0 ASR 4.0 Version 0.9.0 TRS19 Signed
Eiger(SPC58NE) 4.0 ASR 4.0 Version 0.9.0
Bernina(SPC58XE-N) 4.0 ASR 4.0 Version 0.9.0 Signed
AUTOSAR BSW from 3rd parties
• Vector, EB, ETAS deliver BSW validated with ST MCAL
• Joint integration plan review
• Sharing of defect database
• Availability in ST of the 3rd parties development environment to quick reproduce and fix issues during the Acceptance Testing phase
9
Relationship with 3rd parties• ST has a very strong relationship 3rd 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 3rd parties for ticket analysis• Availability in ST of the 3rd parties environment for a quick analysis of the customer defects
10
SW Download Center &SW License request
• 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 www.st.com, 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.• https://my.st.com/collab/APG_SOFTWARE/SW_DC/default.aspx
Team Space – Software Download Center 12
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
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 ([email protected]) 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
License Product overview 15
Customer Developer
Demo
Dev
Prod
Verify Request Form and License rightsDeliver Serial Number
Provide LOCK CODE
Deliver SW package
REQ
UES
TIN
STA
LLA
TIO
NLI
CEN
SIN
G
Select Licensing model (DEMO*/DEVELOPMENT/PRODUCTION)Accept related Disclaimer
Start installation2
Specify SW request1
3
4
5
6# Customer‘s Action # STMicroelectronics‘ Action
DevelopmentProduction
license
Setup and signSW License Agreement
* Not needed for Demo license
Thanks for the attention