FEZConfig Issue

[Gene]

I posted about an issue I am having in an earlier thread where we’ve loaded VS2013, NETMF and the latest pre-release SDK on 3 different computers and everything works fine, we can compile, download and debug. Except on one computer where FEZConfig throws an exception before it even opens a window. Now we’re bringing a fourth computer up and have another fact to toss on the pile. This computer had
NETMF and Gadgeteer Package 2014 R5 on it and we were able to run FEZConfig just fine. We uninstalled
NETMF and Gadgeteer Package 2014 R5 and installed GHI Electronics NETMF SDK 2015 R1 Pre-Release 2. Now FEZConfig throws the same exception we see on the other machine.

1. Can we download just the FEZConfig that came with 2014 R5 from somewhere?
2. Any idea what might be going on?

[mcalsyn]

What is the exception? Can you post some specific details on the exception?

[mcalsyn]

Good point Andre - I missed the reference to the earlier post. Did you follow Mike’s suggestion from there and compare config files? You should continue the discussion over there (if the exception is the same).

[Gene]

We did what Mike suggested. In fact we copied over the entire directory from a machine that FEZConfig worked on to the machine where it didn’t and got the same results.

I started a new thread because I was hoping to get an answer to my question 1 above as quickly as possible.

[Mike]

when you uninstalled the sdks, in preparation to reinstall, did you also uninstall the GHI USB drivers?

[Gene]

I believe so. I don’t explicitly uninstall the USB drivers but I watch pretty closely the messages that pop up when uninstalling the GHI SDK package and at one point early in the uninstall process it says something like “uninstalling USB Drivers”.

My recollection is the drivers used to show up in the programs applet in control panel as a separate program that would have to be reinstalled separately but they don’t show up know and I’m guessing based on the message I see that GHI has folded the install and uninstall of the USB drivers into the SDK install/uninstall.

At this point we have been addressing several really nasty issues that seem to be related to upgrading to the 2015 pre-releases and have been stopping progress for way too long. So, I’m taking the admittedly drastic stop of rolling back everything to what I was using at the end of last year to see if I can get a stable environment again. When I get a chance and a little bit of sanity back, I’ll post what we’ve been seeing. A short summary is a GPS receiver we talk to using I2C seems to now intermittently create problems that prevent the debugger from attaching. We see the same problem while using a flash drive on the USB host and we’re also seeing random reboots that we haven’t been able to get any kind of repeatable handle on what is causing the reboot although at this point I don’t even know if it is a software issue or a electrical noise issue.

[John_Brochue]

@ Gene - All of our installers are now under the single SDK entry in Programs and Features. To get the 2014 R5 SDK, you can copy the directory to a new computer without issue. If you want to get the installer, take a look at the /layout command line parameter for the installer. For the FEZ Config crashes, can you look in the Event Viewer and see if there is a stack trace or other relevant information in the crash entries?

For the reboots, what does LastResetCause in Watchdog tell you? Does the trouble with attaching to the debugger happen with a blank program and the USB drive connected?

[sfugarino]

@ John -

I’m having the same issue. FEZ Config crashes on load after upgrading. Below is the exception text:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at FEZConfig.TinyConfiguaration.TinyConfiguaration_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.6.100.0 built by: NETFXREL2STAGE
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

FEZ Config
Assembly Version: 4.3.7.10
Win32 Version: 4.3.7.10
CodeBase: file:///C:/Program%20Files%20(x86)/GHI%20Electronics/FEZ%20Config/FEZ%20Config.exe

System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Microsoft.SPOT.Debugger
Assembly Version: 4.3.1.0
Win32 Version: 4.3.1.0
CodeBase: file:///C:/Program%20Files%20(x86)/GHI%20Electronics/FEZ%20Config/Microsoft.SPOT.Debugger.DLL

System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.6.81.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll

MFDeployEngine
Assembly Version: 4.3.1.0
Win32 Version: 4.3.1.0
CodeBase: file:///C:/Program%20Files%20(x86)/GHI%20Electronics/FEZ%20Config/MFDeployEngine.DLL

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box. :wall:

[John_Brochue]

@ sfugarino - We’ve seen customers have this issue a few times, though we’ve unable to reproduce it ourselves so far. we are still trying to track it down.

[sfugarino]

First time around, I didn’t. But, I went back and uninstalled everything and reinstalled. Same issue. I wonder if it’s the driver? Seems like that got removed by the uninstall, but I’m not sure. Got a couple things I’m going to try and will report back.

[Gene]

I’m trying once again to upgrade to GHI NetMF SDK 2015 R1 and have the same issue that FezConfig throws an Unhandled exception. Here’s the text from the Unhandled exception window. Below that is what I was able to get out of the Windows Event Viewer. I tried to repair the GHI SDK installation. As part of that process, this website pops up: file:///C:/Program%20Files%20(x86)/Atmel/sam-ba_2.12/doc/usb_notice.html
It talks about the SAM-BA USB driver. I can’t find the ‘atm6124.Sys ATMEL AT91xxxxx Test Board’ entry it refers do anywhere in the device manager if that makes a difference and none of the options for installing it seem to pop up for me.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at FEZConfig.TinyConfiguaration.TinyConfiguaration_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18444 built by: FX451RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

FEZ Config
Assembly Version: 4.3.7.10
Win32 Version: 4.3.7.10
CodeBase: file:///C:/Program%20Files%20(x86)/GHI%20Electronics/FEZ%20Config/FEZ%20Config.exe

System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34251 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34270 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Microsoft.SPOT.Debugger
Assembly Version: 4.3.1.0
Win32 Version: 4.3.1.0
CodeBase: file:///C:/Program%20Files%20(x86)/GHI%20Electronics/FEZ%20Config/Microsoft.SPOT.Debugger.DLL

System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll

MFDeployEngine
Assembly Version: 4.3.1.0
Win32 Version: 4.3.1.0
CodeBase: file:///C:/Program%20Files%20(x86)/GHI%20Electronics/FEZ%20Config/MFDeployEngine.DLL

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

The following is from the Windows Event Viewer

Log Name: Application
Source: Application Error
Date: 11/6/2015 9:40:36 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Vailuluu.shore.mbari.org
Description:
Faulting application name: FEZ Config.exe, version: 4.3.7.10, time stamp: 0x55ba6aa6
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x008127dd
Faulting process id: 0x1ae4
Faulting application start time: 0x01d118ba38c984bc
Faulting application path: C:\Program Files (x86)\GHI Electronics\FEZ Config\FEZ Config.exe
Faulting module path: unknown
Report Id: 7c988faf-84ad-11e5-871b-00247e3b7d3e
Event Xml:



1000
2
100
0x80000000000000

70330
Application
Vailuluu.shore.mbari.org



FEZ Config.exe
4.3.7.10
55ba6aa6
unknown
0.0.0.0
00000000
c0000005
008127dd
1ae4
01d118ba38c984bc
C:\Program Files (x86)\GHI Electronics\FEZ Config\FEZ Config.exe
unknown
7c988faf-84ad-11e5-871b-00247e3b7d3e

Log Name: Application
Source: .NET Runtime
Date: 11/6/2015 9:40:35 AM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Vailuluu.shore.mbari.org
Description:
Application: FEZ Config.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
Stack:
at FEZConfig.ConnectionForm.DisconnectCurrentDevice(Boolean)
at FEZConfig.ConnectionForm.RefreshDeviceNameInList(Boolean)
at FEZConfig.ConnectionForm.ThreadRefeshDevice()
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

Event Xml:



1026
2
0
0x80000000000000

70329
Application
Vailuluu.shore.mbari.org



Application: FEZ Config.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
Stack:
at FEZConfig.ConnectionForm.DisconnectCurrentDevice(Boolean)
at FEZConfig.ConnectionForm.RefreshDeviceNameInList(Boolean)
at FEZConfig.ConnectionForm.ThreadRefeshDevice()
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

[Gene]

@ andre.m - Thanks for the quick response. Can you tell me how to re-install the .net framework? I attached an image of the .Net entries that show up in ControlPanel/Program and Features.

[Gene]

I tried repairing the .Net Framework 4.5.1 that was on my computer: Still no FEZConfig
I tried upgrading to the latest .Net Framework 4.5.2: Still no FEZConfig
I tried loading the FEZConfig directory from the one computer I have where it does work onto a thumb drive and running it on one of my computers where it does work: Still no luck.

I’m open to other ideas. - Thanks

[GZUIdrtHIU]

that makes www.casesam.co.uk troubleshooting only more complicated

[michaelb]

I’ve installed the same SDK’s ect, on several laptops, and after an accident where they were destroyed, & now replaced them, get this same error. Is there any formal fix, rather than just guess & test at re-formatting/re-installing?

Thnx.

For the record, here is the complete error
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at FEZConfig.TinyConfiguaration.TinyConfiguaration_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

FEZ Config
Assembly Version: 4.3.7.10
Win32 Version: 4.3.7.10
CodeBase: file:///C:/Program%20Files%20(x86)/GHI%20Electronics/FEZ%20Config/FEZ%20Config.exe

System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Microsoft.SPOT.Debugger
Assembly Version: 4.3.1.0
Win32 Version: 4.3.1.0
CodeBase: file:///C:/Program%20Files%20(x86)/GHI%20Electronics/FEZ%20Config/Microsoft.SPOT.Debugger.DLL

System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll

MFDeployEngine
Assembly Version: 4.3.1.0
Win32 Version: 4.3.1.0
CodeBase: file:///C:/Program%20Files%20(x86)/GHI%20Electronics/FEZ%20Config/MFDeployEngine.DLL

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[John_Brochue]

@ michaelb - Which SDK are you using?

[michaelb]

@ John -

I’m using 4.3. I’ve installed the exact same software on two brand new laptops, one being a low end macbook used more just as a dumb terminal to eavesdrop on a running system, and a more powerful I7 used for development. Its the I7 that won’t work.
Also running windows 7 professional on both laptops.

Thanks

[Brett]

@michaelb

@ John -

I’m using 4.3.

Thanks

We need to know what GHI SDK version are you using? 2015 R1?

[michaelb]

@ Brett -

2015 R1
Built 2015-08-25
Requires Gadgeteer SDK 2.43.1000
Version 4.3.7.10

I opted for the more stable version, although the idea of driving around to all the sites to update the TinyBooter frustrates me, (as typically a climb of 130feet or so is required).

Michael.

[John_Brochue]

@ michaelb - Is the display DPI on the machine that fails set to something other than 100%?