MCB2400 LabVIEW Embedded 2009 Build error

[Jaggs]

Hello,

I am trying to evaluate MCB2400 with LabVIEW embedded 2009. Whenever I try to build the application (even with an empty VI, no block diagram code), I receive the following error:

" "[3:35:15 PM] Status: Error
linking...
.\Obj\LabVIEW.axf: error: L6047U: The size of this image (16802097 bytes) exceeds the maximum allowed for this version of the linker
Target not created

Status: Build failed."

I am not sure whythe size is exceeding even though I tried with no code at all (blank VI)!

[Jaggs]

Please find the error message screenshot and the project which I am using for the build.

Thanks.

[Jaggs]

Application Enginners! Any input?

[G-Money]

Jaggs,

     Sorry for it taking a while for someone to post back. I was assigned to your post 2 hours ago and just got all my pictures ready to post back literally a minute ago and when I refreshed I saw that you posted back. Just to let you and the community know, it takes on average about 2 days for discussion forums to be processed at NI and then assigned out so depending on how hard the issue is (what R&D developers we have to talk to, hardware we have to set up, code to replicate, etc.) the maximum earliest you will hear back on a new issue is two business days but Mondays see a large influx of posts because of all the ones over the weekend. We try to get back to the community as soon as possible but keep after us because sometimes things just fall through the cracks (hey...no one is perfect but we try to be).

      Anyway, you're issue is actually a known issue. Your copy of the LabVIEW for ARM is in evaluation mode and the Keil compiler that gets packaged with that module has an upper limit of 128 kb for compilation. This is difintely a hinderance for people that have to have a Proof of Concept working before they can get the ok to buy the software. Unfortunately, this is a parameter set by Keil because we have to license their software with each ARM module that we sell. There isn't anything that I can do on my end to up the size for you but I can definitely give the feedback to R&D and Keil that we should reconsider this size if you would like me to. The code that you were trying to compile was 16 Mb according to the error dialog. I opened up your code in my activated 2009 copy and built it without any problems.

The build took about a minute or so, so it wasn't too bad. We don't have a MCB2400 here so I wasn't able to confirm that your code works but it was able to build using the full activated Keil compiler (if there is a maximum compilation size on an activated Keil compiler then I haven't seen it and I've worked with some big programs). Hope this helps out!!

[Jaggs]

Hello G-money,

Thanks for your reply.  My code actually if you can see is an empty VI, so I assume that with evaluation version it should not be a problem.  Is it possible for you to build it on an evauation version pc? 

Thanks.

[G-Money]

Jaggs,

       Yeah. I'm in the process of setting up a virtual machine with an evaluation copy of LabVIEW and the ARM Module. Did you have an older copy of Keil uVision already installed on your computer before you downloaded the evaluation copy of the ARM Module?

[Jaggs]

Yes, I had a previous version which I installed with LabVIEW embedded ARM 1.1.  I don't remember its version.

My current version of uvision3 V3.85

Thanks.

[G-Money]

Jaggs,

       The only reason why I ask is that I only found one other customer issue that had the L6047U error code. That issue dealt with one of the shipping example that was installed with the evaluation software. All shipping examples that we create are under the 128 kb limit so that people can try them out even in evaluation mode so it was strange that they were getting this error (they were told it was around 159 kb though) when it was clearly not that large. The issue was resolved by uninstalling/reinstalling the module. The solution wasn't firmly found, but the customer and the other applications engineer thought the issue came from an older version of Keil being on the machine already when they installed and some hang up coming from that (not all the files were correctly overwritten or something like that). I don't want to advise this yet because I have just got the virtual machine installed with all the needed software and am about to test your code on a pure evaluation copy of LV, ARM, and Keil on a brand new machine (never had Keil or ARM on it before). I will let you know what I find out.

[G-Money]

Jaggs,

       It's something with the actual code. Something is making too large. Here is the build failed error that I got:

[10:23:04 AM] Status: Error
linking...
.\Obj\LabVIEW.axf: error: L6047U: The size of this image (16800848 bytes) exceeds the maximum allowed for this version of the linker
Target not created

Status: Build failed.

I'm going to dig into the code and application a little more and I will let you know what I find.

[G-Money]

Jaggs,

      I have worked on this issue for a couple of hours now and I think I have it narrowed down to a probable bug in LabVIEW for ARM. I am able to successfully build for all targets except the MCB2400 in eval mode. It doesn't make a difference whether the VI included in the Source Files is blank, has a small amount of code, or a lot. It will always fail with the same compiler error saying the image is too large. Even turning off all optimazation code (which shouldn't make that large of a difference) doesn't change the application much. I am going to get with the R&D Developers and talk over this issue. I will let you know what I find out.