Restrictions on development tools under Windows® 10 are described below
No.1 Restriction on starting device file installer (DFINST V3.30 or later)
| [Description] | Device file installer may not start from PM+. |
| [Workaround] | Run device file installer from Windows start menu. |
No.2 Restriction on registering device file (DFINST V3.30 or later)
| [Description] | Device file is not registered to registry by dragging and dropping device file on device file installer. |
| [Workaround] | Use button on device file installer to register device file. |
No.3 LDG does not support Windows® 10
| [Description] | LDG has not been supported Windows® 10. |
No.4 Restriction on not displaying the registered external tool's icon on PM+
| [Description] | If the external tool bar is displayed soon after registering one external tool without the registered external tools, the icons of the registered external tools are not displayed. |
| [Workaround] | Restart PM+. |
No.5 Display in the Register or SFR/IOR window
| [Description] | If you click on [Hide All] in the “Register Select” dialog box or the boundary between “Name” and “Attribute” in the relevant window with registers such as [+PSW] expanded, some garbage will remain in the window. |
No.6 Not support dual core PC
| [Description] | Personal computers that incorporate dual/multi-CPUs or the Hyper-Threading function are not supported. |
No.7 .NET Framework 3.5 and the VS2005 Runtime Library
| [Description] | .NET Framework 3.5 and the VS2005 Runtime library are not included in Windows® 10 by default. |
| [Workaround] | As to VS2005 Runtime library, download the files from the web site of Microsoft Corporation and install them. As to .NET Framework 3.5: 1) Open the control panel. 2) Click the "Turn Windows features on or off" in the "Programs and Features". 3) Check the ".NET Framework 3.5 (includes .NET 2.0 and 3.0)" and click OK. |
No.8 Help Display
| [Description] | Help is not displayed correctly. |
| [Workaround] | Invoke HELP by double-clicking on ".chm file" directly. |
No.9 USB drivers of all emulator and programmer products
| [Description] | When “USB Selective Suspend” is active, USB communications might not operate properly. |
| [Workaround] | Deactivate “USB Selective Suspend”. For details of the procedure for doing this, refer to the following FAQ. FAQ No:1010390 Connection of tools was successful when it was connected. |
No.10 Restriction on display of editor area tab
| [Description] | Even if layout reset is executed, editor area tab is not displayed. |
| [Workaround] | Do not reset a layout. When this problem occurs, editor area tab can be displayed by doing either of the following: The command [which closes all the division panel] is executed. The layout saved in the state where it can be displaying correctly is restored. |
No.11 Wrong indication of help page
| [Description] | After the help window is opened from the “Simulator (S)” menu several times, the page will not be displayed correctly. |
| [Workaround] | Start the help system directly from the “.chm” file. |
No.12 Applilet2 products
| [Description] | Applilet2 cannot create projects when booted up by users who do not have the administrative right. |
| [Workaround] | Have the administrative right when booting the product. |
No.13 Usage of devices which do not support the E100 MCU unit
| [Description] | An application error occurs when a debugger is connected and a device which is not supported by the MCU unit of the E100 is specified. |
No.14 E100 help
| [Description] | The browsing sequence of E100 help is not displayed. |
No.15 Using multiple installed instances of the High-performance Embedded Workshop
| [Description] | An active High-performance Embedded Workshop might not be listed in the list of installed High-performance Embedded Workshops if the “Install Manager” is used to switch between High-performance Embedded Workshops. |
No.16 Flash Development Toolkit
| [Description] | When it is booted under Windows® 10, the Flash Development Toolkit cannot be used due to the error “Request a new UNLOCK key and enter it here”, which is related to access rights. |
| [Workaround] | We have no workaround other than using it with the following operating systems, under which correct operation has been confirmed. Windows® 8 (32- and 64-bit editions)* Windows® 7 (32- and 64-bit editions) Windows Vista® (32-bit edition) Windows® XP (32-bit edition) *This problem will be fixed in V.4.09 R03. |
No 17 Restrictions on Debug Console
| [Description] | The debug console function doesn’t work in Windows® 10. |
| [Workaround] | Use CS+ or e2 studio. |