I have a G120 board that behaves differently than others. When I use Configuration.ReadEntry or Configuration.WriteEntry I get the following error:
FAILED HEADER CRC at a0957794: 0x0c1828b2 != 0x00000000
All boards have the same TinyCLR versions and the same app is running. Does the error above point to something simple?
@ Superpanda - have you tried to reload the firmware?l
@ Mike - Yes I did. The G120 that is behaving this way is remote and the app has been deployed with MFDeploy. Your question prompted a thought however…
I am using 4.3 QFE2 and GHI NETMF SDK 2015 R1. If I created the application deployment from a G120 with TinyBooter 4.3.8.1 and deployed it to one with 4.3.7.7 should I expect problems? The one that has the “Failed Header CRC” issue might have the 4.3.7.7 TinyBooter. I only just realized that all the chips I have here are the later 4.3.8.1, but the one in the field could be older.
-AP
In my experience, yes, you should expect problems. Any changes in the memory map can cause .hex deployment to fail completely or partially. The location of the ‘config’ block may be different between those two versions.
Don’t know if it is written anywhere, but my own rule is to do .hex deployments only to firmware-identical systems.