Possible "Burn" problem in 2.25 release

jsmcortina · Post by **jsmcortina** » Sun Apr 30, 2006 7:57 am

While working on MS2/Extra, adding additional data pages and implementing paging like MS1/Extra I have a problem. Either there is an error in my .ini file or Megatune has a bug. I'm not sure which.

I have moved the ignition tables from physical page 5, logical page 2 onto physical page 7, logical page 3. In RAM this is working just fine and I can also burn the VE tables ok. However these spark tables are not being burned to flash. I did a comm log and the data gets written but there is no Burn command.

It also seems (from MS1/Extra work) that there is no longer any error checking if one dialogue references two pages - there used to be. On MS1/Extra this is forbidden and causes data loss (as seen in 029o), but MS2 allows it because physical pages 4,5 are both in ram. MS2/Extra needs the same checking for flash pages 4,5,7,8 because only one is held in ram at one time.

Here's a chunk of my .ini

endianness = big
nPages = 3
pageSize = 988, 996, 1024
pageIdentifier = "\x00\x04", "\x00\x05", "\x00\x07"
burnCommand = "b%2i", "b%2i", "b%2i"
pageReadCommand = "r%2i%2o%2c", "r%2i%2o%2c", "r%2i%2o%2c"
pageValueWrite = "w%2i%2o%2c%v", "w%2i%2o%2c%v", "w%2i%2o%2c%v"
pageChunkWrite = "w%2i%2o%2c%v", "w%2i%2o%2c%v", "w%2i%2o%2c%v"

There is nothing special about page 3 to tell it not to burn??

James

ischmitz · Post by **ischmitz** » Tue Jun 20, 2006 8:53 am

would this explain that my ignition table changes (bins) do not stick for the most part. (MT2.25, MS-IICAN, latest firmware).

Did you find any solution so far? Is there a version of MT that does not have this issue and is recommended.

Cheers,
Ingo

jsmcortina · Post by **jsmcortina** » Tue Jun 20, 2006 9:00 am

This isn't the exact same issue, but could be related I suppose.

You are doing File->Send to ECU after the changes aren't you?

To debug this please open Megatune and start a Communications->Diagnostic Log
Then open the VE table, change a few bins File->Send to ECU and close the window. Close Megatune.
Then go find comm.log which is likely to be in
C:\Program Files\Megasquirt\car1
and attach it here.

James

ischmitz · Post by **ischmitz** » Tue Jun 20, 2006 9:09 am

OK I will do that tonight and post the findings.
Ingo