public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Tom Deconinck <t.deconinck@gmail.com>
To: Shiang Lei <slei02@yahoo.com>,
	ecos-discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Running Firmware from external SRAM on AT91SAM7SE512
Date: Mon, 07 Dec 2009 10:07:00 -0000	[thread overview]
Message-ID: <e37cb5250912070207r66feb1b1pfed6beca51fee7ab@mail.gmail.com> (raw)
In-Reply-To: <192730.65612.qm@web112412.mail.gq1.yahoo.com>

On Mon, Dec 7, 2009 at 10:11 AM, Shiang Lei <slei02@yahoo.com> wrote:
> Tom:
>
> Thanks for e-mail me. My CPU is ARM 7 and the code can run on the external
> SRAM. The problem happened when running the cyg_thread_delay(). Timer
> interrupt occured inside the subroutine. I cannot step through the
> subroutine, it will not fail and can't exit either. If I let it ran and stop
> the BDI, the SRAM has been wiped out. No trace I can use to debug the
> problem.
>
> Regards,
> Shiang Lei
>
>

On AT91SAM7SE512 it is certainly possible to run code from SRAM and
SDRAM, I have done it in the past.
You need to figure out where you are jumping to when the interrupt
occurs and if the interrupt controllers are all mapped into the
correct address range. Check the ELF file to be sure.
Also, verify that your ELF file fits completely into the SRAM,
otherwise strange things are bound to happen.
The BDI probe will most likely reset the SRAM when stopped (if I
remember correctly).

Regards,
Tom

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

  parent reply	other threads:[~2009-12-07 10:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07  8:37 ShiangLei
     [not found] ` <e37cb5250912070101j2e15c76fnbf689f3ef80b6652@mail.gmail.com>
     [not found]   ` <192730.65612.qm@web112412.mail.gq1.yahoo.com>
2009-12-07 10:07     ` Tom Deconinck [this message]
2009-12-07 15:26       ` [ECOS] Intel 82541 chipset (Pro/1000 GT Desktop adapter) Jim Bradleigh
2009-12-07 18:23         ` Jim Bradleigh

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=e37cb5250912070207r66feb1b1pfed6beca51fee7ab@mail.gmail.com \
    --to=t.deconinck@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=slei02@yahoo.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).