success switching OS, but air bag light now stuck

They go by many names, P01, P59, VPW, '0411 etc. Also covering E38 and newer here.
kur4o
Posts: 948
Joined: Sun Apr 10, 2016 9:20 pm

Re: success switching OS, but air bag light now stuck

Post by kur4o »

Looks like the 2000 models switched to class2 communication.

Reading dtc will be easy.

Some b1001 manual included.
Attachments
B1001_00fbody.pdf
(206.67 KiB) Downloaded 150 times
draz53
Posts: 37
Joined: Mon Feb 03, 2020 1:11 pm
cars: 2000 Camaro SS

Re: success switching OS, but air bag light now stuck

Post by draz53 »

OK thanks!

I believe I found the problem - the VIN was wrong in the PCM!
It appears I was making a wrong assumption, that writing the OS+calibration included the VIN. I see that the VIN should start at 0x4021, but the area starting at 0x4000 is not written. Actually, it looks like it is cleared. So I should have either written the entire bin (somewhat scared of doing this), or done a "change VIN"? Which way is correct?
VX L67 Getrag
Posts: 2877
Joined: Sun Aug 02, 2009 9:16 pm
Location: Bayside, Melbourne, Victoria
Contact:

Re: success switching OS, but air bag light now stuck

Post by VX L67 Getrag »

I'm not 100% sure on this but if you haven't done a write entire bin, I don't think it would have changed the o.s.

But then if you were running on a calibration that didn't suit that o.s. I don't think it would run either.
User avatar
Gampy
Posts: 2331
Joined: Sat Dec 15, 2018 7:38 am

Re: success switching OS, but air bag light now stuck

Post by Gampy »

The VIN is stored in the Parameter Segment ... The Parameter Segment starts at either 0x4000 or 0x6000. The VIN starts 0x21 bytes into the Parameter Segment. (i.e. 0x4021 or 0x6021)

The "Write OS, Calibration & Boot" menu action does NOT include the parameter segment.

The parameter segment is OS dependent and therefore needs to be written when doing an OS change. i.e "Write Full Flash (Clone)" menu action.

After writing the parameter segment, you will lose the security linking ... You will need to do a Security Re-Learn, see here.

The proper way to change the VIN is through the "Change VIN" menu action ... Change the VIN, then turn off the ignition. (do not disconnect battery), wait a minute before Key On again.
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
draz53
Posts: 37
Joined: Mon Feb 03, 2020 1:11 pm
cars: 2000 Camaro SS

Re: success switching OS, but air bag light now stuck

Post by draz53 »

One thing I don't understand is when did the parameter segment get written over? I haven't done any writes of the entire bin, yet that area starting at 0x4000 got written over so the VIN and also the PCM serial number disappeared.
kur4o
Posts: 948
Joined: Sun Apr 10, 2016 9:20 pm

Re: success switching OS, but air bag light now stuck

Post by kur4o »

Th eeprom area between 99-00 and 01- is different format and not compatible between OSs. When you switch over, the pcm sense that and invalidates the data there.
Clone mode is the only way to fix it. Than a theft, case and vin relearn needs to be done.

Also seed key is defaulted to ffff and if not fixed you might have troubles reading the pcm with other software.
User avatar
Gampy
Posts: 2331
Joined: Sat Dec 15, 2018 7:38 am

Re: success switching OS, but air bag light now stuck

Post by Gampy »

Ah, kur4o beat me ...

I do not know what OS you came from so I cannot tell you which parameter segment it stored it's parameter data in ...

However, OsID 12212156 stores it's parameter data in the 0x6000 segment, what is there ??

Remember, when the Ignition is switched off, the Pcm writes it's parameter data to flash ...
I do not know the exact write operation yet, I have not found that code in a disassembly yet ... Still looking. (anyone know that code ?? (preferably in 12587603))

Heck, I have even heard that it flip flops them ... But I don't buy that, that's why I want to see it in the code.
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
draz53
Posts: 37
Joined: Mon Feb 03, 2020 1:11 pm
cars: 2000 Camaro SS

Re: success switching OS, but air bag light now stuck

Post by draz53 »

The 12212156 .bin file (2002_TA_Stick_OS12212156_Stock.bin), that I started with, has the VIN at 0x4021. That's the same place that my 2000 9381344 OS has it at.
kur4o
Posts: 948
Joined: Sun Apr 10, 2016 9:20 pm

Re: success switching OS, but air bag light now stuck

Post by kur4o »

Don`t get fooled by the vin address
Here is the difference

99-00

Code: Select all

53 C3 CF FA 00 F7 81 C2 31 44 47 30 45 52 36 56 39 31 33 38 BC 01 39 56 00 8F 0C 29 43 57 4A 50 00 32 47 31 46 50 32 32 47 37 58 30 30 30 30 30 30 30 FF FF 00 00 00 00 00 00 00 FF 20 00 80 01 7F E2 80 09 80 14 FF FF FF FF FF FF FF FF FF 00 AA 00 00 00 00 07 A5 A0
01-

Code: Select all

12 16 7D 3B 00 8F 3A 22 31 45 42 30 46 37 52 4D 30 32 37 36 BC 00 39 56 00 BA 3B 0B 44 48 59 42 00 32 47 31 46 50 32 32 47 30 30 30 30 30 30 30 30 30 FF FF 00 00 00 00 00 00 00 FF 20 00 80 05 80 2A 7F F5 7F DE FF FF FF FF FF FF FF FF FF 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF A5 A0
It can start either at 4000 or 6000 on random basis.
draz53
Posts: 37
Joined: Mon Feb 03, 2020 1:11 pm
cars: 2000 Camaro SS

Re: success switching OS, but air bag light now stuck

Post by draz53 »

Gampy wrote: However, OsID 12212156 stores it's parameter data in the 0x6000 segment, what is there ??
Just FFFFFFFF.... as far as the eye can see.
Post Reply