public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gatien Gillon <ggillon@ulb.ac.be>
To: Gary Thomas <gary@mlbassoc.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: re:Re: re:Re: re:Re: [ECOS] eCos Romable ? (on AT91EB55)
Date: Fri, 06 May 2005 15:00:00 -0000	[thread overview]
Message-ID: <200505061500.RAA04712@web1.ulb.ac.be> (raw)

Still get an error :
RedBoot> lo -b 0x02006948 -m xm
C*** Abort! Attempt to load ELF data to address: 0x03006948 which is not in RAM
xyzModem - CRC mode, 1025(SOH)/0(STX)/0(CAN) packets, 4 retries


>On Fri, 2005-05-06 at 16:35 +0200, Gatien Gillon wrote:
>> I used the command arm-elf-objcopy -S
>> I get a 135 kb file 
>> when I send it I get this error :
>> *** Abort! Attempt to load ELF data to address: 0x0301c000 which is not in RAM
>> xyzModem - CRC mode, 1(SOH)/128(STX)/0(CAN) packets, 3 retries
>> 
>> I'm can feel I'm nearly there, thanks
>
>Use the -b option to tell RedBoot where to load the code into RAM.
>When you boot, RedBoot will tell you a sensible address to use.
>
>  RedBoot> lo -b 0x????? -m xm
>
>> 
>> >On Fri, 2005-05-06 at 16:08 +0200, Gatien Gillon wrote:
>> >> I don't have a JTAG
>> >> 
>> >> When I compile I get a big image 835 kb wich is too big to 
>> >> send. what command emust I type to get a smaller image so I 
>> >> can send it to redboot : with load ymodem and then write it 
>> >> with fi wr to the ROM ?
>> >
>> >Your image isn't really that big (at least according to the GDB
>> >load info you just sent, it's less than 90KB)  The rest is ELF
>> >overhead (mostly debug info)
>> >
>> >Use arm-elf-objcopy (look at the CDL for some examples) to strip
>> >this down to the raw binary.  That's what you want to download and
>> >then write to FLASH.
>> >
>> >> 
>> >> Does anybody know the adresse of the EB55 board ?
>> >> 
>> >> (I'm really lost I'm quite a newby)
>> >> 
>> >> >
>> >> >Here is the way I do it.
>> >> >
>> >> >If you are not retaining Redboot, rebuild eCos lib with ROM startup.
>> >> >Compile / link your program to the ROM eCos lib.  Strip your executible of debugging
>> >> >/ symbols (arm-elf-objcopy).  Use a JTAG flash loader to program your
>> >> >application to 0x10000000 (start of ROM).  Done.  Resetting the board
>> >> >should run the program.
>> >> >
>> >> >If you want to retain Redboot, modify the .ldi file in HAL to a ROM
>> >> >address just above the Redboot sectors.  Rebuild eCos with ROM
>> >> >startup. Compile / link your program to the ROM eCos lib.  Strip your executible of debugging
>> >> >/ symbols.  Use a JTAG flash loader to program your
>> >> >application to the start sectors just past Redboot sectors.
>> >> >Use the Redboot 'fconfig' script command to have Redboot to 'go' to the
>> >> >start of the application.
>> >> >
>> >> >If you don't have a JTAG / loader, use redboot 'load' to temperarly put
>> >> >the executable into some unused RAM space.  Then use 'fis write' to put the
>> >> >program into the ROM start location.
>> >> >
>> >> >
>> >> >-S
>> >> >
>> >> >On Fri, 6 May 2005, Gatien Gillon wrote:
>> >> >
>> >> >> The plateforme is AT91EB55
>> >> >> I have my application I've debugged it using redboot sending it with GDB now I'd like to put it a the FLASH memory so that when I reset my board my app starts immediatly without having to send it using GDB
>> >> >>
>> >> >> >On Fri, 2005-05-06 at 14:22 +0200, Gatien Gillon wrote:
>> >> >> >> How can I put eCos in a way it starts automatically on
>> >> >> >> a reboot without having to send an image using GDB ?
>> >> >> >
>> >> >> >This is [normally] a supported way of configuring eCos programs.
>> >> >> >
>> >> >> >  CYG_HAL_STARTUP = ROM
>> >> >> >
>> >> >> >What platform/target?
>> >> >> >
>> >> >> >--
>> >> >> >------------------------------------------------------------
>> >> >> >Gary Thomas                 |  Consulting for the
>> >> >> >MLB Associates              |    Embedded world
>> >> >> >------------------------------------------------------------
>> >> >> >
>> >> >> >
>> >> >> >--
>> >> >> >Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>> >> >> >and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>> >> >> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>> >> >>
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> 
>> >> 
>> >> 
>> >-- 
>> >Gary Thomas <gary@chez-thomas.org>
>> >
>> >
>> >-- 
>> >Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>> >and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>> >
>> >
>> 
>> 
>
>-- 
>------------------------------------------------------------
>Gary Thomas                 |  Consulting for the
>MLB Associates              |    Embedded world
>------------------------------------------------------------
>
>



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

             reply	other threads:[~2005-05-06 15:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06 15:00 Gatien Gillon [this message]
2005-05-06 15:21 ` Sean Christensen
2005-05-06 15:46   ` Gary Thomas

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=200505061500.RAA04712@web1.ulb.ac.be \
    --to=ggillon@ulb.ac.be \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=gary@mlbassoc.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).