mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Thomas Mayer <thomas.mayer@telemotive.de>
To: barebox@lists.infradead.org
Subject: Re: Install barebox on target
Date: Wed, 2 Mar 2011 11:17:45 +0100	[thread overview]
Message-ID: <4D6E1949.3050603@telemotive.de> (raw)
In-Reply-To: <20110228081925.GG2667@jasper.tkos.co.il>

Hi,
good know, I will try that.

regards
Thomas


Am 28.02.2011 09:19, schrieb Baruch Siach:
> Hi Sascha, Thomas,
>
> On Mon, Feb 28, 2011 at 10:09:23AM +0200, Baruch Siach wrote:
>   
>> On Mon, Feb 28, 2011 at 08:40:53AM +0100, Sascha Hauer wrote:
>>     
>>> On Fri, Feb 25, 2011 at 05:08:10PM +0100, Thomas Mayer wrote:
>>>       
>>>> thanks, I will try that.
>>>> Today I got our real hardware. It consists of the freescale cpu board, a
>>>> custom baseboard with a different display.
>>>> With that I was able to start barebox completely. Network works fine,
>>>> but I can't access the nand memory, because barebox doesn't find it at
>>>> startup. I added all possible nand drivers to barebox, but it still
>>>> doesn't work.
>>>>
>>>> Any idea?
>>>>
>>>> --------------------------------------- u-boot output
>>>> -----------------------------------------
>>>> U-Boot 2009.08 (Jan 13 2010 -
>>>>
>>>> Page Geometry     :
>>>> 4096+218
>>>>         
>>> This will cause problems. I never had a nand with 4k block size and I
>>> doubt it will work out of the box. I don't know if that's the reason
>>> barebox does not find no nand device at all though.
>>>       
>> I'm also seeing problems with a 4k page size (+218 OOB) SLC NAND flash of 
>> Micron on i.MX25. Barebox does identify the flash chip, but can't read it 
>> correctly.  I'm investigating the issue. So far I've found that the OOB area 
>> is read as 0x00s instead of 0xffs, even for good blocks. This makes Barebox to 
>> mark the whole flash as bad blocks.
>>
>> The Linux kernel, however, seems to work correctly with this flash when 
>> applying a small fix to use the correct(?) nand_ecclayout.
>>     
> I should also add the booting from this NAND with Barebox works perfectly. I 
> used the kernel to program Barebox into the flash.
>
> baruch
>
>   
>>>> --------------------------------------- barebox output
>>>> ------------------------------------------
>>>> barebox 2011.02.0 (Feb 25 2011 - 16:35:47)
>>>>
>>>> Board: Freescale MX35 3Stack
>>>> No NAND device found!!!
>>>> cfi_probe: cfi_flash base: 0xa0000000 size: 0x04000000
>>>> mc13892-i2c@mc13892-i2c0: PMIC ID: 0x000045d0 [Rev: 2.0a]
>>>> smc911x: no smc911x found on 0xb6000000 (byte_test=0x00f000f0)
>>>> imx-ipu-fb@imx-ipu-fb0: i.MX Framebuffer driver
>>>> mc13892-i2c@mc13892-i2c0: revision: 0x45d0
>>>> i.MX35 PDK CPU board version 1.
>>>> Malloc space: 0x86f00000 -> 0x87f00000 (size 16 MB)
>>>> Stack space : 0x86ef8000 -> 0x86f00000 (size 32 kB)
>>>> Open /dev/env0 No such file or directory
>>>> no valid environment found on /dev/env0. Using default environment
>>>> running /env/bin/init...
>>>>
>>>>
>>>>
>>>> regards
>>>> Thomas
>>>>
>>>>
>>>>
>>>> Am 25.02.2011 16:06, schrieb Sascha Hauer:
>>>>         
>>>>> On Fri, Feb 25, 2011 at 10:15:01AM +0100, Thomas Mayer wrote:
>>>>>   
>>>>>           
>>>>>> Hi Sascha,
>>>>>>
>>>>>> That's not quite correct. When you use the debug + personality board you
>>>>>> can boot directly from a mmc-card which contains bootloader, kernel and
>>>>>> rootfs without modifications. Only if you use the single personality
>>>>>> board, you have to modify die board a little bit.
>>>>>>     
>>>>>>             
>>>>> Ah, ok. I didn't know that.
>>>>>
>>>>>   
>>>>>           
>>>>>> Thanks for your short introduction. I tried to run the barebox image
>>>>>> with u-boot and it seems to work. But after I get the following output
>>>>>> barebox stops and do nothing.
>>>>>>     
>>>>>>             
>>>>> That's a bug in the support for multiple network devices. Please pull
>>>>> the -next branch again, then it should work.
>>>>>
>>>>> Sascha
>>>>>           
>   


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

  reply	other threads:[~2011-03-02 10:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 13:08 Thomas Mayer
2011-02-24 16:04 ` Sascha Hauer
2011-02-25  9:15   ` Thomas Mayer
2011-02-25 15:06     ` Sascha Hauer
2011-02-25 16:08       ` Thomas Mayer
2011-02-28  7:40         ` Sascha Hauer
2011-02-28  8:09           ` Baruch Siach
2011-02-28  8:19             ` Baruch Siach
2011-03-02 10:17               ` Thomas Mayer [this message]
2011-03-02 10:39                 ` Baruch Siach

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=4D6E1949.3050603@telemotive.de \
    --to=thomas.mayer@telemotive.de \
    --cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox