Yahoo Groups archive

Lpc2000

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

Message

Re: Unable to access ext memory on EVBA7 with 144 Pin Adapter

2004-08-24 by ian48harry

Rick:

If you have access to JTAG, built-in on EVBA7, then just use the 
supplied PathFinder debugger to manually set-up the external RAM, 
then load the code at that address.  Or, of course allow the flash to 
hold the code that initiallises the external RAM, or ...

Regards,

Ian

--- In lpc2000@yahoogroups.com, "helicopterproject2003" 
<helicopterproject2003@y...> wrote:
> I guess this means there is no way to use the ext RAM to load 
> program code for debugging purposes as you would the on-board RAM 
> because it is not available at reset.
> 
> My program has grown larger than the onboard 16K of memory. I was 
> hoping to use the ext RAM for testing and debugging by loading the 
> program code into this RAM by the JTAG. This would allow for many 
> more breakpoints than loading the program into flash.
> 
> Am I understanding your answer correctly that this is not possible?
> 
> Rick
> 
> --- In lpc2000@yahoogroups.com, "philips_apps" <philips_apps@y...> 
> wrote:
> > Rick,
> > 
> > The 144 Pin Adapter has 1 Mbyte of RAM which is organized as 256K 
> x 
> > 32 ( Two 16 bit RAM chips). The start address of the external RAM 
> is 
> > 0x81000000 ( Bank 1, EMC )
> > 
> > The following registers must be initialized to enable the 
> > read/write/execute access.
> > 
> >    /* Connect A2 - A19, WE and CS1 */
> >    *pinsel2 = 0xC6009E4;
> >    /* Initialize Bank1 config in EMC, 32 bit with minimum waits */
> >    *bcfg1 = 0x20000400;
> > 
> > V18A(143), V3A(14),VSSA(139) and VSSA_PLL(138) power supply pins 
> are 
> > not connected on the adapter. These pins needs to be connected if 
> you 
> > are using the PLL and ADC.
> > 
> > Philips Apps
> > 
> > --- In lpc2000@yahoogroups.com, "helicopterproject2003" 
> > <helicopterproject2003@y...> wrote:
> > > I have a EVBA7 with a 144 pin adapter with a LPC2214 chip. The 
> > > adapter has 1MB of RAM which I think starts at 0x80000000. I 
> also 
> > > belived it is hardware straped to startup in 32bit data bus 
mode.
> > > 
> > > I can't seem to write anything into this memory. Even if I use 
> the 
> > > JTAG and IAR debugger to set any memory location above 
0x8000000 
> it 
> > > stays set to zero which makes it appear to not be working at 
all 
> or 
> > > incorrectly addressed.
> > > 
> > > Anyone have any ideas?
> > > 
> > > Thanks
> > > Rick

Attachments

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.