Lpc2000

Hey Amit,

Thanks for your suggestion on using the hyperterminal to test run 
the on-chip bootloader. I ran a set of basic commands on two boards 
(one good board vs the bad board) and logged the communicated bytes 
as seperate files (below). You might be able to understand this.

NB. all lines proceeded with (comments) represents replies by the 
lpc. Other lines were sent by the PC. Here it is!

Terminal log file -  Good Board
Date: 11/2/2005 - 1:47:27 PM
-----------------------------------------------
Synchronized		(received ? character)
Synchronized
OK			(board officially synchronized)
P 2 3
0			(prepared sector 2&3)
U 23130
0			(unlocked erase/write command)
E 2 3
0			(erase successful)
J
0			(part ID read successful)
16908050		(ID#)

-----------------------------------------------
Date: 11/2/2005 - 1:51:38 PM
End log file

Terminal log file - Bad Board
Date: 11/2/2005 - 1:40:00 PM
-----------------------------------------------
Synchronized		(received 1st character)
Synchronized
OK			(board officially synchronized)
P 2 3
0			(prepared sectors 2&3)
U 23130
0			(unlocked write/erase cmds)
E 2 3
	       <------	(No Code Returned)
-----------------------------------------------
Date: 11/2/2005 - 1:45:40 PM
End log file

I notice that the lpc chip hangs after I send the erase command, and 
fails responding to any future comands sent by the PC.

This probably verifies my suspicion that the chip giving problems 
might have a corrupt bootloader. Otherwise I don't know how to get 
around this problem. Let me know what you think.

Leighton

--- In lpc2000@yahoogroups.com, "Amit" <emailakb@y...> wrote:
>
> Hi,
> 
> Have you tried talking to the device over a serial terminal 
program 
> like "HyperTerminal" or "TeraTerm"  instead of using the ISP 
utility. 
> You can start by issuing a "?" and then the part would return 
> with "Synchronized"...then would follow the ISP procedure. I think 
> this flow is mentioned in the UM.
> 
> By doing this you can get a more detailed picture of why ISP is 
> failing. If a ISP command fails/succeeds the bootloader always 
> returns a "code".
> 
> Using the code, you can get more information from the part 
regarding 
> this problem.
> 
> Amit