[ECOS] dividing the elf object file file in to two binary files

[ECOS] dividing the elf object file file in to two binary files

[ganesh kr]

Hi,

I am using ecos with lwip. I have two flash memory chips of 128 KB
each at addr 0x04000000 and 0x08000000. the binary file is 140KB. I
want to have two binary files from the elf object file so that i can
load one binary file in to each flash. Also I have two libraries
libapp.a and libtarget.a. please let me know how can i do this.

-- 
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] dividing the elf object file file in to two binary files

[Martin Laabs]

Hi,

ganesh kr wrote:
> Hi,
> 
> I am using ecos with lwip. I have two flash memory chips of 128 KB
> each at addr 0x04000000 and 0x08000000. the binary file is 140KB. I
> want to have two binary files from the elf object file so that i can
> load one binary file in to each flash. Also I have two libraries
> libapp.a and libtarget.a. please let me know how can i do this.

You have to change the linker script to get two sections for .text.
However - you have to give every section an unique name.  To assign
functions/files to each section you can use the linker script as well
as the __attribute__ ((section ("<section name>"))) attribute before
any function or variable.

At the end you get one elf file with different section that can be
separated by objcopy/objdump.

Here a short example from an old project:

#define INSRAM_DATA __attribute__ ((section (".sram_data")))
#define INSRAM_TEXT __attribute__ ((section (".sram_text")))

cyg_uint32 rawData[20][64] INSRAM_DATA; //[Channel][TimeSlot]

void INSRAM_TEXT
reader(cyg_addrword_t data)
{
...
}

Greetings,
  Martin Laabs

PS: If you call function in one segment out of the other
segment you have to use far jumps like that:

void (*diag_printf_p)( const char *fmt, ... ) =  &diag_printf;

and then call
diag_printf_p("calculating: %d %d %d\n", i, j, tap); instead of 
diag_printf(....)


-- 
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] dividing the elf object file file in to two binary files

[ganesh kr]

Thanks for the response Martin. Since I am new to ecos and GNU tools,
can any one please provide the reference linker script file to do the
same

On Tue, Jul 21, 2009 at 6:16 PM, Martin Laabs<info@martinlaabs.de> wrote:
> Hi,
>
> ganesh kr wrote:
>>
>> Hi,
>>
>> I am using ecos with lwip. I have two flash memory chips of 128 KB
>> each at addr 0x04000000 and 0x08000000. the binary file is 140KB. I
>> want to have two binary files from the elf object file so that i can
>> load one binary file in to each flash. Also I have two libraries
>> libapp.a and libtarget.a. please let me know how can i do this.
>
> You have to change the linker script to get two sections for .text.
> However - you have to give every section an unique name.  To assign
> functions/files to each section you can use the linker script as well
> as the __attribute__ ((section ("<section name>"))) attribute before
> any function or variable.
>
> At the end you get one elf file with different section that can be
> separated by objcopy/objdump.
>
> Here a short example from an old project:
>
> #define INSRAM_DATA __attribute__ ((section (".sram_data")))
> #define INSRAM_TEXT __attribute__ ((section (".sram_text")))
>
> cyg_uint32 rawData[20][64] INSRAM_DATA; //[Channel][TimeSlot]
>
> void INSRAM_TEXT
> reader(cyg_addrword_t data)
> {
> ...
> }
>
> Greetings,
>  Martin Laabs
>
> PS: If you call function in one segment out of the other
> segment you have to use far jumps like that:
>
> void (*diag_printf_p)( const char *fmt, ... ) =  &diag_printf;
>
> and then call
> diag_printf_p("calculating: %d %d %d\n", i, j, tap); instead of
> diag_printf(....)
>
>

--
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] dividing the elf object file file in to two binary files

[ganesh kr]

Hi,

I am new to ecos. I have  258 KB flash on my board. I am able to build
and run my small appliaction with ecos + lwip as nw stack. the code
size is 69KB.
I want to switch to freebsd/ openbsd based nw stack so that I can use
SNMP and DNS. Please any one let me know the aproximate code siaze if
I use freebsd based nw stack.

regards,
Ganesh K R

-- 
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] dividing the elf object file file in to two binary files

[Simon Kallweit]

ganesh kr wrote:
> Hi,
> 
> I am new to ecos. I have  258 KB flash on my board. I am able to build
> and run my small appliaction with ecos + lwip as nw stack. the code
> size is 69KB.
> I want to switch to freebsd/ openbsd based nw stack so that I can use
> SNMP and DNS. Please any one let me know the aproximate code siaze if
> I use freebsd based nw stack.

I don't have much experience with the other stacks (using lwip myself) 
but you need plenty of RAM to use them, which could be a problem on your 
platform. lwip does have support for DNS and SNMP, the APIs just differ. 
You could check out my current lwip port, which is a lot more up to date 
than the one in the eCos repository:

http://download.westlicht.ch/lwip-20090722.tar.gz

Simon

-- 
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] dividing the elf object file file in to two binary files

[Simon Kallweit]

ganesh kr wrote:
> Hi Simon,
> 
> Thanks a lot for the response. You have kept my project going. Please
> tell me how can I integrate your lwip port with my present ecos code
> base. I have both ecos3.0 and ecos 2.0 code base. By seeing your  port
> it looks like you have used ecos2.0. its OK for me to go with ecos
> 2.0. Only thing is how can I integrate with the code base I have.
> Also, once integrate, can I build it using the config tool as part of
> libtarget.a?

This port is built for ecos 3.0, or better said, for CVS head. I'm not 
sure if it would run for ecos 2.0 too.

The easiest way to integrate this with your code base is to just remove 
the old packages/net/lwip_tcpip folder and replace it with the new 
lwip_tcpip folder. The package also needs to be registered in the 
packages/ecos.db file, but nothing has changed here from the old lwip 
port to the new one, so don't have to change that.

Once this is integrated you can just add lwip to your project as with 
the earlier port.

ecosconfig add lwip

Or you can use the configtool to add the package. Configuration has 
changed considerably from the earlier port, but it's much better 
organized now and should be relatively easy to do.

For a few examples of how to use the port see the examples!

There are two supported modes for running lwip. I called them 
"sequential" and "simple" modes. In the simple mode you run lwip in a 
single thread, making it very resource friendly. But you need to use the 
RAW APIs in this mode. In the sequential mode, lwip is run in multiple 
threads and you can use all the advanced APIs like netconn and sockets.

Best regards
Simon

-- 
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] dividing the elf object file file in to two binary files

[Simon Kallweit]

ganesh kr wrote:
> Hi Simon,
> 
> I have integrated the lwip port provided by you with my ecos 3.0 code
> base and is working fine. However I am not able to use SNMP. Whe I
> give a snmp-get command, my device sends response, but SNMP manager
> does not get the response. when I saw the response packet sent by my
> device in an analyzer ( wireshark), it says  "malformed packet : SNMP
> "  and the in the UDP packet havig SNMP response, the it says "Length
> : 52 (bogus, payload length 8).
> 
> Have you observed any such behavior when you used SNMP? Please let me know

First of all, nice to hear that you got my port running. Unfortunately I 
don't use SNMP myself, so I can't really help here. I think you should 
post your problem to the lwip mailing list. Do you use the port in the 
simple (single-threaded polled) or in the sequential (multi-threaded) 
mode? I don't know, but I assume SNMP should work in both modes, but it 
might be you have to take extra care when in multi-threaded mode.

Simon

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

[ECOS] Re: dividing the elf object file file in to two binary files

[ganesh kr]

Hi,

I am using ecos 3.0.  I am not able to use malloc(). when I call
malloc very first time in my application, it returns null. I called
mallinfo() just before calling malloc. The values of different members
of the returned structure is as bellow:


struct mallinfo {
    int arena = 00000000
    int ordblks = 00000000
    int smblks;   = 00000000
    int hblks;    = 82630000
    int hblkhd;   = 01356353
    int usmblks;  = C0043602
    int fsmblks;  = 330150A8
    int uordblks; = 51010004
    int fordblks; = 00043A80
    int keepcost; = 3BC0A800
    int maxfree; = 27010004
};

all these numbers seems to be not correct.

My linker directive file is as bellow:

STARTUP(./lib/vectors.o)
ENTRY(reset_vector)
INPUT(./lib/extras.o)

GROUP(./lib/libtarget.a libgcc.a libsupc++.a)
MEMORY {

    app_flash0_rsvd1 : ORIGIN = 0x0, LENGTH = 0x200
    app_flash0_memory : ORIGIN = 0x200, LENGTH = 127K-0x200
    app_flash0_rsvd2 : ORIGIN = 0x1fa00, LENGTH = 0x200

    app_flash1_rsvd1 : ORIGIN = 0x08000000, LENGTH = 0
    app_flash1_memory : ORIGIN = 0x08000000, LENGTH = 128K


    sram_rsvd1 : ORIGIN = 0x04000000, LENGTH = 0
    sram_memory : ORIGIN = 0x04000000, LENGTH = 192K

}


SECTIONS
{
    .debug_aranges 0 : { *(.debug_aranges) } .debug_pubnames 0 : {
*(.debug_pubnames) } .debug_info 0 : { *(.debug_info) } .debug_abbrev
0 : { *(.debug_abbrev) } .debug_line 0 : { *(.debug_line) }
.debug_frame 0 : { *(.debug_frame) } .debug_str 0 : { *(.debug_str) }
.debug_loc 0 : { *(.debug_loc) } .debug_macinfo 0 : {
*(.debug_macinfo) } .note.arm.ident 0 : { KEEP (*(.note.arm.ident)) }
    .rom_vectors 0x0000000 : { __rom_vectors_vma = ABSOLUTE(.); . = .;
KEEP (*(.vectors)) } > app_flash0_rsvd1 __rom_vectors_lma =
LOADADDR(.rom_vectors);

    .text ALIGN (0x4) : { _stext = ABSOLUTE(.); PROVIDE (__stext =
ABSOLUTE(.)); *(.text*) *(.gnu.warning) *(.gnu.linkonce.t.*) *(.init)
*(.glue_7) *(.glue_7t) } > app_flash0_memory _etext = .; PROVIDE
(__etext = .);
    .fini ALIGN (0x4) : { . = .; *(.fini) } > app_flash0_memory
    .rodata ALIGN (0x4) : { . = .; *(.rodata*) *(.gnu.linkonce.r.*) }
> app_flash0_memory
    .rodata1 ALIGN (0x4) : { . = .; *(.rodata1) } > app_flash0_memory
    .fixup ALIGN (0x4) : { . = .; *(.fixup) } > app_flash0_memory
    .gcc_except_table ALIGN (0x4) : { . = .; *(.gcc_except_table) } >
app_flash0_memory

    .fixed_vectors 0x04000000 : { . = .; KEEP (*(.fixed_vectors)) } >
sram_memory
    .data ALIGN (0x4) : AT ((LOADADDR (.gcc_except_table) + SIZEOF
(.gcc_except_table) + 4 - 1) & ~ (4 - 1)) { __ram_data_start =
ABSOLUTE (.); *(.data*) *(.data1) *(.gnu.linkonce.d.*) . = ALIGN (4);
KEEP(*( SORT (.ecos.table.*))) ; . = ALIGN (4); __CTOR_LIST__ =
ABSOLUTE (.); KEEP (*(SORT (.ctors*))) __CTOR_END__ = ABSOLUTE (.);
__DTOR_LIST__ = ABSOLUTE (.); KEEP (*(SORT (.dtors*))) __DTOR_END__ =
ABSOLUTE (.); *(.dynamic) *(.sdata*) *(.gnu.linkonce.s.*) . = ALIGN
(4); *(.2ram.*) } > sram_memory __rom_data_start = LOADADDR (.data);
__ram_data_end = .; PROVIDE (__ram_data_end = .); _edata = .; PROVIDE
(edata = .); PROVIDE (__rom_data_end = LOADADDR (.data) +
SIZEOF(.data));
    .bss ALIGN (0x4) : { __bss_start = ABSOLUTE(.); *(.scommon)
*(.dynsbss) *(.sbss*) *(.gnu.linkonce.sb.*) *(.dynbss) *(.bss*)
*(.gnu.linkonce.b.*) *(COMMON) __bss_end = ABSOLUTE (.); } >
sram_memory
    __heap1 = ALIGN (0x8);
    . = ALIGN(4); _end = .; PROVIDE (end = .);
}


Please any one tell me whats the problem.
1. Is dynamic memory allocation dependent on linker directive and
memory layout?
2. What are the steps to be done to use malloc()? Like what are the
options need to choose in ecos config tool to use malloc()?

Please let me know if any more information is needed.

Regards,
Ganesh K R

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