Yahoo Groups archive

Lpc2000

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

Message

Re: Data Aborts

2004-12-21 by ian48harry

Have you "told" Multi-ICE what chip you are dealing with?  The AT91 
is plain ARM7TDMI, the LPC2000 is -S.  Other tools allow specific 
selection of chips rather than basic core types.

Ian

--- In lpc2000@yahoogroups.com, "tah2k" <tah2k@y...> wrote:
> 
> I understand where you are coming from, but I am trying to prevent 
> buying more tools. From what I understand, the keil tools require 
> their own emulator to actually run the debugger, and I already have 
> 3 multi-ice. 
> 
> I am missing something, this should be trivial. If I reload the 
> blinky application, it works just fine.
> 
> I have also got a keil mcb2100 board and I have the same issue.
> 
> 
> --- In lpc2000@yahoogroups.com, "Dan Beadle" <dan.beadle@i...> 
wrote:
> > I suggest you download the Keil tools.  
> > 
> >  
> > 
> > Download their demos.  That will verify that everything is 
working 
> properly.
> > 
> > 
> >  
> > 
> > From there, you could try the ARM tools with the Keil elf 
output.  
> At that
> > point, you know that the board and the code are good.  So you 
> would only be
> > working one problem.
> > 
> >  
> > 
> >  
> > 
> >  
> > 
> >   _____  
> > 
> > From: tah2k [mailto:tah2k@y...] 
> > Sent: Monday, December 20, 2004 4:15 PM
> > To: lpc2000@yahoogroups.com
> > Subject: [lpc2000] Data Aborts
> > 
> >  
> > 
> > 
> > Still not up and running with my Arm tools and the Keil MCB2130.
> > 
> > I setup the Arm AXD debugger to run the following script on 
> startup:
> > 
> > loadsymbols C:\Projects\Sampler_2138\AppFlash\Output\AppFlash.axf
> > setpc 0x0
> > sreg cpsr 0xd3
> > spp vector_catch 0
> > spp semihosting_enabled 0
> > 
> > It basically loads the debug symbols for the image in the 2138 
> > flash, initializes the CPSR, sets the pc to 0, and disables 
> > breakpoints at the Arm exceptions.
> > 
> > The debugger loads the source file correctly and the PC is set at 
> > 0x0 which is a branch to my startup handler at 0x20. However, if 
I 
> > run, or singlestep, or do anything, I get a "Data abort".
> > 
> > Also, if I try and display memory starting at 0x0, the debugger 
> > gives an error "Memory access failed" and only gives the contents 
> of 
> > addresses 0-20, the rest 0's.
> > 
> > I thought perhaps the data abort had something to do with the 
> > remapping done by the Philips boot loader, but I checked the 
> MEMMAP 
> > flag and it is set to 1, so I am running the flash at 0. 
> > 
> > I'm new to the part and evaluating it against the AT91 pocessors, 
> > and I am fresh out of ideas. The memory bus is internal so its 
not 
> > like I can hook up my logic analyzer too get some ideas.
> > 
> > Is it possible the Philips memory accelerator is partly to blame? 
> > Tehre must be otehrs using Arm tools with this part so I am 
hoping 
> > it is something trivial.
> > 
> > Any ideas are appreciated.
> > Tim
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Yahoo! Groups Sponsor
> > 
> > 
> > 
> > ADVERTISEMENT
> >  
> > 
> 
<http://us.ard.yahoo.com/SIG=1297jigje/M=295196.4901138.6071305.30011
> 76/D=gr
> > 
> 
oups/S=1706554205:HM/EXP=1103674517/A=2128215/R=0/SIG=10se96mf6/*http
> :/compa
> > nion.yahoo.com> click here
> > 
> > 
> >  
> > <http://us.adserver.yahoo.com/l?
> M=295196.4901138.6071305.3001176/D=groups/S=
> > :HM/A=2128215/rand=272492819> 
> > 
> >  
> > 
> >   _____  
> > 
> > Yahoo! Groups Links
> > 
> > *	To visit your group on the web, go to:
> > http://groups.yahoo.com/group/lpc2000/
> >   
> > *	To unsubscribe from this group, send an email to:
> > lpc2000-unsubscribe@yahoogroups.com
> > <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe> 
> >   
> > *	Your use of Yahoo! Groups is subject to the Yahoo!
> > <http://docs.yahoo.com/info/terms/>  Terms of Service. 
> > 
> > 
> > 
> > [Non-text portions of this message have been removed]

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.