bezzeb
Posts: 33
Joined: Thu Sep 17, 2020 5:53 am

Problemwith MCU P062F

Fri Apr 30, 2021 9:54 am

Hello
My car arrived with a non-original inverter (MCU)

It did not start until I reflashed the VIN number in the EEPROM (MCU).

After this, the car started but with an error and after 60 km / h i have a turtle

The problem with the turtle can be solved if I delete the error in MCU (P062F) and EVC (P1A1E)
but after shutdown the problem appeared again

Apparently, in addition to the vin number, something else needs to be corrected in EEPROM

Tell me how to change the EEPROM correctly so that there is no error



Also I have a second MCU with another vin number

I can use it, but now, and the immobilizer does not give it to me
He shows the old vin number and the lexia does not allow me to change it, since it changes only 1 time

Please help me solve this problem

kiev
Posts: 1671
Joined: Sun May 03, 2015 7:15 am
Location: The Heart o' Dixie
Contact: Website

Re: Problemwith MCU P062F

Fri Apr 30, 2021 11:04 am

Which car make/model do you have miev, czero, Ion ?

How did you reflash the VIN into the MCU eeprom, using an external programming device or with the OEM tool?
kiev = kenny's innovative electric vehicle

bezzeb
Posts: 33
Joined: Thu Sep 17, 2020 5:53 am

Re: Problemwith MCU P062F

Fri Apr 30, 2021 11:20 am

kiev wrote:Which car make/model do you have miev, czero, Ion ?

How did you reflash the VIN into the MCU eeprom, using an external programming device or with the OEM tool?


mitsubishi i-miev 2012

i have external programming device
i change 2 vin number in hex EEPROM

Image

kiev
Posts: 1671
Joined: Sun May 03, 2015 7:15 am
Location: The Heart o' Dixie
Contact: Website

Re: Problemwith MCU P062F

Fri Apr 30, 2021 7:41 pm

Thank you for posting the contents of the eeprom.

What are the 2 bytes at the end of the line after the VIN--is that a checksum?

What is the part number of your MCU? Is it 9499A620 ?

What about the serial number, does it match the MCU in the car? CF1101004920 and 2 bytes for check sum?
kiev = kenny's innovative electric vehicle

bezzeb
Posts: 33
Joined: Thu Sep 17, 2020 5:53 am

Re: Problemwith MCU P062F

Sat May 01, 2021 1:04 am

kiev wrote:Thank you for posting the contents of the eeprom.

What are the 2 bytes at the end of the line after the VIN--is that a checksum?

What is the part number of your MCU? Is it 9499A620 ?

What about the serial number, does it match the MCU in the car? CF1101004920 and 2 bytes for check sum?


sorry but i dont know

9499A620 its a calculator (MCU program) number

i dont know
I have not found this number anywhere

kiev
Posts: 1671
Joined: Sun May 03, 2015 7:15 am
Location: The Heart o' Dixie
Contact: Website

Re: Problemwith MCU P062F

Sat May 01, 2021 7:35 am

If you look at the label on the MCU, there will be a part number and serial number.

9499A620 is a Mitsubishi part number for the MCU, and the C... number is the serial number.

i suspect that those must also match in the eeprom in addition to the VIN; also if these are changed then the checksum will be different also, so if you didn't calculate a new checksum and program it also, then the controller will detect that as an error.
kiev = kenny's innovative electric vehicle

bezzeb
Posts: 33
Joined: Thu Sep 17, 2020 5:53 am

Re: Problemwith MCU P062F

Sun May 02, 2021 12:32 am

kiev wrote:If you look at the label on the MCU, there will be a part number and serial number.

9499A620 is a Mitsubishi part number for the MCU, and the C... number is the serial number.

i suspect that those must also match in the eeprom in addition to the VIN; also if these are changed then the checksum will be different also, so if you didn't calculate a new checksum and program it also, then the controller will detect that as an error.


yes, you are completely right.
This number is on the MCU sticker.

How can a checksum be calculated when parameters are changed?

kiev
Posts: 1671
Joined: Sun May 03, 2015 7:15 am
Location: The Heart o' Dixie
Contact: Website

Re: Problem with MCU P062F eprom error

Sun May 02, 2021 4:30 am

What was the Old VIN and the new VIN?

What was the Old and New Part Numbers and Serial Numbers?

Did you happen to capture the hex/ascii screens, or the hex files for both versions of eeprom (before and after making changes)?

Coulomb may be able to help decode if this is some sort of checksum, CRC field, parity, etc.

Unused bytes are Blank (x00)
It appears to be using a 32-byte page with the CS in the last 2 bytes of the page.

Here is data from Stan051 eeprom starting @ address x0800
VIN in ASCII: VF71NZKZZBU901984
Hex representation: 56 46 37 31 4E 5A 4B 5A 5A 42 55 39 30 31 39 38 34
last 2 hex bytes CS?: 8B F0
VIN search returned as 2011 Citroen CZero

Here is Bezzeb data from screenshot same address
VIN in ASCII: VF31NZKZZBU801988
Hex representation: 56 46 33 31 4E 5A 4B 5A 5A 42 55 38 30 31 39 38 38
last 2 hex bytes CS?: 8B F1
VIN search returned as 2011 Peugeot iOn

Bezzeb MCU Part Number and Serial Number data starting @address x0A02
PN and SN ASCII string: 9499A620 CF1101004920
Hex representation: 39 34 39 39 41 36 32 30 20 20 43 46 31 31 30 31 30 30 34 39 32 30
last 2 hex bytes CS?: BE CB

i tried several online checksum and CRC calculators but had no success matching the codes.

Does anyone know the vendor of the eeprom? U6 on my board is etched somewhat but i can read "L64" on the first line, with an unusually large circle at pin 1, followed by "2071".

Microchip makes a 24LC64 that comes erased with all locations filled with 'FF' and a 32-byte page buffer. ONsemi has a similar device, as does Atmel, Catalyst, Fairchild, Philips, Rohm, ST, Xicor.
[edit: i think it is a Rohm device, BR24L64]

Also there are I2C and SPI versions of serial eeproms--which is used here?
[edit: Looking at the board it seems I2C since pins 1-4 are all connected to Gnd, so can't be SPI version]

The reason i bring this up is because the data shows the unused locations with blanks, x00. So did they come that way or were they cleared when programmed?

Also the eeprom used in the CMU boards seems to have a common part number but only the vendor datasheet has the correct information for pins and programming. So there may be subtle differences to be aware.
kiev = kenny's innovative electric vehicle

bezzeb
Posts: 33
Joined: Thu Sep 17, 2020 5:53 am

Re: Problemwith MCU P062F

Tue May 04, 2021 9:25 am

I took off my mcu from the car today
Here are the data that was in my first mcu
Image
Image
Image
Image

I only changed the vin number here.
Unfortunately the old one I did not write down

Checksum for old vin number is "AB 11"

Chip is 24C64

kiev
Posts: 1671
Joined: Sun May 03, 2015 7:15 am
Location: The Heart o' Dixie
Contact: Website

Re: Problem with MCU P062F

Tue May 04, 2021 12:07 pm

To help understanding, please confirm or correct the following:

1. Your car is a 2012 Mitsubishi iMiev with VIN# JMBLDHA3WCU00610 ?

2. When you got the car it came with an MCU from a 2011 Peugeot iOn (VIN ..801988) with MCU serial# CF1101004920 ?

3. In the 24C64 eeprom, the VIN and Serial Number are contained in two 32-byte address locations?
VIN is at x0800 and x1000
Serial Number is at x0A02 and x1nnn ?

4. There is no other data on the eeprom from beginning address x0000 to the end at x1FFF ?

5. You have reprogrammed the eeprom in the Peugeot MCU to have the correct VIN of your car and the correct serial number of the MCU in all the address locations?
kiev = kenny's innovative electric vehicle

Return to “General Technical Discussions”