LabVIEW Embedded - Support for device: NXP (ex. Philips) LPC2146 Microcontroller (ARM7)

[AndyVessey]

Hi,

I would like to write some code in 'LabVIEW embedded' 8.5 for the NXP LPC2146 microcontroller (ARM7).

http://www.standardics.nxp.com/products/lpc2000/lpc214x/

The 2146 device is used within one of our main 'volume' products and I would like to write some special test code for the product in LV Embedded. I have the full NI development suite at 8.5 level.

The question is, does LV embedded suport this microcontroller fully?

I have found this info but still not sure: http://zone.ni.com/devzone/cda/tut/p/id/6207 

Many thanks in antisipation of a reply.

Andrew V

[Michael.Phillips]

Hi Andrew,

Using the LabVIEW Microprocessor SDK, you can "port" LabVIEW to build applications for any 32-bit microprocessor. The LabVIEW Microprocessor SDK Porting Guide describes the steps involved in the porting process.

The amount of effort involved depends on these factors:

1. How similar your target is to one of the example targets that are included in the LabVIEW Microprocessor SDK. As you can see in the article you linked, the SDK contains an example target with a Philips ARM and an eCos BSP. If your target is similar to this one (especially if the OS is the same), the porting process might take less than a week.
2. Familiarity with LabVIEW and embedded domain expertise. The porting process involves writing "plug-in" VIs in LabVIEW and building C run-time libraries for your target. However, once the porting process is complete, your target can be programmed solely in LabVIEW by someone with no embedded expertise whatsoever.
3. Target selection. We recommend a target have the following characteristics: 32-bit processor, OS/microkernel (not "bare metal"), and 256 KB RAM. Also, if you plan to make use of the LabVIEW Advanced Analysis libraries, a floating point unit is recommended.

[AndyVessey]

Hi Michael,

Thanks for the reply.

I take it your saying no 'off the shelf' support for our LPC2146 processor is available and porting would be required?

Just wondering if anyone knows how far away the NI supported Phytec ARM7 - phyCORE-ARM7/LPC229x unit is from our LPC2146?

http://www.phytec.com/products/sbc/ARM-XScale/phyCORE-ARM7-LPC229x.html 

Could we easily adapt this application to support our LPC214x processor and reduce the porting overhead?

Alternativley does anyone have a library for the LPC2146? ... NXP/Ex Philips people... are you listening in!??

Regards

Andy

[Michael.Phillips]

Andy,

If you want a more off the shelf embedded solution, there is the LabVIEW Embedded Module for Blackfin processors. Besides that, any target support would need to be developed using the SDK, using the example targets as a reference. I'm not sure how different the Phytec example target is from your target, but if there is an eCos BSP for your board, that could reduce porting effort significantly.

[AndyVessey]

Hi Michael,

Thanks for the advice.

After some investigation, our already defined target application using the LPC2146 only has 32K of RAM and 256K of flash.

Does this mean that eCos/LV Embedded is a none starter due to eCos's 256K RAM requirement?

Regards

Andy

[Michael.Phillips]

Andy,

I wouldn't call that a non-starter. You can run the application from flash. It isn't eCos that has the RAM recommendation, it is LabVIEW. As long as you are mindful not to dynamically allocate memory, that amount of memory should be adequate. What sort of applications will you be using LabVIEW to create?

[AndyVessey]

Hi Michael,

Thanks for the further advice and promising news on the RAM/Flash situation.

The application is 'test mode' firmware for our target alarm telephone product. This will form part of an 'end to end' LabVIEW based production test system. The system would consist of a TestStand/LabVIEW based tester, testing a LabVIEW Embedded constructed Test Mode within the alarm telephone product.

Basically the chain of events to test the target are:

TESTER

1. Use our existing tests (100+) in LabVIEW 8.5 (containing serial/rs232 type test mode commands to target under test)

2. Sequence LV tests with TestStand 4.0

UUT (Unit Under Test)

3. Target to receive, acknowledge and execute test commands using LabVIEW Embedded test mode firmware.

-------------

Just wondering if any other customers or yourselves at NI use a similar system?

Regards

Andy

[Michael.Phillips]

Andy,

Sounds interesting. I don't think I've seen LabVIEW Embedded integrated with a TestStand sequence yet, but that's a great idea! I have seen the use case where LabVIEW Embedded used to test a unit's internals, as sort of a built-in tester. Let us know if you have any more questions.