Yahoo Groups archive

Lpc2000

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

Thread

Res:LPC2106 Programming - ISP - Solved

Res:LPC2106 Programming - ISP - Solved

2004-02-21 by gokbektas

I retouched with the soldering iron to pins of baby, compare function or ISP utility confirms chip is programmed.
Leon, your code sent garbage characters at 9600 baud, I tried other baud rates also...
Then I recompiled uart example of crossworks then loaded to chip...
It is working! Now, I can play ;-)
Thanks a lot! I'll upload my board's picture to my personal website soon.
Show quoted textHide quoted text

----- \ufffdzg\ufffdn \ufffdleti -----
Kimden : lpc2000@yahoogroups.com
Kime : lpc2000@yahoogroups.com
G\ufffdnderme tarihi : 21/02/2004 12:57
Konu : Re: Re: [lpc2000] LPC2106 Programming - ISP and hex file
----- Original Message -----
From: "gokbektas" <gokbektas@...>
To: <lpc2000@yahoogroups.com>
Sent: Saturday, February 21, 2004 10:18 AM
Subject: Ynt: Re: [lpc2000] LPC2106 Programming - ISP and hex file


> Thanks leon,
> I tried the hex file that you sent me.
>
> I read 4293984050 part ID and 1.3 bootloader ID, when I click Upload to
Flash, it
> does not give any error messages, a progress bar shows it is uploading.
>
> When I click Compere Flash, a progress bar shows it is reading but "File
compare Fail"
> message appears at the end.
>
> And there is no data coming from chip when I check it with terminal
window...

It looks like you have a problem with the flash memory. I'd replace the
chip, or try another board if you have one. I'm actually using a '2104, but
it shouldn't make any difference.

Regards,

Leon



Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/lpc2000/

<*> To unsubscribe from this group, send an email to:
     lpc2000-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/


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.