All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: SARTRE Leo <lsartre@adeneo-embedded.com>
Cc: meta-freescale@yoctoproject.org,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-fsl-arm-extra][PATCH 1/2] u-boot-imx: update Congatec qmx6 support to bsp 4.0
Date: Tue, 18 Jun 2013 08:39:15 -0700	[thread overview]
Message-ID: <51C07F23.80108@boundarydevices.com> (raw)
In-Reply-To: <3465D313FDFB824F9A9C8CD24FA4F6BC0108CD2C@frontmail.adetel.com>

Hi Leo,

On 06/18/2013 07:27 AM, SARTRE Leo wrote:
>  > If you have your boot pins (or fuses) correctly setup and flash it to
>  > the correct offset, it should just boot, no?
>  >
>
> When I try to flash a mainline U-boot (that works when I write it in SD
> card)
> into the SPI NOR, the board doesn't boot.
> The binary that I flash is a non-padded Uboot and I place it at the
> beggining
> of the SPI NOR.
> It seems that the same issue occurs with the sabrelite board (see
> https://wiki.linaro.org/Boards/MX6QSabreLite).
>

This isn't an issue, it's a policy decision by Linaro because they
wanted to **force** SD card boot.

This Linaro hack programs SPI-NOR to override the fuses.

In other words, it too boots to SPI NOR.

>  > I don't understand why you say that mainline U-boot cannot boot from
>  > SPI NOR, but the old U-boot can.
>
> Maybe some bits of code maintained by Freescale were not pushed to the
> mainline of U-boot.
>

Can you boot with an erased SPI-NOR and a U-Boot on SD card?

If so, then your fuses are blown to select SD card boot.

Regards,


Eric


  parent reply	other threads:[~2013-06-18 15:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1371224103-1706-1-git-send-email-lsartre@adeneo-embedded.com>
2013-06-14 15:35 ` [meta-fsl-arm-extra][PATCH 1/2] u-boot-imx: update Congatec qmx6 support to bsp 4.0 SARTRE Leo
2013-06-17 17:28   ` Otavio Salvador
2013-06-18  7:12     ` SARTRE Leo
2013-06-18 12:04       ` Otavio Salvador
2013-06-18 12:47         ` SARTRE Leo
2013-06-18 13:32           ` Fabio Estevam
2013-06-18 13:53             ` SARTRE Leo
2013-06-18 14:00               ` Fabio Estevam
2013-06-18 14:27                 ` SARTRE Leo
2013-06-18 14:59                   ` SARTRE Leo
2013-06-18 15:05                     ` Fabio Estevam
2013-06-18 15:39                   ` Eric Nelson [this message]
2013-06-18 15:58                     ` SARTRE Leo
2013-06-18 16:25                       ` Eric Nelson
2013-06-18 17:26           ` Otavio Salvador
2013-06-18 17:35             ` Fabio Estevam
2013-06-18 17:48               ` Otavio Salvador
2013-06-18 17:51                 ` Fabio Estevam
2013-06-18 18:05                   ` Otavio Salvador
2013-06-18 18:14                     ` Fabio Estevam
2013-06-18 18:45                       ` Otavio Salvador
2013-06-19 13:51                         ` SARTRE Leo
2013-06-19 15:13                           ` Otavio Salvador
2013-06-19 15:47                             ` SARTRE Leo
2013-06-19 16:31                               ` Otavio Salvador
2013-06-14 15:35 ` [meta-fsl-arm-extra][PATCH 2/2] linux-imx-3.0.35: " SARTRE Leo

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=51C07F23.80108@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=lsartre@adeneo-embedded.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.