Re: [ECOS] vector.s branch 0 problem

[Gary Thomas <gary at mlbassoc dot com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alexandre wrote:
>> 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 -.-
> 

What format data is openocd expecting?  The file 'boot' is
an ELF executable, which contains not only the binary image
of your program (instructions, data, etc), but also symbolic
information, debug info, etc.  Files in this format have to
be parsed (broken down) for the download to make sense.

My guess is that openocd is expecting just the binary data.
In this case, you need to extract out just that from the ELF
image.  Use objcopy for this:

  % arm-elf-objcopy -O binary boot boot.bin

This has nothing to do with the fact that you were trying to
disassemble the object file (boot.o or vectors.o) and having
trouble making sense of it.

- --
- ------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFGiRdumaKbSsQGV8ARAg+iAJ0bYXRoFw5HbFyFs2e2DHiW2yEnkQCfXX6T
xaqVd6J5lBNljClHAz5H/SE=
=lX3y
-----END PGP SIGNATURE-----

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