public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Issues developing standalone applications
Date: Sat, 23 Mar 2013 01:17:08 +0100	[thread overview]
Message-ID: <20130323001708.846CE200048@gemini.denx.de> (raw)
In-Reply-To: <CAKZOPtKY-WJsZf_PpoC4gV_8Y8PvHSGJm4hhah2Znq=rvGMYxQ@mail.gmail.com>

Dear Lucas Endres,

In message <CAKZOPtKY-WJsZf_PpoC4gV_8Y8PvHSGJm4hhah2Znq=rvGMYxQ@mail.gmail.com> you wrote:
>
> I know it's an issue on the NAND initialization, but I am neither very
> familiar to the U-Boot code nor to debugging errors. What follows is the
> console output I get when trying to run nand_init_chip() from my standalone
> application:

You are not supposed to do things like that. For standalone
applications, ther eis only a very limited, well-defined set of
functionality exported by U-Boot.  NAND access is not part of it.

> I need to run a badblocks test on the NAND device, and I successfully do it
> in the board initialization from within the U-Boot environment, but not
> from the standalone environment.

Why do you want to do it from a standalone application?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The only perfect science is hind-sight.

      reply	other threads:[~2013-03-23  0:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22 20:58 [U-Boot] Issues developing standalone applications Lucas Endres
2013-03-23  0:17 ` Wolfgang Denk [this message]

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=20130323001708.846CE200048@gemini.denx.de \
    --to=wd@denx.de \
    --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