License restriction: Flash image too large for this license

Showing results for 
Show  only  | Search instead for 
Did you mean: 

License restriction: Flash image too large for this license

Senior Contributor I

On rare occasions the LPCXpresso IDE (Free Edition) recognises a license as being activated, but the debug driver does not. This typically causes the following error when launching a debug session...

License restriction: Flash image too large for this license.

Note: that you will also see this error if your license is activated and your image is larger than 256KB (or 128KB with LPCXpresso IDE version 5 or earlier)

This article explain possible causes and additional information that may help resolve the issue.


In most cases this is caused by certain utilities used by the debug drivers being inaccessible. Specifically, the debug drivers (all executables matching crt_emu*.exe in the installation 'bin' directory) must be able to execute the cscript utility from the Windows System directory. If the debug drivers cannot use this utility, then they revert to being unlicensed and restrict application downloads to just 8k.

Note: When installing LPCXpresso 7.3.0 or later, the installer should detect that required utilities are not on the path and issue a warning. For more details, please see:

To resolve this issue, you must ensure that your PATH environment variable is set up correctly, and that cscript.exe is accessible to the debug driver and that any antivirus or firewall software you have installed allows this utility to be run.Another possible cause is that the user running LPCXPresso does not have permission to run cscript.exe. If this is the case, discuss the issue with your sysadmin/IT department.

Simple cscript test

The following simple test will normally show whether there is a script engine problem:

  1. Start a CMD shell from the Start Menu.
  2. Create a file called "hello.vbs" by typing "notepad hello.vbs".
  3. Inside Notepad, place the text :
    • msgbox("Hello world")
  4. Save the file.
  5. Run the file using the command...
    • cscript hello.vbs

This should pop up a small window with "Hello World" in it. If it does not, then the error displayed should allow you to google for a solution.In the past we have seen cases where anti-virus software has replaced the default script engine with its own. And then when the user uninstalls the anti-virus software, no script engine is then available.

Another issue is that scripting may have been disabled causing an error of the form:

"Windows Script Host Access is Disabled on this Machine".

This can be solved by checking that the registry keys:

  • HKEY_CURRENT_USER\Software\Microsoft\Windows Script Host\Settings\Enabled
  • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Script Host\Settings\Enabled

are set to 1 rather than 0 (if they exist).

At a general level, googling for "No Script Engine For File Extension VBS" will show lots of hints regarding cscript problems - for example:


The COMSPEC environment variable points to the full path of the command line interpreter, cmd.exe. Typically it should be set to something like 'C:\Windows\system32\cmd.exe' (depending on your OS). If this is incorrectly set, then this will prevent debug driver license check running successfully.

All platforms

If this does not resolve the issue, the debug driver can be run in a diagnostic mode that will dump information that can then be posted to the LPCXpresso Forum for further assistance.To run the debug driver in diagnostic mode:

  • open a command window
  • navigate to LPCXpresso<Install_Dir>/lpcxpresso/bin
  • execute the following command and post the output
    • crt_emu_cm3_nxp -info-license
  • now zip up and send the following directory
    • (Win7/Vista) c:\Users\Public\NXPLPCXpresso
    • (Win XP) c:\documents and settings\all users\NXPLPCXpresso
    • (Linux) /usr/share/NXPLPCXpresso
    • (Mac OS X) /Users/Shared/NXPLPCXpresso

In addition, you should also supply the ".log" file from within the subdirectory ".metadata" within your workspace directory.

Labels (1)
Tags (2)
0 Kudos
0 Replies