[kimz]

I replaced the damaged* disk in the NBT (not flooded, SMART ok, no bad sectors, the disk is currently working fine** in another NBT) due to restarts, after disconnecting the HDD it stopped restarting every 1.5 minutes, so I decided to replace it. New disk was initialized correctly, the entire unit was flashed to the latest version, repair pack has been loaded (previously it was activated with a patch because I couldn't activate it with FSC codes from the backup) and finally the latest map was installed. After all this the unit was working fine, even after reboot. I tested it for a few hours and all was ok.
Before putting it in the car, something occurred to me and I decided to connect it again - it turned on but with no image, only a black screen, after checking all the connections, I decided to flash it again - I don't remember at what point the flashing bricked the unit but from that moment on there was no communication with it, after uploading the dump to MEGA169p and EMMC the unit came back to life but some SWFLs are now on FFFF. Now you can't flash these SWFLs. Both BTLD and FLSL flash correctly, then HU reboots and I try to upload SWFL, but it always ends in failure.
Through HTTP it can reach 100%, through UDS it sometimes reaches 9%, sometimes up to 15% and ends in failure again. Now i have black screen and "NO SIGNAL" after few minutes.

What I have already checked and it didn't help:
- flash from esys 3.28, 3.30, 22.10,
- flash via UDS,
- flash without DVD/HDD,
- removing swfl 127d from TAL, after that this unit damages emmc/mega169p
- replacing the emmc and jacinto boards - the problem must be on the middle pcb
- bench setup is OK, I flashed two other units after that with success
- check 25PX32 - dump is correct,
- replaced small DVD/HDD connection board
- tried with another (new) HDD,
- I verified my mega/emmc dumps on other units: basic1 and high_ece - ok,
- i checked the voltages on coils 3.3, 5, 12, 9.5 for CID - they are all

Observations:
- from the start I hear the HDD immediately, it runs for about 2 minutes and then turns off (hu is not restarting at this point), I no longer have access to this disk via the console - I think esys stops programming at this moment,
- previously the unit restarted after a long time, eventually every 1.5 minutes. Until then, multimedia/USB/navigation maps worked ok
- esys doesn't show mismatch so I think SVT_SOLL is ok,
- i'm thinking about programming the GL512 - I don't have the 9x9 limiter yet, but I think it's responsible for the bootloader, which is ok, anyway, I replaced the entire board with another one

Conclusions:
Just before I got the unit, someone added it to the car (the previous one was stolen), I think that was the reason for restarting the unit, e.g. using a patch instead of a repair pack and that could have really messed things up, it is possible that something went wrong along the way, the unit was previously disassembled and the PCB and tape was painted with a marker
HU:
934781801 B068 ECE

Code:

TAL execution started.
VCM Update: VCM-Update is deactivated. VCM will not be updated. [C197]
ExecutionID=2023/11/04-22:31:39.987
[] prepareTALExecution started
[] prepareTALExecution finished
[] prepareVehicleForFlash started
[] prepareVehicleForFlash finished
[HU_NBT - 63] prepareECUforFlash started
MCDDiagService<id=352900, job=com.bmw.psdz.jobs.uds.hu.MCD3_PrepareECUforFlash, service=RC_DEACTIVATE_HDD_SAFE_MODE - RoutineControl DeactivateHddSafeMode, description=error: timeout, link=HU_NBT_63_ETHERNET_63>
[HU_NBT - 63] prepareECUforFlash finished
[HU_NBT - 63] authenticateECUforFlash started
[HU_NBT - 63] authenticateECUforFlash finished
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: TA started
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [0% of swfl_0000127d-003_009_004]
[HU_NBT - 63] performEcuFlash started with protocol HTTP
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [0% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [0% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [0% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [0% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [0% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
MCDDiagService<id=333200, job=com.bmw.psdz.jobs.http.MCD3_PerformECUFlash_Http, service=RC_CHECK_MEMORY_HTTP - RoutineControl CheckMemoryHttp, description=error: positive response with negative content, link=HU_NBT_63_ETHERNET_63>
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: 0% progress on ECUId:HU_NBT_0x63 [100% of swfl_0000127d-003_009_004]
[HU_NBT - 63 - swfl_0000127d-003_009_004] Transaction type: swDeploy;  Message: TA finished
[HU_NBT - 63] There was an error during TAL execution, please check the log files.
[HU_NBT - 63] - [Exception - HU_NBT - 63] job failed with negative response error:
code: result of the routine control service is not correct
description: service RoutineControl CheckMemoryHttp returned unexpected result: debugInformation_02_FF; LinkName: HU_NBT_63_ETHERNET_63
severity: FATAL ERROR

[HU_NBT - 63] finalizeECUFlash started
[HU_NBT - 63] finalizeECUFlash finished
[] There was an error, please check the log files.
[] - [Exception - HU_NBT - 63] job failed with negative response error:
code: result of the routine control service is not correct
description: service RoutineControl CheckMemoryHttp returned unexpected result: debugInformation_02_FF; LinkName: HU_NBT_63_ETHERNET_63
severity: FATAL ERROR

[] finalizeVehicleFlash started

[gfriedrichi]

I have already fixed some units that could no be flashed replacing this board
Seems that is possible to restore if you have some soldering skills
There are some threads about it
https://cartechnology.co.uk/showthread.p...t=mmc+dump
https://cartechnology.co.uk/showthread.p...ht=nbt+id4

[kimz]

Thanks for the answer, in my case the problem is a damaged BGA connection on the NVIDIA chip, most likely due to the disassembly of the lower PCB by the previous person. After reflow now it show's the boot logo. Problem solved, nvidia needs to be reballed