Boot Loader Validation
Hai all,
We want to do a Boot Loader Validation for an ECU
In our process we first use to flash the Boot Loader and fallowed with application code and calibration File.
Presently we want to validate the Boot Loader under different circumstance as follows (for XC164cs)
Proposed test scenarios
Repeat 'download file to flash' after the performing these cases
- Break the CAN Communication at different sector boundaries and mid of the sector
- Break the CAN communication after and before downloading the first
- Stretch the inter message period (i.e., the time gap between two messages) for different values (trying between 2 ms to 100ms)
- Short the CAN bus for less than 1 sec a) after 29 sec b) before
- Short the CAN bus for above 5 sec a) after 29 sec b) before 500ms c) between 1 sec to 29secs
- Transmit commands 'Connect', 'Unlock' more than one time and try to download the application.
- Try with different code sizes - with code of maximum possible size of the Micro and beyond the size.
- Check the boot software performance at different voltage levels.
- Recycle the ignition while downloading the application.
- Recycle the power while downloading the application.
- Recycle the power after Connecting/unlocking the ECU i.e., before flashing the code.
- Recycle the ignition after Connecting/unlocking the ECU i.e., before flashing the code.
- Change the data of locations '0xC1FFFE- 0xC1FFFF' i.e., corrupting the valid application information
- Repeat the 'download file to flash' for 50 to 100 times.
Can any one please give your experiences in Boot Loader validation and additional points regarding which i should be through with Precautions to be followed while doing?
Thanking You all raj