public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Batra Rajat-r7aadp <Rajat.Batra@motorola.com>
Cc: "'ecos-maintainers@sources.redhat.com'"
	<ecos-maintainers@sources.redhat.com>
Subject: Re: ecos on OMAP710 using CCS
Date: Tue, 21 Oct 2003 20:25:00 -0000	[thread overview]
Message-ID: <3F95962D.9060508@eCosCentric.com> (raw)
In-Reply-To: <6728517EECE7D511981B00D0B782903103845B18@az33exm27.corp.mot.com>

Batra Rajat-r7aadp wrote:
> Hi,
> 
> I am trying to load redboot into RAM on my OMAP710 based board. I have
> succesfully created a redboot.elf using ecos2.0 and the innovator for
> arm9 config file. When I try to load redboot onto the board using CCS
> version 2.2 using File/load program and selecting my redboot.elf file,
> I get an error stating that the application has terminated because of
> possible stack overflow, or writing into the wrong place.  In fact CCS
> shuts down. Am I even close to following the right steps?  If so, what
> might be the problem?

This isn't really the right forum. You'll get a better chance of good 
responses to future queries in the ecos-discuss list.

As for your problem, it looks like CCS is having a problem with the image, 
rather than the image being necessarily invalid. See if CCS can load 
another format like SREC or just raw binary to the correct address.

If you're not sure if your binary has been built for the correct address 
for the memory map of your board, you could verify by using 
"arm-elf-objdump -h redboot.elf".

One possible thing certainly is to verify you have built RedBoot for RAM 
startup type.

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

      reply	other threads:[~2003-10-21 20:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21 20:13 Batra Rajat-r7aadp
2003-10-21 20:25 ` Jonathan Larmour [this message]

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=3F95962D.9060508@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=Rajat.Batra@motorola.com \
    --cc=ecos-maintainers@sources.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).