Baud rate selection needed for Ecuflash

[Freon]

I started to test baud rate selection for logging on the DBW ecu.

It seems that the baud rate selection is set once on boot for the SCI channel and the baud rate selection is the same for both logging and booting up in test mode.

I was able to successfully flash the change from 4800 to 9600 baud by changing BRR from d'129 to d'64, and I can log just fine at 9600 (with great success and speed up), but now Ecuflash will not connect. I've spent a while troubleshooting it, including a few reinstalls, so I don't think it is just coincidence. I'm pretty sure the baud rate is only set once for both logging and booting into test mode.

Colby, would it be difficult to add this? Does this add up? Are you using 4800 baud to connect Ecuflash? If needed I think it can be set back to 4800 for the flash process by setting BRR2 back to d'129 and reconnecting, though I'm not sure it matters.

[Freon]

Bump...

[cboles]

I'm sorry I haven't addressed this earlier. My plans for higher speed logging on various ECUs involves adding an ECU command to change the baud rate. This way, every time you start the car, the ECU is at the default rate. Only when a logging app wants to increase the baud rate does it actually change. This way you can retain full backward compatibility with other programs and the SSM tools. I'll try to make up a sample ROM soon to show you what I mean.

Colby

[Freon]

Fair enough, only downside is it requires custom code to be applied to every ECU.

Any chance you could help me get my ECU working again in the meantime? I think I'm pretty much stuck since I cannot get it to connect with ECUflash anymore.

[cboles]

Duh. Now I fully understand the magnitude of your problem - you are stuck! I will send you something privately, probably add a reg key for the initial baud rate for Subaru...

Colby

[Freon]

A kind forum member helped me out so I'm back up and running.

I'm now working on adding a new "command" byte to the SSM protocol code to jump out and write the bit rate register to the appropriate value. Just posted on Enguinity and Ecuedit forums with plans and request for support in the logging software.

i.e.

0x80 0xF0 0x10 0x01 0xDF 0x60

... where 0xDF is added into the code as a trigger to pop out and set BRR2 to the appropriate value.