Difference between revisions of "Boot key recovery"

From MotoHawk
Jump to navigationJump to search
m (Added the comment that the module should be isolated on the communications bus)
 
(24 intermediate revisions by 4 users not shown)
Line 2: Line 2:
 
When working in the prototype phase with newly created .srz files from MotoHawk, it possible to program an .srz with errors in the CAN software or in the model that prevent communications with the module once programmed.  When this happens, the module appears to be locked up or frozen when accessing the module via MotoTune.  In this case, use the Boot Key to force the module into reboot mode such that a known, valid .srz can be reprogrammed into the module.
 
When working in the prototype phase with newly created .srz files from MotoHawk, it possible to program an .srz with errors in the CAN software or in the model that prevent communications with the module once programmed.  When this happens, the module appears to be locked up or frozen when accessing the module via MotoTune.  In this case, use the Boot Key to force the module into reboot mode such that a known, valid .srz can be reprogrammed into the module.
  
−
The Boot Key has a 10 pin CAN connector that should be inserted into an open port on the CAN junction box.  The device generates a 555 Hz, 0-Vbatt, 50% duty cycle square wave signal out of pin E when power is applied to pin A and ground applied to pin B.  When this signal is received on the appropriate pin of the module, it is forced into reboot mode and will allow the module to be reprogrammed.
+
The Boot Key has a 10 pin CAN connector that should be inserted into an open port on the CAN junction box.  The device generates a 555 Hz, 0-Vbatt, 50% duty cycle square wave signal out of pin E when power is applied to pin A and ground applied to pin B.  When this signal is received on the appropriate pin of the module when the module wakes, it is forced into reboot mode and will allow the module to be reprogrammed.
  
−
The boot key can be used to recover the following modules: ECM-0555-48, ECM-0555-80, GCM/HCM-0563-48(except GCM-0563-048-0802), ECM-0565-128, ECM-55xx-112, ECM-3R (ECM-0565-218-052-0600).
+
==Boot Key vs Boot Harness==
 +
Some modules are recovered using the boot key,  while others are recovered with a boot harness.  The process is the same.
 +
 
 +
===Modules that are Recovered with a Boot Key===
 +
The boot key can be used to recover the following modules:  
 +
:* ECM-0555-48  
 +
:* ECM-0555-80
 +
:* GCM/HCM-0563-48(except GCM-0563-048-0802)
 +
:* ECM-0565-128
 +
:* ECM-55xx-112
 +
:* ECM-3R (ECM-0565-218-052-0600)
 +
:* SECM112 main processor
 +
:* PCM112-14 main processor
 +
:* SECM70
 +
 
 +
<br>
  
 
'''Woodward Part Number: 1635-1800 Boot Key'''
 
'''Woodward Part Number: 1635-1800 Boot Key'''
 +
<br>
  
−
'''Boot Cables:'''  The following modules use a boot cable for recovery rather than a boot key, but the recovery process is the same.  The boot cable creates a sequence of High/Lows on the Analog inputs of the module, rather than a 555 Hz boot signal on a specified module pin.
+
===Modules that are Recovered with a Boot Harness===
 +
The following modules use a boot cable for recovery rather than a boot key, but the recovery process is the same.   
 
* ECM-S12X-070 -- boot cable 5404-1144
 
* ECM-S12X-070 -- boot cable 5404-1144
 
* HCM-0563-048 -- boot cable 5404-1138
 
* HCM-0563-048 -- boot cable 5404-1138
Line 15: Line 32:
 
* GCM-0S12-024 -- boot cable 5404-1213
 
* GCM-0S12-024 -- boot cable 5404-1213
 
* ECM-0S12-024 -- boot cable 5404-1238
 
* ECM-0S12-024 -- boot cable 5404-1238
 +
* SECM112    -- boot cable p/n TBD.
 +
* PCM112-14 Auxiliary processor
  
 +
The boot cable creates a sequence of High/Lows on the Analog inputs of the module, rather than a 555 Hz boot signal on a specified module pin.
  
−
<big>'''IMPORTANT: Remove the module from all control connections before attempting to recover it with a boot key'''</big>
+
''Note'': SECM112 main processor can be recovered with either a boot key or with a boot harness.  See below for additional information.
−
 
 
  
−
1. Plug the Boot Key into the junction box and make sure that power and ground are connected to pins A and B on the junction box. Connect pin E of the junction box to the channel listed below on the following modules.<br> Or, apply the required sequence to the analog inputs of the ECU, or connect the boot harness.
+
==Recovering the Module==
−
*ECM48_555 – ESTOP<br>
+
<big>'''IMPORTANT: Remove the module from all control connections before attempting to recover it with a boot key.  The module should be isolated on the communications bus.'''</big>
−
*PCM80_555 – ESTOP<br>
 
−
*PCM128_563 – DG1<br>
 
−
*HCM48_563 - STOP<br>
 
−
*ECM_5554-112 - STOP<br>
 
  
−
[[Image:MotoTuneBootKeyDisplay.jpg|500px|center]]
 
  
 +
=== Wiring Connections ===
  
−
2. With the power to the module off and the boot key installed, select a known, valid .srz file to flash onto the module and program the module on its default port.  <br>
+
====Boot Key==== 
 +
Plug the Boot Key into the junction box and make sure that power and ground are connected to pins A (Batt) and B (ground) on the junction box. Connect pin E of the junction box to the STOP pin of the module.  Some modules do not have a STOP pin, use the pin listed below instead.<br>
  
−
Note: The default port setting for all modules is PCM-1 (CAN1, 250kbps, City ID 0x0B) with the following exceptions:
+
*PCM128_563 – DG1<br>
−
* ECM-0S12-024 which has default City Id of 0x81, except the -0804 which has default City ID of 0X0B
+
*SECM112 main processor - DG8<br>
−
* GCM-0S12-024 which has default City ID of 0x91
 
−
 
 
−
3. When the “Looking for an ECU” prompt appears in the dialogue box, turn on power to the ECU.  The module must “wake-up” with the boot key or boot signal applied in order to force a reboot.<br>
 
−
 
 
−
''Note:'' The ECU must recognize the boot signal within 2-3 seconds of waking.  Therefore, it helps to apply power first, begin programming in MotoTune, then immediately key on when MotoTune begins looking for the ECU.
 
  
−
[[Image:MotoTuneBootKeyDisplay.jpg|center]]
+
If you are using a development harness and the 128-pin module, you will need to move the fuse position to 'boot'
  
 +
[[Image:Bootkey_Diagram.png|center]]
  
  
−
To boot strap the following modules,  make the following connections and follow the steps above.
+
====Boot Harness====
 +
Connect the boot harness to the ECU and move the switch position to 'boot'.  The sequence of analog inputs shown below can also be used instead of the boot harness.
  
−
'''HCM/GCM-0563-48'''  See also [http://mcs.woodward.com/user/download.php?filename=490%20 GCM/HCM Module Recovery] document
+
'''HCM/GCM-0563-48'''  See also [http://mcs.woodward.com/content/controllers/Fire48HardbootRecoveryDocument.pdf GCM/HCM Module Recovery] document
 
:AN1,3,5:      Pull to GND   
 
:AN1,3,5:      Pull to GND   
 
:AN2,4,6,7-12:  Pull to +5V
 
:AN2,4,6,7-12:  Pull to +5V
Line 64: Line 77:
 
* AN1,2,3,4,6,7:  Pull to +5V
 
* AN1,2,3,4,6,7:  Pull to +5V
 
* AN5, AN8:        Pull to GND
 
* AN5, AN8:        Pull to GND
−
**Read the following: [http://motocube/content/mototune/hcs12bootcable.doc HCS12 Boot Cable]
+
**Read the following: [http://mcs.woodward.com/content/controllers/UCHI_BootCable.pdf HCS12 Boot Cable]
  
 
'''ECM-S12X-070'''
 
'''ECM-S12X-070'''
 +
New:
 
* AN1,AN4-6: Pull to +5V
 
* AN1,AN4-6: Pull to +5V
 
* AN2,AN3, AN7:  Pull to GND
 
* AN2,AN3, AN7:  Pull to GND
  
−
'''To Use the Boot Key with the 128-pin module on the Desktop IO Simulator:''':Read the following [http://mcs.woodward.com/user/download.php?filename=499 128-pin module boot key with IO simulator]
+
Note:  There was a change to the boot code, so some older 70-pin modules may have a different sequence. 
 +
Old:
 +
AN2,3,4,6:  Pull to +5V
 +
AN4, 7: Pull to GND
 +
 
 +
'''SECM112 main'''
 +
* AN3: Pull to +5V
 +
* AN4: Pull to +5V
 +
* AN16: Pull to GND
 +
* AN17: Pull to GND
 +
* AN18: Pull to +5V
 +
 
 +
'''SECM112 auxiliary'''
 +
* AN3: Pull to +5V
 +
* AN4: Pull to +5V
 +
* AN16: Pull to +5V
 +
* AN17: Pull to GND
  
 +
'''PCM112-14 auxiliary'''
 +
* AN7: Pull to +5V
 +
* AN8: Pull to +5V
 +
* AN9: Pull to +5V
 +
* AN10: Pull to +5V
 +
* AN11: Pull to +5V
 +
* AN14: Pull to +5V
 +
* AN15: Pull to +5V
 +
* AN18: Pull to GND
  
−
== Boot Key Recovery of ECM-OH ==
 
−
The ECM-OH is different in that it has two microprocessors.  The processors are connected on CAN1, so it is important that the baud rate of both processors on CAN1 be the same, or the bus may crash.  The processors must also communicate with MotoTune on different city-id's.
 
  
−
The analog boot sequence for ECM-OH DV, Pre-PV, and PV modules is as follows:
+
'''SECM70'''
−
OH-Main
+
* AN1,AN2,AN3: Pull to +5V
−
AN3: Pull to +5V
+
* AN9,AN10,AN11: Pull to GND
−
AN4: Pull to +5V
 
−
AN16: Pull to GND
 
−
AN17: Pull to GND
 
−
AN18: Pull to +5V
 
  
−
OH-S12
+
=== MotoServer Port Setup for Module Recovery ===
−
AN3: Pull to +5V
+
The MotoServer Port must be set to CAN1, PCM-1, Baud Rate 250kbps.  The CityID should be set to CityID 11 (0x0B) with the following exceptions:
−
AN4: Pull to +5V
+
:* ECM-0S12-024 which has default City Id of 0x81, except the -0804 which has default City ID of 0X0B
−
AN16: Pull to +5V
+
:* GCM-0S12-024 which has default City ID of 0x91
−
AN17: Pull to GND
+
:* SECM112 auxiliary processor has default CityID of 0x81.
 +
:* PCM112-14 auxiliary processor has default CityID of 0x81.
  
−
The main core can also be recovered  by applying the boot-key 555Hz, 0-Vbat, 50% duty cycle, square wave input to DG8.  This is pin E (STOP) of the junction box or boot-key.
+
=== Programming the Module ===
 +
# Turn the Power and Key Off.
 +
# Turn on the Power, but leave the Key OFF.
 +
# Select a known good SRZ file, and begin programming in MotoTune
 +
# When the “Looking for an ECU” prompt appears in the dialogue box, turn on key power to the ECU.  The module must “wake-up” with the boot key or boot signal applied in order to force a reboot.<br><br><br>
 +
 
 +
[[Image:MotoTuneBootKeyDisplay.jpg|center]]
  
−
Use the following MotoServer Port Configurations when connecting with the ECU.  These are the default hardboot settings.
+
<br><br>
−
ECM-OH main: 250kbps on CAN-1, City ID 0xB (11)
+
'''To Use the Boot Key with the 128-pin module on the Desktop IO Simulator:''':Read the following [http://mcs.woodward.com/content/controllers/Boot%20Key%20Recovery%20of%20a%20128%20Pin%20Module%20on%20a%20Simulator.pdf 128-pin module boot key with IO simulator]
−
S12G: 250kbps on CAN-1, City ID 0x81 (129)
 
  
−
The Pre-PV and PV units will ship with a sample application that will connect at 500k on PCM-1 (City-ID 11) or PCM-2 (City-ID 12.  Recovering either microprocessor will force it back to it's default hardboot baud rate of 250kbps.  So, you must reprogram the other microprocessor with an application to change it to 250kbps.  
+
== Boot Key Recovery of SECM112 ==
 +
The SECM112 is different in that it has two microprocessor cores, the main processor and the auxiliary processor.  The processors are connected on CAN1, so it is important that the baud rate of both processors on CAN1 be the same.  The processors must also communicate with MotoTune on different city-id's.
  
−
Also, Battery (BATT) must be toggled before powering up the S12 into boot mode.
+
For detailed instructions see [[SECM112#Recovering_the_SECM112]]

Latest revision as of 09:17, 24 September 2021

Reprogramming Using Boot Key

When working in the prototype phase with newly created .srz files from MotoHawk, it possible to program an .srz with errors in the CAN software or in the model that prevent communications with the module once programmed. When this happens, the module appears to be locked up or frozen when accessing the module via MotoTune. In this case, use the Boot Key to force the module into reboot mode such that a known, valid .srz can be reprogrammed into the module.

The Boot Key has a 10 pin CAN connector that should be inserted into an open port on the CAN junction box. The device generates a 555 Hz, 0-Vbatt, 50% duty cycle square wave signal out of pin E when power is applied to pin A and ground applied to pin B. When this signal is received on the appropriate pin of the module when the module wakes, it is forced into reboot mode and will allow the module to be reprogrammed.

Boot Key vs Boot Harness

Some modules are recovered using the boot key, while others are recovered with a boot harness. The process is the same.

Modules that are Recovered with a Boot Key

The boot key can be used to recover the following modules:

  • ECM-0555-48
  • ECM-0555-80
  • GCM/HCM-0563-48(except GCM-0563-048-0802)
  • ECM-0565-128
  • ECM-55xx-112
  • ECM-3R (ECM-0565-218-052-0600)
  • SECM112 main processor
  • PCM112-14 main processor
  • SECM70


Woodward Part Number: 1635-1800 Boot Key

Modules that are Recovered with a Boot Harness

The following modules use a boot cable for recovery rather than a boot key, but the recovery process is the same.

  • ECM-S12X-070 -- boot cable 5404-1144
  • HCM-0563-048 -- boot cable 5404-1138
  • GCM-0563-048 -- boot cable 5404-1138
  • ECM-0563-048 -- boot cable 5404-1123
  • GCM-0S12-024 -- boot cable 5404-1213
  • ECM-0S12-024 -- boot cable 5404-1238
  • SECM112 -- boot cable p/n TBD.
  • PCM112-14 Auxiliary processor

The boot cable creates a sequence of High/Lows on the Analog inputs of the module, rather than a 555 Hz boot signal on a specified module pin.

Note: SECM112 main processor can be recovered with either a boot key or with a boot harness. See below for additional information.

Recovering the Module

IMPORTANT: Remove the module from all control connections before attempting to recover it with a boot key. The module should be isolated on the communications bus.


Wiring Connections

Boot Key

Plug the Boot Key into the junction box and make sure that power and ground are connected to pins A (Batt) and B (ground) on the junction box. Connect pin E of the junction box to the STOP pin of the module. Some modules do not have a STOP pin, use the pin listed below instead.

  • PCM128_563 – DG1
  • SECM112 main processor - DG8

If you are using a development harness and the 128-pin module, you will need to move the fuse position to 'boot'

Bootkey Diagram.png


Boot Harness

Connect the boot harness to the ECU and move the switch position to 'boot'. The sequence of analog inputs shown below can also be used instead of the boot harness.

HCM/GCM-0563-48 See also GCM/HCM Module Recovery document

AN1,3,5: Pull to GND
AN2,4,6,7-12: Pull to +5V

Note: For the GCM-0563-048-0802, the boot harness (analog sequence) must be used, not the boot key.

ECM48_563

  • AN1 – AN6: Pull to +5V
  • AN8: Pull to GND
  • AN11 & AN12: Pull to +5V

GCM-0S12-024 (MCHI)

  • AN1,AN2,AN4,AN5: Pull to +5V
  • AN3, AN6: Pull to GND

ECM-0S12-024 (SECM)

  • AN1,2,3,4,6,7: Pull to +5V
  • AN5, AN8: Pull to GND

ECM-S12X-070 New:

  • AN1,AN4-6: Pull to +5V
  • AN2,AN3, AN7: Pull to GND

Note: There was a change to the boot code, so some older 70-pin modules may have a different sequence. Old: AN2,3,4,6: Pull to +5V AN4, 7: Pull to GND

SECM112 main

  • AN3: Pull to +5V
  • AN4: Pull to +5V
  • AN16: Pull to GND
  • AN17: Pull to GND
  • AN18: Pull to +5V

SECM112 auxiliary

  • AN3: Pull to +5V
  • AN4: Pull to +5V
  • AN16: Pull to +5V
  • AN17: Pull to GND

PCM112-14 auxiliary

  • AN7: Pull to +5V
  • AN8: Pull to +5V
  • AN9: Pull to +5V
  • AN10: Pull to +5V
  • AN11: Pull to +5V
  • AN14: Pull to +5V
  • AN15: Pull to +5V
  • AN18: Pull to GND


SECM70

  • AN1,AN2,AN3: Pull to +5V
  • AN9,AN10,AN11: Pull to GND

MotoServer Port Setup for Module Recovery

The MotoServer Port must be set to CAN1, PCM-1, Baud Rate 250kbps. The CityID should be set to CityID 11 (0x0B) with the following exceptions:

  • ECM-0S12-024 which has default City Id of 0x81, except the -0804 which has default City ID of 0X0B
  • GCM-0S12-024 which has default City ID of 0x91
  • SECM112 auxiliary processor has default CityID of 0x81.
  • PCM112-14 auxiliary processor has default CityID of 0x81.

Programming the Module

  1. Turn the Power and Key Off.
  2. Turn on the Power, but leave the Key OFF.
  3. Select a known good SRZ file, and begin programming in MotoTune
  4. When the “Looking for an ECU” prompt appears in the dialogue box, turn on key power to the ECU. The module must “wake-up” with the boot key or boot signal applied in order to force a reboot.


MotoTuneBootKeyDisplay.jpg



To Use the Boot Key with the 128-pin module on the Desktop IO Simulator::Read the following 128-pin module boot key with IO simulator

Boot Key Recovery of SECM112

The SECM112 is different in that it has two microprocessor cores, the main processor and the auxiliary processor. The processors are connected on CAN1, so it is important that the baud rate of both processors on CAN1 be the same. The processors must also communicate with MotoTune on different city-id's.

For detailed instructions see SECM112#Recovering_the_SECM112

Retrieved from "http://mcs.woodward.com/support/wiki/index.php?title=Boot_key_recovery&oldid=4295"