Problem with 1.31
Its a way of interpreting data. Basically big endian means you put the most significant byte in the lowest memory address, while in little endian you put the most significant byte in the highest memory address. Basically opposites of each other.
So if the data is represented in the rom as little endian, but its being interpreted as big endian then you see errors like above (number interpretation messing up).
Tephra's example actually shows this pretty nicely.
So if the data is represented in the rom as little endian, but its being interpreted as big endian then you see errors like above (number interpretation messing up).
Tephra's example actually shows this pretty nicely.
I just uninstalled 1.31.
Look at the Scaling manager - every name has "big" for data endian.
Is it a mistake or was it a rig to get the graphing to work?
Honestly, I would prefer a new found emission table over graphical bells and whistles (or other portions of the ECU not seen) when it comes to editing my ECU since I'm not creating a product with helpful visual aids for the tune consumer.
Therefore, back to 1.30 for now - it's been good to me most of the time
Look at the Scaling manager - every name has "big" for data endian.
Is it a mistake or was it a rig to get the graphing to work?
Honestly, I would prefer a new found emission table over graphical bells and whistles (or other portions of the ECU not seen) when it comes to editing my ECU since I'm not creating a product with helpful visual aids for the tune consumer.
Therefore, back to 1.30 for now - it's been good to me most of the time
ok this is the deal.
Previously the little/big endian thing didn't work - so a lot of maps incorrectly used little when they should have used big.
Now because its been fixed all those little entries in our custom maps have taken affect and screwed the byte order.
Just go through and change everything to big instead of little. I don't think there are any maps in ROM that use little endian anyways...
Cheers
Dave
Previously the little/big endian thing didn't work - so a lot of maps incorrectly used little when they should have used big.
Now because its been fixed all those little entries in our custom maps have taken affect and screwed the byte order.
Just go through and change everything to big instead of little. I don't think there are any maps in ROM that use little endian anyways...
Cheers
Dave
I only see the word "little" used in the Evo base xml files. Some lines end with big endian and others with little. Is it in these xml files you change the word "little to big"?
if you copied your xml over from a previous version of ecuflash then you will need to change it.
if you are using the bundled xml's then you shouldn't need todo anything...
if you are using the bundled xml's then you shouldn't need todo anything...
1.31 seems to work OK except for the greyed out entries which still display map, the order of tables and the idle stepper RPM(can't remember if it was like this since it displays the same with several ROM ids ).
