public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Daniel.Andersson@combitechsystems.com
To: jlarmour@redhat.com
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] App works in RAM but not in flash memory
Date: Thu, 16 Aug 2001 09:42:00 -0000	[thread overview]
Message-ID: <2253171AF143D21185A60000F8FA748B02DA4E5C@pluto.combitech.se> (raw)

> Daniel.Andersson@combitechsystems.com wrote:
> > 
> > Hi,
> > 
> > I have some problem with my messages (cyg_mbox_*) in eCos 
> and hope that some
> > of you maybe can give me a hint of what maight be wrong. 
> Currently I am
> > running the entire application in RAM and it works fine. 
> However, when i
> > download the program it into flash then it starts acting 
> very strange. With
> > a trace enabled i can see that some (not all...) messages 
> that are sent
> > between threads dont have any valid data in their header. 
> Every message
> > contains of a header and the data that it contains is just 
> garbage. The
> > first thing i check was that if some process sends an 
> unfilled message but
> > that was not the case.
> > 
> > What can be wrong when an application works fine in RAM but 
> not in flash? I
> > have tried to set the clock to half the speed to give the 
> flash more time to
> > fetch data but the error was still present.
> > 
> > I am using a custom build AT91EB40 with external flash.
> 
> Seems odd certainly. I can't imagine a situation where it 
> would mostly but
> not completely work, in that way. If you had a support 
> contract I could
> look more closely by trying it myself, but otherwise I don't 
> have the time,
> sorry.
> 
> Which situation are you talking about: is it built for "ROM" 
> startup type
> and is running direct from Flash? Or is it built for RAM 
> startup, and being
> loaded into RAM from flash using "fis load"?
> 
> Jifl

I think i have located a few things that causes this error. I have had the
option "include gdb stub in HAL" marked and this is not a good combination
since they interfere with the rest of the code. When i disabled the above
options then I got less strange mbox messages. However, i still get a few
and i think that if i disable all the debug options (and GDB support) in
eCos then my app will run much better. However, I can't get all the debug
info to disaper. I have removed all the debug-flags in the makefiles, both
when building eCos and when building my application. I still get some "debug
info" and "debug lines" in my map-file on address 0x00. How can i remove all
such information?

Regards, Daniel

             reply	other threads:[~2001-08-16  9:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-16  9:42 Daniel.Andersson [this message]
2001-08-16 10:30 ` Jonathan Larmour
  -- strict thread matches above, loose matches on Subject: below --
2001-08-17  2:56 Fano Ramparany
2001-08-17 11:29 ` Jonathan Larmour
2001-08-20  5:39   ` Fano Ramparany
2001-08-21  3:14     ` Prasad Kamath Nala
2001-08-21  7:02       ` Jonathan Larmour
2001-08-20  7:30   ` Fano Ramparany
2001-08-16  6:47 Daniel.Andersson
2001-08-16  7:25 ` Jonathan Larmour

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=2253171AF143D21185A60000F8FA748B02DA4E5C@pluto.combitech.se \
    --to=daniel.andersson@combitechsystems.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jlarmour@redhat.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).