[dstrickland]

No, the 330I EGS does the same....will automatically shift in "M" mode at redline. I didn't pay that close of attention when doing it to see if there was a 100rpm cut in 3-6th. I'm still on 330I EGS now, was planning on moving back to 325I tomorrow. I'll check that before I do.

[Slim125]

Good day
help reset motor Hours
eprom
https://drive.google.com/file/d/0B4g...ew?usp=sharing

[hassmaschine]

motor hours aren't stored in the Eprom. They aren't in flash memory at all - it's stored in RAM, a portion of which is "non volatile" and isn't erased when you unpower the DME.

I could possibly write code to erase the "total running time" and reset it back to zero. The odometer is in the serial EEPROM, which you can only read/write via BDM, and I think there's another copy in RAM, which would also have to be reset via a custom program.

Both would have to be altered in order to change whatever you're trying to change - but to be honest, the only thing it affects is the power class, which you can simply just change to match your car while running the higher power class software.

Even if you did manage to reset the odometer & total running time, as soon as you plug it into your car it's going to download the highest odometer reading on the CAN bus from your instrument cluster or another module.

[Slim125]

I was told that in motor-hours in eeprom edited

[Slim125]

Have told motor-hours it is edited only in Epromm.
861 options not to activate, motor-hours are not dumped yet

[hassmaschine]

I can tell you it's not in the eprom. it's stored in non-volatile RAM. You can't just write to RAM - only the DME can do that.

what options are you trying to enable?

[Slim125]

MILANSTEUERUNG
I to wert_02, and it after coding all the same remains to wert_01. Have told it is necessary to dump motor-hours.

[hassmaschine]

What does MILANSTEUERUNG do?

Maybe it's stored in the Serial EEPROM as well, but it's difficult to erase from RAM. it will just restore itself unless you hack the program code.

[Slim125]

[rjahl]

Originally Posted by Slim125

OK, so why would you want to permanently disable the check engine light for all faults?

[hassmaschine]

Ah, I read it as Milan Steuerung. Not MIL Ansteuerung (MIL control). oops!

I don't think you can change anything on the DME with "coding". It needs to be flashed.

There's a byte on the DME to disable the MIL. so you would turn that on. And instead of changing the speed selector (which isn't possible unless you reset the hours and I believe odometer), you can just max all of them out (FF or 255kph/158mph).

If you have a way to flash your DME I can probably help you change those settings.

[Terraphantm]

Originally Posted by hassmaschine

I can tell you it's not in the eprom. it's stored in non-volatile RAM. You can't just write to RAM - only the DME can do that.

what options are you trying to enable?

Are we sure the serial Eeproms and nvram aren't one in the same? I could have sworn my DME was throwing nvram errors when I deliberately corrupted the serial Eeprom.

[hassmaschine]

I don't think so, but I could be wrong. That's probably worth looking into. I'm pretty sure the non-volatile RAM is part of the MPC5xx CPU itself, while the serial EEPROM is a seperate chip entirely.

The reason I don't think they are the same (aside from the addresses not working out?) is because I blanked out the EEPROM when testing the sport switch settings (I wanted to see if the learned variants were stored in the EEPROM). Blanking it out didn't change anything, and there were no obvious 1's and 0's that matched a pattern which could have tied it to the learned variants.

I think what I will try is a RAM dump compared to a fresh EEPROM dump and see if anything matches. I know there are a few things in there that do (the odometer is stored in both places), nothing else I saw matched that I could tell.

[hassmaschine]

Originally Posted by Terraphantm

Are we sure the serial Eeproms and nvram aren't one in the same? I could have sworn my DME was throwing nvram errors when I deliberately corrupted the serial Eeprom.

I looked closer at this idea. I'm confident the serial EEPROM is not the same as the non-volatile memory.

We know the serial EEPROM is 4kb. The NVMY on the MPC563 happens to be 4kb, but the RAM segments on the MPC555 are completely different and none match the 4kb size.

Further, nothing in the NVMY section of MSV70 matches anything close to what's stored in the serial EEPROM.

Too bad really, because I still don't have any clue where the serial EEPROM fits into the memory map. I'm thinking perhaps the DME doesn't address it directly, but saves and loads data from it through another more indirect method. MSV70 has the segment at 0x1802000 but that doesn't appear to fit the 4kb EEPROM either (and I have no idea how to read that part of the DME). It is however my best guess so far, although there are no references to a similar segment on MS45..

[Terraphantm]

Originally Posted by hassmaschine

I'm thinking perhaps the DME doesn't address it directly, but saves and loads data from it through another more indirect method.

I don't know about that. The traces look like they're going right for the CPU (probably should just remove the CPU from one of my MS45s and trace the pins directly), and I suspect if it was indirectly accessed, dumping it via BDM wouldn't be super feasible (especially for the more generic interfaces that don't know the processor is a part of an MS45 or MSV70 or whatever)

[hassmaschine]

My best guess currently is on MSV70 it's mapped to the 18020000 (which I think is actually 0x702000 in the DME). MS45 could be the same, but interestingly enough there are no definitions of this part of RAM for MS45.

I'm going to try and pull a dump from this segment today to see if PA soft will read it.

[hassmaschine]

so I tried to read the memory at 0x302000 (MS45) and 0x702000 (MSV70) and wasn't successful. Maybe Tool32 could do it, or perhaps a hand written KWP2000 script, but PAsoft can't.

[Terraphantm]

Originally Posted by hassmaschine

so I tried to read the memory at 0x302000 (MS45) and 0x702000 (MSV70) and wasn't successful. Maybe INPA could do it, or perhaps a hand written KWP2000 script, but PAsoft can't.

I was hoping disassembling the ReadMemoryByAddress routine would give us a hint since Tool32 seems to suggest that reading NVRAM should be possible in mode 03, but unless I'm mistaken, that code doesn't handle a mode 03 at all.

Also for whatever it's worth, even though the serial eeprom is 4k on the MS45, it seems like only 0x960 bytes are used by the DME

[hassmaschine]

the code in the DME doesn't? I did try Mode 03 in PAsoft but it did the same thing as everything else.

[Terraphantm]

Originally Posted by hassmaschine

the code in the DME doesn't? I did try Mode 03 in PAsoft but it did the same thing as everything else.

Well, I don't know, I know the I've gotten valid responses to mode 00, 02, 04, 06, and 07. I can definitely see how the code handles mode 07 and 02.

Though I now see that I glossed over a subroutine call within that subroutine, so the other modes might be done in there.

[rjahl]

Hass,

I was going to write a new file this evening with higher valve lift limits and the updated Valvetronic speeds but I can find the parameter. I was thinking that is was one of these but it's not but now that I pulled them up the values are wrong. Can you give me a hint?

c_ang_sp_vel_fast_vvl_cus
c_ang_sp_vel_slow_vvl_cus

[hassmaschine]

Its in the XDF under the valve lift settings. Its not either of those..