Hmmm. I hate PEBKAC.
You know, Problem Exists Between Keyboard And Chair....
For some reason, I was running the v4.3 version of MFDeploy. Running the v4.2 version, in order to connect to TinyCLR 4.2, works just "slightly" better.
Also need to remember to connect DTR when powering up the Netduino Mini, in order to force it into the BootLoader mode (akin to powering up normal Netduinos while holding down the button....).
INTERESTING... note that there are still the occasional "No response" errors. Following, two PINGs, followed by two attempts to Get Device Capabilities (Shift-Control-C) (more than a few seconds apart). Errors out once each, BUT... once all is said and done, I've got a Netduino Mini running 184.108.40.206.
Pinging... Error: No response from device Pinging... TinyCLR Error: No response from device HalSystemInfo.halVersion: 220.127.116.11 HalSystemInfo.halVendorInfo: Netduino Mini (v18.104.22.168) by Secret Labs LLC HalSystemInfo.oemCode: 34 HalSystemInfo.modelCode: 177 HalSystemInfo.skuCode: 4098 HalSystemInfo.moduleSerialNumber: 00000000000000000000000000000000 HalSystemInfo.systemSerialNumber: 0000000000000000 ClrInfo.clrVersion: 22.214.171.124 ClrInfo.clrVendorInfo: Netduino Mini (v126.96.36.199) by Secret Labs LLC ClrInfo.targetFrameworkVersion: 188.8.131.52 SolutionReleaseInfo.solutionVersion: 184.108.40.206 SolutionReleaseInfo.solutionVendorInfo: Netduino Mini (v220.127.116.11) by Secret Labs LLC SoftwareVersion.BuildDate: Sep 19 2012 SoftwareVersion.CompilerVersion: 410894 FloatingPoint: True SourceLevelDebugging: True ThreadCreateEx: True LCD.Width: 0 LCD.Height: 0 LCD.BitsPerPixel: 0 AppDomains: True ExceptionFilters: True IncrementalDeployment: True SoftReboot: True Profiling: False ProfilingAllocations: False ProfilingCalls: False IsUnknown: FalseGo to the full post