Antwort: Re: Antwort: Re: Antwort: Re: Antwort: Re: barebox image size

Christian Kapeller christian.kapeller at
Mon Jul 16 10:25:57 EDT 2012

On 07/16/2012 03:52 PM, christian.buettner at wrote:
> Thx for the hint.
> What i don't understand is that barebox boots from nand but the
> environement can't..

Good point. In any case the driver isn't able to recognize your nand
device. I see from you supplied code snipplets, that your barebox is
at least two weeks old. Maybe you use the upstream tree, as maybe there
are already fixes for imx53 nand flash.

Also you may want to activate mtd debugging:


for example to  your include/linux/mtd/mtd.h file. (Those are config
settings, but they don't appear in any Kconfig file, hence supply them

good luck.

>> 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 at 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

Christian Kapeller
cmotion GmbH
Kriehubergasse 16
1050 Wien / Austria

christian.kapeller at
Phone: +43 1 789 1096 38

More information about the barebox mailing list