From: abhishek srivastava <just_abhi22@yahoo.co.in>
To: ecos-discuss@sourceware.org
Subject: [ECOS] transfer .srec file onto redboot in ARM
Date: Wed, 24 Dec 2008 11:50:00 -0000 [thread overview]
Message-ID: <725000.26707.qm@web94615.mail.in2.yahoo.com> (raw)
sir,
as i did for i386PC, i tried the same for arm-eabi as well
but couldnt get the desired result.
i had successfully generated .srec file........not sure,
that whether .srec file used to be transferred to redboot in
target in case of arm or hex??
when i tried to transfer .srec file to arm board it gave
folllowing error.....plz ckeck and tell what wrong i did
this is the message i got on my hyperterminal at host!!
RedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version UNKNOWN - built 11:24:46,
Dec 24 2008
Platform: Hobby-Robotics LPC2XXX/IH1_PROC_LPC_1
(ARM7TDMI-S)
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
Copyright (C) 2003, 2004, 2005, 2006 eCosCentric Limited
RAM: 0x40000000-0x40010000, [0x40005940-0x40004000]
available
RedBoot> load -v -m yMODEM
CCC*** Abort! Attempt to load S-record to address:
0x00000000, which is not vali
d
xyzModem - CRC mode, 1(SOH)/1(STX)/0(CAN) packets, 5
retries
RedBoot>
i would also like to know, is there any procedure to use ARM ROM space (512k) to write GUI for graphical LCD? actually my graphial LCD RAM is only of 32K, and i need to have few simple GUI on LCD.
any suggestions please!!
thank you
Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2008-12-24 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 11:50 abhishek srivastava [this message]
2008-12-25 13:25 ` 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=725000.26707.qm@web94615.mail.in2.yahoo.com \
--to=just_abhi22@yahoo.co.in \
--cc=ecos-discuss@sourceware.org \
/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).