Flash Image too large for License

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Flash Image too large for License

7,738件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by zamarano72 on Tue Mar 15 09:20:00 MST 2016
Hello,

I'm quite new to NXP ecosystem and also Xpresso tools. I've recently installed LPCXpresso_800 first and then LPCXpresso_812 on my Windows 10 computer. After importing example projects to my IDE and then building a project, I tried to debug the program on LPC1549 xpresso v2 kit, However I received the error message "Flash Image too large for License".

I tried everything is told in this page: https://www.lpcware.com/content/faq/lpcxpresso/flash-image-too-large

When I tried debug driver in diagnostic mode, I received following message:

C:\nxp\LPCXpresso_8.1.2_603\lpcxpresso\bin>crt_emu_cm3_nxp -info-license
Ni: LPCXpresso Debug Driver v8.1 (Mar  4 2016 17:16:07 - crt_emu_cm3_nxp build 327)
Cr:f LPCXpresso Free License - Download limit is 8K (UNREGISTERED)

Then I decided to write her further assistance.

Here is other files, asked in the web page attached.

Anyone any idea, why such problem occured.

Thanks for your help in advance.

Ramazan


Original Attachment has been moved to: NXP_Xpresso.rar

タグ(2)
36 返答(返信)

2,077件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Sat Mar 26 09:45:30 MST 2016

Quote: zamarano72
I have changed PATH variable to "C:\Windows\SysWOW64" folder, and it didn't work. I remember I've tried that before.
.
.
Now, Are we back to "cscript.exe" problem?



The cscript issue has never been resolved. Even if it were, there's the question about the size of the LPCXpresso.sib file, which is not correct. You were asked earlier to reactivate your LPCXpresso license, but you did not confirm you have done so.

1. Reactivate your license as described above. Once you have done so, include your LPCXpresso.acc and LPCXpresso.sib files for examination.

2. Recheck the AVAST virus checker settings. If your PATH environment is setup, I suspect it's still preventing use of cscript.exe and ipconfig.exe. You should be able to open a MS-DOS command shell and use any debug utility (e.g. crt_emu_cm3_nxp.exe, cm_emu_cm_redlink.exe, etc.) to report your license type. Instead, running -info-license elicits a complaint:

'ipconfig.exe' is not recognized as an internal or external command,
operable program or batch file.

and

'cscript.exe' is not recognized as an internal or external command,
operable program or batch file.

It's interesting to note these programs are located in the same Windows directory. If one is not found, the other is not likely to be.

There are tens of thousands of successful LPCXpresso license activations. 99% of the time, there are no license problems. When a license problem is reported, it has been traced to either the system path, disk permissions, and/or virus checkers.

Thanks and regards,
LPCXpresso Support
0 件の賞賛
返信

2,077件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by zamarano72 on Sat Mar 26 01:03:43 MST 2016
I have changed PATH variable to "C:\Windows\SysWOW64" folder, and it didn't work. I remember I've tried that before.

On my Environment Variable pop-up screen, I can just set just one folder for PATH variable. According to this help page:

https://www.lpcware.com/content/faq/lpcxpresso/windows-path-issues

"Generally this problem can be solved by fixing your PATH environment variable, to ensure that the "%SystemRoot%;%SystemRoot%\system32;%SystemRoot%\system32\wbem" directories are on it ."

and then it says:

"Note: on 64 bit Windows systems, cscript.exe is actually run from the  "%SystemRoot%\SysWOW64" directory, which is automatically redirected to by Windows when looking for 32bit executables (ie Windows automatically redirects from the "%SystemRoot%\system32" on the path to "%SystemRoot%\SysWOW64")."

Now, Are we back to "cscript.exe" problem?

Thanks for your help again,

Best Regards,

Ramazan Dermenci
0 件の賞賛
返信

2,077件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Fri Mar 25 07:21:46 MST 2016

To go over this once more, the LPCXpresso debug utilities (e.g. crt_emu_cm_redlink.exe, crt_emu_cm3_nxp.exe, etc.) require the cscript engine, cscript.exe, and also ipconfig.exe to be available for system queries. Be certain the "C:\Windows\SysWOW64" folder is included in your Windows 10 PATH environment variable.

Thanks and regards,
LPCXpresso Support
0 件の賞賛
返信

2,074件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by zamarano72 on Fri Mar 25 05:48:59 MST 2016
Hello LPCXpresso Support,

I have also help assistance from another friend, who supports NXP in Turkey and he asked me to run crt_emu_cm3_nxp -info-license command from LPCXpresso<Install_Dir>/lpcexpresso/bin folder, and then post the output to the forum. Here is the output:

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>crt_emu_cm3_nxp -info-license
Ni: LPCXpresso Debug Driver v8.1 (Mar  4 2016 17:16:07 - crt_emu_cm3_nxp build 327)
'ipconfig.exe' is not recognized as an internal or external command,
operable program or batch file.
'cscript.exe' is not recognized as an internal or external command,
operable program or batch file.
Cr:f LPCXpresso Free License - Download limit is 8K (UNREGISTERED)

Attached the instruction, I was told and also c:\users\public\nxplpcexpresso folder zipped.

Does it make sense to diagnose the license problem? By the way, I'm using Windows 10 in Turkish language.

Best Regards,

Ramazan Dermenci


0 件の賞賛
返信

2,074件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Wed Mar 23 14:36:52 MST 2016

Quote: zamarano72
Although I have administrator privilidges, after ı change the folder write access, it changes back to read-only. However, I could run the crtlicensediag.exe tool while read-only cancelled, and lpcxpresso.inf.bin and lpcspresso.lic.bin files generated. Here is the zipped file includes those files.

After that, I tried debugging the sample project, and this time I've received this error:

"02: Failed on connect: Ep(01). Target marked as not debuggable"

Does that mean, license problem is over now?



It's doubtful the license problem is over. As mentioned earlier, the crtlicensediag.exe does not fix license problems, only collects information. The lpcxpresso.inf.bin encrypted file you supplied does not contain the expected information. This means you either executed crtlicensediag from a directory without write permission (also doubtful), or, the cscript engine wasn't available and it's output not included.

There are other anomalies with your license files. The LPCXpresso.sib file you provided earlier is 616 bytes. It should be 256 bytes.

Please uninstall your LPCXpresso installation on the Windows 10 machine, and archive the contents of the "\Users\Public\NXPLPCXpresso" folder, then delete the folder. Reinstall LPCXpresso and create a serial number (which may be the same as before). Once you have the serial number, reactivate the license.

You might consider completing the license activation after having started the LPCXpresso IDE with adminstrator privilege. The only reason I recommend this is uncertainly regarding the permissions on your machine.

Thanks and regards,
LPCXpresso Support
0 件の賞賛
返信

2,074件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Wed Mar 23 01:40:46 MST 2016

Quote: zamarano72

"02: Failed on connect: Ep(01). Target marked as not debuggable"


See :
[list]
  [*]https://www.lpcware.com/content/faq/lpcxpresso/target-marked-not-debuggable
[/list]
Regards,
LPCXpresso Support
0 件の賞賛
返信

2,074件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by zamarano72 on Wed Mar 23 00:49:26 MST 2016
Although I have administrator privilidges, after ı change the folder write access, it changes back to read-only. However, I could run the crtlicensediag.exe tool while read-only cancelled, and lpcxpresso.inf.bin and lpcspresso.lic.bin files generated. Here is the zipped file includes those files.

After that, I tried debugging the sample project, and this time I've received this error:

"02: Failed on connect: Ep(01). Target marked as not debuggable"

Does that mean, license problem is over now?
0 件の賞賛
返信

2,074件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Mar 22 11:35:38 MST 2016

Do you have write permission in the "\Users\Public\NXPLPCXpresso" directory? I've attached a rebuilt version of the crtlicensediag.exe utility which writes out an additional diagnostic file, lpcxpresso.lic.bin file. If you do not see both the lpcxpresso.inf.bin and lpcxpresso.lic.bin files written to the NXPLPCXpresso folder after running "crtlicensediag.exe -all", then try again with adminstrator privilege.

Note the crtlicensediag.exe utility does not "fix" license problems. It only collects the same system information used by the LPCXpresso license checker to generate the serial number used for your activation code. This information is for license diagnostic purposes only. NXP neither collects nor shares personal information from your PC.

Thanks and regards,
LPCXpresso Support
0 件の賞賛
返信

2,074件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by zamarano72 on Sat Mar 19 09:24:14 MST 2016
I have installed crtlicensediag tool and run with the recommended command-line. It still didn't work. I haven't met any file lpcxpresso.inf.bin in my NXPLPCXpresso folder. Here is the zipped folder attached. Does it help you find out the problem?

Thanks and best regards,

Ramazan Dermenci
0 件の賞賛
返信

2,074件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Fri Mar 18 08:33:23 MST 2016

Attached is zip archive containing a license diagnostic utility, crtlicensediag.exe. You can run this utility from any directory on the disk where your installation resides. Run the utility with the following command-line:

C:\>crtlicensediag.exe -all

On a Windows 7, 8, and 10 machines, you'll find the encrypted lpcxpresso.inf.bin diagnostic output in "\Users\Public\NXPLPCXpresso”. Post this diagnostic file to the thread. You may delete the file once you have done so. NXP neither collects nor shares personal information from your PC.

Thanks and regards,
LPCXpresso Support
0 件の賞賛
返信

2,074件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by zamarano72 on Fri Mar 18 00:51:35 MST 2016
Here is the pathinfo.txt file attached. I hope this works for diagnosing the problem.

Best Regards,
0 件の賞賛
返信

2,074件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Thu Mar 17 05:28:36 MST 2016
Please open a command prompt from within LPCXpresso IDE:

https://www.lpcware.com/content/faq/lpcxpresso/status-bar-shortcuts

and enter the commands:

path > pathinfo.txt
tasklist >> pathinfo.txt


and post the resulting pathinfo.txt file.

Regards,
LPCXpresso Support
0 件の賞賛
返信

2,074件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by zamarano72 on Thu Mar 17 01:10:16 MST 2016
Dear lpcxpresso-support,

If you asking me this script test:

Start a CMD shell from the Start Menu.
Create a file called "hello.vbs" by typing "notepad hello.vbs".
Inside Notepad, place the text :
msgbox("Hello world")

Save the file.
Run the file using the command...
cscript hello.vbs

This should pop up a small window with "Hello World" in it.

Yes this works well for me. I tried the same process deactivating my anti-virus program (AVAST) and still can't debug demo program.

My computer's operating system is Windows 10 - 64bit with x64 based processor. How should I change PATH environment variable?

Thanks again for your help and interest

Ramazan Dermenci
0 件の賞賛
返信

2,074件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Wed Mar 16 11:19:00 MST 2016
For an activated license, you would see this message if the scripting engine was unable to query your system in order to validate your license key and activation.

You didn't provide any feedback with regard to your system path, but if you ran the scripting test at the above link I presume your path is correct. If you did not, I would recommend you first check the path. Next, some virus checkers (e.g. McAfee) can be configured to disallow programs to be run from the TEMP directory. This would also cause a license failure. If this is the case here, you must reconfigure your virus checker.

Thanks and regards,
LPCXpresso Support
0 件の賞賛
返信

2,074件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by zamarano72 on Wed Mar 16 01:19:18 MST 2016
Hello 8473,

My IDE (LPCXPRESSO) seemed to be activated, yet I tried activation again. When I check "Display License Type" on Help menu, I can see "License Type: FULL" and "Debug Limit: 256K" messages. However, when I try to debug, example project, I still receive same error: "License restriction: Flash image too large for this license."

Is it about Windows 10 compliance?
0 件の賞賛
返信

2,074件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by 8473 on Tue Mar 15 11:56:11 MST 2016
Hello Ramazan,

see https://www.lpcware.com/content/faq/lpcxpresso/activating-lpcxpresso-free-edition

:-)

Regards,