Memory dump of ECU - Page 19

Nomake Wan · #**271** 09-20-2007, 01:50 AM

Good thing I'm subscribed to this thread! Instant notification!

Here's the message reported:

usbserial.c: FTDI FT232BM Combatible Converter now attatched to ttyUSB0 (or usb/tts/0 for devfs)

Hopefully this helps?

Nomake Wan · #**272** 09-20-2007, 02:08 AM

Oh whoops, didn't see your edit. Will change it to ttyUSB0 and tell you what happens.

b3lha · #**273** 09-20-2007, 02:15 AM

Looks promising.

I'm sure you're smart enough to have figured this out already, but the command line you want is:

./ecudump -d /dev/ttyUSB0 -s 8000 -e FFFF -f ecu.dat

Isn't it rather late at night where you are?

Nomake Wan · #**274** 09-20-2007, 02:42 AM

Late? So what!?

Oops, I changed the ecudump.c file by hand and remade it, and it failed at ssm_open returning -3... should've waited for your post. Hahaha.

*goes to try again*

Nomake Wan · #**275** 09-20-2007, 02:47 AM

Nope, same thing happened using the command-line change as what happened when I changed the line in the program itself. ssm_open fails returning -3.

b3lha · #**276** 09-20-2007, 03:05 AM

Quote:

Originally Posted by Nomake Wan

Nope, same thing happened using the command-line change as what happened when I changed the line in the program itself. ssm_open fails returning -3.

Hmm. The -3 means that the call to set the custom baud rate failed. Perhaps the USB device has a different way of setting it. I'll do some research and get back to you.

Thanks for your persistance.

Nomake Wan · #**277** 09-20-2007, 03:08 AM

No problem. And don't worry about me staying up late, Thursday is my "throw-away day" before Friday.

I'm supposed to be up in LA Friday night, and was hoping to have the Stage 1 installed prior to that. We'll see though. I'll do some research too so nobody's sitting on their laurels.

Nomake Wan · #**278** 09-20-2007, 03:23 AM

Just a guess at this point, it's been a very long time since I've done any programming...

...is it because we haven't included the USB-Serial driver library in the program's loader?

b3lha · #**279** 09-20-2007, 03:41 AM

Quote:

Originally Posted by Nomake Wan

Just a guess at this point, it's been a very long time since I've done any programming...

...is it because we haven't included the USB-Serial driver library in the program's loader?

It doesn't really work like that. All devices in unix are treated as files, the program uses standard file handling API and the driver should translate that into the specific API for the device.

I've been looking at the source code for the USB serial driver (isn't it great to have an open-source OS?) and it does seem to use the same standard API as the normal serial driver. So in theory it should work fine. Could you make a small modification to the ecudump.c program so I can see what error the driver is returing?

In ecudump.c, following the call to ssm_open(comport), immediately after the line
printf("ssm_open() returned %d\n",rc);
insert a new line
perror("Error Details");
Then "make" the program and try again. Obviously at this point, you can test it without going outside and attaching the device to the car.

Nomake Wan · #**280** 09-20-2007, 03:49 AM

Error Details: Invalid Argument

Nomake Wan · #**281** 09-20-2007, 04:24 AM

Just for kicks I plugged in the Belkin adapter instead and restarted. Mistake, hahaha. It loaded a generic driver instead and the ssm_open only got to -2. Hahahaha. Oh well...

I'm gonna fall asleep on the keyboard if I don't get some rest, so I'll go do that. Here's hoping you can figure out a way to get this adapter to play nice with the penguins!

b3lha · #**282** 09-20-2007, 04:37 AM

Quote:

Originally Posted by Nomake Wan

Error Details: Invalid Argument

I think I see the problem. I'll have to make some changes to the code and get back to you.

b3lha · #**283** 09-20-2007, 09:39 AM

Quote:

Originally Posted by b3lha

I think I see the problem. I'll have to make some changes to the code and get back to you.

Remember I was saying that the serial port selects baud rate using a base and a divisor?

For a standard serial port, you set the base to 115200 and the divisor to 59. (115200/59=1952.5 baud)

It looks like the USB serial port driver (ftdi_sio.c) doesn't allow you to change the base value, only the divisor.

I've modified my program to look up the base value and calculate an appropriate divisor from it. In the case of your device, I think the base is 40000000 and the divisor should be something like 20481. (40000000/20481=1953.0 baud)

The updated software is attached. Let me know how you get on.

Nomake Wan · #**284** 09-20-2007, 01:01 PM

IT WORKS! You're a genious, Phil!! Now to go about making an if,then bit to detect whether the user of your program is using "real" serial or usb and then use the proper version of the baud code accordingly.

I'll go plug it in now! Good-bye, three hours of my life!

Yep, it's dumping smoothly. Just a waiting game at this point. Here's hoping my battery holds up!

Nomake Wan · #**285** 09-20-2007, 03:59 PM

Sorry it took so long, the dump was finished like two hours ago, but I spent the last two hours trying to figure out how to get it off of the laptop. Had a little problem with all the drives I own being NTFS and the only FAT partition being the boot drive. But then I remembered I had an SD card reader, so thanks to that I have the dump! Here you go!!!

EDIT: Oh yeah, do you by chance know what command forces the ECU to forget all of its saved values? I know the select monitor can reset the ECU completely but I see no reason why we can't do it with our laptops.