However with a couple being prepared to ship to a new site, I saw that the version of 4.2 installed with the latest SDK was now 4.2.11.2, and i decided to “upgrade” to that. Bad idea! With that firmware installed, the units go into “standby” mode (Hibernate) and refuse to come out when any of the buttons are pressed. Change the firmware back to 4.2.10.1 (identical application code) and it works correctly. This is with code compiled for 4.2.11.2, if there are any differences?
I think it may have been John who asked me whether I had the other problem with 4.2, or only 4.3, and I said only 4.3. That was before I tried 4.2.11.2 though, so perhaps the hibernation recovery problems had already slipped in by that version?
@ John - Yes, the symptoms are quite different. In the previous one an application built for 4.3 came out of hibernation with uninitialized IO, in this one an application built for 4.2 works with the 4.2.10.1 firmware but fails to come out of hibernation with the 4.2.11.2 firmware.
On the face of it the only common thing is hibernation, but as the actual cause of the first problem was never isolated, it could be a symptom of the same underlying cause.
The only reason I mentioned it was because you asked whether the problem started with 4.3, and as that stage the most recent release of 4.2 I had used was 4.2.10.1, I said I thought it had.
As it won’t come out of hibernation, I can’t check whether the IO is configured or not!
At this stage I’ll just switch back to 4.2.10.1, which is working well for me, and try to move straight to 4.3 when the other problem is fixed.