[U-Boot-Users] porting new hardware

[Mike Lee <eemike@gmail.com>]

Dear Wolfgang 
   I have found the problem,.... i do not cp the config.mk from mx1ads
folder which define the linking address of u-boot in ram.
error come from no text_base value :
      arm-linux-ld -Bstatic -T board/rob/u-boot.lds -Ttext $UNDEF_SYM
after i add the config.mk back:
      arm-linux-ld -Bstatic -T board/rob/u-boot.lds -Ttext 0x08F00000 $UNDEF_SYM

  Thanks for anyone concerned
best regard
Mike,Lee


On Sun, 30 Jan 2005 10:28:49 +0100, Wolfgang Denk <wd@denx.de> wrote:
> Dear Mike,
> 
> in message <1ffb4b0705012918564c0972f4@mail.gmail.com> you wrote:
> >
> >   I am using arm-linux toolchain from www.handheld.org
> > arm-linux-3.3.2. It should be ok which i have tried to compile kernel
> > and other appz before.
> >   Actually, i am using motorola MXL arm9 CPU, and i just copy files in
> > board/mx1ads/ , include/mx1ads.h and patched the makefile. I do not
> > come up with any idea right now, may be i first look deeper what
> > autoscript first
> 
> Well, this error message:
> 
> > > > "arm-linux-ld: invalid hex number `-u__u_boot_cmd_autoscr' "
> 
> comes from these lines in the top level Makefile:
> 
> u-boot:         depend $(SUBDIRS) $(OBJS) $(LIBS) $(LDSCRIPT)
>                 UNDEF_SYM=`$(OBJDUMP) -x $(LIBS) |sed  -n -e 's/.*\(__u_boot_cmd_.*\)/-u\1/p'|sort|uniq`;\
>                 $(LD) $(LDFLAGS) $$UNDEF_SYM $(OBJS) \
>                         --start-group $(LIBS) $(PLATFORM_LIBS) --end-group \
>                         -Map u-boot.map -o u-boot
> 
> Seems either your "objdump" and/or your  "sed"  create  bogus  or  at
> least  unexpected  output.  You  may  want to check the parts of this
> pipeline step by step.
> 
> Best regards,
> 
> Wolfgang Denk
> 
> --
> Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> "Service, VOBISt Du ? - ESCOMmt keiner."
> 


-- 
-------------------------------------------------------
Mike Lee