[ECOS] limit on the number of diag_printf(s) ????

Rycerz Roman-G11565 roman.rycerz@motorola.com
Wed Apr 14 16:52:00 GMT 2004


I have looked a little closer and found the reason it wouldn't load was it failed to connect, even though
Insight said it did.  If I disconnect and reconnect it is successful and will download the application.  
I will let you all know what I find


-----Original Message-----
From: nickg@miso.calivar.com [mailto:nickg@miso.calivar.com] On Behalf Of Nick Garnett
Sent: Tuesday, April 13, 2004 9:27 AM
To: Rycerz Roman-G11565
Cc: Ecos-Discuss@Sources. Com (ecos-discuss@sources.redhat.com)
Subject: Re: [ECOS] limit on the number of diag_printf(s) ????

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

More information about the Ecos-discuss mailing list