public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Taylor <ttaylor.tampa@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] DA850EVM with USE_NAND config does not pad the AIS file
Date: Sat, 26 Apr 2014 13:34:58 -0400	[thread overview]
Message-ID: <535BEE42.3050105@gmail.com> (raw)
In-Reply-To: <1398514631-23956-11-git-send-email-marc.zyngier@arm.com>

I'm a U-Boot newbie so please feel free to correct how I'm reporting 
this issue..

I recently downloaded the 2014.04-rc3 snapshot to build U-Boot for my 
custom DA850-based board.  The only change was to add a new target 
"dav850evm_nand" in boards.cfg with the added parameter "USE_NAND".

The resulting AIS file was programmed into EVM-compatible NAND using 
standard sfh_OMAP-L138 method.

The board failed to boot, and stayed in a loop printing the SPL console 
message repeatedly.

After some debugging with CCS 5.5 and an XDS100v2, I found that 
incorrect code was being loaded into the 0xc108000 RAM destination. The 
da850evm.h file defines CONFIG_SYS_NAND_U_BOOT_OFFS as 0x28000, which 
corresponds to an AIS offset of 0x8000 but the u-boot header did not 
appear there in the AIS file.  A search revealed that the Makefile 
catenated u-boot immediately after the SPL without any padding.

Further investigation revealed that the target Makefile needs 
CONFIG_SPL_MAX_SIZE to be defined as 0x8000 in order for the padding to 
be performed properly; however, this constant was apparently deleted 
during a series of changes in April, 2013 to accommodate separate code 
and BSS size limits for another target.  In its place, 
CONFIG_SPL_MAX_FOOTPRINT was defined as 32768.   Unfortunately, the 
da850evm Makefile does not refer to this constant.

To solve the problem, I added the following 2 lines in my 
custom-modified da850evm.h:
#define CONFIG_SPL_PAD_TO    0x8000
#define CONFIG_SPL_MAX_SIZE  0x8000

although the first line may not be strictly required.  This solved the 
problem and allowed the board to boot.

Doesn't this mean that other similar targets may be broken?

How can I assist with contributing the patch to fix this?  One problem I 
have is that I only have an EXP, not an EVM board.  My custom target 
board shares some features with the EVM such as NOR and NAND memory, but 
other things are different like the use of a fixed PHY.  This makes it 
impossible for me to completely verify a da850evm build.

I would like to see more target configurations available for the 
DA850EVM but it seems like development for this has stopped.  NAND boot 
was a simple change, but adding USB support required me to copy & paste 
code from the da830evm target.  Are there any future plans to do this, 
or will I need to do this development for my custom board only?

Tom Taylor

  reply	other threads:[~2014-04-26 17:34 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-26 12:17 [U-Boot] [PATCH v4 00/10] ARMv7: add PSCI support to U-Boot Marc Zyngier
2014-04-26 12:17 ` [U-Boot] [PATCH v4 01/10] ARM: HYP/non-sec: move switch to non-sec to the last boot phase Marc Zyngier
2014-04-26 12:17 ` [U-Boot] [PATCH v4 02/10] ARM: HYP/non-sec: add a barrier after setting SCR.NS==1 Marc Zyngier
2014-04-26 12:17 ` [U-Boot] [PATCH v4 03/10] ARM: non-sec: reset CNTVOFF to zero Marc Zyngier
2014-04-26 12:17 ` [U-Boot] [PATCH v4 04/10] ARM: add missing HYP mode constant Marc Zyngier
2014-04-26 12:17 ` [U-Boot] [PATCH v4 05/10] ARM: HYP/non-sec: add separate section for secure code Marc Zyngier
2014-04-26 12:17 ` [U-Boot] [PATCH v4 06/10] ARM: HYP/non-sec: allow relocation to secure RAM Marc Zyngier
2014-05-02 20:30   ` Jon Loeliger
2014-05-02 21:03     ` Jon Loeliger
2014-05-07  7:05       ` Marc Zyngier
2014-05-07 14:28         ` Jon Loeliger
2014-05-07  6:51     ` Marc Zyngier
2014-05-07 14:30       ` Jon Loeliger
2014-06-09 19:06   ` Albert ARIBAUD
2014-04-26 12:17 ` [U-Boot] [PATCH v4 07/10] ARM: HYP/non-sec: add generic ARMv7 PSCI code Marc Zyngier
2014-04-26 12:17 ` [U-Boot] [PATCH v4 08/10] ARM: HYP/non-sec: add the option for a second-stage monitor Marc Zyngier
2014-04-26 12:17 ` [U-Boot] [PATCH v4 09/10] ARM: convert arch_fixup_memory_node to a generic FDT fixup function Marc Zyngier
2014-04-26 12:17 ` [U-Boot] [PATCH v4 10/10] ARM: HYP/non-sec/PSCI: emit DT nodes Marc Zyngier
2014-04-26 17:34   ` Tom Taylor [this message]
2014-05-05 13:09     ` [U-Boot] DA850EVM with USE_NAND config does not pad the AIS file Tom Rini
2014-05-02 20:13   ` [U-Boot] [PATCH v4 10/10] ARM: HYP/non-sec/PSCI: emit DT nodes Jon Loeliger
2014-05-07  6:38     ` Marc Zyngier
2014-04-26 14:24 ` [U-Boot] [PATCH v4 00/10] ARMv7: add PSCI support to U-Boot Dennis Gilmore
2014-04-26 16:31   ` Marc Zyngier
2014-04-26 21:34     ` Dennis Gilmore
2014-05-05 14:34 ` Jon Loeliger
2014-05-07  7:08   ` Marc Zyngier
2014-05-25 14:08 ` Albert ARIBAUD
2014-06-08  7:57   ` Albert ARIBAUD
2014-06-09  8:12     ` Marc Zyngier
2014-06-09  9:34       ` Albert ARIBAUD
2014-06-10  8:36 ` Albert ARIBAUD
2014-06-10  9:06   ` [U-Boot] [PATCH v4 00/10] ARMv7: add PSCI support to U-Boot - *not* applied Albert ARIBAUD
2014-06-10  9:11     ` Albert ARIBAUD
  -- strict thread matches above, loose matches on Subject: below --
2014-05-06  8:07 [U-Boot] DA850EVM with USE_NAND config does not pad the AIS file Christian Riesch
2014-05-06 11:30 Christian Riesch
2014-05-06 14:46 ` Heiko Schocher
2014-05-06 16:52   ` Tom Taylor
2014-05-06 18:41   ` Christian Riesch

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=535BEE42.3050105@gmail.com \
    --to=ttaylor.tampa@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