This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: limit on the number of diag_printf(s) ????
- From: Nick Garnett <nickg at ecoscentric dot com>
- To: Rycerz Roman-G11565 <roman dot rycerz at motorola dot com>
- Cc: "Ecos-Discuss at Sources dot Com (ecos-discuss at sources dot redhat dot com)" <ecos-discuss at sources dot redhat dot com>
- Date: 13 Apr 2004 15:27:25 +0100
- Subject: Re: [ECOS] limit on the number of diag_printf(s) ????
- References: <5D454811D0A1D711A12A00065BF36FAD03E40BC0@il06exm11>
Rycerz Roman-G11565 <roman.rycerz@motorola.com> writes:
> The diag_printf(s) are in Redboot, in the single stepping code...
> There are no printf's of any kind in the application
>
> The failure occurs when insight tries to download into the target ram. It just returns immediately
> And no code is loaded. I do not try any printf's during the download
Check where the code is being loaded against the size of RedBoot. It
may be that an extra diag_printf() pushes the BSS of RedBoot up into
the RAM where the application is being loaded.
--
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