Changes

The Simos == Physical info == If you open up the 18.1 ecu casing and look at the number written on the processor, this is what you’ll find:<pre>SAK-TC1791S-384 F200EP3MB total flash200 MHz Processor</pre> Physically it contains 3MB of flash in total, spread over two flash units inside the chip (PMU0 – 2MB and PMU1 - 1MB) Other variants of the chip can have different configurations, for example the 18.10 ECU flash files contain uses a number SAK-TC1791S-512 F240EP chip with 4MB (PMU0 – 2MB and PMU1 – 2MB). All of 'blocks'this is in the free Infineon datasheets. So when the tools read out the contents, sometimes they read past the end of the physical chip! In which case anything after the physical end is just lots of zeroes. The 18.1 only has 3MB physically there, if you get a read bigger than 3MB then is all going to be zeroes and you can ignore it anyway. == The flash blocks == There are written to the memory on the ecu in different areassix blocks:PMU0 (2MB)#SBOOT – supplier boot (READ ONLY!0x0000 0000 -> 0x0001 BFFF)#CBOOT– customer boot (0x0001 C000 - > 0x0003 FFFF)#ASW1 – Application Software SW part #1(0x0004 0000 -> 0x0013 FFFF)#ASW2 – Application Software SW part #2(0x0014 0000 -> 0x001F FFFF)#PMU1 (1MB)#CAL – Calibration (0x0020 0000 -> 0x0027 FFFF)#ASW3 – Application Software SW part #3(0x0028 0000 -> 0x002F FFFF) === Each blocks purpose ======= SBOOT ====SBOOT is not a field replaceable unit, so can’t be flashed over with OBD and you can ignore it for all intents and purposes since you can’t really modify it. The other five can be replaced via OBD and are subject to modifying.#Calibration Block ==== CBOOT ====CBOOT does all the flashing. Basically when you want to reflash via OBD, the ECU reboots into CBOOT and runs all the re-flashing procedures etc out of CBOOT. Once complete, it reboots again into ASW. ASW, the application software, is what controls the combustion process in your petrol engine. CBOOT has nothing to do with ASW. You can’t flash from ASW, you have to go into CBOOT for that. Both CBOOT and ASW have their own UDS comm stack, so when CBOOT is active it uses its own comm stack for CAN messages and similarly when ASW is active its using its own separate comm stack as well