Yes, you are importing an a2l that does not match your binary, or you are importing it with the wrong offset.
That said - you know, EVC support is pretty good if you ask them.

The paid version determines the offset pretty well on it's own.
I haven't used cracked in something like 7 or 8 years...

But you can determine the offset by looking inside the a2l manually, looking at your binary and seeing where things are addressed and where things are.

On C166 variants the extflash where the calibration is, is usually loaded at 0x800000, so that is a good start. But you can see all that from the a2l.

Maybe it coud be helpful for other beginners, if you post your solution.

Remember: you asked for help at the beginning of this theard.

You're right using an offset of 800000 cleared the problem.