public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Adarsh Babu <adarshrbpin@yahoo.co.in>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] MCF5271 Port.
Date: Thu, 1 Feb 2007 15:58:51 +0000 (UTC)	[thread overview]
Message-ID: <loom.20070201T164941-604@post.gmane.org> (raw)
In-Reply-To: loom.20070130T052848-386@post.gmane.org

Adarsh Babu <adarshrbpin <at> yahoo.co.in> writes:

> 
> Zachary P. Landau <kapheine <at> gmail.com> writes:
> 
> > 
> > On 1/29/07, Wolfgang Denk <wd <at> denx.de> wrote:
> > > In message <371814.45747.qm <at> web8321.mail.in.yahoo.com> you wrote:
> > > > I am new to U-Boot. I downloaded u-boot-1.1.6 and plan
> > > > to use the same on the MCF5271 EVB. My host system has
> > > > Red Hat 6.
> > >
> > > Sounds as if you have a favour for old code. Be aware  that  problems
> > > may be lurking in that corner.
> > >
> > > > m68k-elf-gcc: hello_world.o: No such file or directory
> > > > m68k-elf-gcc: unrecognized option `-MQ'
> > > > m68k-elf-gcc: stubs.o: No such file or directory
> > > > m68k-elf-gcc: unrecognized option `-MQ'
> > > ...
> > > Seems your toolchain is not working. Try another one.
> > 
> > As Wolfgang says, old toolchains will do this.  When trying to compile a 
> recent
> > checkout using the 20010318 Snapgear toolchain, I got the same error.  
When I
> > upgraded to the 20060615 release, it worked.
> > 
> > Also note that someone recently had a different problem with compiling the 
> 5271
> > port using the 20060615 toolchain.  Here's a link to his post and someone's
> > reply on how to fix it:
> > 
> > 
> 
http://comments.gmane.org/gmane.comp.hardware.motorola.microcontrollers.coldfir
> e/7212.
> > I haven't looked at the issue yet.  If you (or anyone) gets a chance, it'd 
be
> > helpful to know what the issue is and if this is a real fix or just a
> > workaround.
> > 
> 
> 
Hi Zachary,

Well thanks a lot. The 20060615 tool chain along with the suggestion in the 
link that you sent me did the trick. But now I face a different problem. I did 
get a neat build and the u-boot.bin file. I flashed the same onto the EVB. But 
i can't get a u-boot prompt on Minicom. Its just blank and nothing else. I 
opened the Srec file and compared it with the Srec file I got for MCF5272 with 
u-boot1.1.2 and seemed pretty ok. Do I have to do something to get it on the 
console ? is there any other modifications that i need to do other than make 
M5271EVB_config and make ??? 

Please help me out.

Regards,
Adarsh.

  reply	other threads:[~2007-02-01 15:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-29 11:13 [U-Boot-Users] MCF5271 Port adarsh babu
2007-01-29 13:44 ` Wolfgang Denk
2007-01-29 14:54   ` Zachary P. Landau
2007-01-30  4:44     ` Adarsh Babu
2007-02-01 15:58       ` Adarsh Babu [this message]
2007-02-01 18:27         ` Zachary P. Landau
2007-02-05 16:04         ` Bartlomiej Sieka
2007-02-08 15:22           ` Adarsh Babu
2007-02-08 16:20             ` Wolfgang Denk
2007-02-13 16:37               ` Adarsh Babu
2007-02-05 21:17         ` Bartlomiej Sieka
  -- strict thread matches above, loose matches on Subject: below --
2007-01-29 12:14 adarsh babu

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=loom.20070201T164941-604@post.gmane.org \
    --to=adarshrbpin@yahoo.co.in \
    --cc=u-boot@lists.denx.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