mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Calvin Johnson <linux.cj@gmail.com>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Is there any way to dump more than 0x100 bytes from nand flash?
Date: Mon, 27 Aug 2012 09:59:59 +0530	[thread overview]
Message-ID: <CAEhpT-UoCsSncnEe8TGHQRzF1rzdDE0hBB1KhAu4fCiMxhRykg@mail.gmail.com> (raw)
In-Reply-To: <CAA4bVAHSMjQDgxHngj_2EGwfg2Me8_LVW0CwMkR-vjmZcoqfVQ@mail.gmail.com>

On Fri, Aug 24, 2012 at 9:32 PM, Antony Pavlov <antonynpavlov@gmail.com> wrote:
> On 24 August 2012 18:19, Calvin Johnson <linux.cj@gmail.com> wrote:
>> Hi,
>>
>> In U-Boot there is "nand dump <address>" command which is very useful
>> to check the contents of the NAND page and OOB area.
>>
>> I tried searching for an alternative in Barebox, and found that we can
>> use some thing like "md -b -s /dev/nand0.barebox.bb". But this will
>> dump only 0x100 bytes. In order to increase the size, I need to
>> compile again.
>> Is there any way to dump more bytes from the NAND flash and from
>> different blocks/pages?
>>
>
> please try "md -b -s /dev/nand0.barebox.bb <dump offset>+<dump size>",
> e.g.
>   md -b -s /dev/nand0.barebox.bb 0+0x200

Thanks a lot Antony. It worked out. :)-

>
>> How are the experts working with this?
>>
>
> Sorry, I'm not an expert :)))

:)- For me you are an expert.

> --
> Best regards,
>   Antony Pavlov

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

      reply	other threads:[~2012-08-27  4:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24 14:19 Calvin Johnson
2012-08-24 16:02 ` Antony Pavlov
2012-08-27  4:29   ` Calvin Johnson [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=CAEhpT-UoCsSncnEe8TGHQRzF1rzdDE0hBB1KhAu4fCiMxhRykg@mail.gmail.com \
    --to=linux.cj@gmail.com \
    --cc=antonynpavlov@gmail.com \
    --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