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

Re: Problem with MCU P062F

Tue May 04, 2021 1:56 pm

kiev wrote: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?


1)Yes
2012 Mitsubishi iMiev with VIN# JMBLDHA3WCU00610

2) i got with mcu serial number CO1101022909 but with another VIN number
But now i have 2 mcu
CO1101022909 (installed in the car) and CF1101004920(bought, for repair, if it does not work out with the first mcu )

3)yes,2 vin number and 2 serial number
Yes ,800-810 and 1000-1010 VIN
Serial number 0A00-0A10 and 1A00-1A10

4)

5)I changed only the VIN number in the eeprom
The serial number of the mcu remains old
It matches the sticker on the lid

The only thing that I have not changed and that may give an error is the crc sum at the end of the number VIN


Image

Image

Image

Image

Image

Image

Image

Image

Image

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

Re: Problemwith MCU P062F

Tue May 04, 2021 10:45 pm

Thank you for the answers and for posting the full eeprom contents.

It appears to be other data stored which we do not know the purpose, or if it is corrupted or correct.

But we need to figure out how to calculate the correct check sum for your VIN.
kiev = kenny's innovative electric vehicle

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

Re: Problemwith MCU P062F

Wed May 05, 2021 12:27 am

kiev wrote:Thank you for the answers and for posting the full eeprom contents.

It appears to be other data stored which we do not know the purpose, or if it is corrupted or correct.

But we need to figure out how to calculate the correct check sum for your VIN.


I took as a basis the second MCU with unchanged eeprom
and tried many crc calculators
none were able to calculate the checksum correctly

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

Re: Problemwith MCU P062F

Wed May 05, 2021 10:54 pm

So comparing the eeprom data between the two MCU--in all the other addresses with the random/unknown values other than the VIN and SERIAL Number, Are they identical?
kiev = kenny's innovative electric vehicle

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

Re: Problemwith MCU P062F

Thu May 06, 2021 12:56 am

kiev wrote:So comparing the eeprom data between the two MCU--in all the other addresses with the random/unknown values other than the VIN and SERIAL Number, Are they identical?

there are differences in multiple lines

but there is an opportunity to somehow reprogram the immobilizer in order to install a second MCU ?

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

Re: Problem with MCU P062F

Thu May 06, 2021 6:46 am

There are members who have discussed programming the VIN in the P1A15 threads started by Lic and Gencis who may be able to give you some advice.

Did you remove the eeprom when reading and programming, or try to do it while still on the board? What voltage did you use for Vcc and for the serial lines?

i would be concerned that the Vcc to the board powered up or tried to power up the U1 microcontroller chip, marked 64F7047F40V, and may have corrupted or introduced errors in the eeprom.

A quick check showed continuity to the same power source for numerous pins on the top side (pins 27,46,77,84,85,89) and thru vias to several pins on the bottom side.

There is discussion about an error in reading the eeprom on the CMU boards in the BMU CMU thread.

i know less about the immobilizer and its functions than even the little bit known of the MCU so cannot recommend that approach.
kiev = kenny's innovative electric vehicle

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

Re: Problem with MCU P062F

Thu May 06, 2021 9:40 am

kiev wrote:There are members who have discussed programming the VIN in the P1A15 threads started by Lic and Gencis who may be able to give you some advice.

Did you remove the eeprom when reading and programming, or try to do it while still on the board? What voltage did you use for Vcc and for the serial lines?

i would be concerned that the Vcc to the board powered up or tried to power up the U1 microcontroller chip, marked 64F7047F40V, and may have corrupted or introduced errors in the eeprom.

A quick check showed continuity to the same power source for numerous pins on the top side (pins 27,46,77,84,85,89) and thru vias to several pins on the bottom side.

There is discussion about an error in reading the eeprom on the CMU boards in the BMU CMU thread.

i know less about the immobilizer and its functions than even the little bit known of the MCU so cannot recommend that approach.



Before programming, the microcircuit was removed from the board
I am more inclined to believe that the problem is in the checksum

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

Re: RL78 CRC

Thu May 06, 2021 10:21 am

That's good to hear.

i couldn't find anything about a CRC for the SH-2 32-bit RISC microcontroller used in the MCU in either the hardware or software manuals, which seems very strange. i did find this discussed in connection with the RL78 16-bit series devices and it includes using forward and reverse schemes for reading bytes (LSB vs MSB) which obviously would affect the result. Here is link to English language version, others may be available:
https://www.renesas.com/us/en/document/apn/rl78-family-rl78-hardware-crc-functions?language=en

It could be that the "user" of the VIN data is in a device that uses the RL78 processor and is looking for this checksum; The MCU processor doesn't need this value to do it's task and doesn't care?
kiev = kenny's innovative electric vehicle

martig
Posts: 11
Joined: Wed Jun 09, 2021 2:48 am

Re: Problemwith MCU P062F

Wed Jun 09, 2021 2:53 am

Hi,

I'm also interested in this topic. I found this program --> https://reveng.sourceforge.io/
I tried to use the VIN/CRC combination posted in this thread to find the algorithm, but I didn't get any results. I think it needs at least 4 samples.
Maybe if you could find more samples then it would be possible to figure out the algorithm.

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

Re: Problem with MCU P062F

Wed Jun 09, 2021 7:05 am

Did you try the RL78 method?

i think there are several examples of both the VIN and the Part Number sequence with the check sum in this thread on the first page.
kiev = kenny's innovative electric vehicle

Return to “General Technical Discussions”