Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: [lpc2000] LPC2292 problem

2005-08-17 by Sebastien Jacquemard

I've change the 100nF reset cap by a larger one by a 2.2uF tantalum (It's
quite large but I've got only this one...)
I don't have anymore the strange signal on the PIN P0.10 to P0.16. Now P0.14
(IAP PIN) is High, reset is High (when the board run)
P0.14 is high when I press the reset switch, but the program doesn't toggle
the PIN ???

Sebastien

----- Original Message -----
From: "Sebastien Jacquemard" <sejacquemard@...>
To: <lpc2000@yahoogroups.com>
Sent: Wednesday, August 17, 2005 2:42 PM
Subject: [lpc2000] LPC2292 problem


Hello,

I've problems with my new board with LPC2292. I build my own board and I
plug a module from embest on it (with a LPC2292 + external flash + external
ram). Actually I've solder only the power supply, the rs232 + iap / reset
circuit (same shematic than Keil board).
Reset + iap work well. I can program the LPC2292 internal flash with Philips
flash utility, read the device ID without any problem. So I think the board
work.
I've make a little test program who toggle a GPIO pin.
I use Keil + GCC.
This is my program :

#include <LPC22XX.H>

int main (void)  {
    PINSEL0 = 0x00000400;
    IODIR0 = 0x00000400;
    while (1) {
        delay();
        IOCLR0 = 0x00000400;
        delay();
        IOSET0 = 0x00000400;
    }
}

This program run well on my MCB2130 board from keil.
At startup reset go from low to high (3.3v) see the screen copy of my
oscilloscope on the file section (lpc2292_pb.zip)
The embest module is supply by a 5v switching regulator on my board (LM2576)
and there is two LM1117 for 3.3 and 1.8v supply on the module.

There is a strange signal on PIN P0.10 to P0.17 (see the screen copy of my
oscilloscope for these PIN)

Somebody has got an idea ?

Thanks,
Sebastien







Yahoo! Groups Links

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.