[ChrisF30]

Hi
This is a great post that helps me to downgrade my head unit to ID4 and ease the fsc, and then flashed to ID5 with a G11 VIN. The flashing process seems gone well, I think. But it won't take cdDeploy. Also it won't let me do VO code, I get this error when doing VO code,

"job=com.bmw.psdz.jobs.uds.MCD3_PerformECUCoding, service=WDBI_PLAIN - WriteDataByIdentifier with unlimited Data-ID (plain hex value), description=error: negative response : requestOutOfRange, link=HU_NBT2_63_ETHERNET>"

So, I have to inject a proper CAFD to it and manually change settings one by one. I use NCD tools to compare mine CAFD and a CAFD from G11. However, no matter what I have changed, the screen shows "No signal". Been playing around HMI_VERSION, HMI_ID_VERSION, APIX, color depth and display size. No luck.

Helps.

[pshoey]

You don't mention what screen size you're using. Assuming it is an 8.8 screen, you should choose

CID_APIX_MODE: APIX1
CID_COLOR_DEPTH: 18
CID_DISPLAY_RES: 1280_480
CID_COM_MODE: spi

[ChrisF30]

Followed the instruction, the screen turns black.

Two more things:
1. For coding convenience, I setup a DHCP server and connect it through Ethernet to OABR port without going through a CAN Bridge. But every time when I reconnect it, I have to inject a CAFD again. Seems the injection does not success. I then change to F20 in connection and load a F30 FA with build date set to 0716, and I am able to VO code this head unit. However, it shows "No Signal" again, though now every time I reconnect it with ESYS and I do not have to inject a CAFD anymore.
Check the parameters.
1. CID_APIX_MODE: APIX2
2. CID_COLOR_DEPTH: 24
3. CID_DISPLAY_RES: 1280_480
4. CID_COM_MODE: mii
5. CID_DISPLAY_SIZE: 8_8

2. Even though the FDL coding is success, but I see an error in preparing TAL Execution, especially it has a message showing ECU with address 0xffffffff. The head unit is imported with G11 FSC and not sure if this error related to this FSC set. Perhaps I need a F30 ID5 FSC set.

[] prepareTALExecution finished
MCDDiagService<id=292900, job=com.bmw.psdz.jobs.uds.vcm.MCD3_ReadSVTVersionFromVCM, service=RDBI_SVT_VERSION - ReadDataByIdentifier SVT-Version, description=error: timeout, link=Physical request to ECU with address 0xffffffff>
[] prepareVehicleForCoding started


From the above testings, this leads to me that maybe I should not flash this head unit with a G11 FA but I should flash it with a F30 FA as when I was trying to inject a CAFD, I have to choose S15A in connection. If I choose F20, then I get this error "Failed to get CAFs for swfl_00002718-002_030_002".[C111] KIS error: Die technische Einheit 00002718 konnte in der KIS-Wissensbasis nicht gefunden werden. [1283]

Does anyone have a F30 ID5 SVT for sharing?
By the way, I flashed the head unit with V57.3. Perhaps I should flash it to V59.2.

You don't mention what screen size you're using. Assuming it is an 8.8 screen, you should choose

CID_APIX_MODE: APIX1
CID_COLOR_DEPTH: 18
CID_DISPLAY_RES: 1280_480
CID_COM_MODE: spi

[Gabrola]

VO coding is failing because there is something in your FA file that is invalid for NBT. For example this also occurs if you try to VO code 3AG rear camera on a HU_ENTRY that does not support it.
Try to compare your FA with an FA from a newer car with ID5 stock and adjust you FA file. If this doesn't work you can also generate an NCD using Coding-Verification instead of coding your CAFD manually.

[ChrisF30]

Thanks.
Yes, this is why I changed the connection to F20 and use a F30 FA to VO code it.
Yes, I also generate a NCD using Coding-Verification instead of coding mine CAFD manually at the end.

VO coding is failing because there is something in your FA file that is invalid for NBT. For example this also occurs if you try to VO code 3AG rear camera on a HU_ENTRY that does not support it.
Try to compare your FA with an FA from a newer car with ID5 stock and adjust you FA file. If this doesn't work you can also generate an NCD using Coding-Verification instead of coding your CAFD manually.

[BigBox]

Hello guys,

i make a id5 update on my NBT2. Now I drive since 2 month without navigation because he want a fsc. Is there any solution for this issue? Do I have to erase the FSC after I downgrade to ID4? And if yes how do I get the old bootloader to work?

regards

Dominic

[BhdR]

Can someone share 56.5? I couldn't find the link is working properly.

[gt678]

A question for the masters, I downgraded from 59.4 with ID5 FSC set to 56.5 to BTLD_00001FFD_002_016_006 but I´m not able to delete the FSCs, always it appears "ERROR_ECU_REQUEST_OUT_OF_RANGE".
When I did this downgrade with ID4 ones it was no problem.
Is there any special trick?

[840i]

A question for the masters, I downgraded from 59.4 with ID5 FSC set to 56.5 to BTLD_00001FFD_002_016_006 but I´m not able to delete the FSCs, always it appears "ERROR_ECU_REQUEST_OUT_OF_RANGE".
When I did this downgrade with ID4 ones it was no problem.
Is there any special trick?

Did you reflash bootloader too to 56? Someone reported he just reflashed the bootloader to 56.5 and he was able to delete FSC...

Did you use NBTEVO.PRG instead of NBT.PRG?

[gt678]

It´s complete flashed to 56.5 and I also tried to do it with NBTEVO.PRG, but no sucess