********************************************************************************
*	
* BD32 'Target-Resident' drivers for TRIONIC T5 FLASHing in this package:
*	
* PREPT5.DO 
* Sets up some of the registers of SIM (System integration module)
* for flashing. This script must be executed before any of the target
* resident programs can be executed.
*
* DUMPT5/T52    For reading out the FLASH chips in SAAB T5 ECUs
* 
* FLASHT5/T52   For reflashing original FLASH chips in SAAB T5 ECUs
* AMD29T5/T52   For reflashing AMD 29F010 FLASH chips in SAAB T5 ECUs
* ATMELT5/T52   For reflashing ATMEL 29C010 FLASH chips in SAAB T5 ECUs
*
* ERASET5/T52   For 'Brute Force' erasing original FLASH chips in SAAB T5 ECUs
*               ERASET5/T52 attempts to erase the FLASH chips 10 times.  
*               (Hopefully no longer needed because a bug in the erase
*               algorithm has been fixed now)
*               
* NOTE: filenames of .BIN files must follow DOS '8.3' character format
*
* Examples (run from within from BD32 window):
*
* To read out your original BIN file from your T5 ECU
* 
*   DO PREPT5.DO
*   DUMPT5 ORIGINAL.BIN
* 
* To FLASH a new BIN file to your T5 ECU and read it back again 
* It is a good idea to read a newly FLASHed ECU back to check that the
* FLASHing process was really succesful since there is no error checking
* done over the BDM interface so it is possible for corruption to occur. 
* Use the DOS 'FC' command to compare the files FC /B MODIFIED.BIN CHECK.BIN
*
*   DO PREPT5.DO
*   FLASHT5 MODIFIED.BIN
*   DUMPT5 CHECK.BIN
*    
* Please refer to the Trionic5 manual for details of how to set-up the BDM
* environment so that you can reprogram the FLASH chips in your T5 ECU. 
* 
* I strongly suggest you use a regulated power supply to power your T5 ECU,
* some laptops use a 16V power supply which would be ideal for the purpose.
*
* Sophie x
* 
********************************************************************************
*
* WARNING: Use at your own risk, sadly this software comes with no guarantees.
* This software is provided 'free' and in good faith, but the author does not
* accept liability for any damage arising from its use.
* 
********************************************************************************
*
* What to expect to see in the BD32 window:
* 
* Progress messages are shown to indicate which operation is in progress
* Progress bars indicate progress of longer operations
*   Progress 'bar' during erase can show anywhere from 0 to 13 dots
*   Progress 'bar' for FLASH/DUMPing T5.5 ECUs is 256 dots (3 lines + 16 dots)
*   Progress 'bar' for FLASH/DUMPing T5.2 ECUs is 128 dots (just over 1.5 lines)
* You should see something happening every few seconds at most
* At the end of the process a message indicating the outcome is shown 
*
* NOTE; ERASET5/T52 is different and you might not see anything happen for some
* time:
*   Writing 00s to FLASH can take more than a minute in extreme cases
*   (Writing 00s takes less than 5 seconds with good FLASH chips)
*   Erasing FLASH can take up to 15 seconds in extreme cases
*   (Erasing takes less than 5 seconds with good FLASH chips)
*   The FLASH chips are rested for 10 seconds between erasure cycles
*   
*
* PREVIOUSLY IT WAS SAID:
* Some T5 flashes are so old that it is no longer possible to write 
* to them. Doing this will make them inoperable and the only way to
* fix them is to physicaly replace the flashes.
* Unfortunately the only way to determine the status of the flash
* is to write to it. A rumor says that AMD flashes are the worst.
*
* HOWEVER:
* Some of these problems may have been due to an error in the erase
* verification code in the original FLASHT5 'programs'. I have updated
* the algorithms to correct this error and made a few other
* optimisations/changes to the code.
* 
********************************************************************************
*
* DUMPT5/DUMPT52 Programs for dumping the flash memory from SAAB T5 ECUs
*
* Usage: DUMPT5 'FILENAME.BIN'
* Usage: DUMPT52 'FILENAME.BIN'
*
********************************************************************************
*
* FLASHT5/FLASHT52 Programs for writing original FLASH chips in SAAB T5 ECUs
*
* Usage: FLASHT5 'FILENAME.BIN'
* Usage: FLASHT52 'FILENAME.BIN'
*
********************************************************************************
*
* ERASET5/ERASET52 - Developed to address the problem some people have with
* AMD chips.
* Can be used to try to erase 'problem' chips before re-programming
* Does a 'Brute Force' write 00 and erase of the chips 10 times, ignoring (but
* reporting) verification errors. Reports success if the LAST erasure was OK
*
* Usage: ERASET5
* Usage: ERASET52
*
********************************************************************************
*
* AMD29T5/AMD29T52 - Developed to allow programming T5.5 ECUs fitted with
* AMD 29F010 * chips because the original chips no longer work.
*
* Usage: AMD29T5 'FILENAME.BIN'
* Usage: AMD29T52 'FILENAME.BIN'
*
********************************************************************************
*
* ATMELT5/ATMELT25 - Developed to allow programming T5.5 ECUs fitted with
* ATMEL 29C010 chips because the original chips no longer work.
*
* Usage: ATMELT5 'FILENAME.BIN'
* Usage: ATMELT52 'FILENAME.BIN'
*
********************************************************************************