X5 trailer hitch coding

[oma3710]

I am trying to code my car after I did trailer hitch install and module. I followed below instructions from another forum member. My car was recently in for service and they update my software to the newest update. I keep getting an error.

I found a ton of posts sprinkled throughout the forums about various individual lines to code for the hitch but the approach that looked most promising for 100% replicating what the dealer would do was:
add K235 to the HO-WORT folder and write the FA/FP to car
VO-Code entire car
Inject the CAFD into the AAG unit via:
Connect => Read FA (VO) => Activate FA (VO) => Read ECU(VCM) => Left-Click on desired ECU => Click on "Detect CAF for SWE" => Select the CAFD matching from latest I-Level Shown => Select OK => Right-Click on ECU (the ECU itself not the underlying CAFD) => Select CODE

Notes:
I went with K235 for coding since this is the code recommended in the official BMW retrofit instructions linked.
Despite there being lots of specific per-line coding recommendations in other posts, I VO-Coded the entire car to be safe because I couldn't find a definitive list anywhere of which ECUs would be affected by the K235 addition. Boy did I read a lot about this including all kinds of scary posts about needing a battery charger and bricking the whole car because it might take too long. I did a few test codings and they seemed awfully fast, so I turned off the engine, hooked up ESYS, held my breath, and clicked "code" at the top-level ECU.
Coding the whole car only took about 3 or 4 minutes and despite some scary cycling of various sytems accompanied by a few scary but brief errors on the idrive screen, once complete I disconnected, turned off the power completely to the car, turned it back on and all was well! Tested all the trailer lights, confirmed the hitch zoom feature was enabled when in reverse, etc. YMMV and maybe there's some huge risk here I'm overlooking so don't take this as gospel (I'm super new to coding) but the whole-car coding approach seemed awfully safe considering how fast it happened. I do know my copy of ESYS has some memory updates I think (memory is set to 4000 in the launcher), maybe that helps it go faster?
After the coding I dumped all the .ncd files and compared them to what they were beforehand and found that 10 ECUs had changed (11 if you count the AAG control unit itself). I feel like this confirms my suspicion that the OEM harness + module may be worth it over an aftermarket harness since so many other ECUs are impacted by its presence (everything from the parking assist to the chasis management module).

Impacted ECUs:
KOMBI
HC2
ACSM
DSC2
HU_NBT
KAFAS2
ICM
ICAM
BDC_BODY
PMA2

[oma3710]

Screenshots

[oma3710]

Anyone help me out with this issue?

[blue dragon]

PSZData version?

[oma3710]

Originally Posted by blue dragon

PSZData version?

4.27.20 Full

[CatalinP]

Your i-step is too old.

[blue dragon]

So this involve updating the entire car with any incremental istep versions ...?

[CatalinP]

Either bring the car to the latest I-step, or use older PSZData, compatible with the car's i-step.

And no, it is not incremental update.