There I think is TSB available. If you have access to SI can read it. If you no have let me know to try to get via your VIN

You was correct. Doing HPCM2 reprogram BY DPS using those SPS files from archieve folder was reseting DTC's

 

Now i can do Serial Gateway updating aswell. First A and then B

4 minutes ago, mikko virta said:

You was correct. Doing HPCM2 reprogram BY DPS using those SPS files from archieve folder was reseting DTC's

 

Now i can do Serial Gateway updating aswell. First A and then B

car "ready"?

You really mean brake+start button ready ?

Not service mode (long press for start button ) ??

4 minutes ago, mikko virta said:

You really mean brake+start button ready ?

Not service mode (long press for start button ) ??

test car if ready go to service mode (long press for start button ) and reprogram k56 A after B vin must change

Car was tested OK.
Then power off on and then to service mode.
Then with DPS reprogramming Serial A, no errors
Then after that tried to  Do Serial B got that {0x0047 NOt in mapping matrix error}
I havent done after that anything. Car still on service mode

I don't know is this relted to anything, but if i try to use [get cotroller info] and use adress 47 it hasn't work .
And i am tlak about right after installng module from Donor

Is proramming for serial B done other than high speed GMLAN 6,14 ?

@mikko virtacheck them address and pins via gds2

one gateway is 6/14 other one is pin 1 by diagrams

Yes, pin1 and 33.3kb was correct for address 47(serial B)
I done Serial A reprog and after that Serial B.
Serial B almost gone 100% but then fails 😞

Any help if you look LOG file ?
 

SerialB_Fails.Txt

did you relearn VIN on module B as look like module doesn't respond on wake up signal

Did you ask that did i choosed cars own vin by using [get controller info] dialog.(attachment) ?
This method was atleast work for serial A.

After fail i have this kind of info from [get controller info] dialog.(attachment)
It clearly says that SW is not there

log simple say cannot wake up device. 

38 minutes ago, mikko virta said:

Did you ask that did i choosed cars own vin by using [get controller info] dialog.(attachment) ?
This method was atleast work for serial A.

After fail i have this kind of info from [get controller info] dialog.(attachment)
It clearly says that SW is not there

Could you attach your Serial A and Serial B DPS files?  I'd like to take a look at them.  You're failing at the OS upload so I may have some ideas. 

 

If it's not too much trouble, post the files
which you are trying to program

 

file compressed
although function 34 says it’s wrong

or am I mistaken
publish the archive let's see

 

we try thru SPS, but still fail... log file is from sps.log, not dps

UtilityFileStatus Step = 02, OpCode = 27
  01:36:36.1  MsgType=1, <[...L]00 00 02 53 27 01 [0006] FramePad 
  01:36:36.1  MsgType=2, >[...L]00 00 01 01 FE [0005] ExtAddress TxDone 
  01:36:36.1  MsgType=2, >[...L]00 00 02 53 [0004] TxDone 
  01:36:36.1  MsgType=2, >[...L]00 00 06 53 67 01 00 00 00 00 00 [0011] 
UtilityFileStatus Step = 03, OpCode = A2
  01:36:36.1  MsgType=1, <[...L]00 00 02 53 A2 [0005] FramePad 
  01:36:36.1  MsgType=2, >[...L]00 00 02 53 [0004] TxDone 
  01:36:36.1  MsgType=2, >[...L]00 00 06 53 E2 01 [0006] 
UtilityFileStatus Step = 04, OpCode = 50
UtilityFileStatus Step = 07, OpCode = 34
  01:36:36.1  MsgType=1, <[...L]00 00 02 53 34 00 00 00 0F F0 [0010] FramePad 
  01:36:36.1  MsgType=2, >[...L]00 00 02 53 [0004] TxDone 
  01:36:36.1  MsgType=2, >[...L]00 00 06 53 74 [0005] 
UtilityFileStatus Step = 08, OpCode = B0
  01:36:36.2  MsgType=1, <[...L]00 00 02 53 36 00 00 00 00 00 04 01 00 00 00 01 11 A1 01 03 82 01 00 04 .. [4084] FramePad 
  01:36:36.2  MsgType=2, >[...L]00 00 02 53 [0004] TxDone 
* Timeout Condition:  ECU DID NOT RESPOND - Invoke RETRY LOGIC!
  01:36:37.8  MsgType=1, <[...L]00 00 02 53 36 00 00 00 00 00 04 01 00 00 00 01 11 A1 01 03 82 01 00 04 .. [4084] FramePad 
  01:36:37.8  MsgType=2, >[...L]00 00 02 53 [0004] TxDone 
  01:36:38.3  MsgType=2, >[...L]00 00 06 53 7F 36 78 [0007] 
  01:36:39.5  MsgType=2, >[...L]00 00 06 53 7F 36 78 [0007] 
  01:36:40.3  MsgType=2, >[...L]00 00 06 53 7F 36 78 [0007] 
  01:36:40.4  MsgType=2, >[...L]00 00 06 53 76 [0005] 
  01:36:40.5  MsgType=1, <[...L]00 00 02 53 36 00 00 00 0F EA 44 00 0C 40 0B 66 D1 40 0B 6B 26 00 0E 00 .. [4084] FramePad 
  01:36:40.5  MsgType=2, >[...L]00 00 06 53 30 00 00 00 00 00 00 00 [0012] 
  01:36:40.5  MsgType=2, >[...L]00 00 02 53 [0004] TxDone 
* Timeout Condition:  ECU DID NOT RESPOND - Invoke RETRY LOGIC!
  01:36:42.0  MsgType=1, <[...L]00 00 02 53 36 00 00 00 0F EA 44 00 0C 40 0B 66 D1 40 0B 6B 26 00 0E 00 .. [4084] FramePad 
  01:36:42.0  MsgType=2, >[...L]00 00 02 53 [0004] TxDone 
  01:36:42.5  MsgType=2, >[...L]00 00 06 53 7F 36 78 [0007] 
  01:36:44.7  MsgType=2, >[...L]00 00 06 53 76 [0005] 
  01:36:44.8  MsgType=1, <[...L]00 00 02 53 36 00 00 00 1F D4 7F E6 10 70 70 E8 E0 0B 1C E7 85 3F 4A 04 .. [4084] FramePad 
  01:36:44.8  MsgType=2, >[...L]00 00 06 53 7F 36 78 [0007] 
  01:36:44.8  MsgType=2, >[...L]00 00 02 53 [0004] TxDone 

 

send files from cache
it doesn't matter
just need to see the files
to understand

 

3 minutes ago, KZV said:

send files from cache
it doesn't matter
just need to see the files
to understand

 

that is K56B files wher fail

b.rar

all clear
files are compressed
but this is not reflected in the programming script
you can try to fix the script
or compress files
this is a mistake by the programmers GM

been used official Tis2web SPS, VCI been request to force load software

I can't write you a private message
write to me in telegram
I'll show you what the problem is

@kostia111

3 hours ago, KZV said:

file compressed
although function 34 says it’s wrong

or am I mistaken
publish the archive let's see

 

I've just re-read your log and that's VERY interesting.....  it struggled and struggled to get the first calibration uploaded, it kept timing out but it did eventually make it.  

 

Step 08 - Struggles to send the OS calibration but eventually makes it after lots of logic retries

Step 09 - Fails to get a proper response so jumps to retrying, jumps to Step 13

  It receives this with a return RequestCorrectlyReceived-ResponsePending (expected)

Step 13 - Delay for 1 second jump to step 14

Step 14 - Increment the counter then jump back to step 02 and start again

Step 02 - Request security access again

Step 03 - Reports programming state

Step 04 - Compares, jumps to Step 07 (calibration to decide whether to skip uploading the OS or not)

Step 07 - Prepare to upload the OS calibration again, sends a 34 request

*** Fails this time as the unit responds with code 22 ConditionsNotCorrectOrRequestSequenceError

 

Are you sure this calibration is compatible with this unit? 

 

It is interesting to me though that it does eventually make it through uploading the first calibration (note in step 08, many invoke retry logic messages but it eventually does finish and goes to step 09 to try the next).   I'm leaning it's either not compatible (but not sure) or you have some communication issue going on.

 

The attached will show the logic order  The goto's will depend on whether a step was successful or not.

 

I'll see if I can find my extra unit here after and try it on mine.

 

 

There is some weird/missing data in GDS2 log too..
Communication issues are totally not out of the question here!

 

OP, is your MDI2 original?

Try updating MDI software and firmware if necessary (write "bosch mdi software" in any search engine, it will take you to the right place). Also, do not use wireless connection.

Or your GDS2 and deliverable packet is quite outdated (from 2020..) and have some issues reading/interpreting data from newer control units.