The Uv3 simulator and JTAG debugger use the wrong SFR symbols for the LPC213X ARM processors. It appears the symbols for the LPC210x are used. I've changed the device database for the LPC2138 to show the proper register file (LPC213x.h), but that doesn't change anything. The symbols listed in the View->Symbols window are still those for the 211x. Can anyone point me in the right direction? Many thanks in advance. Dave Sidlauskas
Dave; Which symbols are you questioning? In the LPC2130 examples, several of the header files still refer to the LPC21x.h fles. I change the examples on my system to the LPC213x.h files. Debugger symbols look correct to me. Tell me what symbols are incorrect. I need to look at them also. Bradford
Bradford, The ones I'm having a problem with are for the SSP peripheral. The debugger doesn't recognize and of the SSP registers, and they don't show up under View->Symbols. I'm not sure if this is the only problem. There must be some configuration setting somewhere that informs the debugger about SFR names and addresses, but I haven't been able to find it. Dave
We have missed the new SSP Peripheral when we have implemented the LPC213x simulation/target dialogs. The simulation will come til End of Feb. 2005. However the header file should correctly implement the SSP symbols. Also you should be able to debug the SSP software using ULINK. Only the target display dialog (which adds a peripheral specific dialog) is missing for SSP.
Thanks for the information. I can debug using Ulink, but the debugger does not recognize the SSP registers. For example, typing SSPSR in the Command Line produces an error message. I've been using the memory display to show the register values. View->Symbols does not show the SSP registers. Also, there are a couple of 16 bit SSP registers that are defined as char * rather than short * in LPC213x.h. (SSPCR0 and SSPDR).
You may just enter in the Watch Window the registers using the _RDWORD definition. For example:
_RDWORD (0xE0068000) // SSPCR0