Forums

Re: Problem Starting Up LPC2138 Board

Started by Leon November 2, 2007
----- Original Message -----
From: "Geoffrey Wossum"
To:
Sent: Friday, November 02, 2007 6:58 PM
Subject: [lpc2000] Problem Starting Up LPC2138 Board
> Hi all,
>
> I'm trying to get started on a custom board using an LPC2138. To jump
> start
> things, I got an eval of the Rowley Cross Studio for ARM, and installed
> the
> LPC2000 CPU support package. I can compile programs using Cross Studio,
> and
> download them using lpc21isp. Problem is, nothing happens.
>
> To start out, I just took a blinky example that goes with a Keil eval
> board.
> It's simple, and the IO lines it uses aren't hooked up on my board. I've
> included the source at the end of the message.
>
> Looking at the dissassembly, I figured out I needed to define
> STARTUP_FROM_RESET if I ever wanted it to do anything (I don't have a
> JTAG).
>
> I'd expect to see the IO lines toggling, but I see nothing. I've tried
> RAM
> and flash builds, ARM and THUMB builds, debug and release, all do nothing.
> My external 10.0 MHz crystal and 32 kHz crystals are both oscillating,
> but
> no other indication the part is doing anything once programmed.
>
> Anyone have any ideas?

How have you defined STARTUP_FROM_RESET?

Leon

An Engineer's Guide to the LPC2100 Series

On Friday 02 November 2007 05:25:53 pm Leon wrote:

> > Looking at the dissassembly, I figured out I needed to define
> > STARTUP_FROM_RESET if I ever wanted it to do anything (I don't have a
> > JTAG).
> >
> > I'd expect to see the IO lines toggling, but I see nothing. I've tried
> > RAM
> > and flash builds, ARM and THUMB builds, debug and release, all do
> > nothing. My external 10.0 MHz crystal and 32 kHz crystals are both
> > oscillating, but
> > no other indication the part is doing anything once programmed.
>
> How have you defined STARTUP_FROM_RESET?

Went into the project properties for my executable in Cross Studio and
added "STARTUP_FROM_RESET=1" in the "Preprocessor Definitions" setting under
the "Preprocessor Options" section.

I dissasembled the resulting firmware to verify that this actually gets the
CPU going at reset_handler, rather than having spin at reset_wait.

---
Geoffrey