All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@kaod.org>
To: openbmc@lists.ozlabs.org
Subject: Re: Flashing Image using 'pflash' Tool
Date: Mon, 12 Nov 2018 19:43:10 +0100	[thread overview]
Message-ID: <e235eedb-e62f-13d2-5beb-921678797d8b@kaod.org> (raw)
In-Reply-To: <CAE33tLEFXcushQzAthRY6LNMLfFh9YSVySPFudn+KmSHTqXUYw@mail.gmail.com>

On 11/8/18 11:04 AM, AKASH G J wrote:
> I tried to flash kernel image /fitImage.bin/ to the flash memory address /0x20100000/ using the following command.


If you are trying to flash a custom BMC kernel only and bypassing 
the standard procedure to do so, you should update the correct
MTD device with dd or flashcp.

	# cat /proc/mtd 
	dev:    size   erasesize  name
	mtd0: 02000000 00010000 "bmc"
	mtd1: 00060000 00010000 "u-boot"
	mtd2: 00020000 00010000 "u-boot-env"
	mtd3: 00440000 00010000 "kernel"
	mtd4: 01740000 00010000 "rofs"
	mtd5: 00400000 00010000 "rwfs"
	mtd6: 02000000 00010000 "pnor"

I don't have a zaius but it should be roughly similar.  

Cheers,

C.


> root@zaius:/var# /pflash -a 0x20100000 -f -p fitImage.bin /
> 
> It exited with following error.
> 
> /About to program "fitImage.bin" at 0x20100000..0x20371e20 !
> Programming & Verifying...
> [                                                  ] 0%Flash write error 3 for chunk at 0x20100000/
> /
> /
> Please someone help to resolve the problem.
> //
> 
> Thanks and Regards ,
> 
> Akash G J

      parent reply	other threads:[~2018-11-12 21:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 10:04 Flashing Image using 'pflash' Tool AKASH G J
2018-11-09  3:51 ` Lei YU
2018-11-09  8:56   ` AKASH G J
2018-11-12 12:21     ` AKASH G J
2018-11-12 18:37       ` Adriana Kobylak
2018-11-12 18:43 ` Cédric Le Goater [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=e235eedb-e62f-13d2-5beb-921678797d8b@kaod.org \
    --to=clg@kaod.org \
    --cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.