(22-04-2024, 06:04 AM)evaldazj Wrote:  If mgu come with 6u3 originaly, 8.8 screen won't work. And Your's resolution is wrong

(23-11-2024, 23:51 PM)TIGHTFIN Wrote:  If you connect the MGU to the bench from one car in conjunction with the BDC3 module from another car, perform flashing. And return the MGU to the car from where it was filmed. Will component protection appear? And will I need to generate an f5с code to remove the protection? Or nothing will happen if you return the MGU after firmware to the original BDC ?

(18-12-2024, 07:31 AM)kreatif74 Wrote:  use several different configurations in order to find correct one. F.e. from the car where was display installed or from mgus car
MB, display from NBT

(19-04-2024, 17:34 PM)kimz Wrote:  I hooked up BDC2 <-> MGU with CAN+ETH. However, I only have a black screen, no їшяgё, only backlight. MGU and BDC are not from the same car. My question is: does it have to be from the same car for the MGU to get їшяgё? During flashing i got blue boot screen, that's why i think the cable and CID are good. I know about component protection with an incompatible VIN, but I'm wondering if I should get an їшяgё

Coding:
6U3 with FDL changes

Code:

- CID_DISPLAY_RES to 1440_540
- CID_APIX_MODE apix2
- CID_DISPLAY_SIZE 8_8
- CID_COLOR_DEPTH 24
- CID_COM_MODE mii
- DISPLAY_VARIANTE breites_display
Size and resolution with _2021 also 8_8 and 1440_540

With 6U2 same issue
Screen: G20 8.8 9841821 (with entrynav cid cable)

What seems strange to me is that even after flashing ё5у5, the f5с certificates were not rejected (AppID 341(0x155) AppID 381(0x17D) and AppID 371(0x173) all other are not available)
Is this the fault of this error? 026372  IPSEC_FEHLER_AUFGETRETEN