uboot v2 build issues.

GoogleGroups
1

I'm working to rebuild uboot-v2 (I think it's 2.0.0-rc10) for the
Beagle board and I'm running into some build issues. It looks like
the include/drivers.h file doesn't have the "driver_d" struct updated
with fields for the read/write/open/etc function pointers. So when
the code below in the board-beagle.c is compiled I get the error
below.

static struct driver_d ram_drv = {
       .name = "ram",
       .probe = dummy_probe,
       .open = dev_open_default,
       .close = dev_close_default,
       .read = mem_read,
       .write = mem_write,
       .lseek = dev_lseek_default,
};

make[1]: `arch/arm/include/asm/mach-types.h' is up to date.
  CHK include/linux/version.h
  CHK include/linux/utsrelease.h
  SYMLINK include/config.h -> board/omap/config.h
  CC board/omap/board-beagle.o
board/omap/board-beagle.c:254: error: unknown field 'open' specified
in initializer
board/omap/board-beagle.c:254: warning: initialization from
incompatible pointer type
board/omap/board-beagle.c:255: error: unknown field 'close' specified
in initializer
board/omap/board-beagle.c:255: warning: initialization from
incompatible pointer type
board/omap/board-beagle.c:256: error: unknown field 'read' specified
in initializer
board/omap/board-beagle.c:256: warning: initialization from
incompatible pointer type
board/omap/board-beagle.c:257: error: unknown field 'write' specified
in initializer
board/omap/board-beagle.c:257: warning: initialization makes integer
from pointer without a cast
board/omap/board-beagle.c:258: error: unknown field 'lseek' specified
in initializer
board/omap/board-beagle.c:258: warning: initialization from
incompatible pointer type
board/omap/board-beagle.c: In function 'beagle_devices_init':
board/omap/board-beagle.c:277: warning: implicit declaration of
function 'armlinux_add_dram'
make[1]: *** [board/omap/board-beagle.o] Error 1
make: *** [board/omap] Error 2

2

Hi,

Matthew a �crit :

I'm working to rebuild uboot-v2 (I think it's 2.0.0-rc10) for the
Beagle board and I'm running into some build issues. It looks like
the include/drivers.h file doesn't have the "driver_d" struct updated

u-boot v2 has its own mailing list here where you may get some answers :
http://lists.infradead.org/mailman/listinfo/u-boot-v2

Eric

3

Don't know if anyone answered you Matthew, but these there were some
recent patches that addressed some of the issues of compiling for the
BeagleBoard. I remember the above example being addressed specifically.

Good luck.

-Freeman

4

i just git pull'ed the u-boot v2 stuff and wanted to take a crack at
building it. i notice that there's no v1-style "make
omap3_beagle_defconfig" or something similar, or am i just missing it?
do i really have to "make menuconfig" and select everything by hand?

rday

5

http://groups.google.com/group/beagleboard/browse_thread/thread/9bc51b4b292bb6c9/67ed93adce9f91df?lnk=gst&q=How+to+use+u-bootv2#67ed93adce9f91df

Best regards

Dirk

6

Argh :frowning:

Seems that the U-Boot v2 mailing list moved and the link to the patch in above mail doesn't work any more. :frowning:

Try

http://lists.infradead.org/pipermail/barebox/2009-December/000175.html

instead.

Best regards

Dirk

7

and which pre-built arm-none-linux-gnueabi- toolchain would you
recommend?

rday

8

so, given that i already had the Denx ARM toolchain on my system for
building u-boot v1, i just now:

  1) "git pull"ed u-boot v2
  2) export ARCH=arm
  3) export CROSS_COMPILE=arm-linux-
  4) make omap3530_beagle_per_uart_defconfig
  5) make

got a "uboot.bin", copied it to SD/MMC card as "u-boot.bin", and
booted off of it:

Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Reading boot sector
Loading u-boot.bin from mmc

U-Boot 2.0.0-rc10-00512-gf522d42 (Dec 16 2009 - 14:40:58)

Board: Texas Instrument's Beagle
Malloc space: 0x87bfff10 -> 0x87ffff10 (size 4 MB)
Stack space : 0x87bf7f10 -> 0x87bfff10 (size 32 kB)
running /env/bin/init...
not found
X-load Beagle>

  i'm assuming that's what i was after.

rday