I am working with a G120 on a custom board. I’m using Visual C# 2010 Express & 4.2 SDK & can deploy & debug successfully. I have observed 2 issues that I think might be related.
From a cold start, the device is recognized by Win7 via USB, but none of the tools can talk to it (VCE, Fezconfig 188.8.131.52, MFDeploy 184.108.40.206). The GHI updater for G120 (1.0.4) can always see the device & talk to it. I run the GHI updater, which updates everything (except GHI b/l, I believe) and thereafter all the other tools work fine, as long as the device is powered.
In what I think is a related behavior, any application that I deploy to the device persists only until power is cycled.
I’ve been able to deploy with VCE, then use FezConfig to capture a hex file of my app. After power cycle, I need to run GHI Updater again. Then I can successfully deploy the hex file with FezConfig (& sometimes with MFDeploy). Unfortunately, once again, this only persists until the next power cycle.
Any ideas? Running the GHI Updater every time is a PITA but not being able to retain an image across power cycles is clearly a deal-breaker. Help?
In case this sheds any light, this is the output of the GHI Updater:
– Log –
Connecting to device…
GHI Boot Loader Interface found at Port#: COM4
GHI Bootloader Version: 1.01
Device will be updated automatically! DO NOT disconnect or turn off the device!
Updating TinyBooter. Please wait…
TinyBooter updated sucessfully. Version number: 220.127.116.11
Updating Firmware. Please wait…
Deploying C:\Program Files (x86)\GHI Electronics\GHI Premium NETMF v4.2 SDK\G120\Firmware\Config.hex … successful!
Deploying C:\Program Files (x86)\GHI Electronics\GHI Premium NETMF v4.2 SDK\G120\Firmware\Firmware.hex … successful!
Deploying C:\Program Files (x86)\GHI Electronics\GHI Premium NETMF v4.2 SDK\G120\Firmware\Firmware2.hex … successful!
Firmware updated sucessfully. Version number: 18.104.22.168
Updating TinyBooter and Firmware is complete!