Delco OSE FlashTool V1.51

Programs / Tools / Scripts
User avatar
Posts: 4991
Joined: Sun Mar 01, 2009 2:54 pm
Location: Perth, WA

Delco OSE FlashTool V1.51

Postby VL400 » Tue Apr 14, 2009 11:56 pm

Sick of having to always remove the memcal or EPROM just to make a calibration change? Well this small tool will mean the end of that. Just read the calibration data, use your favourite bin editor to make changes and write it back in. Simple! All this is done over ALDL so no extra cables or boxes lying on the passenger floor and no EPROM burner and UV light everytime you want to change a bit.

Memcal Based ECU/PCM: The requirements are that the ECM or PCM is fitted with a NVRAM in place of the memcal loaded with a write capabale bin (ie OSE code) and you have an interface for data - either over the vehicles 8192baud ALDL port or an add-on board for the early 160baud ECMs to allow 8192 ALDL

Flash Memory Based ECU/PCM: Before you try anything read the very important information on using the flashtool with a flash based PCM here

For a brief rundown of ALDL and also the device ID of different models of ECM/PCM and the BCM see the thread here

OSE 12P Calibration version migration: If you have an older 12P tune you wish to migrate to the latest, you can use this tool to automate most of the process. The app will show details of new tables added or tables which the resolution has changed. If this is the case you will need to locate those scalars or tables in the output and populate the empty data. Note also that this is designed to work on a cal file. You can migrate a bin but note that it wont add an updated operating system. We recommend to update a cal or bin, save it as cal, then use this tool to upload to an ECM with the right operating system. This will merge the calibration with the right operating system. You can then download the bin to have a complete bin image on your pc.

Common Issues:
The mouse goes crazy when trying to log data. This is a known windows driver issue, the ALDL interface gets detected as a mouse. Use the instructions and Microsoft tool to disable this .. http://support.microsoft.com/kb/819036


Download Here:
Here is the latest version of the program...
OSE Enhanced Flash Tool V151.exe
(566.5 KiB) Downloaded 4695 times


You will also need the .NET 3.5 framework which can be downloaded from here.

User avatar
Posts: 4991
Joined: Sun Mar 01, 2009 2:54 pm
Location: Perth, WA

Re: The FlashTool

Postby VL400 » Tue Apr 14, 2009 11:57 pm

<<< Setting Up The FlashTool >>>


There are a number of options that need to be setup before using the tool. They are all saved on your system for future use. To access the options, load the FlashTool and select Options and then Preferences from the menu strip. You will see a dialog box like this…

Preferences.png
Preferences.png (27.91 KiB) Viewed 30385 times


Step 1: From the Vehicle and Interface drop down selection box choose the options that best suit your setup. This automatically populates all the configuration options other than the com port.

Step 2: Select the com port you wish to use for ALDL communication using the ECM com port drop down box.

Step 3: Click Ok to save the options and close the preference screen.

Advanced/Custom Settings
Device ID and BCM ID: The ALDL guide has the device ID’s for all devices in the commodore range. Set this to match your vehicle. You will also need to select the ‘Disable BCM Chatter’ and ‘Disable ECM Chatter’ checkboxes, if your vehicle does not have a BCM then do not select ‘Disable BCM Chatter’.

Heartbeat: The heartbeat frame is used in VX and later commodores only when many devices started to be placed on the vehicle bus. It is used to tell devices that a large amount of free time will be available on the bus. The frame that needs to be searched out is 0x08, 0x55, 0xA3. The timeout figure of 2000mS should be left as is unless you have trouble detecting the heartbeat.

Ignore Echo: This must be set to match your interface. The documentation will tell you if your device has data echo, if so select this option to ignore it.

Other Settings:
The wait for silence, com retries and com timeout settings can normally be left as the default values. If you are having issues getting reliable data on a vehicle that has lots of bus traffic then these may need to be adjusted.

High speed communication options are best left on Auto. They allow for 2x read speed and 16x write speed if the binary in the ECM/PCM supports it. Auto retries should be set to approx half that of the Comm Re-Tries option. In auto mode the flash tool attempts high speed mode, if this is not supported or there are too many errors it drops back to normal speed and continues.

Under the general program options you can select what devices should be detected and identified. The program always looks for OSE devices but it is also compatible with Kalmaker and RT enabled factory devices. Validate file before writing should never be de-selected and is there for code testing purposes only – if you upload a bin that’s not compatible expect to have to reburn the NVRAM.

User avatar
Posts: 4991
Joined: Sun Mar 01, 2009 2:54 pm
Location: Perth, WA

Re: The FlashTool

Postby VL400 » Tue Apr 14, 2009 11:57 pm

<<< Using The FlashTool >>>


When opening the program you will be presented with a screen similar to the one below. Clicking 'Connect to ECM' will search for a device, if a known device is found it will load all the memory allocations and enable the data control buttons for the device. This is an example of the FlashTool finding a $12 OSE device...


Main_Screen.jpg
Main_Screen.jpg (39.6 KiB) Viewed 14500 times




If the device found is not identifiable a screen will be displayed to enter the memory mapping details manually. The values for custom memory mapping of common ECM/PCMs will be posted below

CustomMapping_v126.jpg
CustomMapping_v126.jpg (36.76 KiB) Viewed 14500 times




Once a device has been found the data control buttons will be enabled and certain operations can be performed. If a button is still greyed out after connecting then the function is not supported. Here is a brief description of each button....

*** Get Cal - This function gets only the calibration data - ie all the tune-able data
*** Get Bin - This function gets the entire binary.
*** Get RAM - This function gets only the RAM
*** Get EEPROM - In VR Auto and later PCMs there is EEPROM. This function gets that memory area.
*** Write Cal - The calibration file that was read can be written back using this function. You can also choose this function and select a binary file. The flashtool will only write the calibration portion of the bin.
*** Write Bin – This is used to update the entire ECM code and should only be used when upgrading to a new version not for making tuning changes. It is currently only used for OSE 12P and flash based PCMs. It should be used very carefully, if you are getting data errors when doing a get bin function, write bin should not be used until you have 0 errors.

User avatar
Posts: 4991
Joined: Sun Mar 01, 2009 2:54 pm
Location: Perth, WA

Re: The FlashTool

Postby VL400 » Tue Apr 14, 2009 11:57 pm

<<< Custom Memory Mapping Info >>>


------------ VR/VS Auto ($11/$58) ------------
ROM Mapping = 0 to FFFF
Calibration Mapping = 6000 to 8FFF
RAM Mapping = 0 to 8FF
EEPROM Mapping = E00 to FFF


------------ VR/VS Manual ($12/$5A) ------------
ROM Mapping = 8000 to FFFF
Calibration Mapping = 8000 to 8FFF
RAM Mapping = 0 to 1FF
EEPROM Mapping = Any address, the ECM does not have EEPROM


------------ VS Ecotec ($51) ------------
ROM Mapping = 0 to FFFF
Calibration Mapping = 2000 to 5FFF
RAM Mapping = 0 to 1FFF
EEPROM Mapping = E00 to FFF



* Note - VS Ecotec and newer PCMs that have a 128k binary use a memory bank switching method.
The flash tool only supports reading and writing to bank 1, the first 64k. This means the 'Get Bin'
function does not get the entire binary.

Site Admin
User avatar
Posts: 5789
Joined: Sat Feb 28, 2009 8:34 pm

Re: The FlashTool

Postby antus » Wed Apr 15, 2009 11:38 am

Looks great! This will certainly be a useful swiss army knife for ecm games.
Have you read the FAQ? For lots of information and links to significant threads see here: viewtopic.php?f=7&t=1396

User avatar
Posts: 4970
Joined: Sat Feb 28, 2009 8:38 pm
Location: Wellington NZ

Re: The FlashTool

Postby delcowizzid » Wed Apr 15, 2009 11:54 am

nice little program VL400.has evolved a bit since the early version i looked at ages ago.you the man :D
If Its Got Gas Or Ass Count Me In.if it cant be fixed with a hammer you have an electrical problem

User avatar
Posts: 9812
Joined: Sat Feb 28, 2009 9:05 pm
Location: Tenambit, NSW

Re: The FlashTool

Postby Holden202T » Wed Apr 15, 2009 12:21 pm

yeah it sure has come along way :)

ose flash tool, antusprom, scanner pro and tuner pro and you have a nice functioning suite of programs that do all you need and are FREE!

User avatar
Posts: 4970
Joined: Sat Feb 28, 2009 8:38 pm
Location: Wellington NZ

Re: The FlashTool

Postby delcowizzid » Sat Apr 25, 2009 4:38 pm

nice just sorted my new PC so i can run .net 3.5 now so i can check out the new changes to the flasher tool.allso got my FTDI cable this week too :D
If Its Got Gas Or Ass Count Me In.if it cant be fixed with a hammer you have an electrical problem

User avatar
Posts: 4970
Joined: Sat Feb 28, 2009 8:38 pm
Location: Wellington NZ

Re: The FlashTool

Postby delcowizzid » Sun Apr 26, 2009 12:46 am

well flashtool works great mate been playing with it tonight with my new FTDI usb>serial cable.no issues so far.sucked bin out all good tables all looked good in tunerpro.just need to charge up the laptop now and im good to go testing.
If Its Got Gas Or Ass Count Me In.if it cant be fixed with a hammer you have an electrical problem

Posts: 19
Joined: Wed Apr 29, 2009 10:45 pm

Re: The FlashTool

Postby L2-Max » Thu Apr 30, 2009 4:34 pm

Thanks for you work but smalest problem exists.

The read timeout between arrival of two bytes is small. I'm using adapter on ftdi chip and coudnt read any dump of memory. I have run PORTMON NT which capture adapter port and I see that your program has been interrupted by timeout every request it do. It reads not fully data which my ECM transfer.

Next

Return to Tools

Who is online

Users browsing this forum: No registered users and 2 guests