[ECOS] Help !!

[ECOS] Help !!

[Annamalai Prakash K. (Tata Elxsi )]

 Hi,

            I am using ARM Integrator Board /AP (arm920t) with 128MB RAM. It
would be very greatful, if anyone provide some suggestion for my doubts...

	1. Is there any way to fi want to know, How much RAM space consumed by my
ecos + application ?..

I have choosen very basic io functionalities like serial port and flash
support.(removed networking packages) ... my application is thread program.
(twothread.c - thread example program comes along with ecos).  I would like
to test this application in an enviroment where i have only 256KB of RAM .

         2.  is it possible to simulate the above sincerio in my existing
environment ?.. what are the changes, should i do ?.. Could any provide my
suggestion ....

           Apart from this, i need redboot also required to boot the Board
...  i thought to make executable to run from Flash ..


        Looking for more Inputs  regarding this ....

Thanks
Prakash





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

Re: [ECOS] Help !!

[John Carter]

On Thu, 16 Jun 2005, Annamalai Prakash  K. (Tata Elxsi ) wrote:

> 	1. Is there any way to fi want to know, How much RAM space consumed by my
> ecos + application ?..

arm-elf-size, although arm-elf-objdump --syms gives you more details where 
it went.

> I have choosen very basic io functionalities like serial port and flash
> support.(removed networking packages) ... my application is thread program.
> (twothread.c - thread example program comes along with ecos).  I would like
> to test this application in an enviroment where i have only 256KB of RAM .

Mostly dosn't matter as the linker gc drops things you don't use.

>
>         2.  is it possible to simulate the above sincerio in my existing
> environment ?.. what are the changes, should i do ?.. Could any provide my
> suggestion ....

Yes, fiddle the memory map (.mlt) file, if the lib/target.ld is right, the 
linker will whinge if you exceed the ram requirements.



John Carter                             Phone : (64)(3) 358 6639
Tait Electronics                        Fax   : (64)(3) 359 4632
PO Box 1645 Christchurch                Email : john.carter@tait.co.nz
New Zealand

Carter's Clarification of Murphy's Law.

"Things only ever go right so that they may go more spectacularly wrong later."

From this principle, all of life and physics may be deduced.

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

Re: [ECOS] Help!

[Jonathan Larmour]

windy wrote:
> 
> We have ported ecos to our arm7 system.It seems work well,But division fail always confuses us.
> 
> the function which list below is my thread entry,I will create and execute it in cyg_user_start
> 
> void our_app1(int argc,char* argv[])
> {
>         float numerator,denominator;
>         numerator = 4000;
>         denominator = 100;
>         numerator /= denominator;   ==>every time step over here,gdb will report "bus error",Why?
> }
> Who can tell me why the gdb alway report bus error,and what should I do?

Where exactly does it fail? If you are using an arm7di (i.e. with no fast
multiplier) are you compiling with -mcpu=arm7di?
 
> the function _simple_mkdate in wallclock.inl maybe miss a parentheses,doesn't it?

Good catch.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

Re: [ECOS] Help!

[windy]

> > We have ported ecos to our arm7 system.It seems work well,But division fail always confuses us.
> > 
> > the function which list below is my thread entry,I will create and execute it in cyg_user_start
> > 
> > void our_app1(int argc,char* argv[])
> > {
> >         float numerator,denominator;
> >         numerator = 4000;
> >         denominator = 100;
> >         numerator /= denominator;   ==>every time step over here,gdb will report "bus error",Why?
> > }
> > Who can tell me why the gdb alway report bus error,and what should I do?
> 
> Where exactly does it fail? If you are using an arm7di (i.e. with no fast
> multiplier) are you compiling with -mcpu=arm7di?
>  
> Jifl
> -- 
Today I have traced into __divsf3 . The bus error is reported when executing the instruction like "LDR R2, [R1,#2]".
When 'LDR' is used to load data which is not word align ,it will always cause bus error.
It seems arm7 on Samsung S3C44 box couldn't execute this type instruction correctly, although the manual book says
support. So strange!

Windy

Re: [ECOS] Help!

[Jonathan Larmour]

windy wrote:
> 
> > > We have ported ecos to our arm7 system.It seems work well,But division fail always confuses us.
> > >
[snip]
> Today I have traced into __divsf3 . The bus error is reported when executing the instruction like "LDR R2, [R1,#2]".
> When 'LDR' is used to load data which is not word align ,it will always cause bus error.
> It seems arm7 on Samsung S3C44 box couldn't execute this type instruction correctly, although the manual book says
> support. So strange!

See the thread "Access unaligned address" which I just replied to. This
looks like the same issue.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

RE: [ECOS] Help!

[Nielsen Linus]

Well, I don't know the first thing about ARM7, but how about floating point
support? Is it in hardware or is it emulated in software? If you have
compiled
the code for an ARM with hardware floating point support, and then run it on
a system without hardware floating point, you might get a problem like this.
Maybe the floating point emulation library needs some initialisation or the
like?

/Linus

> We have ported ecos to our arm7 system.It seems work well,But 
> division fail always confuses us.
>  
> the function which list below is my thread entry,I will 
> create and execute it in cyg_user_start
> 
> void our_app1(int argc,char* argv[])
> {
> 	float numerator,denominator;
> 	numerator = 4000;
> 	denominator = 100;
> 	numerator /= denominator;   ==>every time step over 
> here,gdb will report "bus error",Why?
> }
> Who can tell me why the gdb alway report bus error,and what 
> should I do?
> 
> 
> 
> the function _simple_mkdate in wallclock.inl maybe miss a 
> parentheses,doesn't it?
> 
> static void
> _simple_mkdate(time_t time,
>                cyg_uint32* year, cyg_uint32* mon,
>                cyg_uint32* day, cyg_uint32* hour,
>                cyg_uint32* min, cyg_uint32* sec)
> {
>     cyg_int32 days, hms, y, m, *dpm;
> 
>     days = (cyg_int32) (time / (24*60*60));
>     hms  = (cyg_int32) (time % (24*60*60));
> 
>     // Nothing fancy about the time - no leap year magic involved
>     *sec = hms % 60;
>     *min = (hms % (60*60)) / 60;
>     *hour = hms / 60*60;   ==============> *hour = hms/(60*60);
> 
> 	.....
> }
> 
> 
> Best regards
>  Windy
> 

[ECOS] Help!

[windy]

We have ported ecos to our arm7 system.It seems work well,But division fail always confuses us.
 
the function which list below is my thread entry,I will create and execute it in cyg_user_start

void our_app1(int argc,char* argv[])
{
	float numerator,denominator;
	numerator = 4000;
	denominator = 100;
	numerator /= denominator;   ==>every time step over here,gdb will report "bus error",Why?
}
Who can tell me why the gdb alway report bus error,and what should I do?



the function _simple_mkdate in wallclock.inl maybe miss a parentheses,doesn't it?

static void
_simple_mkdate(time_t time,
               cyg_uint32* year, cyg_uint32* mon,
               cyg_uint32* day, cyg_uint32* hour,
               cyg_uint32* min, cyg_uint32* sec)
{
    cyg_int32 days, hms, y, m, *dpm;

    days = (cyg_int32) (time / (24*60*60));
    hms  = (cyg_int32) (time % (24*60*60));

    // Nothing fancy about the time - no leap year magic involved
    *sec = hms % 60;
    *min = (hms % (60*60)) / 60;
    *hour = hms / 60*60;   ==============> *hour = hms/(60*60);

	.....
}


Best regards
 Windy