<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Adam,<br>
<br>
as long as the UEFI is still functional, you can run a tool to
update the firmware. unfortunately the ones that have the firmware
corrupted can not be recovered without flashing via the SPI header.<br>
<br>
we have already started plans to add a jumper to the board to allow
the firmware to be reset to factory defaults. if we had done this on
the current design, we could have avoided this situation....<br>
<br>
Dave<br>
<br>
<div class="moz-cite-prefix">On 08/14/2014 10:42 AM, Adam Goode
wrote:<br>
</div>
<blockquote
cite="mid:CADN=WdoMPqvwyERuNQpD8V4_22iusdA1vnvcadTdPY5h=eHDSg@mail.gmail.com"
type="cite">
<p dir="ltr">Can these boards do self-flashing? Like with the
flashrom tool?</p>
<p dir="ltr">It would be nice to have future firmware updates
available and not need an external programmer.<br>
</p>
<p dir="ltr">Adam</p>
<div class="gmail_quote">On Aug 14, 2014 11:37 AM, "Hawley, John"
<<a moz-do-not-send="true"
href="mailto:john.hawley@intel.com">john.hawley@intel.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
If you have a SPI programmer that can do 1.8v (dediprog for
instance), you can do the flashing yourself, but as I have
been led to believe, a 3.3v spi flasher won't work. You may
need to talk to contact CircuitCo and send it back.<br>
<br>
If you do have something like a dediprog, let me know and I'll
get you a firmware package to flash onto the board, and what
you need to connect and such.<br>
<br>
- John<br>
<br>
> -----Original Message-----<br>
> From: <a moz-do-not-send="true"
href="mailto:elinux-minnowboard-bounces@lists.elinux.org">elinux-minnowboard-bounces@lists.elinux.org</a>
[mailto:<a moz-do-not-send="true" href="mailto:elinux-">elinux-</a><br>
> <a moz-do-not-send="true"
href="mailto:minnowboard-bounces@lists.elinux.org">minnowboard-bounces@lists.elinux.org</a>]
On Behalf Of Lasse Kaila<br>
> Sent: Thursday, August 14, 2014 1:04 AM<br>
> To: <a moz-do-not-send="true"
href="mailto:elinux-minnowboard@lists.elinux.org">elinux-minnowboard@lists.elinux.org</a><br>
> Subject: Re: [MinnowBoard] Minnowboard Max no longer
booting to UEFI<br>
> Shell<br>
><br>
> Bryan Smith <a class="moz-txt-link-rfc2396E" href="mailto:bryan@..."><bryan@...></a> writes:<br>
><br>
> ><br>
> > Hey Dave,<br>
> ><br>
> > I actually started looking at a flyswatter already
as I figured that<br>
> > this was the case. Just wanted to report the issue.<br>
> ><br>
> > Thanks,<br>
> ><br>
> > Bryan<br>
> > > Bryan,<br>
> > ><br>
> > > this is the second report from an early adopter
with this issue. it<br>
> > > appears to be a corruption of the UEFI firmware
and appears to be<br>
> > > software related.<br>
> > > we are<br>
> > > looking into it now. the only way to fix this
is to reflash the UEFI<br>
> > > firmware via the SPI header.<br>
> > ><br>
><br>
> Hi,<br>
><br>
> It seems we have a similar problem. Out of the two boards
we have, the first<br>
> one stopped working yesterday. Both blue LEDs are lit,
but there's no video<br>
> output at all, USB and Ethernet are also dead.<br>
><br>
> What procedure do you recommend, should we return the
board or is it<br>
> possible to do this reflash? I couldn't find any
instructions or firmware<br>
> for the MAX board anywhere on Intel's site.<br>
><br>
> On another note, I had to go through several monitors
until I found one that<br>
> would accept the video signal output by the board
(apparently it's 720p @<br>
> 60Hz). Perhaps a more universal video mode as default
would be more<br>
> useful?<br>
><br>
> _______________________________________________<br>
> elinux-MinnowBoard mailing list<br>
> <a moz-do-not-send="true"
href="mailto:elinux-MinnowBoard@lists.elinux.org">elinux-MinnowBoard@lists.elinux.org</a><br>
> <a moz-do-not-send="true"
href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard"
target="_blank">http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a><br>
_______________________________________________<br>
elinux-MinnowBoard mailing list<br>
<a moz-do-not-send="true"
href="mailto:elinux-MinnowBoard@lists.elinux.org">elinux-MinnowBoard@lists.elinux.org</a><br>
<a moz-do-not-send="true"
href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard"
target="_blank">http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
elinux-MinnowBoard mailing list
<a class="moz-txt-link-abbreviated" href="mailto:elinux-MinnowBoard@lists.elinux.org">elinux-MinnowBoard@lists.elinux.org</a>
<a class="moz-txt-link-freetext" href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard">http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a>
</pre>
</blockquote>
<br>
</body>
</html>