@(#)bootload.doc 1.3 HDS-300/68HC11 Bootload Data Files ================================== By Peter S. Gilmour, Motorola Development Systems, Austin, TX This file contains the latest information for the HDS-300/68HC11 Bootload data files (*.DAT) which are used by the EE commands when programming devices. ------------------------------------------------------------------------------- The new 2.1 release of HDS-300/68HC11 software contains a new Bootload file, named BOOTABE.DAT, which allows programming of all A, B, and E devices, including 811E2, 811A8, E1 and E9. The only known exception is 711E9 devices which are just starting to be sampled now (AUG. '89). Support for the 711E9 is anticipated in 4Q89 (requires new Programming Board and .DAT file). The new .DAT file also protects itself and its internal registers, except CONFIG, from errant PGM/ERAS commands. It forces an error which shows up as "Lost communication...". Thus to program the the CONFIG register, exactly one (1) byte must be specified at the CONFIG register address ($103F). Example: PGM 5000,1 103F Enter the following commands on your HDS-300/68HC11 system to create this new Bootload file, BOOTABE.DAT. Or you can edit the commands below into a macro file named BOOTABE.MAC, and HDSWRITE it to your HDS-300 disk for execution via the MF command. * Macro file to generate BOOTABE.DAT file. * * BOOTABE.DAT requires HDS-300/68HC11 software version 2.0 or higher! RESET MAP UNDO ;D PROC BT 0 2FF ;NP ** TEST SHOULD COMPLETE WITHOUT ERRORS! ** BF 0 2FF 0 MS 0000 8E 00 FF CE 10 00 1C 2D 0C 6F 35 20 0B 00 00 00 MS 0010 00 00 00 00 00 00 AE 04 8D 64 C1 01 26 FA 8D 5E MS 0020 17 18 CE 00 00 8D 57 18 E7 00 18 08 4A 26 F6 8D MS 0030 4D C1 04 26 E3 96 01 27 23 DC 02 D3 04 18 8F DC MS 0040 02 4D 27 D4 1A 83 10 40 24 12 18 8C 10 00 23 0C MS 0050 1A 83 10 3F 26 C2 18 8C 10 40 26 BC D6 08 18 DE MS 0060 02 96 01 81 02 27 25 2E 54 8D 5F 18 E6 00 18 08 MS 0070 8D 13 8D 52 26 F5 6F 3B C6 04 8D 09 20 9A 1F 2E MS 0080 20 FC E6 2F 39 1F 2E 80 FC E7 2F 39 8D 3C 8A 12 MS 0090 A7 3B 18 CE 00 07 18 08 18 E6 00 3C DE 02 E7 00 MS 00A0 08 DF 02 38 6C 3B 3C 96 07 CE 01 4D 09 26 FD 4A MS 00B0 26 F7 38 6A 3B 8D 0F 26 DD 8D 0F 20 B9 18 1C 00 MS 00C0 FF 8D 07 17 20 CA 7A 00 05 39 96 06 A7 3B 39 00 * MS 0200 FF SAVE BOOTABE 200,1 SAVE BOOTABE 0,100 ;A REN BOOTABE.DAT=BOOTABE.MEM * * NOTES: * OLDER style pods have programming sockets inside the pod. * NEWER style pods have external programming board. * * To program 811A8, 01-W3431 (bottom bd.): (MUST have NEWER style pod!) * - MUST have J5= 39K resistor between pins 2-3 (+19V) when program- * ing EEM memory. Do not jumper pins 2-3 directly, as this may damage * the 8K EEM array. * - SHOULD have J5= 1-2 (+5V) when programming EEPROM memory. Does * not "hurt" the device if +19V is used, it is just not recommended. * - set "EEDEF 10,100" for PGM/ERAS delays (consult latest data sheet). * - when programming the EEM, be sure to specify the EEM option! * * All other devices MUST have J5= 1-2 (bottom bd.). * MUST specify exactly 1 byte when programming the CONFIG register. *** ALL DONE - GOOD LUCK! *** ------------------------------------------------------------------------------- The BOOTD.DAT file should not be used anymore, because the part's pin assign- ments have changed from the preliminary information used to design the external Programming Board (01-W3463B01). Thus the warning message below. ***** DO NOT ATTEMPT TO PROGRAM "D" TYPE DEVICES! ***** ------------------------------------------------------------------------------- Also, because of the way the 811E2 device was designed and the way the HDS-300 operates (powers up/down the device being programmed for each EE command entered), it is not possible to read the actual CONFIG register value back after programming. Even the Evaluation Modules do not read back the actual CONFIG register; they fake it by writing to the CONFIG latches to ensure programming verification. Design Engineering is aware of this problem, but no solution is planned yet. **EOF**
Bulow