Hi there.

Was plesently surprised to find a noob questions area.
Im flashing my 2001 B5 S4 to turn off the EGTs, the car is completly stock and i believe ive edited the .bin file corectly in order to shut them off.
CDATR, CDATS and CATR all set to 0. checksum corrected and checked with ME7check as OK.

its a 551n box using an R box definition which is apparently compatible.

Editing seemed to go smoothly but when i go to write the modded .bin i get this message



i tried flashing the original .bin and i get the same message.

at this point i proverbially shit myself and disconnected, verified the car still starts and came inside to try and figure out whats going on.
im not all that keen on erasing the entire flash if i dont at least have some kind of good idea that itll work.

i dont have a spare ECU on hand and i dont have gear to bootmode recover.

Im hoping someone with alot more experience here will be able to give me a kick in the right direction.

the car was hooked to a battery charge aswell. if you need any other details do let me know!

Hi,
I bricked my ecu up sometime back, from there it got worse with me panicking and foolishly changing out ecu's, clusters, and keys etc.

Honestly,.... It was the best thing that happened to me through this process. It forced me to start reading and learning about Bootmode and doing it on the bench. It would have been impossible for me by the way, without the help that I was given through this forum but I had a crude bench harness rigged up in 90 minutes or so.

Bootmode isn't hard at all it turns out, and as Marty said, you really should get that up and running first. 

All the best
O.T.

It's very unlikely that the ecu is chipped. But I will pop it open and make sure now.

I'll look into what's involved with a boot mode setup, I had hoped since I was only making a small change that it would be pretty risk free but I can't afford to knock this car out of service as its my daily and the shed is already full of projects!

Can anyone explain why I'm getting this error? Even when I try flash with the original file?

Things I've considered but may not matter are ;

The baudrate in device manager was set to 9600 and in nef it was at 34800 during the read, would this cause the data to be copied wrong in the first place?

The ftdi cable may not have the correct d2xx driver, I had downloaded it to my computer and tried to use a different cable that turned out not to be ftdi, the new cable plugged in and worked right away so I didn't think about it.

Cheers for the help!

i did not even notice the R def wasnt an 8d0 file! ive downloaded the 551M file you posted Nyet

would this have caused the issues ive seen? or given that when i tried to flash the original bin i ripped from the ecu. has the issue happened somewhere else.
perhaps an issue with an incorrect driver, or disparity between the baud in nef and the baud set on the cable in device manager?

ill make sure i have a boot mode setup before i try again, but for obvious reasons id like to nail and issues before i run into them!

Why bother? Get a spare ecu, they're cheap.

Then you'll have to desolder the riser, replace the flash with a stock flash, and bootmode it back to stock.