All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Guillaume Fournier" <gfournier@brioconcept.com>
To: "'Gary Thomas'" <gary@mlbassoc.com>, <meta-freescale@yoctoproject.org>
Subject: Re: Unable to get u-boot running on i.MX6 SABRE for Smart Devices Eval Board
Date: Wed, 5 Nov 2014 11:41:21 -0500	[thread overview]
Message-ID: <00c201cff917$54ccb6a0$fe6623e0$@brioconcept.com> (raw)
In-Reply-To: <545A4E9A.8060106@mlbassoc.com>

>> I'm now using the cfimager instead of the mfgtool as suggested by Daiane.
I am using u-boot.imx as follow:
>> cfimager -f u-boot.imx -raw -offset 1024 -skip 1024 -d d
>>
>> If I use an .sdcard file from a Yocto build like this:
>> cfimager -f core-image-base-imx6dlsabresd.sdcard -raw -d d
>>
>> That works.  If I'm using, *from the same build*, the u-boot.imx like
this:
>> cfimager -f u-boot.imx -raw -offset 1024 -skip 1024 -d d
>>
>> It doesn't!  Of course, if I use my custom built u-boot, it doesn't
either.  I'm starting to believe that cfimager parameter are the culprit.
>
>I'd be suspicious of '-offset 1024' - I doubt that you need both.
>Give it a try - leave out either the 'offset' or 'skip' options

Ok, there was a problem with the -skip option.  Removing it altogether
solves the problem for the u-boot.imx coming from a Yocto build:
cfimager -f u-boot-from-Yocto-build.imx -raw -offset 1024 -d d

However, the u-boot.imx coming from u-boot-fslc cross-compiled with a Yocto
installed toolchain doesn't.  Back to square one...




  parent reply	other threads:[~2014-11-05 16:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 22:44 Unable to get u-boot running on i.MX6 SABRE for Smart Devices Eval Board Guillaume Fournier
2014-11-05  0:03 ` Fabio Estevam
2014-11-05 14:38   ` Guillaume Fournier
2014-11-05 14:52     ` Wally Yeh
2014-11-05 15:24       ` Guillaume Fournier
2014-11-05 14:56     ` Daiane Angolini
2014-11-05 15:37       ` Guillaume Fournier
2014-11-05 15:45         ` Otavio Salvador
2014-11-05 16:05           ` Guillaume Fournier
2014-11-05 15:42     ` Otavio Salvador
2014-11-05 15:50       ` Guillaume Fournier
2014-11-05 15:54         ` Otavio Salvador
2014-11-05 15:59           ` Wally Yeh
2014-11-05 16:15           ` Guillaume Fournier
2014-11-05 16:21             ` Gary Thomas
2014-11-05 16:40               ` Otavio Salvador
2014-11-05 16:41               ` Guillaume Fournier [this message]
2014-11-05  0:23 ` Eric Bénard
2014-11-05 14:51   ` Guillaume Fournier
2014-11-05 17:25     ` Eric Bénard
  -- strict thread matches above, loose matches on Subject: below --
2014-11-05 20:43 Guillaume Fournier
2014-11-05 21:04 ` Otavio Salvador
2014-11-05 21:50   ` Guillaume Fournier
2014-11-06 17:31 Guillaume Fournier
2014-11-06 17:47 ` Otavio Salvador
2014-11-06 17:53   ` Gary Thomas
2014-11-06 17:56     ` Otavio Salvador

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='00c201cff917$54ccb6a0$fe6623e0$@brioconcept.com' \
    --to=gfournier@brioconcept.com \
    --cc=gary@mlbassoc.com \
    --cc=meta-freescale@yoctoproject.org \
    /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.