[ECOS] error: no memory region specified for loadable '.ram_vectors'

[ECOS] error: no memory region specified for loadable '.ram_vectors'

[Agus Ariffianto]

Dear ALL,
I am trying to build hello program to run in LEON. During dong that, I faced
some problem (and peculiarity)
eCos configuration setting:

Menu Build repository                : /src/ecos
Menu Build tempaltes                : LEON Processor
        Packages                        :default
Menu Tools-Paths-Build Tools    : /gnutools/sparc-elf-3.2.3/bin
Menu Tools-Paths-user tools       : /bin
The rest, I leave it by default

-Configuration
    - Global Build options
        - Global command prefix    : sparc-rtems <why sparc-rtems, NOT sparc-elf
?, in fact I use sparc-elf-3.2.3>

Then I build library....
Then I got target.ld file (in folder leon_install/lib/)

Next, I compile it:
[agus]$ sparc-elf-gcc -I leon_install/include/ ../hello.c -o hello.out -L
leon_install/lib/ -Ttarget.ld -nostdlib

then the error turn up:
/gnutools/sparc-elf-3.4.4/bin/../lib/gcc/sparc-elf/3.4.4/../../../../sparc-elf/bin/ld:
error: no memory region for loadable section '.ram_vectors'
collect2: ld returned 1 exit status

second trial, I change Global command prefix setting: sparc-elf (was
sparc-rtems) and change the compiler version to sparc-elf-3.2.3 (was 3.4.4). The
error was same.

Can anybody please help me solving these problem. Thank you very much.

In addition, I use ecos-2 but set the repository to ecos (not ecos-2, different
folder). I did that under fedore core 5.

Best regards,
Agus Ariffianto



-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

----- End forwarded message -----




-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

-- 
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] error: no memory region specified for loadable '.ram_vectors'

[Andrew Lunn]

On Mon, May 29, 2006 at 04:59:20PM +0700, Agus Ariffianto wrote:
> Dear ALL,
> I am trying to build hello program to run in LEON. During dong that, I faced
> some problem (and peculiarity)
> eCos configuration setting:
> 
> Menu Build repository                : /src/ecos
> Menu Build tempaltes                : LEON Processor
>         Packages                        :default
> Menu Tools-Paths-Build Tools    : /gnutools/sparc-elf-3.2.3/bin
> Menu Tools-Paths-user tools       : /bin
> The rest, I leave it by default
> 
> -Configuration
>     - Global Build options
>         - Global command prefix    : sparc-rtems <why sparc-rtems, NOT sparc-elf
> ?, in fact I use sparc-elf-3.2.3>
> 
> Then I build library....
> Then I got target.ld file (in folder leon_install/lib/)
> 
> Next, I compile it:
> [agus]$ sparc-elf-gcc -I leon_install/include/ ../hello.c -o hello.out -L
> leon_install/lib/ -Ttarget.ld -nostdlib
> 
> then the error turn up:
> /gnutools/sparc-elf-3.4.4/bin/../lib/gcc/sparc-elf/3.4.4/../../../../sparc-elf/bin/ld:
> error: no memory region for loadable section '.ram_vectors'
> collect2: ld returned 1 exit status
> 
> second trial, I change Global command prefix setting: sparc-elf (was
> sparc-rtems) and change the compiler version to sparc-elf-3.2.3 (was 3.4.4). The
> error was same.
> 
> Can anybody please help me solving these problem. Thank you very much.

How do you configure eCos? 

do 

ecosconfig export loan.ecm

and email the leon.ecm file.

My guess is you have the interface to Redboot enabled, but the current
leon port does not support this.

     Andrew

-- 
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] error: no memory region specified for loadable '.ram_vectors'

[Agus Ariffianto]

[-- Attachment #1: Type: text/plain, Size: 1811 bytes --]



> On Mon, May 29, 2006 at 04:59:20PM +0700, Agus Ariffianto wrote:
>> Dear ALL,
>> I am trying to build hello program to run in LEON. During dong that, I 
>> faced
>> some problem (and peculiarity)
>> eCos configuration setting:
>>
>> Menu Build repository                : /src/ecos
>> Menu Build tempaltes                : LEON Processor
>>         Packages                        :default
>> Menu Tools-Paths-Build Tools    : /gnutools/sparc-elf-3.2.3/bin
>> Menu Tools-Paths-user tools       : /bin
>> The rest, I leave it by default
>>
>> -Configuration
>>     - Global Build options
>>         - Global command prefix    : sparc-rtems <why sparc-rtems, NOT 
>> sparc-elf
>> ?, in fact I use sparc-elf-3.2.3>
>>
>> Then I build library....
>> Then I got target.ld file (in folder leon_install/lib/)
>>
>> Next, I compile it:
>> [agus]$ sparc-elf-gcc -I leon_install/include/ ../hello.c -o hello.out -L
>> leon_install/lib/ -Ttarget.ld -nostdlib
>>
>> then the error turn up:
>> /gnutools/sparc-elf-3.4.4/bin/../lib/gcc/sparc-elf/3.4.4/../../../../sparc-elf/bin/ld:
>> error: no memory region for loadable section '.ram_vectors'
>> collect2: ld returned 1 exit status
>>
>> second trial, I change Global command prefix setting: sparc-elf (was
>> sparc-rtems) and change the compiler version to sparc-elf-3.2.3 (was 
>> 3.4.4). The
>> error was same.
>>
>> Can anybody please help me solving these problem. Thank you very much.
>
> How do you configure eCos?
>
> do
>
> ecosconfig export loan.ecm
>
> and email the leon.ecm file.
>
> My guess is you have the interface to Redboot enabled, but the current
> leon port does not support this.
>
>     Andrew
>
> -- 

Andrew, thank you for your response. Also attached target.ld file (I don't 
know wether you need this file or not)

Regards,
Agus Ariffianto 

[-- Attachment #2: leon.ecm --]
[-- Type: application/octet-stream, Size: 4418 bytes --]

cdl_savefile_version 1;
cdl_savefile_command cdl_savefile_version {};
cdl_savefile_command cdl_savefile_command {};
cdl_savefile_command cdl_configuration { description hardware template package };
cdl_savefile_command cdl_package { value_source user_value wizard_value inferred_value };
cdl_savefile_command cdl_component { value_source user_value wizard_value inferred_value };
cdl_savefile_command cdl_option { value_source user_value wizard_value inferred_value };
cdl_savefile_command cdl_interface { value_source user_value wizard_value inferred_value };

cdl_configuration eCos {
    description "" ;
    hardware    sparc_leon ;
    template    default ;
    package -template CYGPKG_HAL current ;
    package -template CYGPKG_IO current ;
    package -template CYGPKG_IO_SERIAL current ;
    package -template CYGPKG_INFRA current ;
    package -template CYGPKG_KERNEL current ;
    package -template CYGPKG_MEMALLOC current ;
    package -template CYGPKG_ISOINFRA current ;
    package -template CYGPKG_LIBC current ;
    package -template CYGPKG_LIBC_I18N current ;
    package -template CYGPKG_LIBC_SETJMP current ;
    package -template CYGPKG_LIBC_SIGNALS current ;
    package -template CYGPKG_LIBC_STARTUP current ;
    package -template CYGPKG_LIBC_STDIO current ;
    package -template CYGPKG_LIBC_STDLIB current ;
    package -template CYGPKG_LIBC_STRING current ;
    package -template CYGPKG_LIBC_TIME current ;
    package -template CYGPKG_LIBM current ;
    package -template CYGPKG_IO_WALLCLOCK current ;
    package -template CYGPKG_ERROR current ;
    package -hardware CYGPKG_HAL_SPARC current ;
    package -hardware CYGPKG_HAL_SPARC_LEON current ;
};

cdl_option CYGBLD_GLOBAL_COMMAND_PREFIX {
    user_value sparc-elf
};

cdl_component CYG_HAL_STARTUP {
    user_value RAM
};

cdl_option CYGBLD_ISO_CTYPE_HEADER {
    inferred_value 1 <cyg/libc/i18n/ctype.inl>
};

cdl_option CYGBLD_ISO_ERRNO_CODES_HEADER {
    inferred_value 1 <cyg/error/codes.h>
};

cdl_option CYGBLD_ISO_ERRNO_HEADER {
    inferred_value 1 <cyg/error/errno.h>
};

cdl_option CYGBLD_ISO_STDIO_FILETYPES_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDIO_STREAMS_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDIO_FILEOPS_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDIO_FILEACCESS_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDIO_FORMATTED_IO_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDIO_CHAR_IO_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDIO_DIRECT_IO_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDIO_FILEPOS_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDIO_ERROR_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDLIB_STRCONV_HEADER {
    inferred_value 1 <cyg/libc/stdlib/atox.inl>
};

cdl_option CYGBLD_ISO_STDLIB_ABS_HEADER {
    inferred_value 1 <cyg/libc/stdlib/abs.inl>
};

cdl_option CYGBLD_ISO_STDLIB_DIV_HEADER {
    inferred_value 1 <cyg/libc/stdlib/div.inl>
};

cdl_option CYGBLD_ISO_STRERROR_HEADER {
    inferred_value 1 <cyg/error/strerror.h>
};

cdl_option CYGBLD_ISO_STRTOK_R_HEADER {
    inferred_value 1 <cyg/libc/string/string.h>
};

cdl_option CYGBLD_ISO_STRING_LOCALE_FUNCS_HEADER {
    inferred_value 1 <cyg/libc/string/string.h>
};

cdl_option CYGBLD_ISO_STRING_BSD_FUNCS_HEADER {
    inferred_value 1 <cyg/libc/string/bsdstring.h>
};

cdl_option CYGBLD_ISO_STRING_MEMFUNCS_HEADER {
    inferred_value 1 <cyg/libc/string/string.h>
};

cdl_option CYGBLD_ISO_STRING_STRFUNCS_HEADER {
    inferred_value 1 <cyg/libc/string/string.h>
};

cdl_option CYGBLD_ISO_C_TIME_TYPES_HEADER {
    inferred_value 1 <cyg/libc/time/time.h>
};

cdl_option CYGBLD_ISO_C_CLOCK_FUNCS_HEADER {
    inferred_value 1 <cyg/libc/time/time.h>
};

cdl_option CYGBLD_ISO_SIGNAL_NUMBERS_HEADER {
    inferred_value 1 <cyg/libc/signals/signal.h>
};

cdl_option CYGBLD_ISO_SIGNAL_IMPL_HEADER {
    inferred_value 1 <cyg/libc/signals/signal.h>
};

cdl_option CYGBLD_ISO_SETJMP_HEADER {
    inferred_value 1 <cyg/libc/setjmp/setjmp.h>
};



[-- Attachment #3: target.ld --]
[-- Type: application/octet-stream, Size: 2302 bytes --]

STARTUP(vectors.o)
ENTRY(reset_vector)

INPUT(extras.o)


GROUP(libtarget.a libgcc.a libsupc++.a)
MEMORY
{
    ram : ORIGIN = 0x40000000, LENGTH = 0x80000
}

SECTIONS
{
   
    .rom_vectors 0x40000000 : { . = .; KEEP (*(.vectors)) } > ram
    .text ALIGN (0x1) : { _stext = ABSOLUTE(.); *(.text*) *(.gnu.warning) *(.gnu.linkonce*) *(.init) } > ram _etext = .; PROVIDE (etext = .);
    .fini ALIGN (0x1) : { . = .; *(.fini) } > ram
    .rodata ALIGN (0x1) : { . = .; *(.rodata*) } > ram
    .rodata1 ALIGN (0x1) : { . = .; *(.rodata1) } > ram
    .fixup ALIGN (0x1) : { . = .; *(.fixup) } > ram
    .gcc_except_table ALIGN (0x1) : { . = .; *(.gcc_except_table) } > ram
    .data ALIGN (0x1) : { __ram_data_start = ABSOLUTE (.); *(.data*) *(.data1) _GOT1_START_ = ABSOLUTE (.); *(.got1) _GOT1_END_ = ABSOLUTE (.); _GOT2_START_ = ABSOLUTE (.); *(.got2) _GOT2_END_ = ABSOLUTE (.); . = ALIGN (4); KEEP(*( SORT (.ecos.table.*))) ; __CTOR_LIST__ = ABSOLUTE (.); KEEP(*(SORT(.ctors*))) __CTOR_END__ = ABSOLUTE (.); __DTOR_LIST__ = ABSOLUTE (.); KEEP(*(SORT(.dtors*))) __DTOR_END__ = ABSOLUTE (.); _GOT_START = ABSOLUTE (.); _GLOBAL_OFFSET_TABLE_ = ABSOLUTE (.) + 32768; _SDA_BASE_ = ABSOLUTE (.); *(.got.plt) *(.got) _GOT_END_ = ABSOLUTE (.); *(.dynamic) *(.sdata*) *(.sbss*) *(.eh_frame) } > ram __rom_data_start = LOADADDR (.data); . = ALIGN (8); __ram_data_end = .; PROVIDE (__ram_data_end = .); _edata = .; PROVIDE (edata = .);
    .bss ALIGN (0x8) : { __bss_start = ABSOLUTE (.); *(.scommon) *(.dynbss) *(.bss) *(COMMON) __bss_end = ABSOLUTE (.); } > ram
    __heap1 = ALIGN (0x8);
    . = ALIGN(8); _end = .; PROVIDE (end = .); .debug 0 : { *(.debug) } .line 0 : { *(.line) } .debug_srcinfo 0 : { *(.debug_srcinfo) } .debug_sfnames 0 : { *(.debug_sfnames) } .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) } .debug_weaknames 0 : { *(.debug_weaknames) } .debug_funcnames 0 : { *(.debug_funcnames) } .debug_typenames 0 : { *(.debug_typenames) } .debug_varnames 0 : { *(.debug_varnames) }
}


[-- Attachment #4: Type: text/plain, Size: 148 bytes --]

-- 
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] error: no memory region specified for loadable '.ram_vectors'

[Andrew Lunn]

> >My guess is you have the interface to Redboot enabled, but the current
> >leon port does not support this.

Try turning off:

CYGPKG_HAL_ROM_MONITOR 
CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT

        Andrew

-- 
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] error: no memory region specified for loadable '.ram_vectors'

[Agus Ariffianto]

>> >My guess is you have the interface to Redboot enabled, but the current
>> >leon port does not support this.
>
> Try turning off:
>
> CYGPKG_HAL_ROM_MONITOR
> CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT
>
>        Andrew
>
I couldn't find where the CYGPKG_HAL_ROM_MONITOR and 
CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT were located. I have search in target.ld 
and leon.ecm files, but I couldn't find it. Did I miss something? Thank you

Regards,
Agus Ariffianto 



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

AW: [ECOS] error: no memory region specified for loadable '.ram_vectors'

[Ram Sudhir Tadavarthi]

You can find them in your .ecc file. You can even open the project in the
ecos-config tool and search for the MACROS CYGPKG_HAL_ROM_MONITOR and 
CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT to locate them by using "find" option in
"edit" menu.

If you cant disable them in the project because of conflicts you can modify
the corresponding cdl file to disable them.

Hope this helps.

-----Ursprüngliche Nachricht-----
Von: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] Im Auftrag von Agus
Ariffianto
Gesendet: Dienstag, 30. Mai 2006 06:04
An: Andrew Lunn
Cc: ecos-discuss@ecos.sourceware.org
Betreff: Re: [ECOS] error: no memory region specified for loadable
'.ram_vectors'


Dear Andrew, 
the option CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT couldn't be disable. Thank you

regards,
Agus Ariffianto

-----Ursprüngliche Nachricht-----
Von: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] Im Auftrag von Agus
Ariffianto
Gesendet: Dienstag, 30. Mai 2006 05:20
An: Andrew Lunn
Cc: ecos-discuss@ecos.sourceware.org
Betreff: Re: [ECOS] error: no memory region specified for loadable
'.ram_vectors'


I couldn't find where the CYGPKG_HAL_ROM_MONITOR and 
CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT were located. I have search in target.ld 
and leon.ecm files, but I couldn't find it. Did I miss something? Thank you

Regards,
Agus Ariffianto 


--
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] error: no memory region specified for loadable '.ram_vectors'

[Andrew Lunn]

On Tue, May 30, 2006 at 09:26:54AM +0200, Ram Sudhir Tadavarthi wrote:
> You can find them in your .ecc file. You can even open the project in the
> ecos-config tool and search for the MACROS CYGPKG_HAL_ROM_MONITOR and 
> CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT to locate them by using "find" option in
> "edit" menu.
> 
> If you cant disable them in the project because of conflicts you can modify
> the corresponding cdl file to disable them.

No, you should never have to edit a .cdl file when configuring eCos. 

The only reason to edit a .cdl file is to fix bugs in the .cdl file.

    Andrew

-- 
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] error: no memory region specified for loadable '.ram_vectors'

[Agus Ariffianto]

Dear Andrew, Ram, Mahmud, and ALL,

Instead of using sparc-elf-gcc (which is produce error message), now I'm 
using sparc-rtems-gcc. sparc-rtems-gcc produce warning ONLY and output file 
created (I don't know wether this 'output file' was the right one).

[agus]$ which sparc-rtems-gcc
    /gnutools/rtems-4.6/bin/sparc-rtems-gcc

[agus]$ sparc-rtems-gcc -I leon_install/include/ ../hello.c -o hello.out -L 
leon_install/lib/ -Ttarget.ld -nostdlib
 GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.

GDB is free software, covered by the GNU General Public License, and you are

welcome to change it and/or distribute copies of it under certain 
conditions.

Type "show copying" to see the conditions.

There is absolutely no warranty for GDB. Type "show warranty" for details.

This GDB was configured as 
"--host=i686-pc-linux-gnu --target=sparc-tsim-elf"..."/home/agus/work/project-eCos/LEON/sparc-elf-3.2.3/hello.exe": 
not in executable format: File format not recognized


The hello.out was created then I enter the following command:
[agus]$ sparc-rtems-objcopy -O binary hello.out hello.bin

Then the hello.bin was successfully created.

Next, I use tsim (evaluation version).
In terminal 1:
[agus@localhost ~]$ tsim-leon3 -gdb

This TSIM evaluation version will expire February 1, 2007



TSIM/LEON3 SPARC simulator, version 2.0.4 (evaluation version)

Copyright (C) 2001, Gaisler Research - all rights reserved.

This software may only be used with a valid license.

For latest updates, go to http://www.gaisler.com/

Comments or bug-reports to tsim@gaisler.com

serial port A on stdin/stdout

allocated 4096 K RAM memory, in 1 bank(s)

allocated 2048 K ROM memory

icache: 1 * 4 kbytes, 16 bytes/line (4 kbytes total)

dcache: 1 * 4 kbytes, 16 bytes/line (4 kbytes total)

gdb interface: using port 1234



In terminal 2:
[agus@localhost sparc-elf-3.2.3]$ sparc-rtems-gdb hello.bin

GNU gdb 5.3

Copyright 2002 Free Software Foundation, Inc.

GDB is free software, covered by the GNU General Public License, and you are

welcome to change it and/or distribute copies of it under certain 
conditions.

Type "show copying" to see the conditions.

There is absolutely no warranty for GDB. Type "show warranty" for details.

This GDB was configured as 
"--host=i686-pc-linux-gnu --target=sparc-tsim-elf"..."/home/agus/work/project-eCos/LEON/sparc-elf-3.2.3/hello.bin": 
not in executable format: File format not recognized

(gdb) tar extended-remote localhost:1234

Remote debugging using localhost:1234

0x00000000 in ?? ()

(gdb) load

No executable file specified.

Use the "file" or "exec-file" command.

(gdb) run

The program being debugged has been started already.

Start it from the beginning? (y or n)



My questions are:

1. Why message: "...hello.bin": not in executable format: File format not 
recognized." turn up?

2. How to create 'the executable file'? I was successfully created ecos 
bootable disk (run in PC, showing hello ecos). I enter command (in cygwin 
environment):

    [cygwin-agus]$ dd conv=sync if=hello.bin of=/dev/fd0

    What should I do to produce the same executable (or bootable <?>) file?

    Thank you very much



Best regards,

Agus



-- 
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] error: no memory region specified for loadable '.ram_vectors'

[Andrew Lunn]

> My questions are:
> 
> 1. Why message: "...hello.bin": not in executable format: File format not 
> recognized." turn up?


gdb wants the elf file, not the binary you produced.

> 2. How to create 'the executable file'? I was successfully created ecos 
> bootable disk (run in PC, showing hello ecos). I enter command (in cygwin 
> environment):
> 
>    [cygwin-agus]$ dd conv=sync if=hello.bin of=/dev/fd0
> 
>    What should I do to produce the same executable (or bootable <?>) file?

How do you intend to get the image onto the system? Does it have a
floppy and a BIOS to boot it? Are you going to burn it into an EEPROM?
Do you have a JTAG interface to load the program into RAM?

   Andrew

-- 
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] error: no memory region specified for loadable '.ram_vectors'

[Agus Ariffianto]

>> My questions are:
>>
>> 1. Why message: "...hello.bin": not in executable format: File format not
>> recognized." turn up?
>
>
> gdb wants the elf file, not the binary you produced.
>

Ok, finally I use the hello.out, which is the elf file (I guess so...)
I successfully load it using gdb (and tsim eval version, I haven't use the 
real target). Eventhoght it can be loaded, but tsim refuse to run it. Here 
is the message:
[agus@localhost sparc-elf-3.2.3]$ sparc-rtems-gdb hello.out

GNU gdb 5.3

Copyright 2002 Free Software Foundation, Inc.

GDB is free software, covered by the GNU General Public License, and you are

welcome to change it and/or distribute copies of it under certain 
conditions.

Type "show copying" to see the conditions.

There is absolutely no warranty for GDB. Type "show warranty" for details.

This GDB was configured as 
"--host=i686-pc-linux-gnu --target=sparc-tsim-elf"...

(gdb) tar extended-remote localhost:1234

Remote debugging using localhost:1234

0x00000000 in ?? ()

(gdb) load

Loading section .rom_vectors, size 0x1300 lma 0x40000000

Loading section .text, size 0xf9fc lma 0x40001300

Loading section .rodata, size 0x324 lma 0x40010cfc

Loading section .data, size 0x490 lma 0x40011020

Start address 0x40001300, load size 70832

Transfer rate: 566656 bits in <1 sec, 276 bytes/write.

(gdb) run

The program being debugged has been started already.

Start it from the beginning? (y or n) y

Starting program: 
/home/agus/work/project-eCos/LEON/sparc-elf-3.2.3/hello.out

Program received signal SIGILL, Illegal instruction.

0x00000008 in ?? ()

(gdb)


1. Why this tsim said: "Program received signal SIGILL, Illegal instruction"

>> 2. How to create 'the executable file'? I was successfully created ecos
>> bootable disk (run in PC, showing hello ecos). I enter command (in cygwin
>> environment):
>>
>>    [cygwin-agus]$ dd conv=sync if=hello.bin of=/dev/fd0
>>
>>    What should I do to produce the same executable (or bootable <?>) 
>> file?
>
> How do you intend to get the image onto the system? Does it have a
> floppy and a BIOS to boot it? Are you going to burn it into an EEPROM?
> Do you have a JTAG interface to load the program into RAM?
>

If I successfully run this 'hello.out' file, the next step I plan to load 
ogg-vorbis decoder into Altera Stratix FPGA board. I don't know yet where I 
will put the image (?) into this board (wether into SRAM or EEPROM or 
something else). This ogg-vorbis decoder will run under eCos (and LEON 
implemented on this board).

Thank you, Andrew

Regards,
Agus Ariffianto 



-- 
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] error: no memory region specified for loadable '.ram_vectors'

[Andrew Lunn]

> Loading section .rom_vectors, size 0x1300 lma 0x40000000
> 
> Loading section .text, size 0xf9fc lma 0x40001300
> 
> Loading section .rodata, size 0x324 lma 0x40010cfc
> 
> Loading section .data, size 0x490 lma 0x40011020
> 
> Start address 0x40001300, load size 70832
> 
> Transfer rate: 566656 bits in <1 sec, 276 bytes/write.
> 
> (gdb) run
> 
> The program being debugged has been started already.
> 
> Start it from the beginning? (y or n) y
> 
> Starting program: 
> /home/agus/work/project-eCos/LEON/sparc-elf-3.2.3/hello.out
> 
> Program received signal SIGILL, Illegal instruction.
> 
> 0x00000008 in ?? ()

You loaded the program into memory at 0x40000000

I expect run starts from 0x0. Hence it is executing rubbish, not your
program.

try

set $pc=0x40000000
c

        Andrew

-- 
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] error: no memory region specified for loadable '.ram_vectors'

[Agus Ariffianto]

>> My questions are:
>>
>> 1. Why message: "...hello.bin": not in executable format: File format not
>> recognized." turn up?
>
>
> gdb wants the elf file, not the binary you produced.
>
>> 2. How to create 'the executable file'? I was successfully created ecos
>> bootable disk (run in PC, showing hello ecos). I enter command (in cygwin
>> environment):
>>
>>    [cygwin-agus]$ dd conv=sync if=hello.bin of=/dev/fd0
>>
>>    What should I do to produce the same executable (or bootable <?>) 
>> file?
>
> How do you intend to get the image onto the system? Does it have a
> floppy and a BIOS to boot it? Are you going to burn it into an EEPROM?
> Do you have a JTAG interface to load the program into RAM?
>
>   Andrew

Then I use target board (Alter Stratix S40). First of all I load LEON into 
the board (via JTAG), then I load hello.out (via serial). Here is the 
result:

Agus@aariffianto /opt/grmon-eval-1.1.3/win32/ecos/project-ecos
$ ../../grmon-eval.exe -u -uart COM8

 GRMON LEON debug monitor v1.1.3 (evaluation version)

 Copyright (C) 2004,2005 Gaisler Research - all rights reserved.
 For latest updates, go to http://www.gaisler.com/
 Comments or bug-reports to support@gaisler.com

 This evaluation version will expire on 8/2/2006
try open device COM8
###opened device COM8

 GRLIB plug&play not found, switching to LEON2 legacy mode

 initialising ..........
 detected frequency:  50 MHz




 Component                            Vendor
 LEON2 Memory Controller              European Space Agency
 LEON2 SPARC V8 processor             European Space Agency
 LEON2 Configuration register         European Space Agency
 LEON2 Timer Unit                     European Space Agency
 LEON2 UART                           European Space Agency
 LEON2 UART                           European Space Agency
 LEON2 Interrupt Ctrl                 European Space Agency
 LEON2 I/O port                       European Space Agency
 AHB Debug UART                       Gaisler Research
 LEON2 Debug Support Unit             Gaisler Research

 Use command 'info sys' to print a detailed report of attached cores

grmon> load hello.out
section: .rom_vectors at 0x40000000, size 4864 bytes
section: .text at 0x40001300, size 63996 bytes
section: .rodata at 0x40010cfc, size 804 bytes
section: .data at 0x40011020, size 1168 bytes
total size: 70832 bytes (30.7 kbit/s)
read 406 symbols
entry point: 0x40001300
grmon> run
IU in error mode (tt = 0x07)
 400077bc  d0026010   ld  [%o1 + 0x10], %o0
grmon>

1. Is the error appear because of warning message which turn up when I 
compile the source using ecos-configtool?
2. What should I do?
Thank you very much.

Regards,
Agus 



-- 
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] error: no memory region specified for loadable '.ram_vectors'

[Andrew Lunn]

On Mon, May 30, 2005 at 08:02:01PM +0700, Agus Ariffianto wrote:
> 
> 
> >>My questions are:
> >>
> >>1. Why message: "...hello.bin": not in executable format: File format not
> >>recognized." turn up?
> >
> >
> >gdb wants the elf file, not the binary you produced.
> >
> >>2. How to create 'the executable file'? I was successfully created ecos
> >>bootable disk (run in PC, showing hello ecos). I enter command (in cygwin
> >>environment):
> >>
> >>   [cygwin-agus]$ dd conv=sync if=hello.bin of=/dev/fd0
> >>
> >>   What should I do to produce the same executable (or bootable <?>) 
> >>file?
> >
> >How do you intend to get the image onto the system? Does it have a
> >floppy and a BIOS to boot it? Are you going to burn it into an EEPROM?
> >Do you have a JTAG interface to load the program into RAM?
> >
> >  Andrew
> 
> Then I use target board (Alter Stratix S40). First of all I load LEON into 
> the board (via JTAG), then I load hello.out (via serial). Here is the 
> result:
> 
> Agus@aariffianto /opt/grmon-eval-1.1.3/win32/ecos/project-ecos
> $ ../../grmon-eval.exe -u -uart COM8
> 
> GRMON LEON debug monitor v1.1.3 (evaluation version)
> 
> Copyright (C) 2004,2005 Gaisler Research - all rights reserved.
> For latest updates, go to http://www.gaisler.com/
> Comments or bug-reports to support@gaisler.com
> 
> This evaluation version will expire on 8/2/2006
> try open device COM8
> ###opened device COM8
> 
> GRLIB plug&play not found, switching to LEON2 legacy mode
> 
> initialising ..........
> detected frequency:  50 MHz
> 
> 
> 
> 
> Component                            Vendor
> LEON2 Memory Controller              European Space Agency
> LEON2 SPARC V8 processor             European Space Agency
> LEON2 Configuration register         European Space Agency
> LEON2 Timer Unit                     European Space Agency
> LEON2 UART                           European Space Agency
> LEON2 UART                           European Space Agency
> LEON2 Interrupt Ctrl                 European Space Agency
> LEON2 I/O port                       European Space Agency
> AHB Debug UART                       Gaisler Research
> LEON2 Debug Support Unit             Gaisler Research
> 
> Use command 'info sys' to print a detailed report of attached cores
> 
> grmon> load hello.out
> section: .rom_vectors at 0x40000000, size 4864 bytes
> section: .text at 0x40001300, size 63996 bytes
> section: .rodata at 0x40010cfc, size 804 bytes
> section: .data at 0x40011020, size 1168 bytes
> total size: 70832 bytes (30.7 kbit/s)
> read 406 symbols
> entry point: 0x40001300
> grmon> run
> IU in error mode (tt = 0x07)
> 400077bc  d0026010   ld  [%o1 + 0x10], %o0
> grmon>
> 
> 1. Is the error appear because of warning message which turn up when I 
> compile the source using ecos-configtool?
> 2. What should I do?

You should go talk to your Mentor/supervisor. Hopefully he can arrange
some basic training on how to use all these tools. Maybe you need to
make contacts with ESA or Gaisler. 

My opinion is that you need a professional support contract from
somebody who actually knows this system and can teach you the basics.

         Andrew



     

-- 
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] error: no memory region specified for loadable '.ram_vectors'

[Agus Ariffianto]

>
> You should go talk to your Mentor/supervisor. Hopefully he can arrange
> some basic training on how to use all these tools. Maybe you need to
> make contacts with ESA or Gaisler.
>
> My opinion is that you need a professional support contract from
> somebody who actually knows this system and can teach you the basics.
>
>         Andrew
Thank you Andrew, please let me send it for the last time.
In linux environment (using tsim) after I do set $pc=0x40000000, the result 
is the same
In cygwin (using real target), here's what i did:

grmon> register

          INS       LOCALS      OUTS     GLOBALS
   0:  40015954   7FFEFF9F   FFDDFF84   00000000
   1:  4000A5E0   40013400   7FFEFFBB   80000000
   2:  40009C10   40001BDC   400FFF50   00000003
   3:  400FFF50   00000001   80000070   00000079
   4:  4000A5E0   00000040   80000070   00000001
   5:  4000A2B8   00000040   80000070   00000770
   6:  00000000   4000A000   400FFFF0   00000001
   7:  00000000   00001000   40001DCC   00000000

 psr: F28000E0   wim: 00000002   tbr: 00000050   y: 00000000

 pc:  00000000  unknown opcode: 0xffffffff
 npc: 00000004  unknown opcode: 0xffffffff

grmon> register pc:40000000
grmon> register

          INS       LOCALS      OUTS     GLOBALS
   0:  40015954   7FFEFF9F   FFDDFF84   00000000
   1:  4000A5E0   40013400   7FFEFFBB   80000000
   2:  40009C10   40001BDC   400FFF50   00000003
   3:  400FFF50   00000001   80000070   00000079
   4:  4000A5E0   00000040   80000070   00000001
   5:  4000A2B8   00000040   80000070   00000770
   6:  00000000   4000A000   400FFFF0   00000001
   7:  00000000   00001000   40001DCC   00000000

 psr: F28000E0   wim: 00000002   tbr: 00000050   y: 00000000

 pc:  00000000  unknown opcode: 0xffffffff
 npc: 00000004  unknown opcode: 0xffffffff

grmon> set $pc=40000000
Command "set" exited with return code = -1
grmon> register pc:40000000
grmon> register

          INS       LOCALS      OUTS     GLOBALS
   0:  40015954   7FFEFF9F   FFDDFF84   00000000
   1:  4000A5E0   40013400   7FFEFFBB   80000000
   2:  40009C10   40001BDC   400FFF50   00000003
   3:  400FFF50   00000001   80000070   00000079
   4:  4000A5E0   00000040   80000070   00000001
   5:  4000A2B8   00000040   80000070   00000770
   6:  00000000   4000A000   400FFFF0   00000001
   7:  00000000   00001000   40001DCC   00000000

 psr: F28000E0   wim: 00000002   tbr: 00000050   y: 00000000

 pc:  00000000  unknown opcode: 0xffffffff
 npc: 00000004  unknown opcode: 0xffffffff

grmon> run
IU in error mode (tt = 0x02)
 00000000  ffffffff   unknown opcode: 0xffffffff
grmon>

Thank you

Regards,
Agus 



-- 
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] error: no memory region specified for loadable '.ram_vectors' => Now it works

[Agus Ariffianto]

Dear ALL,
I would like to say thank you to everybody, especially Andrew Lunn, Ram 
Sudhir Tadavarthi, Jiri Gailser, and anybody else I forgot to mention, who 
helped me solving my problem. Now it works.

Regards,
Agus Ariffianto 



-- 
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] error: no memory region specified for loadable '.ram_vectors'

[Agus Ariffianto]

>> >My guess is you have the interface to Redboot enabled, but the current
>> >leon port does not support this.
> 
> Try turning off:
> 
> CYGPKG_HAL_ROM_MONITOR 
> CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT
> 
>        Andrew

Dear Andrew, 
the option CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT couldn't be disable. Thank you

regards,
Agus Ariffianto


-- 
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] error: no memory region specified for loadable '.ram_vectors'

[Andrew Lunn]

On Tue, May 30, 2006 at 11:03:50AM +0700, Agus Ariffianto wrote:
> 
> 
> >>>My guess is you have the interface to Redboot enabled, but the current
> >>>leon port does not support this.
> >
> >Try turning off:
> >
> >CYGPKG_HAL_ROM_MONITOR 
> >CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT
> >
> >       Andrew
> 
> Dear Andrew, 
> the option CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT couldn't be disable. Thank you

Ah, O.K. I did not read the cdl closely enough. 

You want this either disabled, or not active.  

It is active if CYGINT_HAL_VIRTUAL_VECTOR_SUPPORT is 1 or more. What
value does it have for you? If it is 1 or more what implements it?

      Andrew


-- 
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] error: no memory region specified for loadable '.ram_vectors'

[Agus Ariffianto]

[-- Attachment #1: Type: text/plain, Size: 812 bytes --]

>> >>>My guess is you have the interface to Redboot enabled, but the current
>> >>>leon port does not support this.
>> >
>> >Try turning off:
>> >
>> >CYGPKG_HAL_ROM_MONITOR
>> >CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT
>> >
>> >       Andrew
>>
>> Dear Andrew,
>> the option CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT couldn't be disable. Thank 
>> you
>
> Ah, O.K. I did not read the cdl closely enough.
>
> You want this either disabled, or not active.
>
> It is active if CYGINT_HAL_VIRTUAL_VECTOR_SUPPORT is 1 or more. What
> value does it have for you? If it is 1 or more what implements it?
>
>      Andrew
>

Property        Value
Macro            CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT
Enabled        True
Activelf        CYGINT_HAL_VIRTUAL_VECTOR_SUPPORT
Calculated    1
Compile        hal_if.c    hal_misc.c

Regards,
Agus

[-- Attachment #2: leon.rar --]
[-- Type: application/octet-stream, Size: 48726 bytes --]

[-- Attachment #3: Type: text/plain, Size: 148 bytes --]

-- 
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] error: no memory region specified for loadable '.ram_vectors'

[Andrew Lunn]

On Tue, May 30, 2006 at 04:35:14PM +0700, Agus Ariffianto wrote:
> >>>>>My guess is you have the interface to Redboot enabled, but the current
> >>>>>leon port does not support this.
> >>>
> >>>Try turning off:
> >>>
> >>>CYGPKG_HAL_ROM_MONITOR
> >>>CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT
> >>>
> >>>       Andrew
> >>
> >>Dear Andrew,
> >>the option CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT couldn't be disable. Thank 
> >>you
> >
> >Ah, O.K. I did not read the cdl closely enough.
> >
> >You want this either disabled, or not active.
> >
> >It is active if CYGINT_HAL_VIRTUAL_VECTOR_SUPPORT is 1 or more. What
> >value does it have for you? If it is 1 or more what implements it?
> >
> >     Andrew
> >
> 
> Property        Value
> Macro            CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT
> Enabled        True
> Activelf        CYGINT_HAL_VIRTUAL_VECTOR_SUPPORT
> Calculated    1
> Compile        hal_if.c    hal_misc.c

You need to start understanding things for yourself. Why is
CYGINT_HAL_VIRTUAL_VECTOR_SUPPORT 1? It is an interface, so something
must be implementing it. What? Is it possible to disable what is
implementing the interface?

You will probably find this documentation useful. It tells you all
about the cdl language.

http://ecos.sourceware.org/docs-latest/cdl-guide/cdl-guide.html

        Andrew

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