Thanks for the attention to this issue- by your question I’m assuming this is not a “known issue” so I am evaluating work-around options.
However, it would be great to get this working the same way as it does on NetMF v4.2 so that we don’t have to change our PCB to reroute to different pins.
First, the symptoms of the problem:
- A manual power cycle is required after erasing the G120’s accessible memory and reloading the loader, firmware, and application.
- A manual power cycle is required after an in-field update after the device loads the new code, resets, and runs the application. The applicatoin is hanging up when the reboot command is issued.
Next- context of the issue:
We do an in-field update, which clears the display configuration.
The reboot out of the in-field-update works fine.
It is my understanding that we need to configure the display as “headless” to use the P1_21 and P1_22 pins as inputs.
So, we use Display.Disable() and then check the boolean return to see if we need to reboot the G120.
If the display is already disabled, the application runs fine.
However, if the application does the RebootDevice(false) call, the G120 locks up.
The references we make:
The code we run:
bool bReset = Display.Disable();