Here's a beta of the command line reflashing tool

OpenECU software executables and source code

Moderator: Freon

Changes in OpenPort 1.2

Postby cboles » Tue Oct 25, 2005 11:46 am

There was only OpenPort 1.0 and now OpenPort 1.2. The 1.1 design was passed over. The OpenPort 1.2 has the following improvements

* crystal USB oscillator instead of ceramic resonator (I had a couple of bad units because of this)
* removal of opto isolators to increase speed (can now go up to 1Mbaud)
* addition of serial EEPROM for USB VID/PID to allow software to automatically identify OpenPort
* switchable 12V programming line to allow safe connection to non-Subarus and to initialize EVOs
* better regulated 12V line - now usually within 50mV of 12V
* connection of L-line to both Subaru and standard L-lines
* improved board design for easier manufacture / assembly
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Postby Jeramie » Tue Oct 25, 2005 11:59 am

Humm.... Should I be ordering a new cable? I assume the faster cable won't allow for faster logging speeds? Or will it? Thanks
Jeramie
 
Posts: 155
Joined: Thu Jun 23, 2005 12:45 pm
Location: Quakertown, PA

Postby cboles » Tue Oct 25, 2005 1:03 pm

In the end, the functionality is software dependent. Nothing you are using today will go faster with the OP 1.2. I haven't experimented with how fast you can run the Subaru ECUs, but I suspect its not much faster that the old OpenPort will run, considering the unshielded wiring bus that it is connected to. In any case, everything I write will support the 1.0 as well.

Colby
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Postby Jeramie » Tue Oct 25, 2005 1:26 pm

Do I get a discount if I buy another? LOL

BTW sent you an e-mail.
Jeramie
 
Posts: 155
Joined: Thu Jun 23, 2005 12:45 pm
Location: Quakertown, PA

Postby ride5000 » Fri Nov 25, 2005 6:43 am

tried it out this morning and got this:

Code: Select all
1452 byte kernel read.
kernel checksum is valid (n = 2).
kernel image loaded and verified.
Connect the green test mode connector under your dash, turn your ignition to the
 'ON' position,then quickly, press the D key to dump all of ecu memory,
or any other key to cancel.
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
kernel flash disable
rkrv: preamble 1 error


fuel pump and fans never stopped cycling.

i'm going to try the gui version for the hell of it in a few minutes. i have an 03.

ken
ride5000
 
Posts: 44
Joined: Tue Feb 01, 2005 12:18 pm
Location: lincoln, ri

Postby New2Scoobs » Fri Nov 25, 2005 12:44 pm

Have you jumpered the pins in the flash connector?

http://forums.openecu.org/viewtopic.php?t=170&start=0

ride5000 wrote:tried it out this morning and got this:

Code: Select all
1452 byte kernel read.
kernel checksum is valid (n = 2).
kernel image loaded and verified.
Connect the green test mode connector under your dash, turn your ignition to the
 'ON' position,then quickly, press the D key to dump all of ecu memory,
or any other key to cancel.
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
denso02_bootloader_cmd_start
kernel flash disable
rkrv: preamble 1 error


fuel pump and fans never stopped cycling.

i'm going to try the gui version for the hell of it in a few minutes. i have an 03.

ken
New2Scoobs
 
Posts: 60
Joined: Fri Nov 04, 2005 5:55 am

Postby ride5000 » Sat Nov 26, 2005 9:05 am

no, i just connected my "green" terminals together. i will crawl under the dash again today to check if i have other terminals.

the gui version did not work, as expected.
ride5000
 
Posts: 44
Joined: Tue Feb 01, 2005 12:18 pm
Location: lincoln, ri

Postby dust12 » Mon Dec 05, 2005 8:19 pm

Ken, were you able to get it to work?
dust12
 
Posts: 4
Joined: Tue Nov 15, 2005 8:21 pm

Postby m1borromeo » Tue Jan 03, 2006 7:28 am

I'm also getting similar results when I tried this:

1452 byte kernel read.
kernel checksum is valid (n = 2).
kernel image loaded and verified.
denso_cmd_0x81
denso_cmd_0x83
denso challenge-response
denso_cmd_0x10
validating denso kernel ram area addr: 020000 len: 05AC
validating denso kernel ram area addr: 020000 len: 05AC
writing denso kernel area addr: 020000 len: 05AC
writing denso flash block addr: 020000 len: 0080
validating denso kernel ram area addr: 020000 len: 0008
entering kernel
kernel get version
rkrv: preamble 1 no response

My setup is as follows:
MY2004-AH792
Cobb AP serial cable (com1)

Steps I took/tried to read/dump my ecu:

1)connected Cobb cable, green test connector, ecuflash, key on.
2)connected Cobb cable, green test connector, ecuexplorer, key on.

In both cases I get the same results above. The fan/pump never cycled. It only cycled if i turned power (key) on without running ecuflash. I will try to jumper 1-2,3-4 as stated earlier - even if I dont want to flash yet.
m1borromeo
 
Posts: 17
Joined: Wed Oct 19, 2005 8:24 am

Postby cboles » Tue Jan 03, 2006 8:47 am

This has been covered many times. The Cobb cable cannot work for reflashing using a standard serial port.

Colby
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Postby m1borromeo » Tue Jan 03, 2006 1:57 pm

Sorry, my initial search did get me to that info. Anyway, for folks like me who missed that vital information - here is a link.

http://forums.openecu.org/viewtopic.php ... t=cobb+usb
m1borromeo
 
Posts: 17
Joined: Wed Oct 19, 2005 8:24 am

Postby ride5000 » Thu Jan 12, 2006 4:23 pm

ride5000 wrote:no, i just connected my "green" terminals together. i will crawl under the dash again today to check if i have other terminals.

the gui version did not work, as expected.


i did have other terminals, the expected "4 wire" block. finally got around to jumpering them today and tried again (using the gui ecuflash however).

now i'm one step closer :), but it seems my 03 ecu might have a different tpu checksum algorhythm... see http://forums.openecu.org/viewtopic.php?t=209
ride5000
 
Posts: 44
Joined: Tue Feb 01, 2005 12:18 pm
Location: lincoln, ri

Postby cboles » Thu Jan 12, 2006 4:37 pm

just curious: have you tried reading out your ecu using the 04 mode? it might just work...

colby
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Postby ride5000 » Fri Jan 13, 2006 2:05 pm

cboles wrote:just curious: have you tried reading out your ecu using the 04 mode? it might just work...

colby


i did indeed try that colby, unfortunately.

i am off to try the CLI version (0.91) since crazymikie said he had slightly better luck with it. who knows?

ken
ride5000
 
Posts: 44
Joined: Tue Feb 01, 2005 12:18 pm
Location: lincoln, ri

Postby ride5000 » Sat Jan 14, 2006 4:19 am

ride5000 wrote:
cboles wrote:just curious: have you tried reading out your ecu using the 04 mode? it might just work...

colby


i did indeed try that colby, unfortunately.

i am off to try the CLI version (0.91) since crazymikie said he had slightly better luck with it. who knows?

ken


as suspected, no go. same status messages. didn't do a portmon cap.
ride5000
 
Posts: 44
Joined: Tue Feb 01, 2005 12:18 pm
Location: lincoln, ri

Previous

Return to OpenECU Software

Who is online

Users browsing this forum: No registered users and 9 guests