MCB2400 LabVIEW Embedded 2009 Build error

[Jaggs]

Thanks.

[Gmg]

Thanks for looking into this Grant.

The large program size is actually due to a large heap allocation.  Since the MCB2400 has large banks of external memory, the heap is also rather large.  This does prevent users from easily using the MCB2400 while in evaluation mode and should be fixed in the next version.  In the mean time, you can fix this issue yourself with the following steps:

1. Open the startup file located at <LabVIEW folder>\Targets\Keil\Embedded\RealView\MCB2400\Template\System\ LPC2400.s  (you may want to make a backup copy if you ever decide to license)
2. Find the line that reads "Heap_Size       EQU     0x1000000"  and change the value to something on par with the MCB2300 such as 0x4000.
3. Create a new build specification under your project and build (this should work)

Note that this changes the project template, which is copied every time you create a new build specification / project.  Thus this change will not apply to any build specifications you have created before the change.

[Jaggs · Accepted solution]

Yes, this should work for now..

Thanks.

[NicB]

---

Gmg wrote:

Thanks for looking into this Grant.

---

😉

[rpfene]

I'm using the MCB2400 eval software and building a VI which sizes to about 290K when compiled for the MCB2300, but when compiled for the MCB2400 it shows at 17MB size.

The MCB2400 build error is a previously documented error, and what is your status on fixing this problem.  Additionally, how mature is your MCB2400 Labview software as we are making a decision to go down this route for our development.

[G-Money]

tttrrr,

        This bug hasn't been given a firm date for completion but we are still hoping to have it solved be the next release of LabVIEW for ARM. Right now, the work around a couple of posts up is a completely viable workaround. As far as maturity of the product, I don't know quite you are looking for here. There have been 7 releases over the past 5 years of the LabVIEW for ARM product line. We have been a full module for two releases now (8.6 and 2009). Normally the transition from just a toolkit to an actual module is triggered by industry acceptance and product robustness but there are no set guidelines for this. Our LabVIEW Embedded SDK, LabVIEW Embedded for ARM, and LabVIEW Embedded for Blackfin have been used by numerous customers for quick concise prototyping and further scalability after acceptance for a wide array of applications. For more information on case studies and customer applications, please visit our website or work with our sales department (I'm better at the 1s and 0s of programming and not so much on the marketing fluff 🙂 ). Let me know if there is anything else I can help with.

[NicB]

I was thinking the module had been released in 2008. And there were three releases (1.0, 1.1 and 2009).

tttrr go ahead. It is very probable to take shorter time to develop your application than taking a decision.

Message Edited by NicB on 01-27-2010 01:03 PM