Ecuflash error problem

User topics relating to software that provides a tuning UI to alter ECU code and data

Moderator: Freon

Ecuflash error problem

Postby DonArm » Thu Dec 29, 2005 4:01 pm

Ok guy's,

Here is the latest attempt to use the Ecuflash program to obtain an image of my ecu.
I have a Cobb Stg 2 AP flash. Attached is the error that I received.
I'm using Cobbs cable with a Belden serial to USB converter.
Any help?

[0.000] kernel flash disable
[3.045] denso02_bootloader_cmd_start
[0.020] 1452 byte kernel read.
[0.000] kernel checksum is valid (n = 2).
[0.200] writing denso kernel area addr: 020000 len: 05AC
[2.924] kernel get version
[2.013] unable to load kernel
[42.071] kernel flash disable
[3.084] denso02_bootloader_cmd_start
[0.020] 1452 byte kernel read.
[0.000] kernel checksum is valid (n = 2).
[0.200] writing denso kernel area addr: 020000 len: 05AC
[2.874] kernel get version
[2.013] unable to load kernel

btw, everything is hooked up appropriately, green test connector and I tried w and w/o the flash block.
Thanks
DonArm
 
Posts: 13
Joined: Sat Dec 03, 2005 9:02 am

Postby cboles » Fri Dec 30, 2005 7:15 am

Most USB to serial cables will not work because the don't support atypical baud rates, such as the 39373 baud needed by the OpenECU kernel. You need to have a FTDI USB to serial chipset or one that can perform similarly. Or get an OpenPort.
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Postby DonArm » Fri Dec 30, 2005 2:15 pm

Is that chipset something that is part of the USB convertor cable?
The Belkin cable is a fairly high quality item.

Don

Edit: Specs say only 115kbps :cry:
DonArm
 
Posts: 13
Joined: Sat Dec 03, 2005 9:02 am

Postby cboles » Fri Dec 30, 2005 2:37 pm

Yes, the chipset of the adapter. It's not a quality issue - it's one of functionality. Most USB-serial chipsets/drivers do not support anything other than the standard baud rates (e.g. 300, 1200, 2400, 4800, 9600, 14400, 19200, 38400, 57600, 115200).

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

Postby diablerouge » Sat Dec 31, 2005 10:51 am

i get the same errors when i try to connect, but i'm not using usb. i'm using just the cobb cable attached directly to the db9 comm port on the pc. maybe it has to do with the baud settings in windows for the comm port. does either ecuExplorer or ecuFlash set the baud rate or do they fetch the windows setting? what hardware/software are you guys using successfully?
diablerouge
 
Posts: 21
Joined: Tue Dec 27, 2005 7:41 am
Location: pittsburgh

Postby cboles » Sat Dec 31, 2005 10:53 am

This will not work. Your PC serial port does not support 39373 baud. Let me break it down here - there are only 2 working combinations:

1) Openport cable.
2) Cobb + FTDI based USB adapter.

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


Return to Tuning Software

Who is online

Users browsing this forum: No registered users and 3 guests