public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot POST
Date: Mon, 22 Mar 2010 17:09:53 +0100	[thread overview]
Message-ID: <m2pr2ws5gu.fsf@ohwell.denx.de> (raw)
In-Reply-To: <2658E54B540D284981EA57E6A549EA70A177129488@INBLRK77M1MSX.in002.siemens.net> (Anoop Sasi's message of "Fri, 19 Mar 2010 14:21:34 +0530")

Hi,

> I have tried to build u-boot for Beagle board with POST enabled but its throwing some compilation errors.
> What might be the reason? Am I missing some config options? Please help me.....
>
> Error messages I got
>
> make[2]: Leaving directory `/home/anoop/beagleboard-default-u-boot-mainline/common'
> make -C libfdt/
> make[2]: Entering directory `/home/anoop/beagleboard-default-u-boot-mainline/libfdt'
> arm-none-linux-gnueabi-ar crv libfdt.a
> make[2]: Leaving directory `/home/anoop/beagleboard-default-u-boot-mainline/libfdt'
> make -C api/
> make[2]: Entering directory `/home/anoop/beagleboard-default-u-boot-mainline/api'
> arm-none-linux-gnueabi-ar crv libapi.a
> make[2]: Leaving directory `/home/anoop/beagleboard-default-u-boot-mainline/api'
> make -C post/
> make[2]: Entering directory `/home/anoop/beagleboard-default-u-boot-mainline/post'
> make[2]: Leaving directory `/home/anoop/beagleboard-default-u-boot-mainline/post'
> make[2]: Entering directory `/home/anoop/beagleboard-default-u-boot-mainline/post'
> arm-none-linux-gnueabi-gcc -g  -Os   -fno-strict-aliasing -fno-common -ffixed-r8 -msoft-float   -fno-strict-aliasing -fno-common -ffixed-r8 -msoft-float   -D__KERNEL__ -DTEXT_BASE=0x80e80000 -I/home/anoop/beagleboard-default-u-boot-mainline/include -fno-builtin -ffreestanding -nostdinc -isystem /home/anoop/arm-2008q3/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/include -pipe  -DCONFIG_ARM -D__ARM__ -march=armv5  -mno-thumb-interwork -march=armv5  -mno-thumb-interwork -Wall -Wstrict-prototypes -fno-stack-protector -c -o post.o post.c
> post.c: In function 'post_init_f':
> post.c:52: error: 'gd_t' has no member named 'post_init_f_time'
> post.c:53: error: 'gd_t' has no member named 'post_init_f_time'
> post.c: In function 'post_bootmode_init':
> post.c:86: error: 'gd_t' has no member named 'post_log_word'
> post.c: In function 'post_log_mark_start':
> post.c:110: error: 'gd_t' has no member named 'post_log_word'
> post.c: In function 'post_log_mark_succ':
> post.c:115: error: 'gd_t' has no member named 'post_log_word'
> post.c: In function 'post_output_backlog':
> post.c:124: error: 'gd_t' has no member named 'post_log_word'
> post.c:126: error: 'gd_t' has no member named 'post_log_word'
> post.c:453:2: warning: #warning "Not implemented yet"
> make[2]: *** [post.o] Error 1
> make[2]: Leaving directory `/home/anoop/beagleboard-default-u-boot-mainline/post'
> make[1]: *** [post/libpost.a] Error 2
> make[1]: Leaving directory `/home/anoop/beagleboard-default-u-boot-mainline'
> make: *** [beagle] Error 1

[dzu at pollux u-boot-testing (master)]$ grep CONFIG_ARM `grep -l CONFIG_POST include/configs/*`
[dzu at pollux u-boot-testing (master)]$ 

So there is no arm board in mainline using the POST framwork.  Feel free
to fix all problems until it works ;)

Cheers
  Detlev

-- 
Indeed, the author firmly believes that the best serious work is also
good fun.   We needn't apologize if we enjoy doing research.
                                        -- Donald Knuth
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de

      reply	other threads:[~2010-03-22 16:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19  8:51 [U-Boot] u-boot POST Sasi, Anoop IN BLR SISL
2010-03-22 16:09 ` Detlev Zundel [this message]

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=m2pr2ws5gu.fsf@ohwell.denx.de \
    --to=dzu@denx.de \
    --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