[ECOS] What is RedBoot_INIT_TAB,

[ECOS] What is RedBoot_INIT_TAB,

[Narayana, Venkat A.]

Hi,
I am trying to make a ROM startup for my XScale based board
and i am getting an error, while single-stepping this code, which is in
main.c/cyg_start fucn:

for (init_entry = __RedBoot_INIT_TAB__; init_entry !=
&__RedBoot_INIT_TAB_END__;  init_entry++) {
        (*init_entry->fun)();
    }

I found that RedBoot_INIT_TAB is defined, in CYG_HAL_TABLE_BEGIN macro,
but by the time i reach the above point, i.e cyg_start function, i haven't
seen anything
which is poulating this Table. So the question is, if no one is putting some
data(actual a 
function pointer), the why is it that we are calling init_entry->fun,
function?
Is there something i didn't understood or missed?
Could i choose to call this guy, only when the board is ' warm_reset'?

Your help is greatly appreciated.

Thanks in Advance,
Venkat N.

RE: [ECOS] What is RedBoot_INIT_TAB,

[Gary Thomas]

On 31-May-2001 Narayana, Venkat A. wrote:
> Hi,
> I am trying to make a ROM startup for my XScale based board
> and i am getting an error, while single-stepping this code, which is in
> main.c/cyg_start fucn:
> 
> for (init_entry = __RedBoot_INIT_TAB__; init_entry !=
> &__RedBoot_INIT_TAB_END__;  init_entry++) {
>         (*init_entry->fun)();
>     }
> 
> I found that RedBoot_INIT_TAB is defined, in CYG_HAL_TABLE_BEGIN macro,
> but by the time i reach the above point, i.e cyg_start function, i haven't
> seen anything
> which is poulating this Table. So the question is, if no one is putting some
> data(actual a 
> function pointer), the why is it that we are calling init_entry->fun,
> function?

This table is filled in using the RedBoot_init() macro.  E.g. this is used
by the network initialization code in the file "redboot/current/src/net/net_io.c"

Depending on your configuration, you may or not have any entries in the table.

I'd suggest that you put some prints around the call and see what it's calling
and whether or not it gets back.  For example:

        printf("Calling %p/%p\n", init_entry, init_entry->fun);
        (*init_entry->fun)();
        printf("Back\n");

The extra value printed (init_entry) is to see whether or not things are properly
aligned.  This particular table has only 4 byte entries, but I've seen the compiler
do funny things like try and align table elements on 16 byte boundaries, etc.

> Is there something i didn't understood or missed?
> Could i choose to call this guy, only when the board is ' warm_reset'?

No, it needs to be there always.

Please run the test I've outlined. Let us know what happens.

Re: [ECOS] What is RedBoot_INIT_TAB,

[Jonathan Larmour]

"Narayana, Venkat A." wrote:
> 
> Hi,
> I am trying to make a ROM startup for my XScale based board
> and i am getting an error, while single-stepping this code, which is in
> main.c/cyg_start fucn:
> 
> for (init_entry = __RedBoot_INIT_TAB__; init_entry !=
> &__RedBoot_INIT_TAB_END__;  init_entry++) {
>         (*init_entry->fun)();
>     }
> 
> I found that RedBoot_INIT_TAB is defined, in CYG_HAL_TABLE_BEGIN macro,
> but by the time i reach the above point, i.e cyg_start function, i haven't
> seen anything
> which is poulating this Table. So the question is, if no one is putting some
> data(actual a
> function pointer), the why is it that we are calling init_entry->fun,
> function?
> Is there something i didn't understood or missed?
> Could i choose to call this guy, only when the board is ' warm_reset'?

Look for the RedBoot_init macro. You'll find instances in redboot and
probably some drivers.

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
<advert> Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/

[ECOS] Executable Size

[Carlos Camargo]

Hi all.

I have a question:

I have arm evaluator 7t, i build ecos:

ecosconfig new e7t
ecosconfig tree
make

The Makefile is:

PKG_INSTALL_DIR = /root/ecos-work/install
XCC = arm-elf-gcc -mcpu=arm7di                        
ifeq ($(XCC),sh-elf-gcc)
#CFLAGS        = -ggdb
else
#CFLAGS        = -g
CFLAGS		= -static
endif

CXXFLAGS      = $(CFLAGS)

EXTRACFLAGS   = -Wall -I$(PKG_INSTALL_DIR)/include
-ffunction-sections -fdata-sections

EXTRACXXFLAGS = $(EXTRACFLAGS) -fno-exceptions
-fno-rtti -fvtable-gc -finit-priority

LDFLAGS       = -nostartfiles -L$(PKG_INSTALL_DIR)/lib
-Wl,--gc-sections
LIBS          = -Ttarget.ld -nostdlib

LD            = $(XCC)
XCXX          = $(XCC)



When i compile the hello world example the executable
size is 1.1M, is this posible??? How i Can erase
drivers for ecos in linux???

Thanks

Carlos Camargo


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

Re: [ECOS] Executable Size

[Jonathan Larmour]

> 
> When i compile the hello world example the executable
> size is 1.1M, is this posible??? 

The executable size may be 1.1M, but that's because of debug information.
Use arm-elf-size on the executable to get the true size.

But you're correct that more unnecessary stuff could be stripped out by
judicious configuration of eCos using the Configuration Tool. But that's up
to you. At least, the situation is not what you think anyway.

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
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/

Re: [ECOS] Executable Size

[Carlos Camargo]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]

Hi..
Jonathan thanks for your answer..

When i compile the twothreads example:

arm-elf-gcc -mcpu=arm7di -c -o twothreads.o -g -Wall
-I/root/ecos-work/install/include -ffunction-sections
-fdata-sections twothreads.c
arm-elf-gcc -mcpu=arm7di -nostartfiles
-L/root/ecos-work/install/lib -Wl,--gc-sections -o
twothreads twothreads.o -Ttarget.ld -nostdlib  


and i execute arm-elf-size twothreads:

   text	   data	    bss	    dec	    hex	filename
  45880	   1956	  23544	  71380	  116d4	twothreads

When i Buils whitout "-g" option 


arm-elf-gcc -mcpu=arm7di -c -o twothreads.o -static
-Wall -I/root/ecos-work/install/include
-ffunction-sections -fdata-sections twothreads.c
arm-elf-gcc -mcpu=arm7di -nostartfiles
-L/root/ecos-work/install/lib -Wl,--gc-sections -o
twothreads twothreads.o -Ttarget.ld -nostdlib 


   text	   data	    bss	    dec	    hex	filename
  45880	   1956	  23544	  71380	  116d4	twothreads

But, i don`t understand this information, when i use
man size don´t provide information about this format

Thanks Carlos Camargo



__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

Re: [ECOS] Executable Size

[Jonathan Larmour]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]

Carlos Camargo wrote:
> 
>    text    data     bss     dec     hex filename
>   45880    1956   23544   71380   116d4 twothreads
> 
> But, i don`t understand this information, when i use
> man size don´t provide information about this format

Try "info size" which is a little bit better.

But basically, text==code, and data+bss==your program data. This totals
71380 bytes in this case (rather large for such a simple case, but easily
reduced by tailoring your eCos configuration if you choose).

For a program programmed into ROM/Flash, you would find the total ROM usage
to be text+data, and the total RAM usage to be data+bss.

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
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/

RE: [ECOS] Executable Size

[Dan Conti]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]

> -----Original Message-----
> From: Carlos Camargo [ mailto:carlos_ivan_camargo@yahoo.com ]

[snip]

> arm-elf-gcc -mcpu=arm7di -c -o twothreads.o -static
> -Wall -I/root/ecos-work/install/include
> -ffunction-sections -fdata-sections twothreads.c
> arm-elf-gcc -mcpu=arm7di -nostartfiles
> -L/root/ecos-work/install/lib -Wl,--gc-sections -o
> twothreads twothreads.o -Ttarget.ld -nostdlib 
> 
> 
>    text	   data	    bss	    dec	    hex	filename
>   45880	   1956	  23544	  71380	  116d4	twothreads
> 
> But, i don`t understand this information, when i use
> man size don´t provide information about this format

It's giving you the size in bytes of each of the sections (sort of).
text is the size of the code, so 45k code. data is, i believe, both the
.data section and the .rodata section (which are preinitialized data,
the latter being const). bss is zero initialized data. the next value,
dec, is the total size in decimal, and the following one, hex, is the
total size in hex.

It's quite easy to get very small images with eCos. I've packed a lot
into a 160k image. :)

-Dan


> 
> Thanks Carlos Camargo
> 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Get personalized email addresses from Yahoo! Mail - only $35 
> a year!  http://personal.mail.yahoo.com/
>