Skip to contentSkip to conversation

u-boot fails with custom board support

Buildroot mike sander 3 participants 6 messages Apr 8, 2009 1 message not in the archive

lore
Share & tools
lore

mike sander

author
#0 lore raw

Hi All:

I'm using buildroot-2009.02. I have a custom board based on atmel
at91sam9g20. I have created a top level board config.

I invoke make as follows:

make BOARD=xx

u-boot is failing with the following messages (see below). I have
specified "at91sam9g20ek" in the "board name" section for u-boot (same behaviour with default setting). It appears that u-boot does correctly
do the at91sam9g20ek_config. I cannot see how/why make is looking for
"Project Name" items under u-boot towards the end of the u-boot
build. Manually building u-boot with "make
at91sam9g20ek_config;make" works fine. Stock u-boot is perfectly
acceptable.

I've read the br docs. I did not see any indication that u-boot needs to be tailored when using custom board support. Any suggestions on how to force u-boot to build the stock config? I have tried latest br
snapshot too. same behavior. I suspect I have missed something obvious.

/usr/bin/make -C board/atmel/xx/
make: Entering an unknown directory
make: *** board/atmel/xx/: No such file or directory. Stop.
make: Leaving an unknown directory
make[1]: *** [board/atmel/xx/libxx.a] Error 2
make[1]: Leaving directory `/home/br/buildroot/project_build_arm/xx/u-boot-2009.03'
make: *** [/home/br/buildroot/project_build_arm/xx/u-boot-2009.03/u-boot.bin] Error 2

thanks in advance,

mike sander

#1 lore raw

Hi Mike,

Quoted 9 lines · mike sander

/usr/bin/make -C board/atmel/xx/
make: Entering an unknown directory
make: *** board/atmel/xx/: No such file or directory. ?Stop.
make: Leaving an unknown directory
make[1]: *** [board/atmel/xx/libxx.a] Error 2
make[1]: Leaving directory `/home/br/buildroot/project_build_arm/xx/u-boot-2009.03'
make: *** [/home/br/buildroot/project_build_arm/xx/u-boot-2009.03/u-boot.bin] Error 2

Are you sure it's the same u-boot sources? AFAIK, Atmel didn't push
u-boot patches to upstream, and therefore it were using a prepatched u-boot that was comming from somewhere else. That's the reason we have different u-boot versions and special handling for ARM.
This might have change since I last saw it though as I don't use ARM myself.

Kind Regards,
Thiago A. Correa

author
#2 lore raw
Quoted 15 lines · Thiago A. Corr?a

Hi Mike,

Quoted 10 lines · mike sander

/usr/bin/make -C board/atmel/xx/
make: Entering an unknown directory
make: *** board/atmel/xx/: No such file or directory. Stop.
make: Leaving an unknown directory
make[1]: *** [board/atmel/xx/libxx.a] Error 2
make[1]: Leaving directory `/home/br/buildroot/project_build_arm/xx/u-boot-2009.03'
make: *** [/home/br/buildroot/project_build_arm/xx/u-boot-2009.03/u-boot.bin] Error 2

Quoted 10 lines

Are you sure it's the same u-boot sources? AFAIK, Atmel didn't push
u-boot patches to upstream, and therefore it were using a prepatched u-boot that was comming from somewhere else. That's the reason we have different u-boot versions and special handling for ARM.
This might have change since I last saw it though as I don't use ARM myself.

Kind Regards,
Thiago A. Correa

Thiago,

yes these are right sources, this is the u-boot from buildroot with at91
specific patches. Ulf pointed out that I was probably building
incorrectly (see other messages in thread). Still the way I was
building with "make BOARD=<project>" worked for everything but u-boot. Based on the current documentation "make BOARD=<project> " seem to be the right way to build a custom board configuration. Somehow the <project> identifier gets pushed into the u-boot make and it fails.

If I follow the "normal" build command line pointed out by Ulf "make
BOARD=<project> getconfig ; make" I do not see this error. Honestly I
do not know if this is a buildroot bug, or if the error is at the keyboard interface level.

If this is a bug, I can debug further if you can give me some ideas on where to look in the build process.

regards,

mike

Quoted 6 lines

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Scanned with Copfilter Version 0.84beta3a (P3Scan 2.2.1)
AntiSpam: SpamAssassin 3.2.3
by Markus Madlener @ http://www.copfilter.org

#3 lore raw
In reply to mike sander

mike sander skrev:

Quoted 9 lines

Hi All:

I'm using buildroot-2009.02. I have a custom board based on atmel at91sam9g20. I have created a top level board config.

I invoke make as follows:

make BOARD=xx

The normal way of using buildroot is to do:

$ make at91sam9g20ek_defconfig
$ make

If you do any modifications to any the configs (busybox, linux, .config etc.)
you can do:

$ make saveconfig

which will copy all your configs to $(LOCAL)/$(PROJECT) It will also update the .config file so that it will use your updated config files instead of the default.

You can then retrieve this by making:

$ make BOARD=<PROJECT> getconfig
I.E:
$ make BOARD=at91sam9g20-mike getconfig

which will fetch the new config file into the top directory of buildroot

You then type

$ make
to build the project

BR
Ulf Samuelsson

Quoted 35 lines

u-boot is failing with the following messages (see below). I have specified "at91sam9g20ek" in the "board name" section for u-boot (same behaviour with default setting). It appears that u-boot does correctly do the at91sam9g20ek_config. I cannot see how/why make is looking for "Project Name" items under u-boot towards the end of the u-boot build. Manually building u-boot with "make at91sam9g20ek_config;make" works fine. Stock u-boot is perfectly acceptable.

I've read the br docs. I did not see any indication that u-boot needs to be tailored when using custom board support. Any suggestions on how to force u-boot to build the stock config? I have tried latest br snapshot too. same behavior. I suspect I have missed something obvious.

/usr/bin/make -C board/atmel/xx/
make: Entering an unknown directory
make: *** board/atmel/xx/: No such file or directory. Stop.
make: Leaving an unknown directory
make[1]: *** [board/atmel/xx/libxx.a] Error 2
make[1]: Leaving directory `/home/br/buildroot/project_build_arm/xx/u-boot-2009.03'
make: *** [/home/br/buildroot/project_build_arm/xx/u-boot-2009.03/u-boot.bin] Error 2

thanks in advance,

mike sander
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

author
#4 lore raw
Quoted 32 lines · Ulf Samuelsson

mike sander skrev:

Quoted 10 lines

Hi All:

I'm using buildroot-2009.02. I have a custom board based on atmel at91sam9g20. I have created a top level board config.

I invoke make as follows:

make BOARD=xx

The normal way of using buildroot is to do:

$ make at91sam9g20ek_defconfig
$ make

If you do any modifications to any the configs (busybox, linux, .config etc.)
you can do:

$ make saveconfig

which will copy all your configs to $(LOCAL)/$(PROJECT) It will also update the .config file so that it will use your updated config files instead of the default.

You can then retrieve this by making:

$ make BOARD=<PROJECT> getconfig
I.E:
$ make BOARD=at91sam9g20-mike getconfig
Quoted 7 lines

which will fetch the new config file into the top directory of buildroot

You then type

$ make
to build the project

Thank You. It appears I was doing it wrong. I did the "make
BOARD=<PROJECT> getconfig ; make" and it worked as expected..

To be honest, the documentation is a bit vague (IMHO).

I understood "make BOARD=<project>" to be the mechanism to build for a
specific project. This does work, except for u-boot. The getconfig
is used if you want to modify the configuration (prior to another
saveconfig). What then is the use of "make BOARD=<project>"?

<quote>

Once a package has been unpacked, it is possible to manually update configuration files. Buildroot can automatically save the configuration of buildroot, linux, busybox, uclibc and u-boot in "local/$(PROJECT) by using the command:

 $ make saveconfig

Once a buildroot configuration has been created by saveconfig, the default "$(TOPDIR)/.config" file can be overridden by

 $ make BOARD=<project>

Buildroot will then use "local/<project>/<project>.config" instead of ".config".

If you want to modify your board, you can copy the project configuration file to ".config" by using the command:

 $ make BOARD=<project> getconfig

</end quote>

Could I propose the following wording:

Once a package has been unpacked, it is possible to manually update configuration files. Buildroot can automatically save the configuration of buildroot, linux, busybox, uclibc and u-boot in "local/$(PROJECT) by using the command:

 $ make saveconfig

If you want to modify your board, you can copy the project configuration file to ".config" by using the command:

 $ make BOARD=<project> getconfig
 <make changes to configuration>
 $ make saveconfig

To build your board:

 $ make BOARD=<project> getconfig
 $ make

Once again, thanks for you assistance. If you find this proposed
wording better, can you make changes or should I submit a bug report?

Regards,

Mike

Quoted 50 lines

BR
Ulf Samuelsson

Quoted 28 lines

u-boot is failing with the following messages (see below). I have specified "at91sam9g20ek" in the "board name" section for u-boot (same behaviour with default setting). It appears that u-boot does correctly do the at91sam9g20ek_config. I cannot see how/why make is looking for "Project Name" items under u-boot towards the end of the u-boot build. Manually building u-boot with "make at91sam9g20ek_config;make" works fine. Stock u-boot is perfectly acceptable.

I've read the br docs. I did not see any indication that u-boot needs to be tailored when using custom board support. Any suggestions on how to force u-boot to build the stock config? I have tried latest br snapshot too. same behavior. I suspect I have missed something obvious.

/usr/bin/make -C board/atmel/xx/
make: Entering an unknown directory
make: *** board/atmel/xx/: No such file or directory. Stop.
make: Leaving an unknown directory
make[1]: *** [board/atmel/xx/libxx.a] Error 2
make[1]: Leaving directory `/home/br/buildroot/project_build_arm/xx/u-boot-2009.03'
make: *** [/home/br/buildroot/project_build_arm/xx/u-boot-2009.03/u-boot.bin] Error 2

Quoted 8 lines

thanks in advance,

mike sander
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Scanned with Copfilter Version 0.84beta3a (P3Scan 2.2.1)
AntiSpam: SpamAssassin 3.2.3
by Markus Madlener @ http://www.copfilter.org

A message that is not in the archive (sent off-list or not yet received): [email protected]

author
#6 lore raw
Quoted 25 lines · Ulf Samuelsson

mike sander skrev:

Quoted 17 lines

Hi All:

I'm using buildroot-2009.02. I have a custom board based on atmel at91sam9g20. I have created a top level board config.

I invoke make as follows:

make BOARD=xx

u-boot is failing with the following messages (see below). I have specified "at91sam9g20ek" in the "board name" section for u-boot (same behaviour with default setting). It appears that u-boot does correctly do the at91sam9g20ek_config. I cannot see how/why make is looking for "Project Name" items under u-boot towards the end of the u-boot build. Manually building u-boot with "make at91sam9g20ek_config;make" works fine. Stock u-boot is perfectly acceptable.

Quoted 5 lines

I've read the br docs. I did not see any indication that u-boot needs to be tailored when using custom board support. Any suggestions on how to force u-boot to build the stock config? I have tried latest br snapshot too. same behavior. I suspect I have missed something obvious.

Quoted 7 lines

As for U-Boot, there is NO support for at91sam9g20 in vanilla u-boot. You have to apply the Atmel specific sam9g20 patches
in menuconfig
BR
Ulf Samuelsson

yes, I am aware of this. I *can* build stock u-boot targeting the
at91sam9g20ek from the u-boot-2009.01 directory.

regards,

ms

Quoted 30 lines
Quoted 13 lines

/usr/bin/make -C board/atmel/xx/
make: Entering an unknown directory
make: *** board/atmel/xx/: No such file or directory. Stop.
make: Leaving an unknown directory
make[1]: *** [board/atmel/xx/libxx.a] Error 2
make[1]: Leaving directory `/home/br/buildroot/project_build_arm/xx/u-boot-2009.03'
make: *** [/home/br/buildroot/project_build_arm/xx/u-boot-2009.03/u-boot.bin] Error 2

Quoted 8 lines

thanks in advance,

mike sander
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Scanned with Copfilter Version 0.84beta3a (P3Scan 2.2.1)
AntiSpam: SpamAssassin 3.2.3
by Markus Madlener @ http://www.copfilter.org