[Skyline92]

Hey guys.
I've updated my best friends F10 and the DSC2 update failed. I've done this like 20x already so I'm not new to it.
All other ECUs went through fine, just the DSC2 died. Anyone has an idea how to fix this?

ESYS shows attached errors.

EDIT: ISTA shows the ECU in red, not blue.

Code:

code: TIMEOUT P2/T2 occurred

 description: P2 timeout on Service RDBI_FTP has error in result: [Severity=2051][ErrorCode=58640][ErrorCodeDescription=resource not available][VendorCode=2142][VendorCodeDescription=P2 timeout occured]; LinkName: DSC2_29_ETHERNET
 severity: ERROR

<MCDDiagService<Id: 46900, Jobname: com.bmw.psdz.jobs.uds.MCD3_GetSVKfromECU, Diagnoseservice: RDBI_SVK - ReadDataByIdentifier SVK, Beschreibung: error: timeout, LogicalLink: DSC2_29_ETHERNET> [DIAGSERVICE]>

<MCDDiagService<Id: 46900, Jobname: com.bmw.psdz.jobs.uds.MCD3_GetSVKfromECU, Diagnoseservice: RDBI_SVK - ReadDataByIdentifier SVK, Beschreibung: error: timeout, LogicalLink: DSC2_29_ETHERNET> [DIAGSERVICE]>
<MCDDiagService<Id: 46900, Jobname: com.bmw.psdz.jobs.uds.MCD3_GetSVKfromECU, Diagnoseservice: RDBI_SVK - ReadDataByIdentifier SVK, Beschreibung: error: timeout, LogicalLink: DSC2_29_ETHERNET> [DIAGSERVICE]>
<[DSC2 - 29] Während der TAL-Abarbeitung ist ein Fehler aufgetreten, bitte überprüfen Sie die Log-Datei. [WARN]>
<[DSC2 - 29] - [Exception - DSC2 - 29] negative response error: 
 code: TIMEOUT P2/T2 occurred
 description: P2 timeout on Service RDBI_SVK has error in result: [Severity=2051][ErrorCode=58640][ErrorCodeDescription=resource not available][VendorCode=2142][VendorCodeDescription=P2 timeout occured]; LinkName: DSC2_29_ETHERNET
 severity: ERROR

[bmchicago]

u checked fuse for DSC?

[leo04]

can you still ping DSC via Tool32?
Why did you program this? How did you create a TAL?

[Skyline92]

DSC Fuses are fine. Checked all 3 of them.

If you let me know how to ping it, I'll try. Trying to access it via Tool32 however (reading error memory etc) doesn't work though.

I've created TAL via the TAL-Calculation Tab.

Is it possible that it somehow got removed from ZGW and now we cannot access it?

Updated with an ICOM Next.

[user_530d]

Open up all Flexray port's from ZGW. Then read out ecu tree with esys. When DSC not come up in tree it is out off work, fuse (ok you have checked), cabeling or whatever.
If the bootloader update failed, the dsc is died.
You can try Flexray-init with ISTA.

[larshutten]

Try removing battery terminal for 1h or more and try again.

[Siki78]

DSC Fuses are fine. Checked all 3 of them.

If you let me know how to ping it, I'll try. Trying to access it via Tool32 however (reading error memory etc) doesn't work though.

I've created TAL via the TAL-Calculation Tab.

Is it possible that it somehow got removed from ZGW and now we cannot access it?

Updated with an ICOM Next.

Did you try to write svt to vcm again?

[vanos]

Try battery reset, as Larshutten wrote.