This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Problem with go command
- From: Nick Garnett <nickg at ecoscentric dot com>
- To: "Prabhat Shrivastav" <shrivastavp at myw dot ltindia dot com>
- Cc: <andrew at lunn dot ch>, <ecos-discuss at ecos dot sourceware dot org>
- Date: 29 Sep 2004 10:46:14 +0100
- Subject: Re: [ECOS] Problem with go command
- References: <s15acc89.091@EMAIL>
"Prabhat Shrivastav" <shrivastavp@myw.ltindia.com> writes:
> Hi Andrew
>
> Thanx for reply.
> I have gone through the FAQ's but not found any clue.
> Is there any thing wrong with this .
>
> RedBoot> load -r -b 0x8c020000 -m xmodem
> Redboot>go
> I got garbage on the serial console.
>
> I checked RAM location, got the right data. And if I load the redboot_RAM and execute from ram............ it run's happily.
> And if I run the same application through GDB console, it runs fine.
> Pl suggest me solve this problem
These sorts of problem have been covered in this list many times
before. The list archive would contain all of these.
What you see on the serial console is a GDB protocol message. If you
connect via GDB in the usual way, it will tell you what the problem
is.
Is 0x8c020000 the correct base address for the program you are
loading? When you run it under GDB, where does it get loaded? You may
be better off trying to load an S-record version of the program rather
than the bare binary.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com/ The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss