vector.com|Contact
Search tips

apple banana
Find rows that contain at least one of the two words.

+apple +juice
Find rows that contain both words.

+apple macintosh
Find rows that contain the word 'apple', but rank rows higher if they also contain 'macintosh'.

+apple -macintosh
Find rows that contain the word 'apple' but not 'macintosh'.

+apple ~macintosh
Find rows that contain the word 'apple', but if the row also contains the word 'macintosh', rate it lower than if row does not. This is "softer" than a search for '+apple -macintosh', for which the presence of 'macintosh' causes the row not to be returned at all.

+apple +(>turnover >strudel)
Find rows that contain the words 'apple' and 'turnover', or 'apple' and 'strudel' (in any order), but rank 'apple turnover' higher than 'apple strudel'.

apple*
Find rows that contain words such as 'apple', 'apples', 'applesauce', or 'applet'.

"some words"
Find rows that contain the exact phrase 'some words' (for example, rows that contain 'some words of wisdom' but not "some noise words").

By continuing to use this site you agree to the use of cookies. For more information and to find out how to change this click here. Accept Cookies
Please enable cookies in your browser for this website.
Search:
Advanced search

Cancel or Kill NvM_WriteAll to Reach Required Start-Up Times

Last updated: 2019-05-02
Issue:
Cancel or kill NvM_WriteAll for a fast restart of the ECU because of a noticed wake-up during processing NvM_WriteAll.
Solution:
If a wake-up during processing NvM_WriteAll occurs, in many cases the ECU has to reach a fast start-up time. The first message on the bus is required to be sent at the latest within a certain time. To reach this requirement, the BSW Management calls NvM_CancelWriteAll. But with this API, the NvM does not cancel the WriteAll-processing immediately. The NvM waits until the on-going job is finished. If this job is a big block or if the interface layer just has to do internal management operations like sector switch or garbage collection, it can take a longer time and you will not reach the required start-up times. 

To accelerate the start-up, MICROSAR has the possibility to cancel NvM_WriteAll hard after a certain timeout and after NvM_CancelWriteAll was called.

In BSW Management configuration editor of DavinciConfigurator Pro (Version 5 in higher), the ECU State Handling has already a pre-defined rule ESH_WaitToWakeup. This rule is executed when the ECU State handling waits until NvM_WriteAll is finished and a wake-up event is noticed during this waiting time. The rule executes an action list called ESH_AL_WaitForNvMWakeup. The action list includes an action to start a timer and to call NvM_CancelWriteAll. The duration of this timer is configurable so that you can assure your re-start requirements.


 
Configure the value of the timer to reach the required start-up times. If the timer is expired, NvM_KillWriteAll shall be called. This step is not done automatically. Therefore, add an additional user-defined rule which is executed when the CancelWriteAllTimer is expired. The user action of the rule calls NvM_KillWriteAll.
 
 
Article Options
2019-05-02
Views: 352
Error(s) occurred processing form.
Please complete all required fields. Fields marked with * are required.