blinky led example

[serkanb]

Hello,

I want to run a blinker led program on LPC2294 board.

There is a demo led which connected port pin P0.8 (GPIO0) on the LPC2294. (It illumunates when pin goes low)

I used an ElementalIO as output and I connect it a boolean false.  

First I tried LineGPIO_0_8

then I tried LineGPIO_0_0 pins. But the led didn't illumunate.

What would be the problem here?

[Michael.Phillips]

Open the LabVIEW Embedded Porting Guide (in labview\manuals) and go to page 2-17. This section of the document lists all the connections you need to make to use the GPIO with LabVIEW Embedded. It appears that the LEDs actually start at LineGPIO_1_16.

[serkanb]

That leds on GPIO Expansion Board. But I havent an GPIO Expansion board.

I use HD200 development board. There is one led on HD200 and its adress is P0.8

I tried to use both Elemental IO and PHYTEC Write Digital Line Function.vi but result

was the same.

Note:  In the hardware manual there is some information about this led:

Programmable LED D3

The phyCORE Carrier Board HD200 offers a programmable LED at

D3 for user implementations. This LED can be connected to port pin

P0.8 (TxD1) of the phyCORE-LPC2292/94 which is available via

signal GPIO0 (JP17 = closed). A low-level at port pin P0.8 causes the

LED to illuminate, LED D3 remains off when writing a high-level to P0.8.

 

[Michael.Phillips]

Hi,

Based on the documentation you pasted, make sure you have the appropriate jumpers closed. Also, it appears that the polarity is inverted for your development board. Have you tried turning the LED "off"?

[ROMP]

Hello,

I have the same target as serkanb ( Phythec LPC2294 board on HD200 core, without extra GPIO board ). I'm running LV 8.5 with LV Embedded 2.5 on Win XP Professional.
I've done installation of cygwin and ecos. Also flash uploading redboot with LPC2000 utility was OK.
But when I opened new empty project and  created one Elemental I/O on Phytec LPC229x, eCos target ( LineGPIO_O_8 which drives LED3) and drop it on diagram it was not valid. In I/O Node Properties it says: Not Available.
Then I checked all other available elemental nodes and all of them are not available. Obviously I have a problem, looks like there is no connection between LV and physical target.

The procedure in the Porting Guide is OK, but not very helpful in case something go wrong

serkanb: can you please describe your setup procedure and did you succeed to get working LED blinking?

Any suggestion about possible solution will be welcome. Looks like I'm stuck right at the beginning, before even try to build RAM application.

[MattP]

Hello,

If you're referring to the Elemental I/O properties dialog for GPIO_0_8 having the message "LineGPIO_0_8 : No Node Specific Properties Available", this is normal, as there are no special properties to set for this digital line.  You mention "drop it on diagram it was not valid.", but I am unsure what you mean by this.  Is your run arrow broken?  Does it throw an error of some kind?

Can you compile and run a program on the target at all?  If you're able to successfully deploy an app to the target, this implies that the connection there is ok. 

I should note also that you do not need any hardware attached to create the project and VI successfully, so you shouldn't have to worry about a connection to the target until it is actually time to deploy your code.

[ROMP]

Hi Matt,

sorry about not being clear enough. Let me be more specific. I made a mistake and opened new VI in My Computer instance, this is probably why my elemental node was not available.

Ok, I started new VI in the target instace. Now adding elemental I/O node to the block diagram is OK, but as soon as I try to connect wire to the input I get Fatal Internal Error: "exec.cpp", line 3334 and LV ends. So I'm not even near compiling process....


Do I need to do any setups with Target Editor or Elemental I/O Wizzard?


Any idea what can be wrong? Excuse me for my beginner's question, this is really my first attempt to play with Embedded modul and microprocessor hardware despite I'm long time LV user.

Cheers,

romp

[MattP]

Hello,

This was reported to R&D (# 4BPBRQWD) for further investigation.  We're looking into the issue now to see if there are good workarounds for you.  Thanks for letting us know about this - if you encounter any troubles like this as you continue on, please let us know!

Message Edited by MattP on 10-02-2007 03:39 PM

[MattP]

Hello,

We have a workaround for you that should meet your needs.

You can prevent this error by mass compiling the VI's in your Phytec target directory: labview\Targets\NI\Embedded\ecos\phytec_lpc229x\

The mass compile operation can be performed by navigating to Tools»Advanced»Mass Compile in the LabVIEW environment.

Please give this a try and let me know if it works for you!

[ROMP]

MattP,


thank you. Yes, mass compiling all VIs in this folder helped. Now I can finish the VI, create Build Specifiacations and start Build process without errors. But when trying to hit Run button to download application, I get : Connection to RedBoot failed!

I checked all recommended actions ( VISA installed, COM not used, device reseted), but notning helps. Looks I have problem with uploading redboot.hex to device with LPC2000 Flash Utility programm from PHILIPS, despite this utility gives me status File Upload Successfully Completed.
Strange is that if I press Compare Flash button on LPC2000 Utility after that, I get : File compare failed! Message. Does this mean that redboot is not loaded OK?

There is jumper JP28 on HD200 board, my setting is default: 3+4 and 6+8. I'm using this procedure for restarting:

1. press Reset+Boot buttons
2. release Reset
3. wait 3 sec
4. release Boot

If I connect Terminal to COM1 port and restart board, I sometimes receive <00> only or most often nothing ! Is this normal? I guess I should get some message...

Can you please help me troubleshoot this problem. What should I do to upload redboot.hex and verify if it is actually uploaded fine?

Thank you.