Flash Image too large for License

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

Flash Image too large for License

2,047 Views
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

36 Replies

1,157 Views
lpcware
NXP Employee
NXP Employee
bump
0 Kudos

1,157 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by zamarano72 on Sun Apr 03 23:39:04 MST 2016
Dear lpcxpresso-support,

Thank you for your help on resolution of license problem. It seems the new archive file works well for me now. Although, I'm quite new to NXP, hope to use for years, as I did ST MCU's, and some others so far.

Best Regards,

Ramazan Dermenci
0 Kudos

1,157 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by LessThanZero on Fri Apr 01 11:38:47 MST 2016

Quote: zamarano72
Dear LessThanZero,

Thank you for informative link.I meant if the "variable name" is important or not, on the on Environment Variables settings. Because I can only name just one "PATH" named environmen variables. If I need to set another path, like "C:\Windows\System32" and "C:\Windows\System32\wbem", name them "PATH2" and "PATH3", as seen attached screenshot.

By the way, this settings didn't help solving the problem.

Best Regards,

Ramazan Dermenci



I guess I did understand what you meant. There is only one PATH environment variable. You can specify multiple paths in this environment variable. Each individual path is ultimately separated by a ';' semi-colon on Windows computers. The link I sent you allows you to edit the PATH without regard to this. The path editor should do this for you.

LessThanZero
0 Kudos

1,157 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Fri Apr 01 11:32:00 MST 2016
Ramazan,

Sorry, I'm not sure what happened. It seems to be the only debug utility missing from the archive. Attached.

Thanks and regards,
LPCXpresso Support

PS  By the way, you can check the license information using any of the other debug utilities in the first archive. Same option as you've used before. The license updates made to these binaries can be checked in any/all of the executables. Here's the option:

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>crt_emu_cm3_nxp.exe --info-license
0 Kudos

1,157 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by zamarano72 on Fri Apr 01 10:53:55 MST 2016
Dear LessThanZero,

Thank you for informative link.I meant if the "variable name" is important or not, on the on Environment Variables settings. Because I can only name just one "PATH" named environmen variables. If I need to set another path, like "C:\Windows\System32" and "C:\Windows\System32\wbem", name them "PATH2" and "PATH3", as seen attached screenshot.

By the way, this settings didn't help solving the problem.

Best Regards,

Ramazan Dermenci
0 Kudos

1,157 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by TheFallGuy on Fri Apr 01 10:50:53 MST 2016
.
0 Kudos

1,157 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by zamarano72 on Fri Apr 01 10:33:38 MST 2016
Dear LPCXpresso-Support,

It seems the archive file, you uploaded, doesn't include "crt-emu_cm_redlink.exe" The other files, are the same as you shown on your message.

"C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>dir crt*.exe
Volume in drive C is OS
Volume Serial Number is A8B6-DCB7

Directory of C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin

29.03.2016  10:58           368.128 crt_emu_a7_nxp.exe
29.03.2016  10:58           374.784 crt_emu_a9_nxp.exe
29.03.2016  10:58           455.168 crt_emu_cm3_gen.exe
29.03.2016  10:58           462.336 crt_emu_cm3_nxp.exe
14.03.2016  08:01           414.720 crt_emu_cm_redlink.exe
29.03.2016  10:58           461.312 crt_emu_lpc11_13_nxp.exe
29.03.2016  10:58           456.704 crt_emu_lpc18_43_nxp.exe
               7 File(s)      2.993.152 bytes
               0 Dir(s)  855.931.904.000 bytes free"

Best Regards,

Ramazan Dermenci
0 Kudos

1,157 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by LessThanZero on Thu Mar 31 14:04:08 MST 2016

Quote: zamarano72
Dear LessThanZero,

I had to replace "PATH" variable, because it doesn't allow two "PATH" variable names. If I have to add another "variable name" instead "PATH", I can try that too. If you suggest so, I'd try.



?? I'm not sure I understand what you're trying to say. Read the information at this link:

Windows 10 finally adds a new Path editor

Regards,
LessThanZero
0 Kudos

1,157 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Thu Mar 31 10:01:00 MST 2016

Quote: zamarano72
Dear lpcxpresso-support,

I have copied the archive binaries over the existing ones, as shown in the attached link. When I run the crt_emu_cm_redlink.exe debug utility:

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>crt_emu_cm_redlink.exe -v
Ni: LPCXpresso RedlinkMulti Driver v8.1 (Mar 11 2016 13:34:34 - crt_emu_cm_redlink.exe build 672)

so, build 672, not 332. Is that because the archive file uploaded?



The build number 332 is a engineering build designation for the binaries in the archive file. If you're using the correct binaries, the '-v' parameter will show they were all built on March 29, sometime between 10:56 and 10:58 AM. I don't know where you think you're extracting the files in the provided archive, but they're apparently not getting written to the "C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin" folder. Perhaps you need help from a system administrator?

Here's the build times of the debug utility files in the archive you were provided. Keep trying.

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>dir crt*.exe
Volume in drive C is OS
Volume Serial Number is 3C08-B1C1

Directory of C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin

03/29/2016  10:58 AM           368,128 crt_emu_a7_nxp.exe
03/29/2016  10:58 AM           374,784 crt_emu_a9_nxp.exe
03/29/2016  10:58 AM           415,232 crt_emu_cm_redlink.exe
03/29/2016  10:58 AM           455,168 crt_emu_cm3_gen.exe
03/29/2016  10:58 AM           462,336 crt_emu_cm3_nxp.exe
03/29/2016  10:58 AM           461,312 crt_emu_lpc11_13_nxp.exe
03/29/2016  10:58 AM           456,704 crt_emu_lpc18_43_nxp.exe
               7 File(s)      2,993,664 bytes
               0 Dir(s)  146,521,899,008 bytes free

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>crt_emu_a7_nxp.exe -v
Ni: LPCXpresso Debug Driver v8.1 (Mar 29 2016 10:57:23 - crt_emu_a7_nxp.exe build 332)

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>crt_emu_a9_nxp.exe -v
Ni: LPCXpresso Debug Driver v8.1 (Mar 29 2016 10:57:21 - crt_emu_a9_nxp.exe build 332)

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>crt_emu_cm_redlink.exe -v
Ni: LPCXpresso RedlinkMulti Driver v8.1 (Mar 29 2016 10:56:21 - crt_emu_cm_redlink.exe build 332)

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>crt_emu_cm3_gen.exe -v
Ni: LPCXpresso Debug Driver v8.1 (Mar 29 2016 10:57:18 - crt_emu_cm3_gen.exe build 332)

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>crt_emu_cm3_nxp.exe -v
Ni: LPCXpresso Debug Driver v8.1 (Mar 29 2016 10:57:16 - crt_emu_cm3_nxp.exe build 332)

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>crt_emu_lpc11_13_nxp.exe -v
Ni: LPCXpresso Debug Driver v8.1 (Mar 29 2016 10:57:19 - crt_emu_lpc11_13_nxp.exe build 332)

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>crt_emu_lpc18_43_nxp.exe -v
Ni: LPCXpresso Debug Driver v8.1 (Mar 29 2016 10:57:13 - crt_emu_lpc18_43_nxp.exe build 332)

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>


Thanks and regards,
LPCXpresso Support
0 Kudos

1,157 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by zamarano72 on Thu Mar 31 09:16:26 MST 2016
Dear lpcxpresso-support,

I have copied the archive binaries over the existing ones, as shown in the attached link. When I run the crt_emu_cm_redlink.exe debug utility:

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>crt_emu_cm_redlink.exe -v
Ni: LPCXpresso RedlinkMulti Driver v8.1 (Mar 11 2016 13:34:34 - crt_emu_cm_redlink.exe build 672)

so, build 672, not 332. Is that because the archive file uploaded?
0 Kudos

1,157 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by zamarano72 on Thu Mar 31 09:03:24 MST 2016
Dear LessThanZero,

I had to replace "PATH" variable, because it doesn't allow two "PATH" variable names. If I have to add another "variable name" instead "PATH", I can try that too. If you suggest so, I'd try.

Best Regards,

Ramazan Dermenci
0 Kudos

1,157 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by LessThanZero on Wed Mar 30 11:16:17 MST 2016
I have a question. Why would you replace other "standard" Windows system paths when you add a path? That's what it looks like you've done. Besides "C:\Windows\SysWOW64", I would expect (as a minimum) "C:\Windows\System32;C:\Windows\System32\wbem" (for 32-bit applications) and "C:\Windows"?

Regards,
LessThanZero
0 Kudos

1,157 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Wed Mar 30 11:04:31 MST 2016

Quote: zamarano72
Dear lpcxpresso-support,

I have removed LPCXPresso program and reinstalled clean, after deleting relevant folders, then copied the archive files into "C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin' folder. I checked the same folder, and the message:

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>crt_emu_cm_redlink.exe --info-license
Ni: LPCXpresso RedlinkMulti Driver v8.1 (Mar 11 2016 13:34:34 - crt_emu_cm_redlink.exe build 672)
Cr:f LPCXpresso Free License - Download limit is 8K (UNREGISTERED)

My system path is "C:\Windows\SysWOW64" as it's recommended for Windows 10 64bit OS.

I have attached, system path and cmd line screenshot outputs. Is there any other way, to use LCXpresso IDE?



It's quite obvious you haven't copied the archive binaries over the existing ones in the LPCXpresso_8.1.4_606 installation. If you had, you'd see the following version reported by the crt_emu_cm_redlink.exe debug utility:

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>crt_emu_cm_redlink.exe -v
Ni: LPCXpresso RedlinkMulti Driver v8.1 (Mar 29 2016 10:56:21 - crt_emu_cm_redlink.exe build 332)


Thanks and regards,
LPCXpresso Support
0 Kudos

1,157 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by zamarano72 on Wed Mar 30 04:34:16 MST 2016
Dear lpcxpresso-support,

I have removed LPCXPresso program and reinstalled clean, after deleting relevant folders, then copied the archive files into "C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin' folder. I checked the same folder, and the message:

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>crt_emu_cm_redlink.exe --info-license
Ni: LPCXpresso RedlinkMulti Driver v8.1 (Mar 11 2016 13:34:34 - crt_emu_cm_redlink.exe build 672)
Cr:f LPCXpresso Free License - Download limit is 8K (UNREGISTERED)

My system path is "C:\Windows\SysWOW64" as it's recommended for Windows 10 64bit OS.

I have attached, system path and cmd line screenshot outputs. Is there any other way, to use LCXpresso IDE?
0 Kudos

1,157 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Mar 29 11:47:38 MST 2016

Your machine system information returned from these queries is significantly larger than is typical. In fact, we've seen nothing like it before. I've attached updated debug utility programs which should handle the query.

First, install the latest LPCXpresso_8.1.4_606 release. You can follow the link in the signature.

Once installed, copy the binaries in the attached archive over the ones in the 'C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin' folder. As a quick command line check, open an MS-DOS command shell and navigate to this same folder. Then issue the command-line below. You should see the following license report provided your system path is correct.

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>crt_emu_cm_redlink.exe --info-license
Cr:v LPCXpresso Free License - Download limit is 256K

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>


Thanks and regards,
LPCXpresso Support
0 Kudos

1,157 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Mon Mar 28 07:01:26 MST 2016

Thanks for confirming. We'll get back to you.

Thanks and regards,
LPCXpresso Support
0 Kudos

1,157 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by zamarano72 on Mon Mar 28 01:45:35 MST 2016
Dear lpcxpresso-support,

When I run the command, I have received this message:

"C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin>crt_emu_cm_redlink.exe --info-license
Ni: LPCXpresso RedlinkMulti Driver v8.1 (Mar 11 2016 13:34:34 - crt_emu_cm_redlink.exe build 672)
Cr:f LPCXpresso Free License - Download limit is 8K (UNREGISTERED)"

So it's still looks download limit 8K.
0 Kudos

1,159 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Mon Mar 28 00:51:00 MST 2016
We know the LPCXpresso IDE considers your license valid. The debug utilities do not. To see if the path problem is resolved, open an MS-DOS shell, then navigate to the '<install>\lpcxpresso\bin' folder and try one of the debug utility programs with the '--info-license' command line. For example:

C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin\crt_emu_cm_redlink.exe --info-license

This should print out your license type (LPCXpresso Free or Unregistered) if the path problem is resolved. The LPCXpresso.sib file you just provided is 760 bytes in size, larger than the previous file at 616 bytes. These are both incorrect. The file size should be 256 bytes. Something appears to be failing during the LPCXpresso license activation, but it's nothing we've seen before on Windows 10.

LPCXpresso Support
0 Kudos

1,159 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by vtw.433e on Mon Mar 28 00:45:50 MST 2016
You don't get an explicit "CMSIS-DAP" option. (Red)Linkserver is the driver that supports CMSIS_DAP.

But if you just press "Debug" LPCXpresso will find your debug probe automatically.
0 Kudos

1,159 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by zamarano72 on Sun Mar 27 23:52:42 MST 2016
Dear lpcxpresso-support,

Although I haven't confirmed that I reinstalled and reactivated LPCXpresso and it's license, I had done it before, and now I tried again, this time with Avast anti-virus program shutted down. I have attached LPCXpresso.acc and LPCXpresso.sib files zipped.

When I check "Display License Type" on LPCXpresso IDE Help Menu, I can see

"License type: FULL
Debug limit: 256k
Activation code: A5O4-IWCY-NZAW-B0C1-DWO5-LTM5-LTJX-M1G4

A FULL copy of LPCXpresso (Free Edition) may be used for production."

message.

On the other hand, when I connect LPC1549 XPresso V2 Rev B development board to my computer, I can see "LPC-LINK2 CMSIS-DAP V5.147" device on "Devices and Printers" on Control Panel. However, CMSIS-DAP doesn't show up, at the "Debug Configurations" pop-up menu, and "Debugger" segment and "Emulator" selection combo menu. There are "Link Server", "LPC-Link (WinUSB) or RDB-Link", "LPC-Link (HID)" and "Red Probe Family" options at "Emulator" selection combo menu, but not CMSIS-DAP selection. My friend said, it shows up for his computer.  Does it make sense to diagnose the problem?
0 Kudos