mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: christian.buettner@rafi.de
To: Christian Kapeller <christian.kapeller@cmotion.eu>
Cc: barebox@lists.infradead.org
Subject: Antwort: Re: Antwort: Re: Antwort: Re: Antwort: Re: barebox image size
Date: Mon, 16 Jul 2012 15:52:32 +0200	[thread overview]
Message-ID: <OF4671681E.10E4C59C-ONC1257A3D.004BF387-C1257A3D.004C38C5@o0802.rafi.inhouse> (raw)
In-Reply-To: <50041B84.9080707@cmotion.eu>


[-- Attachment #1.1: Type: text/plain, Size: 1962 bytes --]

Thx for the hint. 
What i don't understand is that barebox boots from nand but the 
environement can't..



Von:    Christian Kapeller <christian.kapeller@cmotion.eu>
An:     christian.buettner@rafi.de, 
Kopie:  Sascha Hauer <s.hauer@pengutronix.de>, barebox@lists.infradead.org
Datum:  16.07.2012 15:47
Betreff:        Re: Antwort: Re: Antwort: Re: Antwort: Re: barebox image 
size



> I flashed from 0x0 to 0x7FFFF (image size: 479K).
> I flashed the environment image (image size: 3K) from 0x80000 to 0xFFFFF
> and changed the config code from barebox/environs/common/config to:
> 
> ...
> nand_parts="512k(barebox)ro,768k(bareboxenv),4M(kernel),120M(root)"
> ...
> 
> Barebox can boot now but the startup log says:
> barebox 2012.03.0-dirty (Jul 16 2012 - 09:01:01)
> 
> Board: i.MX53
> eth@eth0: got MAC address from EEPROM: *********************
> nand_get_flash_type: second ID read did not match ef,ef against c0,c0
> No NAND device found (-19)!
> Malloc space: 0x7df00000 -> 0x7fefffff (size 32 MB)
> Stack space : 0x7def8000 -> 0x7df00000 (size 32 kB)
> Open /dev/env0 No such file or directory
> running /env/bin/init...
> not found
> barebox:/
> 
> How can i get the environment loaded?

Normally you would issue 'saveenv' which writes the environment to the
environment partition. On subsequent boots the environment will be loaded.

But the flash device on your board isn't detected by barebox, so you
will have to fix the detection first.

> nand_get_flash_type: second ID read did not match ef,ef against c0,c0

This line suggests, that the nand flash isn't working property. The line
is generated in drivers/mtd/nand/nand_base.c, after reading manufacturer
id and chip id two times, and checking them for equality.

Not only does your board different values for manufacturer and flash id
on first and second read, but they are also the same. manuf id=ef and
chip id=ef isn't plausible. Maybe you should check your hardware.

Regards
Christian


[-- Attachment #1.2: Type: text/html, Size: 2971 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2012-07-16 13:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16  8:37 christian.buettner
2012-07-16  8:54 ` Sascha Hauer
2012-07-16  9:15   ` Antwort: " christian.buettner
2012-07-16  9:20     ` Eric Bénard
2012-07-16  9:21     ` Antwort: " Sascha Hauer
2012-07-16  9:37       ` Antwort: " christian.buettner
2012-07-16 10:30         ` Sascha Hauer
2012-07-16 12:17           ` Antwort: " christian.buettner
2012-07-16 13:47             ` Christian Kapeller
2012-07-16 13:52               ` christian.buettner [this message]
2012-07-16 14:25                 ` Antwort: " Christian Kapeller
2012-07-16 14:30                   ` Antwort: " christian.buettner
2012-07-16 14:32                   ` Eric Bénard
2012-07-16 22:29             ` Antwort: Re: Antwort: Re: Antwort: " Marc Reilly
2012-07-17  9:58               ` Antwort: " christian.buettner
2012-07-17 10:44                 ` Marc Reilly
2012-07-17 10:49                   ` Antwort: " christian.buettner

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=OF4671681E.10E4C59C-ONC1257A3D.004BF387-C1257A3D.004C38C5@o0802.rafi.inhouse \
    --to=christian.buettner@rafi.de \
    --cc=barebox@lists.infradead.org \
    --cc=christian.kapeller@cmotion.eu \
    /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