SHBootMode - Revision history

Cboles at 17:05, 19 June 2009

2009-06-19T17:05:04Z

←Older revision		Revision as of 17:05, 19 June 2009
Line 19:		Line 19:

	===Obtain the ROM===		===Obtain the ROM===
-	Since the boot mode is a write-only operation, you will need the complete ROM you intend to reflash the ECU with~~. Make note of the XML ID of this ROM as you will need to modify its XML metadata in the next step~~.	+	Since the boot mode is a write-only operation, you will need the complete ROM you intend to reflash the ECU with.

	===Turn on SH Boot Mode in EcuFlash===		===Turn on SH Boot Mode in EcuFlash===
-	Go to '''File -> Options -> ~~Force SH Boot~~ Mode''' and check the box. Remember to uncheck this after you are done.	+	Go to '''File -> Options -> Flashing -> Flash Recovery Mode''' and check the box. Remember to uncheck this after you are done so that you can read and flash ECUs normally.

	This will tell EcuFlash to use the SH boot mode method instead of the standard kernel based reflash method.		This will tell EcuFlash to use the SH boot mode method instead of the standard kernel based reflash method.
-
-	~~===Start EcuFlash===~~
-	~~You must start / restart EcuFlash to read the XML changes~~

	===Load the ROM===		===Load the ROM===
Line 33:		Line 30:
	===Flash the ROM to the ECU===		===Flash the ROM to the ECU===
	This is a slow process as compared to a standard reflash!		This is a slow process as compared to a standard reflash!
		+
		+	===Turn off the SH Boot Mode in EcuFlash===
		+	Go to '''File -> Options -> Flashing -> Flash Recovery Mode''' and uncheck the box.

Cboles: /* Build the hardware */

2009-01-16T00:43:04Z

Build the hardware

←Older revision		Revision as of 00:43, 16 January 2009
Line 6:		Line 6:

	===Build the hardware===		===Build the hardware===
-	You need to build a serial interface with which to talk to the CPU. The schematic for this interface is shown below. EcuFlash only supports FTDI based USB to serial interfaces. The schematic below shows what the interface must look like. You could build this by taking apart a FTDI-based USB to serial device and making the needed modifications. Basically, this is a simple TTL-level serial interface where the raw TXD and RXD signals are taken from the FTDI chip. There is also a 555 timer based circuit to provide the watchdog signal while in the boot mode.	+	You need to build a serial interface with which to talk to the CPU. The schematic for this interface is shown below. EcuFlash only supports FTDI based USB to serial interfaces. The schematic below shows what the interface must look like. You could build this by taking apart a FTDI-based USB to serial device and making the needed modifications, or there are many FTDI based evaluation and prototyping modules which can be used. Basically, this is a simple TTL-level serial interface where the raw TXD and RXD signals are taken from the FTDI chip. There is also a 555 timer based circuit to provide the watchdog signal while in the boot mode to prevent the CPU from resetting.

	'''[http://openecu.org/downloads/shbootmode.pdf Download SH Boot Mode Schematic Here]'''		'''[http://openecu.org/downloads/shbootmode.pdf Download SH Boot Mode Schematic Here]'''

Cboles at 20:10, 5 September 2008

2008-09-05T20:10:33Z

←Older revision		Revision as of 20:10, 5 September 2008
Line 22:		Line 22:

	===Turn on SH Boot Mode in EcuFlash===		===Turn on SH Boot Mode in EcuFlash===
-	Go to File -> Options -> Force SH Boot Mode and check the box. Remember to uncheck this after you are done.	+	Go to '''File -> Options -> Force SH Boot Mode''' and check the box. Remember to uncheck this after you are done.

	This will tell EcuFlash to use the SH boot mode method instead of the standard kernel based reflash method.		This will tell EcuFlash to use the SH boot mode method instead of the standard kernel based reflash method.

Cboles at 20:09, 5 September 2008

2008-09-05T20:09:56Z

←Older revision		Revision as of 20:09, 5 September 2008
Line 21:		Line 21:
	Since the boot mode is a write-only operation, you will need the complete ROM you intend to reflash the ECU with. Make note of the XML ID of this ROM as you will need to modify its XML metadata in the next step.		Since the boot mode is a write-only operation, you will need the complete ROM you intend to reflash the ECU with. Make note of the XML ID of this ROM as you will need to modify its XML metadata in the next step.

-	===~~Modify the XML~~===	+	===Turn on SH Boot Mode in EcuFlash===
-	~~Locate~~ the ~~XML file for the ROM you wish~~ to ~~use in your rommetadata directory. Temporarily change~~ this ~~line in your XML metadata file for the ROM~~ you are ~~using from:~~	+	Go to File -> Options -> Force SH Boot Mode and check the box. Remember to uncheck this after you are done.
-		+
-	~~<flashmethod>sti05</flashmethod>~~	+
-		+
-	~~to:~~	+
-		+
-	~~<flashmethod>shbootmode</flashmethod>~~	+

	This will tell EcuFlash to use the SH boot mode method instead of the standard kernel based reflash method.		This will tell EcuFlash to use the SH boot mode method instead of the standard kernel based reflash method.

Cboles: /* Connect the hardware to the ECU */

2007-09-12T20:48:35Z

Connect the hardware to the ECU

←Older revision		Revision as of 20:48, 12 September 2007
Line 13:		Line 13:
	Make the connections diagrammed in the schematic. If the test points listed in the schematic (Pxxx) are not on your ECU PCB, you should be able to find the needed pads by tracing them from the CPU pins (also listed in the schematic).		Make the connections diagrammed in the schematic. If the test points listed in the schematic (Pxxx) are not on your ECU PCB, you should be able to find the needed pads by tracing them from the CPU pins (also listed in the schematic).

-	[[Image:Shbootmode.jpg]]	+	[[Image:Shbootmode.jpg\|200px]]

	===Power the ECU===		===Power the ECU===

Cboles: /* Connect the hardware to the ECU */

2007-09-12T20:43:47Z

Connect the hardware to the ECU

←Older revision		Revision as of 20:43, 12 September 2007
Line 13:		Line 13:
	Make the connections diagrammed in the schematic. If the test points listed in the schematic (Pxxx) are not on your ECU PCB, you should be able to find the needed pads by tracing them from the CPU pins (also listed in the schematic).		Make the connections diagrammed in the schematic. If the test points listed in the schematic (Pxxx) are not on your ECU PCB, you should be able to find the needed pads by tracing them from the CPU pins (also listed in the schematic).

-	[[Image:~~downloads/shbootmode~~.jpg]]	+	[[Image:Shbootmode.jpg]]

	===Power the ECU===		===Power the ECU===

Cboles: /* Connect the hardware to the ECU */

2007-09-12T20:11:42Z

Connect the hardware to the ECU

←Older revision		Revision as of 20:11, 12 September 2007
Line 12:		Line 12:
	===Connect the hardware to the ECU===		===Connect the hardware to the ECU===
	Make the connections diagrammed in the schematic. If the test points listed in the schematic (Pxxx) are not on your ECU PCB, you should be able to find the needed pads by tracing them from the CPU pins (also listed in the schematic).		Make the connections diagrammed in the schematic. If the test points listed in the schematic (Pxxx) are not on your ECU PCB, you should be able to find the needed pads by tracing them from the CPU pins (also listed in the schematic).
		+
		+	[[Image:downloads/shbootmode.jpg]]

	===Power the ECU===		===Power the ECU===

Cboles at 21:15, 5 June 2007

2007-06-05T21:15:55Z

←Older revision		Revision as of 21:15, 5 June 2007
Line 7:		Line 7:
	===Build the hardware===		===Build the hardware===
	You need to build a serial interface with which to talk to the CPU. The schematic for this interface is shown below. EcuFlash only supports FTDI based USB to serial interfaces. The schematic below shows what the interface must look like. You could build this by taking apart a FTDI-based USB to serial device and making the needed modifications. Basically, this is a simple TTL-level serial interface where the raw TXD and RXD signals are taken from the FTDI chip. There is also a 555 timer based circuit to provide the watchdog signal while in the boot mode.		You need to build a serial interface with which to talk to the CPU. The schematic for this interface is shown below. EcuFlash only supports FTDI based USB to serial interfaces. The schematic below shows what the interface must look like. You could build this by taking apart a FTDI-based USB to serial device and making the needed modifications. Basically, this is a simple TTL-level serial interface where the raw TXD and RXD signals are taken from the FTDI chip. There is also a 555 timer based circuit to provide the watchdog signal while in the boot mode.
		+
		+	'''[http://openecu.org/downloads/shbootmode.pdf Download SH Boot Mode Schematic Here]'''

	===Connect the hardware to the ECU===		===Connect the hardware to the ECU===

192.168.0.3 at 21:12, 5 June 2007

2007-06-05T21:12:21Z

←Older revision		Revision as of 21:12, 5 June 2007
Line 1:		Line 1:
-	Reflashing Subaru SH705x ECUs using the Renesas boot mode	+	==Reflashing Subaru SH705x ECUs using the Renesas boot mode==

-	Summary	+	===Summary===

	If a Subaru ECU becomes unresponsive due to an incorrect or incomplete reflash, it is possible erase and reflash the SH705x CPU using the built in boot mode by utilizing some special hardware and EcuFlash. This page describes the procedure step-by-step.		If a Subaru ECU becomes unresponsive due to an incorrect or incomplete reflash, it is possible erase and reflash the SH705x CPU using the built in boot mode by utilizing some special hardware and EcuFlash. This page describes the procedure step-by-step.

-	* Build the hardware	+	===Build the hardware===
	You need to build a serial interface with which to talk to the CPU. The schematic for this interface is shown below. EcuFlash only supports FTDI based USB to serial interfaces. The schematic below shows what the interface must look like. You could build this by taking apart a FTDI-based USB to serial device and making the needed modifications. Basically, this is a simple TTL-level serial interface where the raw TXD and RXD signals are taken from the FTDI chip. There is also a 555 timer based circuit to provide the watchdog signal while in the boot mode.		You need to build a serial interface with which to talk to the CPU. The schematic for this interface is shown below. EcuFlash only supports FTDI based USB to serial interfaces. The schematic below shows what the interface must look like. You could build this by taking apart a FTDI-based USB to serial device and making the needed modifications. Basically, this is a simple TTL-level serial interface where the raw TXD and RXD signals are taken from the FTDI chip. There is also a 555 timer based circuit to provide the watchdog signal while in the boot mode.

-	* Connect the hardware to the ECU	+	===Connect the hardware to the ECU===
	Make the connections diagrammed in the schematic. If the test points listed in the schematic (Pxxx) are not on your ECU PCB, you should be able to find the needed pads by tracing them from the CPU pins (also listed in the schematic).		Make the connections diagrammed in the schematic. If the test points listed in the schematic (Pxxx) are not on your ECU PCB, you should be able to find the needed pads by tracing them from the CPU pins (also listed in the schematic).

-	* Power the ECU	+	===Power the ECU===
	You will also need to provide the ECU with +12V and ground on the power supply pins.		You will also need to provide the ECU with +12V and ground on the power supply pins.

-	* Obtain the ROM ~~you wish to reflash the ECU with~~	+	===Obtain the ROM===
	Since the boot mode is a write-only operation, you will need the complete ROM you intend to reflash the ECU with. Make note of the XML ID of this ROM as you will need to modify its XML metadata in the next step.		Since the boot mode is a write-only operation, you will need the complete ROM you intend to reflash the ECU with. Make note of the XML ID of this ROM as you will need to modify its XML metadata in the next step.

-	* Modify the XML	+	===Modify the XML===
	Locate the XML file for the ROM you wish to use in your rommetadata directory. Temporarily change this line in your XML metadata file for the ROM you are using from:		Locate the XML file for the ROM you wish to use in your rommetadata directory. Temporarily change this line in your XML metadata file for the ROM you are using from:

Line 25:		Line 25:

	<flashmethod>shbootmode</flashmethod>		<flashmethod>shbootmode</flashmethod>
-		+
	This will tell EcuFlash to use the SH boot mode method instead of the standard kernel based reflash method.		This will tell EcuFlash to use the SH boot mode method instead of the standard kernel based reflash method.

-	* Start EcuFlash	+	===Start EcuFlash===
	You must start / restart EcuFlash to read the XML changes		You must start / restart EcuFlash to read the XML changes

-	* Load the ROM	+	===Load the ROM===
-	* Flash the ROM to the ECU	+
		+	===Flash the ROM to the ECU===
	This is a slow process as compared to a standard reflash!		This is a slow process as compared to a standard reflash!

192.168.0.3 at 20:56, 5 June 2007

2007-06-05T20:56:52Z

New page

Reflashing Subaru SH705x ECUs using the Renesas boot mode

Summary

If a Subaru ECU becomes unresponsive due to an incorrect or incomplete reflash, it is possible erase and reflash the SH705x CPU using the built in boot mode by utilizing some special hardware and EcuFlash. This page describes the procedure step-by-step.

* Build the hardware
You need to build a serial interface with which to talk to the CPU. The schematic for this interface is shown below. EcuFlash only supports FTDI based USB to serial interfaces. The schematic below shows what the interface must look like. You could build this by taking apart a FTDI-based USB to serial device and making the needed modifications. Basically, this is a simple TTL-level serial interface where the raw TXD and RXD signals are taken from the FTDI chip. There is also a 555 timer based circuit to provide the watchdog signal while in the boot mode.

* Connect the hardware to the ECU
Make the connections diagrammed in the schematic. If the test points listed in the schematic (Pxxx) are not on your ECU PCB, you should be able to find the needed pads by tracing them from the CPU pins (also listed in the schematic).

* Power the ECU
You will also need to provide the ECU with +12V and ground on the power supply pins.

* Obtain the ROM you wish to reflash the ECU with
Since the boot mode is a write-only operation, you will need the complete ROM you intend to reflash the ECU with. Make note of the XML ID of this ROM as you will need to modify its XML metadata in the next step.

* Modify the XML
Locate the XML file for the ROM you wish to use in your rommetadata directory. Temporarily change this line in your XML metadata file for the ROM you are using from:

<flashmethod>sti05</flashmethod>

to:

<flashmethod>shbootmode</flashmethod>

This will tell EcuFlash to use the SH boot mode method instead of the standard kernel based reflash method.

* Start EcuFlash
You must start / restart EcuFlash to read the XML changes

* Load the ROM
* Flash the ROM to the ECU
This is a slow process as compared to a standard reflash!