Targeting LabVIEW to MCB2140 board using Microprocessor SDK problem

[MihaiC]

First, in the Labview project, the target device is still LPC2138. My device is LPC2148, so I selected it. 

The application builds and is downloaded to the device, but the program halts at:

while(OCDI_RDMStart != 0x01);

from OCDICheckPoint.c 

If I deselect the Enable Debugging from test.lvprog -> Application, the code stops when reaches:

for (;;){

}

in the RTX_Config.c 

[Claire_Reid]

Hi MihaiC,

I am very confused as to why the target(or even how) the target could show up as anything other than LCP2148.

Here is what is  shows up as on my computer, and my two of my collegues (one did not even install the port files I sent you)

Did you delete your old port files before proceeding with mine? Can you send me a screen shot of your C:\Program Files\National Instruments\LabVIEW 2009\Targets\Keil\Embedded\RealView\Generic\ folder.

[MihaiC]

Hi ClaireR, 

I'm sorry. 

I wasn't very explicit, I meant the uVision LabVIEW project, the one from \MCB 2140 Port\Example\test\LPC2148\Application\2.0\Project

I uploaded the screenshot. 

[Claire_Reid]

HI MihaiC,

So I went back and reviewed how I did the port process-basically I started with files from the Blinky example for the MCB2140. When I opened this example and looked at what chip it uses, I realized it uses the LPC2138- which explains why the files I sent you are showing LPC2138 as the target. I will have to check with R&D to see if just changing the chip is all we have to do to make the port work.

As for the code just stopping in for( ; ; )..this is because our test VI has nothing in it, it is just a "wait" really. Please try adding some code to the test VI as show in the screen shot below...

 Does this change the behavior?

It is very possible that the port will need to be redone. So if the above code doesn't work, let me know and I am willing to try another port.  

Message Edited by Claire R on 04-20-2010 11:42 PM

[MihaiC]

Hi ClaireR,

Sorry for the delayed reply.

As far as I can tell it's not working, even if I add something in the while loop. It seems that the loop doesn't execute and the code stacks before entering the loop.

Also, if I remove the "Enable debugging" option from test.lvproj -> Application -> App Information, the VI doesn't execute at all.

[Claire_Reid]

Hi MihaiC, My guess is this is because I started the port with the Blinky example MCB2140 and LPC2138- I am still waiting to hear back from R&D on whether this would cause problems. Will keep you posted

[Claire_Reid]

Hi MihaiC,

In the generated C code, please add a breakpoint inside the while loop and see if it reaches the breakpoint. Let me know the results of this.

[JensL]

Hi Claire R and MihaiC.

Did you ever manage to solve this problem? The reason I'm asking is that I'm trying to port to the LPC2148 myself (on a MCB2140) and run into exactly the same problems as MihaiC with the application hanging in the same places as he mentions.

I'm working with LabVIEW Embedded module for ARM (LV2010).

Regards.

Jens L.

[MihaiC]

Hi JensL,

No, I haven't solved the problem. The application continued to hang and at that moment I assumed the porting was too problematic to continue.

Instead, I can tell you that LabVIEW works fine with the LM3S8962 CortexM3 board, for which NI offers support:

http://zone.ni.com/devzone/cda/tut/p/id/7066. But even for that, the peripheral devices were not implemented, interrupts, etc. 

At the moment I've tried the porting I was using LabVIEW 2009, maybe the new 2010 version offers some bug fixes.

Still, if you want a fast implementation with an MCB2140 board you should consider the good old C language.

Have a nice day!

Mihai

[JensL]

Hi Mihai,

That was what I was afraid off ...

I started out using the MCB2300 which also works fine with LabVIEW although I had to write some C code for setting the RTC, power-down and wake-up (including configuring the PLL). But we use the LPC2148 on the board we're developing and after reading through the guides I thought porting would be the least of our problems.

I'll contact NI support and see if they can help me get this porting thing to work. I'd really like to continue using LabVIEW, but as you said there's always C ...

If I succeed I'll post the solution here.

Have a nice day!

Jens