From: "Cédric Le Goater" <clg@kaod.org>
To: Joel Stanley <joel@jms.id.au>, Shay Slobodkin <shays@mellanox.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Flashing U-Boot using DediProg(R) on Aspeed AST2500 EVB
Date: Fri, 17 Jun 2016 07:52:43 +0200 [thread overview]
Message-ID: <5763902B.9050106@kaod.org> (raw)
In-Reply-To: <CACPK8Xft-LvtjE9gQ7a0WD+5kD_wLfOYiBfCjoytHD3huWg7LA@mail.gmail.com>
On 06/17/2016 07:32 AM, Joel Stanley wrote:
> Hi Shay,
>
> On Wed, Jun 15, 2016 at 9:39 PM, Shay Slobodkin <shays@mellanox.com> wrote:
>> Recently we had some problems with our AST2500 EVB U-Boot.
>>
>> Had several systems gone bad.
>>
>> We want to use the DediProg® tool in order to recover.
>>
>> If you have used this tool, could you please explain briefly how to use it
>> with Aspeed AST2500 EVB?
>
> I've not done this myself on the evb.
>
> Looking at the board, you want header J70 is for the ast2500 boot
> flash. It's a 5 pin connector on the south west area of the board. The
> pins are labeled in the order: CS0, Clock, MOSI, MISO, Ground.
Yes. It works pretty well from a raspberry pi. I also have used a
Flashcat programmer.
You should make sure that the board is not booting from the flash
module. For that you need to unselect the flash chip, CS0 on header J44.
> If you need further help perhaps send a photo of your programmer and
> whatever cables it came with.
and one of your board perhaps. With details of what is around the
flash.
Cheers,
C.
> Cheers,
>
> Joel
>
next prev parent reply other threads:[~2016-06-17 5:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 5:32 Flashing U-Boot using DediProg(R) on Aspeed AST2500 EVB Joel Stanley
2016-06-17 5:52 ` Cédric Le Goater [this message]
2016-06-23 17:34 ` Rick Altherr
2016-06-27 8:44 ` Shay Slobodkin
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=5763902B.9050106@kaod.org \
--to=clg@kaod.org \
--cc=joel@jms.id.au \
--cc=openbmc@lists.ozlabs.org \
--cc=shays@mellanox.com \
/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.