public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Pawel Sikora <pluto@agmk.net>
To: Hadi Aminzadeh <hadi60@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: ARM7TDMI problem
Date: Thu, 13 Oct 2011 11:18:00 -0000	[thread overview]
Message-ID: <2137989.MiA6Gvp2CO@pawels> (raw)
In-Reply-To: <CANWn+yE3kyB8my9U0AVkopsc2EByu3G5mFvVEza1RK4vjbPB5g@mail.gmail.com>

On Thursday 13 of October 2011 14:40:50 Hadi Aminzadeh wrote:
> 2011/10/13 Paweł Sikora <pluto@agmk.net>:
> > On Thursday 13 of October 2011 07:37:26 Hadi Aminzadeh wrote:
> >> 2011/10/12 Paweł Sikora <pluto@agmk.net>:
> >> > On Wednesday 12 of October 2011 18:41:42 Hadi Aminzadeh wrote:
> >> >> On Tue, Oct 11, 2011 at 2:55 PM, Pawel Sikora <pluto@agmk.net> wrote:
> >> >> > On Tuesday 11 of October 2011 14:35:30 Hadi Aminzadeh wrote:
> >> >> >> Hi Dear,
> >> >> >>
> >> >> >> I have a LPC2478 arm processor and want to use gcc to cross compile my
> >> >> >> code in x86 for LPC2478
> >> >> >> I use arm-linux-gnueabi-gcc to do that but (I think) the output of gcc
> >> >> >> is an application that can be run in arm ported linux kernel but I
> >> >> >> need Intel HEX-like format that can be programmed to micro controller
> >> >> >> (I haven't any OS)
> >> >> >> I haven't any idea what to do or what keyword I must search.
> >> >> >
> >> >> > you basically need a proper linker script for small embedded device.
> >> >> > please, see an example at http://www.dreamislife.com/arm/ -> lpc2106_gcc.zip
> >> >> > and search arm groups for similar one tuned for LPC2478...
> >> >> >
> >> >> >
> >> >>
> >> >> Thanks for your replay
> >> >> I find a linker script for my device (that tested with my board) and
> >> >> used gnuarm pre-compiled binary and eclipse to compile my tested
> >> >> simple LED flasher program. but no success :-(
> >> >> you can see the output of eclipse. have any idea?
> >> >>
> >> >> make all
> >> >> Building file: ../main.c
> >> >> Invoking: GCC C Compiler
> >> >> /home/noBackup/arm/gnuarm-4.0.2/bin/arm-elf-gcc -O3 -g -Wall -c
> >> >> -fmessage-length=0 -mcpu=arm7tdmi-s -MMD -MP -MF"main.d" -MT"main.d"
> >> >> -o"main.o" "../main.c"
> >> >> Finished building: ../main.c
> >> >>
> >> >> Building target: lpc2478
> >> >> Invoking: GCC C Linker
> >> >> /home/noBackup/arm/gnuarm-4.0.2/bin/arm-elf-gcc -mcpu=arm7tdmi-s
> >> >> -nostartfiles -T /home/hadi/workspace/lpc2478/LPC2478.ld -o"lpc2478"
> >> >> ./main.o
> >> >> Finished building target: lpc2478
> >> >>
> >> >> make --no-print-directory post-build
> >> >> /home/noBackup/arm/gnuarm-4.0.2/bin/arm-elf-objcopy --output-target
> >> >> ihex lpc2478 lpc2478.hex
> >> >>
> >> >
> >> > please show the 'simple LED flasher' source and 'arm-elf-objdump -hw lpc2478'.
> >> >
> >>
> >> I attach all of them.
> >> Thanks for your time.
> >>
> >
> >
> > the delay_ms() function was optimized at compile time to plain 'return'
> > you can see this with -fdump-tree-optimized gcc option.
> > and finally the hexdump shows .debug* sections in binary - there's no need
> > to waste eeprom resources with debuginfo.
> >
> 
> ok I disable the optimization ( -O0 ) but nothing happend :-(
> Is it possible to generate an lst file ? I think it can help to find problem.

man gcc: --save-temps, -fverbose-asm

> 
> Regards,
> Aminzadeh

  reply	other threads:[~2011-10-13 11:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANWn+yESRriP137hJHtL2J5oWTuQnq9t3a=paJSQvU-RyAbVAw@mail.gmail.com>
2011-10-11 11:06 ` Hadi Aminzadeh
2011-10-11 11:26   ` Pawel Sikora
2011-10-12 16:42     ` Hadi Aminzadeh
2011-10-12 17:51       ` Paweł Sikora
     [not found]         ` <CANWn+yEDQyw9_LKfsxeNLHo6_EYdyg1pbnfFGSv442bnwq=bWQ@mail.gmail.com>
2011-10-13  5:50           ` Paweł Sikora
2011-10-13 11:11             ` Hadi Aminzadeh
2011-10-13 11:18               ` Pawel Sikora [this message]
2011-10-11 11:29   ` Kai Ruottu

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=2137989.MiA6Gvp2CO@pawels \
    --to=pluto@agmk.net \
    --cc=gcc-help@gcc.gnu.org \
    --cc=hadi60@gmail.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).