Forums

Olimex 2148 problems

Started by farmckon June 12, 2006
Hey Folks,
I've been lurking on the list a while, and am finally posting. I have
an Olimex 2148 that I'm messing with at home for hobby work, and I've
run into a problem that might be chip burn-out.

I've been using it for the last week without problem. Yesterday I was
working with it, and it started to smell like 'magic smoke' I felt
around, and the ARM chip was warm, so I shut it down.

After letting it cool off, I plugged it back in. It runs the last
program that was on it (a very simple blinking LED program) but it
gets hot very quickly (5 seconds until I can't keep my finger on it),
and if I try to connect with the Phillips LPC flash utility (v2.2.3)
it does not read the device ID.

Has anyone run into something like this on this board? Any other
idea, other than my chip burnt out? I can't seen any visible scortch,
but that's not saying much.

I've just finally got time to work on hobby ARM stuff again, and this
happens. Sheesh. Thanks for any help/advice anyone can send my way.

- Jon McKamey





An Engineer's Guide to the LPC2100 Series

--- In l..., "farmckon" wrote:
>
> Hey Folks,
> I've been lurking on the list a while, and am finally posting. I
have
> an Olimex 2148 that I'm messing with at home for hobby work, and
I've
> run into a problem that might be chip burn-out.
>
> I've been using it for the last week without problem. Yesterday I
was
> working with it, and it started to smell like 'magic smoke' I felt
> around, and the ARM chip was warm, so I shut it down.
>
> After letting it cool off, I plugged it back in. It runs the last
> program that was on it (a very simple blinking LED program) but it
> gets hot very quickly (5 seconds until I can't keep my finger on
it),
> and if I try to connect with the Phillips LPC flash utility
(v2.2.3)
> it does not read the device ID.
>
> Has anyone run into something like this on this board? Any other
> idea, other than my chip burnt out? I can't seen any visible
scortch,
> but that's not saying much.
>
> I've just finally got time to work on hobby ARM stuff again, and
this
> happens. Sheesh. Thanks for any help/advice anyone can send my
way.
>
> - Jon McKamey
>

First suggestion, check the supply voltage and/or try to connect USB
(it can be powered from USB)

Jan

--- In l..., "farmckon" wrote:
>
> Hey Folks,
> I've been lurking on the list a while, and am finally posting. I have
> an Olimex 2148 that I'm messing with at home for hobby work, and I've
> run into a problem that might be chip burn-out.
>
> I've been using it for the last week without problem. Yesterday I was
> working with it, and it started to smell like 'magic smoke' I felt
> around, and the ARM chip was warm, so I shut it down.
>
> After letting it cool off, I plugged it back in. It runs the last
> program that was on it (a very simple blinking LED program) but it
> gets hot very quickly (5 seconds until I can't keep my finger on it),
> and if I try to connect with the Phillips LPC flash utility (v2.2.3)
> it does not read the device ID.
>
I think I would measure the Vcc. It should be 3.3V.

Does it overheat if the serial cable is removed? How are you powering
the module?

Richard

----- Original Message -----
From: "farmckon"
To:
Sent: Tuesday, June 13, 2006 3:10 AM
Subject: [lpc2000] Olimex 2148 problems
Hey Folks,
I've been lurking on the list a while, and am finally posting. I have
an Olimex 2148 that I'm messing with at home for hobby work, and I've
run into a problem that might be chip burn-out.

I've been using it for the last week without problem. Yesterday I was
working with it, and it started to smell like 'magic smoke' I felt
around, and the ARM chip was warm, so I shut it down.

After letting it cool off, I plugged it back in. It runs the last
program that was on it (a very simple blinking LED program) but it
gets hot very quickly (5 seconds until I can't keep my finger on it),
and if I try to connect with the Phillips LPC flash utility (v2.2.3)
it does not read the device ID.

Has anyone run into something like this on this board? Any other
idea, other than my chip burnt out? I can't seen any visible scortch,
but that's not saying much.

I've just finally got time to work on hobby ARM stuff again, and this
happens. Sheesh. Thanks for any help/advice anyone can send my way.

I'd change the chip. I did that for someone once, it isn't difficult but you
do need the right equipment. Use ChipQuik to remove it.

Leon

Hi,
I have had similar problem with Olimex P2148 board. Accidently shorted 3.3V power pins with a probe and the input 3.3V regulator has become shorted itself.
Try to measure voltage on 3.3V pins of the board. If it's the same as the input voltage, you'll have to replace the regulator (LM1117 on P2148 board) and (most likely) LPC2148 and MAX3232 ICs.

Regards,
Max
> ----- Original Message -----
> From: "farmckon"
> To:
> Sent: Tuesday, June 13, 2006 3:10 AM
> Subject: [lpc2000] Olimex 2148 problems
> Hey Folks,
> I've been lurking on the list a while, and am finally posting. I have
> an Olimex 2148 that I'm messing with at home for hobby work, and I've
> run into a problem that might be chip burn-out.
>
> I've been using it for the last week without problem. Yesterday I was
> working with it, and it started to smell like 'magic smoke' I felt
> around, and the ARM chip was warm, so I shut it down.
>
> After letting it cool off, I plugged it back in. It runs the last
> program that was on it (a very simple blinking LED program) but it
> gets hot very quickly (5 seconds until I can't keep my finger on it),
> and if I try to connect with the Phillips LPC flash utility (v2.2.3)
> it does not read the device ID.
>
> Has anyone run into something like this on this board? Any other
> idea, other than my chip burnt out? I can't seen any visible scortch,
> but that's not saying much.
>
> I've just finally got time to work on hobby ARM stuff again, and this
> happens. Sheesh. Thanks for any help/advice anyone can send my way.
>
> I'd change the chip. I did that for someone once, it isn't difficult but you
> do need the right equipment. Use ChipQuik to remove it.
>
> Leon
>