In my attempts to try and figure out why my raptor would not work with my T43 Module, I used Fez Config to try and update the firmware. I used the firmware from the 4.3 R5 SDK (it was the default that fez config chose):
R5 SDK is the latest released version, so you’re OK with that.
Did you deploy one version of your app after the firmware update ?
Can you PING the device from FezConfig? Do you get “TinyCLR” response? Can you also do a “Reboot CLR” from FezConfig as a final check.
What I tend to do if the debugger hasn’t attached during deployment (when it’s ~20 iterations in) I’ll hit reset on the board and that often allows the debugger process to communicate with the deployment and you’ll get a result.
(and no need to panic, you will not have bricked anything )
You should reselect your device in the VS project settings of your project. It’s on the deploy page I think.
Even if the device is displayed in the drop down box: Open the Box and select it again.
This is always necessary when your device is renamed, or you use a different device.
I did try erasing the main application from fez config as part of my attempts to get it working with VS again, but that didn’t seem to help. It’s still a mystery, but it hasn’t stopped working since, which is good.
I think I will use a button to trigger some things now, though, as per your suggestion. Thanks.