RE: [ECOS] Adding redboot commands or parameters results in ROM image that won't run (but RAM image that will).

["Shmuel Vagner" <Shmuel dot Vagner at celeno dot com>]

Problem solved.
All I had to do was to enlarge the size of the ROM section in target.ld.
(I think that it has to be done anyway if you compile your code with the
Intel NPE driver)
Shmuel



-----Original Message-----
From: Dave Rensberger [mailto:dave@thingmagic.com] 
Sent: Tuesday, March 14, 2006 6:21 PM
To: Shmuel Vagner
Cc: eCos Discussion
Subject: Re: [ECOS] Adding redboot commands or parameters results in ROM
image that won't run (but RAM image that will).

No, I haven't.   For now, I'm using a workaround to my original  
problem that doesn't involve modifying redboot at all (I work at a  
small company, and we simply can't afford to spend days messing  
around with a problem like this if there's a workaround).   If anyone  
has any ideas, I'd still be interested in trying them though.   There  
clearly seems to be some hard coded limit somewhere that conflicts  
with the way that the macro is allocating its memory in the data  
segment, but it's not clear to me where that is.   Maybe someone  
who's more familiar with the pre-processor and the RedBoot macros  
might understand the problem better.

--Dave

Dave Rensberger - Project Engineer
ThingMagic, Inc., One Broadway, Cambridge, MA 02142
Tel: 617-682-3784
Cell: 617-834-6425


On Mar 14, 2006, at 7:08 AM, Shmuel Vagner wrote:

>
> Dave (and List),
> I have a similar problem.
> Did you find a solution?
> Thanks
> Shmuel
>
> -----Original Message-----
> From: ecos-discuss-owner@ecos.sourceware.org
> [mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Dave
> Rensberger
> Sent: Friday, March 10, 2006 10:53 PM
> To: Gary Thomas
> Cc: eCos Discussion
> Subject: Re: [ECOS] Adding redboot commands or parameters results  
> in ROM
> image that won't run (but RAM image that will).
>
> Gary,
>
> Thanks for the suggestion.  I keep thinking that it must be something
> more basic than that. I've attached a copy of my code.   I think it's
> about as simple as it could possibly be... As far as I can tell,
> there isn't anything fundamentally different between the macro call
> that adds my new command "pibinit" and any of the macro calls that
> add the standard commands.
>
> --Dave


 
 
************************************************************************
************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals &
computer viruses.
************************************************************************
************


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss