public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: Richard Slaughter <rslaughter@anatel.com>,
	eCos discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] ecos atmel eb40 demo board
Date: Tue, 07 Aug 2001 07:16:00 -0000	[thread overview]
Message-ID: <3B6FF834.4E6C1CC3@redhat.com> (raw)
In-Reply-To: <002301c11f48$a03a82a0$740aa8c0@richards>

Richard Slaughter wrote:
> 
> Jonathan,
> Yes, I'm following the instructions.
> I have been able to install redboot_rom.elf on the eb40 board.
> The file redboot_ramrom.srec per the instructions does not exist.
> I assumed it was redboot_romram.srec.  I could not get this file to
> download but redboot_rom.srec, transfered to flash and will run.

RAMROM is a typo - it should have been ROMRAM.

So the RedBoot ROM works absolutely fine, but RedBoot ROMRAM can't even
load.
 
> If I try to replace it I have this problem with the board resetting
> and displaying the Angel logon before finishing the download.

If you are _already_ running the RedBoot ROM image, you should first load
the redboot RAM image into it and run that before downloading the ROMRAM
image. This is because RedBoot executes in place, which means that when you
write a new version in flash, it overwrites the currently executing
program. I wouldn't be at all surprised if weird stuff happens then.

> It almost acts like a  watch dog timer is running and restting the board.
> I'm using the snapshot insight+dejagnu-20010419 version of gdb and I'm
> just using binary images posted to redhat for the eb40.
> what are the distictions between:
> redboot_ram.elf

Loads into and runs from RAM.

> redboot_romram.elf

Loads into ROM, relocates itself to RAM when it starts, and runs from RAM.

> redboot rom.elf

Loads and runs from ROM.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

  parent reply	other threads:[~2001-08-07  7:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-06 12:05 Richard Slaughter
2001-08-06 16:27 ` Jonathan Larmour
     [not found]   ` <002301c11f48$a03a82a0$740aa8c0@richards>
2001-08-07  7:16     ` Jonathan Larmour [this message]
2001-08-07  9:43       ` [ECOS] variant rm7000 interrupt masking Chris Morrow
2001-08-07 18:36         ` Chris Morrow
2001-08-08 11:29           ` Jonathan Larmour
2001-08-09  0:53             ` Jesper Skov

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=3B6FF834.4E6C1CC3@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=rslaughter@anatel.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).