This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: vector.s branch 0 problem

From: Alexandre <thekyz at gmail dot com>
To: "Gary Thomas" <gary at mlbassoc dot com>
Cc: ecos-discuss <ecos-discuss at ecos dot sourceware dot org>
Date: Mon, 2 Jul 2007 16:47:01 +0200
Subject: Re: [ECOS] vector.s branch 0 problem
References: <d5aafeec0707020634k25c4eaeerde5a6e7022072a52@mail.gmail.com> <46890104.7010406@mlbassoc.com> <d5aafeec0707020714y66c87b19q8c9b0fd27b9e6ede@mail.gmail.com> <46890BDA.7020603@mlbassoc.com>
Reply-to: thekyz at gmail dot com

No, but you *must* run 'arm-elf-objdumop' on "boot", not "boot.o"

That makes sense indeed -.-

Does that size seem right ?
$ arm-elf-size boot
  text    data     bss     dec     hex filename
 23392     824    7420   31636    7b94 boot

If I understand well "boot" is my binary file, yet i can't upload it
to the board using openocd because it keeps telling me the file is too
large -.-

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

References:
- vector.s branch 0 problem
  - From: Alexandre
- Re: vector.s branch 0 problem
  - From: Gary Thomas
- Re: vector.s branch 0 problem
  - From: Alexandre
- Re: vector.s branch 0 problem
  - From: Gary Thomas

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]