Posts 1-7 of 7
Oliver Meili28 May 2010, 09:30 am
1. How is the ECU Parameter Definition File generated from the ECU Extract?
I assume you are trying to generate an ECU Configuration Description from the ECU Extract of a System Description. The Specification of System Template contains a chapter which describes the mapping of ECU configuration parameters to the corresponding elements in the Sytem Template (Harmonisation between Upstream Templates and ECU Configuration). Other information can be derived by logical combination (though this requires quite a bit of know-how of the system template and the ECU configuration).
2. On what basis does a tool decide what BSWs are required for the specific ECU?
The communication busses can easily be derived from the system template. Anything else has to be done manually in the ECU configuration step.
3. On what basis does a tool set the values for certain parameters in ECU Parameter Definition File that are not available from the ECU Extract?
Either the tool gets additional knowledge or more commonly, there is an engineer typing the information in the tool.
Markus Hardt Premium Member Group moderator28 May 2010, 12:15 pm
regarding the FrameTriggering there is according information in the ECU extract that can be used by the ECU configurator to fill the ECU Configuration Description.
JobLists etc. configurations are local to one ECU and cannot be shared via a system extract. Hence, an engineer or appropriate tooling needs to come up with a configuration afterwards.
This two step process is intended.
Oliver Meili28 May 2010, 2:11 pm
My ECU extract uses a FlexRay communication system and so I know what PDUs are used, what p parameters and g parameters are used.
But, my ECU extract does not have information regarding FrameTriggering and JobList which are used by my AUTOSAR FlexRay Interface.
How would I generate configuration structures for these?
It seems that your ECU extract is incomplete. Typically even for ECU configuration there are communication system related configuration options (PDUs, Signals, Timings, etc.) and ECU related configuration options (Callbacks, Interrupt use, etc.).
The configuration options you are referring to are system related and ought to be derived from the ECU extract as you state. You might want to talk to the provider of your ECU extract whether the information is not defined at this time or simply missing in you ECU extract (refer to system template spec, chapter 8.1, Core Communication).
Hope this helps
PS: Oops, took me too long to responde, I guess ;-)
Markus Hardt Premium Member Group moderator28 May 2010, 3:28 pm
I guess that your Windows tool is delivered with the FlexRay stack and therefore knows most of the local dependencies that have to be configured here. This will be some intellectual property that the provider doesn't want to share, I guess.
Using ARTOP will not bring the configuration description for free. ARTOP is just a framework to use AUTOSAR artifacts as datamodel of your application. It cannot provide you with the necessary configuration information of a particular BSW module.
Sign up for free: