Reply by krishnamurthy babu●February 22, 20102010-02-22
Dear Developers,
Thanks for providing me with hints and suggestions.
I verified all aspects and found that a jumper was incorrectly set on my board.
Once thatis was correctly set, the lpc21isp utility has recognized the chip and
synchronizationalso works.
Regards,
babu K
>
> And, of course, P0.14 must be at GND when the processor comes out of
> reset.
>
> Richard
If the LPC-2148 is bricked, put a paperclip on the Po.14 and GND pins
(physically on the board,) and hit RST at the same time, or as many
times as it makes you happy. Then remove the paperclip, and reprogram.
Leave all of the jumpers and sliders in stock position. I thought I was
f'ed, and this worked for me.
DON
Reply by rtstofer●February 21, 20102010-02-21
And, of course, P0.14 must be at GND when the processor comes out of reset.
Richard
Reply by rtstofer●February 21, 20102010-02-21
The -PHILIPSARM flag is not necessary. By default, lpc21isp wants to talk to a
lpc21xx device.
I don't think I have ever used the interactive feature.
One thing that gets me fouled up is minicom. If I have minicom connected to the
same serial device as lpc21isp, synchronizing will never happen. I have to
close down minicom before invoking lpc21isp and then restart it for console
IO.
Richard
Reply by capiman26061973●February 21, 20102010-02-21
Hello,
Have you pressed reset / pgm button manually ?
Or should this happen autopmatically (done by lpc21isp) ?
Try adding "-control" to command line option of lpc21isp.
Best regards,
Martin
Reply by krishnamurthy babu●February 21, 20102010-02-21
Dear Developers,
I am facing the following problem on a Linux machine with a LPC2148 BOARD. If
you havecome across a similar problem and figured the solution, please let me
know:
LPC21ISP#./lpc21isp -detectonly -PHILIPSARM /dev/ttyUSB0 38400 12000
Target: Philips
lpc21isp version 1.78
Synchronizing (ESC to abort)
............................................................................
no answer on '?'
