Hey boxsport, there's really three parts of the approach here; one is the unbricking, for which more info can be found here:
LT1 UnBrick. The read/write flash routine I think is figured out but not implemented (i'm leaving that up to Tom H, steveo and kur4o). The third part is actually defining where all the parameters are in the data files ("bin files"). I was brute force reverse engineering and quickly found the spark, VE, MAF, injector, and some transmission tables. Seeing as I had hundreds more parameters to go, I decided to write an automated finder tool (which then life pulled me away from). This will only find identical tables and non-zero scalars between '95 and '96 files; it won't work for scalars that are 00 or flags. So..
The last piece of the puzzle is actually learning disassembly and piecing through all the memory locations to figure out what scalars and flags are where. This part has the steepest learning curve; kur4o has provided me disassembly to work from but I'm not yet at the point of proficiency, and haven't had time.
If your OBD2 PCM is in a vehicle, you can buy any of these to communicate with it:
OBDX PRO VT/. Be aware that every run is quickly selling out so you may have to get on the mailing list to get one.