MotoHawk-FAQ: Difference between revisions
Jump to navigation
Jump to search
m (/* There are some tasks I need to perform when an app is booting up on an ECM that has never had my application on it before. In other words, it's either a blank ECM or has had some other application on it. I need to do some memory initalization an) |
|||
| Line 1: | Line 1: | ||
==Memory Questions== | ==Memory Questions== | ||
===How is memory initialized, without having to build a specific flash file, for a new application?=== | :===How is memory initialized, without having to build a specific flash file, for a new application?=== | ||
:There should be an init checkbox in the fixed Non-Volatile manager window. This will allow you to say if you want the app to load the default values or values previously on the module. This should take care of initializing the values yourself. | :There should be an init checkbox in the fixed Non-Volatile manager window. This will allow you to say if you want the app to load the default values or values previously on the module. This should take care of initializing the values yourself. | ||
:Similarly, the same result is done by performing an offline calibration change in the System | NonVolatile Storage | NonVolatile Storage Config | NonVolatileRestoreOnFirstStartup calibration. After changing this cal to "Load saved application values on next startup," you just need to merge back into your programming file, and then use the merged file for programming. | :Similarly, the same result is done by performing an offline calibration change in the System | NonVolatile Storage | NonVolatile Storage Config | NonVolatileRestoreOnFirstStartup calibration. After changing this cal to "Load saved application values on next startup," you just need to merge back into your programming file, and then use the merged file for programming. | ||
Revision as of 03:39, 14 December 2009
Memory Questions
- ===How is memory initialized, without having to build a specific flash file, for a new application?===
- There should be an init checkbox in the fixed Non-Volatile manager window. This will allow you to say if you want the app to load the default values or values previously on the module. This should take care of initializing the values yourself.
- Similarly, the same result is done by performing an offline calibration change in the System | NonVolatile Storage | NonVolatile Storage Config | NonVolatileRestoreOnFirstStartup calibration. After changing this cal to "Load saved application values on next startup," you just need to merge back into your programming file, and then use the merged file for programming.