public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Torsten Mohr <tmohr@s.netic.de>
To: binutils <binutils@sources.redhat.com>
Subject: A section is missing in S-Record
Date: Tue, 17 Dec 2002 14:32:00 -0000	[thread overview]
Message-ID: <200212172306.15411.tmohr@s.netic.de> (raw)

Hi everybody,

i configured, compiled and installed binutils-2.13 and gcc-3.2.1
for the target v850-unknown-elf on a linux host.

I'd like to use this tool chain for a NEC V850/SF1, an embedded
controller.  This controller has its interrupt vectors in the
range 0x0000 to 0x0340, so i wrote a v850.ld:

MEMORY
{
  vectors (rx) : ORIGIN = 0, LENGTH = 0x340
  rom (rx) : ORIGIN = 0x340, LENGTH = 0x40000
  ram (!rx) : ORIGIN = 0xffffb000, LENGTH = 0x2000
}

SECTIONS
{
  .vectors : { *(.vectors)} >vectors
  .rodata : { *(.rodata) } >rom
  .text : { *(.text) } >rom
....

In crt0.s i wrote:
	.section	.vectors
	.offset		0
	jr		start

When i link it all together i get this in the map file:


Memory Configuration

Name             Origin             Length             Attributes
vectors          0x00000000         0x00000340         xr
rom              0x00000340         0x00040000         xr
ram              0xffffb000         0x00002000         !xr
*default*        0x00000000         0xffffffff

Linker script and memory map


.vectors        0x00000000        0x4
 *(.vectors)
 .vectors       0x00000000        0x4 out/crt0.o

.rodata
 *(.rodata)


So the section vectors made it into the ELF file, but when i
try to generate an S-Record with this command:

v850-unknown-elf-objcopy -O srec --srec-forceS3 qwe.elf qwe.srec

There is NOTHING at address 0x0000, it all starts at 0x340.


Where are the interrupt vectors?


Thank you for any hints,
Torsten.

             reply	other threads:[~2002-12-17 22:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-17 14:32 Torsten Mohr [this message]
2002-12-17 14:53 ` Alan Modra
2002-12-18  4:39   ` Torsten Mohr
2002-12-18  5:14     ` Alan Modra

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=200212172306.15411.tmohr@s.netic.de \
    --to=tmohr@s.netic.de \
    --cc=binutils@sources.redhat.com \
    /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).