1997 F-Body Tools

[Tom H]

Actually didn't take much time to make a binary. I dumped the content of both FLASH (both pages for TSide) in about 4 minutes. This is still with X1 speed.

Here is the output file. I added a few comments to show why I added the bit at the front. You can open it with just your notepad (open with ...) to see the comments stored with the code.This should help keep track of what mods are in the file and so on. One more thing though don't change the comments with notepad. This would probably offset the entire content of the file and make it a producer of bricks.

Here is the output file of my first run. You can change the extension to .bin and you will have what I started with.

-Tom

[JimCT_9C1]

Thanks for sharing, Tom.

Took a quick look and played with it a little bit.

One thing I would suggest is to place the comment/scratch area at the end of the file rather than the beginning; starting after the 192k bin data. This will avoid having to deal with offset memory addresses in definition files etc, and also avoids the potential problem you pointed out of inserted or deleted comment bytes offsetting the following bin data in the file.

I verified that TunerPro would correctly read, interpret, edit, and write files with additional information appended after the bin data. I tested using LT1 OBD1 xdf and bin files. I added and edited comments via Notepad, as well as cut and pasted the comment block from your file and edited that, before and after editing the bin data. Random length comments, separators, etc all worked with no need or effort to try to maintain a fixed block size or structure. The only downside was the need to drag to the bottom of the file after opening with Notepad to view or add comments. I think the robustness to accept unstructured input and not affect the bin data outweighs this minor inconvenience.

Interested to hear what other potential users may think.

Thanks again for all you've done!

Jim

[Tom H]

Jim,

I changed the format as you suggest. The only difference is that to view the comment (identify what the file contains) you need to scroll to the end. No big deal.

The Upload/Read part of the program is just about done now. I had trouble with the reading taking more time than windows permitted before marking the window as unresponsive. To fix this all the program is now multi-threaded so that controls such as progress bars and whatnot can all be updated with ease.

Here is the latest image of the main screen:

Tool2.jpg

Once you build the HBC, let me know and I will send over test software.

Now starting on the programming. Kur4o provided all the programming code we need to download into PCM RAM. I can re-use the same code was written for the upload section in most cases.

I need to get out to the local U-PULL-A_PART people and see if I can score another PCM. No luck till now, I think most of these were melted down up here in the salt belt.

-Tom

[Tom H]

Reading/upload is now complete except for the request from Kur4o for debug logging. I will get a look at that while the search for an LT1 OBDII PCM goes on...

There may be some interest in duplicating this capability for use with another cable. I have enclosed a transcript of the Class II bus for anyone interested.

In the file attached the first line is just to ensure the correct port is selected and opened
Lines 2 through 15 set up the download of code into internal ram
Lines 16 through 105 are downloading of the code to support modes $35 and $37 (not supported by the PCM native code)
Line 106 causes the downloaded code to execute, line 107 is the acknowledgement
Lines 108 through 9323 are the upload of flash from TSide bank 0, TSide bank 1 and ESide
Line 9324 causes the downloaded code to exit and reset the PCM, Line 9325 is the acknowledgement
Last two lines.. not necessary but are a request to normal activity on the ALDL

I hope to get to the programming side soon.

-Tom

[JimCT_9C1]

Thanks for the updates, Tom!

I'll catch up and take a look, been away from this for a couple weeks.
Great progress, thanks for the continued hard work!

Jim

[Tom H]

Hi,
Project is going ok, but with a few wrinkles. I have the module used to program the TSide loading into the PCM now. I can do all the easy work prior to programming like turn on/off vpp, read the mfg codes, checksum the part. I have looked through the zero the flash and erase the flash routines, they look OK. In addition most of the "feed the ESide fro programming" looks ok. There is trouble with the programming software however. There is no way to set the bank. Half the software looks like it wants to do a complete programming (that would be OK if we had the space to buffer the complete load somewhere), while the other half looks like it will only program the upper bank.
So that needs a bit of attention. I have already corrected two faults in the code and wonder if this module was ever used before. Alternative is that points of entry other than the start of the routine were used. I will spend a bit of time looking through this and changing it.

Main problem going forward is that I need to revive all that I did looking at bootstrapping. This is necessary because making bricks will be part of the debug. Probably can't avoid unless I am way too careful. Careful = slow.

I have not been able to find any OBDII PCMs locally. The Ontario/Canadian way seems to promote recycling as soon as possible. There are few of these cars around now. I am still on the hunt for any OBDII PCMs brick or working.

Looks like we will get a foot of snow today, so I will have time to go through the TSide programming module again and start to make the modifications needed.

-Tom