public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: DaveKucharczyk <david.kucharczyk@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] MKIMAGE u-boot.imx build error
Date: Wed, 29 Oct 2014 06:52:26 -0700 (MST)	[thread overview]
Message-ID: <1414590746597-193874.post@n7.nabble.com> (raw)
In-Reply-To: <CAPnjgZ2O2yWaiPMt+9aM3jQv2zTqUFaG9QPJYkTc8h_XOywEQw@mail.gmail.com>

Simon, thank you for your help.

Simon Glass-3 wrote
> BTW best not to have this in your sig when sending to a public mailing
> list.

I have no control of over my company's email signature so I switched my
subscription to use gmail.

Simon Glass-3 wrote
> There are only 3 places in mkimage.c which call usage() so you should
> be able to track which one it is. Probably building with V=1 will show
> you the mkimage command line you are using. 

I was able to build using V=1 and noticed the entry point,
CONFIG_SYS_TEXT_BASE, wasn't defined in include/configs/mx53_xxx.h file. We
previously had it defined in /board/freescale/mx53_xxx/config.mk. Now
everything builds without error. 

But?I do not get serial output. I really need a small victory and see some
life out of the board. 

Here?s what I think is necessary to get serial output to console? 

1.	At minimum the uart setup in /board/freescale/mx53_xxx/mx53_xxx.c
2.	Version, boot device and DCD setup in
/board/freescale/mx53_xxx/imximage.cfg
3.	Minor changes to build successfully in /include/configs/mx53_xxx.h

I?ve ported flash_header.S to imximage.cfg.
I?ve moved our old /board/freescale/mx53_xxx/mx53_xxx.c to the new u-boot
directory, setup the pads using the new nomenclature and modified the
library includes to use the new ones. 
I?ve moved include/configs/mx53_xxx.h file to the new u-boot directory and
made the necessary edits to build successfully. 

I?ve triple checked the pads and flash header. I dd the resulting,
non-padded, u-boot.imx image to sd card by ?dd if=u-boot.imx of=/dev/sdd
seek=2 && sync?, but I get no life.

I?m stuck at the moment and hoping someone has some advice as to what I may
be missing or doing wrong. 

Best,
Dave



--
View this message in context: http://u-boot.10912.n7.nabble.com/MKIMAGE-u-boot-imx-build-error-tp193606p193874.html
Sent from the U-Boot mailing list archive at Nabble.com.

  reply	other threads:[~2014-10-29 13:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 18:18 [U-Boot] MKIMAGE u-boot.imx build error Kucharczyk, David
2014-10-28  1:04 ` Simon Glass
2014-10-29 13:52   ` DaveKucharczyk [this message]
2014-10-29 14:18     ` Fabio Estevam
2014-10-29 14:34       ` DaveKucharczyk
2014-10-29 21:44         ` Fabio Estevam
2014-10-29 17:02     ` Stefano Babic

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=1414590746597-193874.post@n7.nabble.com \
    --to=david.kucharczyk@gmail.com \
    --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