Does Silicon Labs offer Windows 7 drivers (32-bit or 64-bit) for the Ember InSight USBLink device (EM2XX-USB-PROG-R)?
Currently there is no driver for USBLink that will natively support either Windows 7 or a 64-bit system (even under Windows XP), nor is there a commitment at this time to to retrofit the USBLink driver to these newer systems (as it's meant to be more of a development/debug tool for legacy EM2xx systems), although Silicon Labs is tracking a feature request for this for potential inclcusion if demand warrants it.
For the moment, the workaround options are as follows:
 Acquire/install an older machine with Windows XP (32-bit) to support this software/hardware.
 Install Microsoft Virtual PC and run Windows XP Compatibility Mode to create an XP environment, then run the USBLink executables under that environment. For more about this, see article @ http://windows.microsoft.com/en-us/windows7/install-and-use-windows-xp-mode-in-windows-7.
 Use Ethernet-based ISA (P/N: EM2XX-ISA-R) device for programming rather than USBLink (P/N: EM2XX-USB-PROG-R). Note that both of these devices are becoming more an more rare as supplies are reduced and no further builds of this material are being performed at this time, so customers are encouraged get in any orders of these items while it is still possible.
You might wonder if you can easily migrate your existing projects to use the newer stack without having to create new projects in Simplicity Studio.
In the example below, we show an AppBuilder project based on an "HA sample light" application for an EM35x SoC, originally created using EmberZNet 5.3.1, and we want to move it over to use a newer version, in this case EmberZNet 5.4.0.
Do either of the following steps (1a or 1b) before opening the ISC file:
1a.) Do this if you need to keep the ISC file in the directory structure for the related stack: In your file system, copy your ISC file (like myproject.isc) from the old stack's directory tree (the one with the stack name, like EmberZNetX.Y.Z, in older releases, or the "protocol/zigbee_X.Y" subdirectory of the Gecko SDK Suite in newer stack releases) to somewhere in the new stack SDK directory structure. This method allows you to keep the older stack active in Simplicity Studio while also making use of the new stack version for this project.
1b.) Do this if you don't need the ISC file to be saved within the stack SDK's directory tree: First make sure that the ISC file you want to migrate is outside of a stack SDK directory tree, so that AppBuilder doesn't try to assume a specific stack version. Then, in Simplicity Studio's menus, go to Window | Preferences | Simplicity Studio | SDKs, and de-select the older SDK version that the AppBuilder project originally referenced.
2.) Now (assuming you have already added the new stack SDK to Simplicity Studio and marked it active using the Preferences settings discussed in 1b), open your .isc file in the new location, and Simplicity Studio will perform an upgrade of the AppBuilder project using an upgrade wizard as follows:
3.) Next the upgrade wizard generates an “Auto upgrade notice” that looks something like this (shown for an EM35x SOC application migrating from EmberZNet 5.3.1 to 5.4.1):
The changes will vary depending on the migration path (old->new SDK version) you choose and the settings of your ISC file. Some upgrades are automatic as they can be assumed, while others are recommended for you to review and decide what new plugins/options might be needed to maintain similar functionality in your target version.
3. Now in the “General” tab in the app builder, unlock “Directory for generated files:”, and change the target path from the old SDK's target directory path to a path in the new SDK's directory structure so that your generated project files will be put under the new directory and not be confused with your project using the older stack version. NOTE: Newer releases based on the Gecko SDK Suite now use the top-level SDK Suite directory as the target path for generated files, such as C:\SiliconLabs\SimplicityStudio\v4\developer\sdks\gecko_sdk_suite\v1.1, rather than using an application-specific generated path, like "..\EmberZNet5.4.0-GA\em35x\app\builder\myproject".)
4. Note that Simplicity Studio IDE cannot be used to build the project after this migration. It must be compiled externally via the generated IAR EWW project. In the appropriate IAR EWARM version, such as 7.80, open the newly generated myproject.eww and build.
You can follow similar steps for NCP-based projects and other stack versions, however the process may be less straightforward if you use plugins that have been updated. It is important to leave your current working appbuilder file (.isc) and IAR project files as-is or have a backup copy in case of any migration surprise.