jayanthyk192
Full Member level 3
- Joined
- Sep 17, 2010
- Messages
- 179
- Helped
- 1
- Reputation
- 2
- Reaction score
- 1
- Trophy points
- 1,298
- Activity points
- 2,580
I checked my circuit and its pretty much the same except for a fewHi jayanthyk,
I attach for you some good working schematic (checked in my projects) for LPC2106,
use this to check your connections...
CRP3 0x43218765
Access to chip via the JTAG pins is disabled. ISP entry by pulling P0.14
LOW is disabled if a valid user code is present in Flash sector 0.
This mode effectively disables ISP override using P0.14 pin. It is up to
the user’s application to provide need Flash update mechanism using
IAP calls if necessary.
Caution: If CRP3 is selected, no future factory testing can be
performed on the device.
Most NXP LPC series ARMs offer a bootloader in ROM which provides In System Programming (ISP) through the devices serial port or USB if available.
There are several utilities which ease the programming task using ISP:
Flash Magic
However, if Code Read Protection (CRP) Level 3 has been invoked, the device is effectively locked from ISP or JTAG Read, Write or Erasure, permanently disabling any future attempts to reprogram or read the contents of the flash rendering the device useless other than for its original purpose.
The only method of disabling CRP3 is through an existing routine already programmed into Flash before CRP3 was invoked.
Reference:UM10275 LPC2104/2105/2106 User Manual, Section:Table 194. Code Read Protection options, Page:232
Commercial products containing an LPC series ARM may invoke CRP3 before the releasing the product to prevent theft or alteration of the devices firmware.
Some devices are programmed to include a routine within the firmware for revoking CRP3 and allowing upgrading of the firmware, some do not.
BigDog
Post your circuit. Is your MCU and PC have same baud rates?
My reply was an attempt to alert you of the possibility of CRP3 having been invoked.
You mentioned manipulating P0.14 had no effect, if this were the case then CRP3 could certainly be the source of the issue.
While you should be able issue ISP commands using a terminal emulation program, the easiest method of determining whether or not CRP3 has been invoked is simply to use Flash Magic and attempt to erase the device.
It could also determine if you can initialize the ISP bootloader.
Assuming of course, your ultimate goal is programming the device for other tasks.
BigDog
If I remember correctly...
After the device indicates it has synchronized type an uppercase U, the device should echo back an uppercase U.
If it does not echo the uppercase U it is an indication there is an issue with either the device configuration, the RS-232 transceiver or cabling.
Ensure you have echoing disabled in the terminal emulation program.
BigDog
The spurious characters maybe due to noise or an improper/poor connection at the LPCs side, it's difficult to say.
At least it appears you've managed to invoke the ISP bootloader, although there still seem to be an issue with the connection reliability.
According to the LPC2106 User Manual, XON/XOFF flow control should be implemented.
It's been quite a while since I've typed ISP commands in by hand or use ISP at all for that matter as I have several JTAG programmer/debuggers I typically use.
I may have been incorrect concerning the uppercase U, try sending an uppercase J which should return the device part ID number.
Reference the LPC2106 User Manual, Section: 9. ISP commands, Page: 233, all the commands are listed along with the required format and successful replies.
BigDog
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?