This is the mail archive of the
ecos-devel@sources.redhat.com
mailing list for the eCos project.
Re: running apps on redboot with cirrus ep7312
- From: Jonathan Larmour <jifl at eCosCentric dot com>
- To: Aaron Case <aaron dot case at dynazign dot com>
- Cc: ecos-devel at sources dot redhat dot com, robert dot mullis at dynazign dot com
- Date: Wed, 02 Jul 2003 05:28:53 +0100
- Subject: Re: running apps on redboot with cirrus ep7312
- References: <GBEOKKOEOGFDMKDFCHIMKEAHCAAA.aaron.case@dynazign.com>
[ Sorry if this was already resolved, I didn't see an answer here and I
know it's been a while ]
Aaron Case wrote:
Hello,
I am trying to load an application onto Redboot, no eCos build, just Redboot
rom monitor. I load the application as described in the documentation and it
appears successful.
I type go at the Redboot prompt and I get a bunch of garbage.
Let me guess: $T00(something)
Just exactly how are you building your application? Do you mean one based
on the newlib C library and with an appropriately configured toolchain?
It's probable then that you have to build the application to know it will
be using RedBoot. This support hasn't been added universally, but if it
exists, it's normally included by adding --specs=redboot.specs on your
link line. It should probably work for the 7312.
Of course you could just use eCos ;-).
So my question is how do I know where the application is and where the
jumping off point is in memory after downloading the application.
RedBoot should report it when you've downloaded it.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine