public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Agus Ariffianto" <aariffianto@s.ee.itb.ac.id>
To: "Andrew Lunn" <andrew@lunn.ch>,
		"Ram Sudhir Tadavarthi" <ram.tadavarthi@netco.de>
Cc: "Mahmud Galela" <mgalela@vlsi.itb.ac.id>,
		<ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] error: no memory region specified for loadable '.ram_vectors'
Date: Tue, 30 May 2006 11:49:00 -0000	[thread overview]
Message-ID: <03e601c683de$e8dc5510$6c44cda7@aariffianto> (raw)
In-Reply-To: <20060530071313.2C71820E04C@gemmini.netco.de>

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

  parent reply	other threads:[~2006-05-30 11:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-29  9:20 Agus Ariffianto
2006-05-29  9:44 ` Andrew Lunn
2006-05-29 10:40   ` Agus Ariffianto
2006-05-29 12:20     ` Andrew Lunn
2006-05-30  4:00       ` Agus Ariffianto
2006-05-30  7:28         ` AW: " Ram Sudhir Tadavarthi
2006-05-30  7:38           ` Andrew Lunn
2006-05-30 11:49           ` Agus Ariffianto [this message]
2006-05-30 12:02             ` Andrew Lunn
2006-05-30 12:40               ` Agus Ariffianto
2006-05-30 12:59                 ` Andrew Lunn
2006-05-30 13:02               ` Agus Ariffianto
2006-05-30 13:18                 ` Andrew Lunn
2006-05-30 13:28                   ` Agus Ariffianto
2006-06-13  9:31                   ` [ECOS] error: no memory region specified for loadable '.ram_vectors' => Now it works Agus Ariffianto
2006-05-30  4:06       ` [ECOS] error: no memory region specified for loadable '.ram_vectors' Agus Ariffianto
2006-05-30  7:43         ` Andrew Lunn
2006-05-30  9:36           ` Agus Ariffianto
2006-05-30 11:19             ` Andrew Lunn
2006-05-29  9:38 Agus Ariffianto
2006-05-29 11:21 Agus Ariffianto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='03e601c683de$e8dc5510$6c44cda7@aariffianto' \
    --to=aariffianto@s.ee.itb.ac.id \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=mgalela@vlsi.itb.ac.id \
    --cc=ram.tadavarthi@netco.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).