Skip to contentSkip to conversation

porting new hardware

U-Boot-Users Mike Lee 2 participants 5 messages Jan 29, 2005 – Jan 30, 2005

lore
Share & tools
lore

Mike Lee

author
#0 lore raw

Dear all

I am trying to port new hardware, but i get a linking error
"arm-linux-ld: invalid hex number `-u__u_boot_cmd_autoscr' "

Could anyone give me some ideas on this?

best regard

Signature · 2 lines
-------------------------------------------------------
Mike Lee
#1 lore raw
Quoted 3 lines · In message <[email protected]> you wrote:

I am trying to port new hardware, but i get a linking error
"arm-linux-ld: invalid hex number `-u__u_boot_cmd_autoscr' "

Which sort of build environment are you using?

Best regards,

Wolfgang Denk

Signature · 3 lines
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Don't hit a man when he's down - kick him; it's easier.
author
#2 lore raw

Dear Wolfgang

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

bset regard
Mike Lee

Quoted 16 lines · Wolfgang Denk
Quoted 3 lines · In message <[email protected]> you wrote:

I am trying to port new hardware, but i get a linking error
"arm-linux-ld: invalid hex number `-u__u_boot_cmd_autoscr' "

Which sort of build environment are you using?

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 Don't hit a man when he's down - kick him; it's easier.

Signature · 2 lines
-------------------------------------------------------
Mike Lee
#3 lore raw

Dear Mike,

Quoted 8 lines · in message <[email protected]> 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:

Quoted 1 line
Quoted 1 line
Quoted 1 line

"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

Signature · 3 lines
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."
author
#4 lore raw

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

Quoted 37 lines · Wolfgang Denk

Dear Mike,

Quoted 8 lines · in message <[email protected]> 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:

Quoted 1 line
Quoted 1 line
Quoted 1 line

"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."

Signature · 2 lines
-------------------------------------------------------
Mike Lee