blinky led example

[Michael.Phillips]

Hi,

It sounds like the Redboot boot loader is not written properly into flash.

There are a few things you can check when uploading the Redboot image to flash:

- make sure the extension board is disconnected from HD200 evaluation board;
- check the LPC2000 Flash Utility settings described in the instructions in the LabVIEW Embedded Porting Guide, Chapter 2 Example Targets, page 2-16 - Installing the RedBoot Bootloader
- JP28 looks like this on my board:

Message Edited by Michael P on 10-03-2007 12:29 PM

[ROMP]

Michael,

my JP28 settings is same as yours, as I described in my previous post. Also LPC2000 settings are OK I guess, since I can read Device ID, Erase the Flash and Upload. In NI document you suggest baud rate 9600, but I can also connect with 38400.

Can you confirm please if you can successfully do Compare Flash after uploading and reseting the board? Because I'm can not!

If this is of any importance, I do not have GPIO board at all, using PCM-023 on HD200 only.

I also try to run LEP_Redboot_Find.vi and it can not detect any RedBoot running on target. Can you tell me how the download configuration cluster at this VI should be configured ( besides COM1 ). Adresses, protocol, ....

Can you please describe your detailed step-by-step procedure and settings ( baud rates, addresses, jumpers, any other relevant ones ) that you used to upload RedBoot into your target? Following instructions in NI document obviously not working for me.

Is there any other way to determine if RedBoot is really loaded and running or not?

I just can not beleive that my hardware is damaged, since it is completely new ( unused so far ), but I can not completely discard this option too.

Regards,

romp

[Michael.Phillips]

Hi,

When you connect terminal, make sure to set the speed to 57,600.

---

Can you confirm please if you can successfully do Compare Flash after uploading and reseting the board?

---

Yes, the compare flash succeeds.

The instructions in the LabVIEW Embedded Development Module Porting Guide are the most detailed and specific directions I can give you. I am starting to think that there is something wrong with the hardware or the flash programming software. You might want to contact Phytec and see if they are aware of any related issues.

[ROMP]

Michael,

thank you for Compare confirmation. Now I can narrow down the problem to the Flash utility and/or hardware fault. I have already contacted Phytec a day ago but still didn't get any answer . ( NI support is far better   )

Thank you for now. I guess you can not help me beyond this. I will update this thread with the results when I fiinally find the exact reason.

Regards,
romp

[ROMP]

Michael,

after my colegue completely deleted the device with JTAG/USB device using Keil tools and loaded original Blinky application, I can finaly upload RedBoot to my LPC2294. I'm not sure what was wrong here, but darn thing just started to work now ?!

This is the response string I get on my terminal utility after reset:

+
RedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version UNKNOWN - built 12:42:10, Feb 15 2007

Platform: PHYTEC phyCORE/LPC229x (ARM7TDMI-S)
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

RAM: 0x81000000-0x81100000, [0x81005930-0x81100000] available
     0x40000000-0x40004000, [0x40000000-0x40004000] available
RedBoot>

Next, I want to run simple VI to make LED3 on HD200 to blink. Like initial posts in this thread describe, LED3 should be controlled with digital line P0.8; pulling it low should turn LED3 on.

I built simple VI, using Elemental node LineGPIO_0_8, made new default RAM Application ( following NI document: ARM Microcontroller Development with LabVIEW ), built it with no errors and hit Run button.
Download process started with no errors, but LED3 doesn't blink and VI is not running ( I guess this is because I didn't enable debug option )

Do I have to configure something with Elemental Device Wizard or what? I just used default Elemental node for this target.
How can I be sure that application is actually downloaded and running on the target?

Can you attach your working VI ( or complete project) for me to try? Please don't forget I don't have GPIO expansion board.

Thank you,

Romp

[Michael.Phillips]

Hi,

This output from the bootloader looks good, I'm glad you were able to get that working. Have you tried using the One Button Dialog function to print out the serial port? I recommend that you try that first as a "sanity check". The One Button Dialog function serves as a "printf" for LabVIEW Microprocessor SDK. Any strings sent to that function will appear in a terminal connection to the serial port.

Regarding the LED blinking, I recommend that you verify all the connections on the I/O Extender board -- those are easy to miss.