Part of issue is resolved. While I cannot give specifics because I don't understand them
, but anyway, I had to do a reset, courtesy of Craig and so far so good.
As a courtesy and assuming Craig and Paul have no issues, I am going to share what information was given to me.
From Craig regarding resetting RR:
For the reset, try the following:
-Turn key off
-Make sure Roadrunner is in ‘Emulation’ mode
-Open Roadrunner control, and set Roadrunner to ‘flash’ mode.
-Turn key on, wait 20 seconds.
-Turn key off, wait 20 seconds.
-Set roadrunner to ‘emulation’ mode.
-Turn key on, and try it out.
Another variation is:
-Turn key off
-Make sure Roadrunner is in ‘Emulation’ mode.
-Turn key on, wait 20 seconds.
-Open Roadrunner control, and set Roadrunner to ‘flash’ mode.
-Turn key off, wait 20 seconds.
-Set roadrunner to ‘emulation’ mode.
-Turn key on, and try it out.
Once you get a good tune / OS in there, it should stay good and no further resets should be needed.
From Paul regarding why I had issues with checksum errors:
While changing data in the RR unit, the checksum bytes in the RR unit are not updated in real-time and are therefor "wrong". The RR checksum routines are disabled to prevent the incorrect checksums from causing a problem during real time changes.
If you then save the *.tun file to disk, EFILive is "smart enough" to update the checksums in the *.tun file so that if/when that *.tun file is programmed into a non-RR PCM the checksums will be OK.
That has the side effect of causing the RR memory validation to fail at that point. Basically because the RR checksums have not been updated and the *.tun file's checksums have been updated (because the file was saved to disk) the RR memory verify option will report that the RR memory differs from the PC *.tun file. To "fix" that you should perform a full RR reflash after saving the *.tun file to disk.