+- CarTechnoloGY (https://cartechnology.co.uk)
+-- Forum: Discussions All about Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=310)
+--- Forum: Automotive Help & Discussions / Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=40)
+---- Forum: BMW - Mini - Rolls Royce (https://cartechnology.co.uk/forumdisplay.php?fid=61)
+---- Thread: HU_NBT2 flashing fails without useful information (/showthread.php?tid=44950)
HU_NBT2 flashing fails without useful information - vilord - 12-01-2019
I am in the process of updating an HW3.2 evo from J16383I (2017-02?) to 2018-07.
I am working on a bench, with a ZGW2. I've flashed the ZGW2 with an updated FA including the VIN, type and VO for the car the HU_NBT2 came from (I don't have access to anything else from the HU_NBT2's vehicle).
I'm running e-sys 3.27.1, with 4.13.14 PsdZData. Flashing worked fine for the ZGW2.
When I try to run the TAL execution, updating the blFlash, swDeploy, cdDeploy, and ibaDeploy for the HU_NBT2, the evo screen goes black, the progress indicates:
preparevehicleforflash started
preparevehicleforflash finished
and then the time left goes from 35 minutes to 1 minute, and it eventually comes back FinishedWithError, but has nothing else in the log to indicate what happened (or didn't).
I have a DHCP server running, using connection type gateway connection, target F020_18_07_531_V_005_005_000, Connection via VIN.
Anyone have any ideas?
The vehicle was built 2016-11-4, I guessed the shipping i-step as F020-16-07-506, since there's no way to read the i-step from the nbt directly
RE: HU_NBT2 flashing fails without useful information - BugFix - 12-01-2019
What the ip zgw and What the ip HU
RE: HU_NBT2 flashing fails without useful information - vilord - 12-01-2019
zgw is 172.16.1.101, HU is 172.16.1.104, e-sys is 172.16.1.102
should i try changing them all to be 169.254.199.x?
RE: HU_NBT2 flashing fails without useful information - BugFix - 12-01-2019
It have to work
RE: HU_NBT2 flashing fails without useful information - vilord - 12-01-2019
Tried with e-sys 3.30.1 instead of 3.27.1. Instead of saying FinishedWithError, it says "Medium in dvd drive. Flash may have problems when updating drive firmware. Please remove medium from drive before flash"
So... apparently the problem is there's something in the drive. So glad that 3.30 has better error messaging!
If only I had an eject button on my coding bench... now to see if I can find the right CAN bus message to send to trigger an eject. Wheee!
Ejected the disk with tool32's STEUERN_ROUTINE command: ARG;STEUERN_EJECT;STR;04
RE: HU_NBT2 flashing fails without useful information - vilord - 13-01-2019
Programming complete! I now have a fully functional touchscreen 10.25" NBT evo with ID6
e-sys is only a little of a pain in the rear.