hinkxx wrote:I'm not sure about the year, but the sticker on the flash chip that could suggest a release date states 03.01.02, so it is probably 2002.
Also the transmission type is unknown to me - ECU is from the UK.

It came from a 2002 406 Coupe, thats as much as i know about it :)

nutski, delivery was pretty fast ;)

I'm glad it arrived quickly, Interested to see what can be learned from it!

No doubt about that ;)

very interesting topic.
Any advances on make dump?

Thanx for the info on ecu..

Long time no update as I've been busy on several fronts.
Nevertheless I've managed to get some work done. I'll make a separate thread for progress logging, pics, videos, wiring, etc.. info still needs to be organized and verified.

For now let me just say that it is progressing nicely 8-)

great topic

looking at some of the info from the first post

0001A400 - 0005FFFF : 100% difference (ignoring padding with 0xC3C3 at the end). This is likely our executable code that is different among software versions. Almost every byte in this region is different from map to map. What backups up my theory about software versions is the fact that for each bin file compared, length of this region is different (when ignoring 0xC3C3 at the end of this region) - changes in software sources were made. So:
- 1037353776 ends at 00055420
- 1037364307 ends at 000575c0
- 1037364397 ends at 00058b80

The software upgrade path looks similar to some smart cards. eg Hard coded secure ROM on cpu cannot be updated (boot loader and specific built in functions) to allow for major bugs or future improvement in hardware a eeprom based look-up/jump table is used to call these routines.

Patches/updates are then applied to the bottom of the existing data area (not moving existing code lowers risk of introducing new bugs) and the jump table updated to call these updated routine instead of internal functions etc.

Very nice, thx.

Is this still going or has it moved?
Very interesting reading.

Very interesting. Thanks