Fw: Bootloader

Hi Sujan,


Technically, this is not a CAN-related set of questions.


1.  The ECU Bootloader is a piece of software (OK, firmware) that enables the ECU to start up and run the main application.  Typically, it will look for the latest valid piece of firmware (using signatures, checksums or whatever) and will then activate it (jump to its start address, call it, whatever).  A bootloader may use whatever communications bus is available (such as CAN) to allow downloading of a new piece of software.

2. Impact on the ECU diagnostics SHOULD be zero if the ECU bootloader is changed (if it is designed properly).  The bootloader SHOULD have no effect on the diagnostics while the ECU is running.  It will only really affect the operation during a firmware update (possibly).  In short, "it depends".


3. Who develops it will depend very much on how the contract is written.  With some OEMs, we've developed the entire package, while others have just asked for a board support package or hardware abstraction layer.  One even had their own bootloader, but we had to write our own for production purposes.

Again, "it depends".

Hope this helps,

Geoff

 
-- 
Geoff Field
Professional Geek, Amateur Stage-Levelling Gauge



On Monday, 30 December 2013 4:29 PM, Sujan S <[email protected]> wrote:
 
Hello All,

I am new to automotive domain and trying to understand the ECU bootloader.

Have few questions.

1. What is ECU Bootloader?
2. What is the impact of ECU Diagnositc software if there is a change in the ECU boot?
3. Who will develop the ECU boot when OEM is concerned?

Can any body help me to understand the impact on diagnostic software and application software if there are any changes in the ECU Boot.

Thanks
Sujan.