public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@de.bosch.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 8/9] MX53: Add support to ESG ima3 board
Date: Wed, 22 Feb 2012 12:46:16 +0100	[thread overview]
Message-ID: <4F44D588.50503@de.bosch.com> (raw)
In-Reply-To: <4F44C76A.6070000@denx.de>

On 22.02.2012 11:46, Stefano Babic wrote:
> On 22/02/2012 11:30, Dirk Behme wrote:
>> On 22.02.2012 11:24, Stefano Babic wrote:
>> ...
>>> +BOOT_FROM      nor
>> I assume that you have tested this and it works with the imximage?
> 
> I have not any problem with the current imximage, so I am quite
> confused. 

Hmm, yes, this is quite confusing :(

> Agree that you are fixing a bug, but I have not understood why
> I have not seen any issue on my board, a MX53 using V2 image header.
> 
> My board boots flawlessly from the NOR interface. I will try to
> investigate why and, of course, I will be able to test your patch on my
> board.
> 
> Can you confirm that your board does not boot ? 

Yes, removing the imximage fix stops the board from booting. 
Unfortunately it's hard to debug how the boot ROM deals with the header 
information. So either it works, or not, but there is little chance to 
debug :(

For testing, taking the SabreLite (mx6qsabrelite), switching it to NOR 
[1] and then compiling it without and with my imximage fix, results in 
the following difference in the header (disassembly of u-boot.imx):

-      20:      177ff800
+      20:      177fec00

At offset 0x20 in the header, this is the target address in the 
destination memory. Having a header with the size of 0x400 (like here) 
the destination address should be TEXT_BASE - 0x400 (header size) - 
0x1000 (NOR offset), i.e. 0x17800000 - 0x1400. So my understanding is 
that 0x177fec00 is correct for NOR, while 0x177ff800 is valid for all 
FLASH_OFFSET_STANDARD devices.

Best regards

Dirk

[1]

board/freescale/mx6qsabrelite/imximage.cfg
BOOT_FROM	nor

  reply	other threads:[~2012-02-22 11:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 10:24 [U-Boot] [PATCH 1/9] Define UART4 and UART5 base addresses Stefano Babic
2012-02-22 10:24 ` [U-Boot] [PATCH 2/9] NET: fec_mxc.c: Add support for MII for MX5 SOCs Stefano Babic
2012-05-15 12:39   ` Dirk Behme
2012-06-12 17:02     ` Stefano Babic
2012-02-22 10:24 ` [U-Boot] [PATCH 3/9] NET: fec_mxc.c: Add a way to disable auto negotiation Stefano Babic
2012-02-22 10:24 ` [U-Boot] [PATCH 4/9] MX5: Add definitions for SATA controller Stefano Babic
2012-02-22 10:24 ` [U-Boot] [PATCH 5/9] SATA: check for return value from sata functions Stefano Babic
2012-02-22 10:24 ` [U-Boot] [PATCH 6/9] MX53: add function to set SATA clock to internal Stefano Babic
2012-02-22 10:24 ` [U-Boot] [PATCH 7/9] SATA: add driver for MX5 / MX6 SOCs Stefano Babic
2012-02-22 10:24 ` [U-Boot] [PATCH 8/9] MX53: Add support to ESG ima3 board Stefano Babic
2012-02-22 10:30   ` Dirk Behme
2012-02-22 10:46     ` Stefano Babic
2012-02-22 11:46       ` Dirk Behme [this message]
2012-02-22 10:24 ` [U-Boot] [PATCH 9/9] MX53: mx53loco: Add SATA support Stefano Babic
2012-02-23 15:40   ` Jason Hui

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=4F44D588.50503@de.bosch.com \
    --to=dirk.behme@de.bosch.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