public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Roman Jordan" <RomanJordan@gmx.de>
To: Jay Bennie <jay@lincore.co.uk>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Loading the rom on an AT91EB40A
Date: Tue, 21 Oct 2003 14:39:00 -0000	[thread overview]
Message-ID: <30569.1066747140@www31.gmx.net> (raw)
In-Reply-To: <1066743305.13667.35.camel@blade>

Hi,
yes, you have to give the localtion of the file you want to download.
The command
load -m ymodem -b %{FREEMEMLO}
brings RedBoot in download mode. The download has to be started using
minicom (key CTRL-a s). Select ymodem and select the file. You can watch the
progress.
After the download is complete, you can burn the image into flash.

Greetings, Roman Jordan

> Hi, 
> 
> after days of digging, I'm starting to get the hang of eCos and embedded
> development in general.
> 
> Anyway to describe the setup. 
> 
> I have a standard AT91EB40A(Ver 1.0 Rev 0) Eval board from Atmel. 
> Flash is a AT49BV1614A
> 
> so far - after many wrong turns i have the following 
> 
> ecos-2.0 installed to /opt/ecos as installed by the scripts 
> cvs is current (21st October 2003) and located in /opt/ecos/cvs/ecos
> 
> i have modified /opt/ecos/ecosenv.sh to point to the cvs Package
> repository
> 
> Then in my home directory i have ecos/ram and ecos/rom  
> 
> to build the file redboot.elf  (Ram version)
> 
> i run the following commands: 
> $ cd ram
> $ ecosconfig new eb40a redboot
> $ ecosconfig import
>
/opt/ecos/cvs/ecos/ecos/packages/hal/arm/at91/eb40a/current/misc/redboot_RAM.ecm
> $ ecosconfig tree
> $ make 
> 
> to build the ROM files
> 
> $ cd ../rom
> $ ecosconfig new eb40a redboot
> $ ecosconfig import
>
/opt/ecos/cvs/ecos/ecos/packages/hal/arm/at91/eb40a/current/misc/redboot_ROM.ecm
> $ ecosconfig tree
> $ make 
> 
> then return to ram/install/bin 
> and type 
> $ arm-elf-gdb redboot.elf
> 
> <now in GDB type> 
> tar rdi s=/dev/ttyS0
> set $cpsr=0xd3
> load
> <the file loads>
> cont
> <escape with ^Z>
> 
> < now open minicom >
> $ minicom
> <the following is the output from this command. >
> // ================================ Start of paste ===============
> 
> RedBoot> AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
> ** Error: Illegal command: "AT"
> RedBoot> version
>                                                                           
>                                 
> RedBoot(tm) bootstrap and debug environment [RAM]
> Non-certified release, version UNKNOWN - built 13:41:16, Oct 21 2003
>                                                                           
>                                 
> Platform: Atmel AT91/EB40A (ARM7TDMI)
> Copyright (C) 2000, 2001, 2002, Red Hat, Inc.
>                                                                           
>                                 
> RAM: 0x00000000-0x00040000, [0x0001ff88-0x0003f000] available
> FLASH: 0x01000000 - 0x01200000, 32 blocks of 0x00010000 bytes each.
> RedBoot> load -m ymodem -b %{FREEMEMLO}
> CCCCCCCCC...........Can't load '<null>': Timed out
> RedBoot>
> 
> 
> // ================================ End of paste ===============
> 
> I have to say i don't follow what this is doing, i assumed that i would
> need to specify the loactaion of the rom file
> /home/jbennie/ecos/rom/install/bin/redboot.srec but from the help for
> the AT91 this does not appear to be the case. I now assume that the ram
> image is dumped from memory into the flash using the next command 
> 
> e.g. RedBoot> fi wr -f 0x01100000 -b %{FREEMEMLO} -l 0x010000 
> 
> - I also noted that there are differences between my memory map and that
> published in the help 
> 
> http://sources.redhat.com/ecos/docs-latest/ref/at91.html
> 
> Anyway, given that I'm new to all of this any help would be appreciated
> and if anyone has any specific advice on the eb40a I'd appreciate a
> quick email as i need to compile as much of this information into an
> eCos for the eb40a FAQ/mini-HOWTO, it will help the other people i'm
> working with get up to speed and hopefully be of some use to the
> community as well.
> 
> Regards
> Jay 
> 
> ---------------------------------------
> lincore information systems limited
> mob:07976 300036
> eml:jay@lincore.com | jay@lincore.co.uk
> ---------------------------------------
> 
> 
> 
> 
> 
> 
> 
> -- 
> Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> 

-- 
NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien...
Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService

Jetzt kostenlos anmelden unter http://www.gmx.net

+++ GMX - die erste Adresse für Mail, Message, More! +++


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

  parent reply	other threads:[~2003-10-21 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21 13:35 Jay Bennie
2003-10-21 13:58 ` Artur Lipowski
2003-10-21 14:39 ` Roman Jordan [this message]
     [not found] ` <20031021160727.A17571@frqwol30ux.frequentis.frq>
2003-10-21 14:47   ` Jay Bennie

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=30569.1066747140@www31.gmx.net \
    --to=romanjordan@gmx.de \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jay@lincore.co.uk \
    /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).