YAMAHA ECU FLASH TUCSON UPDATE
YAMAHA ECU FLASH TUCSON PLUS

protect some areas of Subaru CAN ROMs to avoid accidental reflashing of critical areas.fix bitmask errors when using blobbits data type.make table editing shortcuts quicker by not using Alt key anymore.

YAMAHA ECU FLASH TUCSON UPDATE

create UI for Openport 2.0 firmware update process.

add variable block sizing for troublesome Mitsubishi CAN vehicles.

Later processors like the SH2 and M32R generate this reflash voltage internally, and have minimal current requirements, which is why the Openport 1.3 works with the Evo 7/8/9 without a problem. The Openport 1.3 does generate a voltage large enough to cause the processor to startup in boot mode, which is why you could read and compare in past versions, but unfortunately, it just isn't usable for reflashing. The reason being that the Openport 1.3 power supply circuit that generates the ~16V the ECU needs to supply the regulated reflashing voltage to the CPU does not have a sufficient current capacity, causing this voltage to drop to levels insufficient to safely flash the CPU (the CPU goes into a protection mode to prevent you from even trying).

we will not be able to release a version of EcuFlash for the Mitsubishi H8 processor family of ECUs that works with the Openport 1.3.

add support for EVO 5/6 and other Mitsubishi H8 reflashing.

increase maximum allowable ISO9141 baud rate to be 125000 baud.

fix bug where resting voltage of adjustable power supply can be low enough to trigger undervoltage protection of voltage multiplexer IC.

fix bug which can cause CAN receive buffer overruns during large ISO15765 transfers.

(no changes other than new firmware payload).

fixed bug in Subaru K-line reflashing that did not initialize the parity mode of the vehicle interface, causing errors if the interface had previously been used with odd or even parity.

fixed error that limited data type to 4 bytes in size (doubles and bloblists can be bigger).

this allows ROMs of the same version to be shared amongst users without refusal-to-flash errors.

allow unique ID data in Subaru CAN ROM protected area to be different without requiring this area to be reflashed (which is not allowed).

add some retries to kernel reads, instead of failing.

actively pull up OBD pin 9 when communicating with HC16 Subarus to avoid reflash mode initialization problems on some EDM models.

fix programming voltage warning errors in Subaru HC16 kernels.

YAMAHA ECU FLASH TUCSON PLUS

up to Generic2048K, including all powers of 2, plus many other common sizes.

add many generic memory models to allow support for arbitrary ROMs from ECUs that EcuFlash has no flashing support for.

support for flashing H8/539FA processor (e.g.

that shop owner asked me if i had already done a reflash b4 by another shop, i said yes, then he suggested that i go back to the shop where my car was 1st done with ecu reflash after the 2nd workshop revert all the settings back to same state b4 he did a reflash.

somehow, later i went to another workshop to get another reflash done deal to fuel consumption, but after that, my ignition can turned on but engine cannot start up. i had the same problem with my JDM type R that did a ecu reflash with a hondata flashpro. as the ecu is 'locked' with the 1st bin file ever use for that ecu's reflash. u will need to use back the same bin file with the race tools to revert every setting back to stock setting before u can use another set of woolich race tool with new bin file for another ecu reflash. Hi.i had done a few reflash with my 15' R1 and did not have any issue.did u save all the setting when u 1st login with your race tool kit b4 u did a reflash? i do not know whether it's true or not that whenever the ecu was 1st reflash ( from fully stock ecu ) with a bin file.

Yamaha ecu flash tucson