public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Jean-David Vuillemain <jdvuillemain@gmail.com>
Cc: ecos-discuss@sourceware.org
Subject: Re: [ECOS] arm7 lpc2xxx abort data exception
Date: Fri, 25 Jan 2008 07:53:00 -0000	[thread overview]
Message-ID: <20080125075307.GL13131@lunn.ch> (raw)
In-Reply-To: <d9d367f0801241538v2a3dbdb7o3057d65798a9cccd@mail.gmail.com>

On Thu, Jan 24, 2008 at 03:38:14PM -0800, Jean-David Vuillemain wrote:
> hi,
> 
> i have been working with ecos for a couple of months now. I had no
> problem at all with a 8 months old repository source files and my own
> port for my target board. After some problem with my working
> environment  and updating the ecos source files, i can't have my old
> work and my new  code running on the board.
> It seems that my code always go through the same steps and finishes by
>  an exception abort data.
> 
> Here is the code where it fails:
> 0x80020070 <start>:    ldr r0, [pc, #1020]    ; 0x80020474 <.init_flag>
> 0x80020074 <start+4>:  ldr r1, [r0]
> 0x80020078 <start+8>:  cmp r1, #0    ; 0x0
> 0x8002007c <start+12>: bne 0x80020078 <start+8>
> 0x80020080 <start+16>: ldr r1, [pc, #196]    ; 0x8002014c <init_done>
> 0x80020084 <start+20>: str r1, [r0]
> 0x80020088 <start+24>: mov r0, #0    ; 0x0
> 0x8002008c <start+28>: ldr r1, [pc, #988]    ; 0x80020470
> <.__exception_handlers>
> 0x80020090 <start+32>: cmp r7, #19    ; 0x13
> 0x80020094 <start+36>: beq 0x800200a0 <start+48>
> 0x80020098 <start+40>: ldr r2, [r1, #40]
> 0x8002009c <start+44>: str r2, [r0, #40]
> 0x800200a0 <start+48>: ldr r2, [r1, #24]
> 0x800200a4 <start+52>: str r2, [r0, #24]    <-- this line fails on my
> old and new programs
> It ends up in an abort data:
> 0x00000010 swp             r1, r3, [r2]

What is the value of r0? You should be able to look at the exception
bank of registers and see a value. Is it legal, does RAM/FLASH/IO
exist there etc.

The fact you are in exception handlers is not good anything. It
suggests something else has gone wrong. Have you checked your stacks
are big enough. It seems like 75% of random crashes are stack
overflows.

        Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2008-01-25  7:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d9d367f0801241535wb8f95b3x30dbfbbd9f97e7b2@mail.gmail.com>
2008-01-24 23:38 ` Jean-David Vuillemain
2008-01-25  7:53   ` Andrew Lunn [this message]
2008-01-25 16:53     ` Jean-David Vuillemain
2008-01-25 16:59       ` Gary Thomas
     [not found]         ` <d9d367f0801250941u6cdf1b4et681f4587e3472587@mail.gmail.com>
2008-01-25 21:11           ` Gary Thomas
2008-01-25  9:02   ` Sergei Gavrikov
     [not found]     ` <d9d367f0801251021s797a8cd8r231907231972be90@mail.gmail.com>
     [not found]       ` <20080125212412.GA5919@ubuntu>
2008-01-25 21:55         ` Jean-David Vuillemain
2008-01-25 22:06           ` Sergei Gavrikov
2008-01-28  7:39             ` Tom Deconinck
2008-01-29  4:31               ` Alergent
     [not found]             ` <d9d367f0801251520i317089e9n736e1f7b00e23ae9@mail.gmail.com>
2008-01-30 23:24               ` Jean-David Vuillemain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080125075307.GL13131@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@sourceware.org \
    --cc=jdvuillemain@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).