<div dir="ltr">So I FOLLOWED the procedure to pass from 64 to 32. I think the system filled 2 lines of dots, when the screen goes black. I waited about a half hour but there was no sign of new action, so I tried to reboot. Now the board has not EUFI Shell. But it does have setup, where the third line says it is MNW2CRB1.86C.0071.R30.1408131324. I was wondering what coused this, and how I get the board on work again?.<br><br>Thanks<br></div><div class="gmail_extra"><br><div class="gmail_quote">2014-09-10 13:04 GMT-05:00 Hawley, John <span dir="ltr"><<a href="mailto:john.hawley@intel.com" target="_blank">john.hawley@intel.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I think there's some value in being explicit or otherwise we'll actually<br>
cause confusion. I.E. when you download the firmware and people see<br>
32-bit vs. 64-bit firmware in the same place will they always flash the<br>
right one? Part of the problem is there is no UI to these firmware<br>
flashers, they are command line utilities.<br>
<span class="HOEnZb"><font color="#888888"><br>
- John<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Wed, 2014-09-10 at 13:18 -0400, Adam Goode wrote:<br>
> I see the zip files already contain both EFI binaries. Assuming the<br>
> firmware updaters present some firmware selection UI, the<br>
> simplification I can see here is consolidating by putting both<br>
> firmware files into the same zip file. You could go further and<br>
> combine the release and debug versions as well, but that might be<br>
> unnecessary.<br>
><br>
><br>
> Thanks,<br>
><br>
> Adam<br>
><br>
><br>
> On Wed, Sep 10, 2014 at 11:45 AM, Darren Hart <<a href="mailto:dvhart@linux.intel.com">dvhart@linux.intel.com</a>> wrote:<br>
> > On 9/10/14, 8:22, "Adam Goode" <<a href="mailto:adam@spicenitz.org">adam@spicenitz.org</a>> wrote:<br>
> ><br>
> >>Does this mean that both files can just be put into place? If so,<br>
> >>could you update the distribution to include both and not worry about<br>
> >>what the current firmware is? It would simplify the process and<br>
> >>documentation.<br>
> ><br>
> > That strikes me as a pretty good suggestion.<br>
> ><br>
> > --<br>
> > Darren<br>
> ><br>
> >><br>
> >><br>
> >>Adam<br>
> >><br>
> >><br>
> >>On Wed, Sep 10, 2014 at 11:08 AM, Darren Hart <<a href="mailto:dvhart@linux.intel.com">dvhart@linux.intel.com</a>><br>
> >>wrote:<br>
> >>> On 9/10/14, 1:35, "Roel Jordans" <<a href="mailto:r.jordans@tue.nl">r.jordans@tue.nl</a>> wrote:<br>
> >>><br>
> >>>><br>
> >>>>><br>
> >>>>><a href="http://www.elinux.org/Minnowboard:MaxBios#Switching_from_64-bit_to_32-b" target="_blank">http://www.elinux.org/Minnowboard:MaxBios#Switching_from_64-bit_to_32-b</a><br>
> >>>>>it<br>
> >>>>><br>
> >>>>> Basically you have to re-flash the firmware with a 32-bit firmware.<br>
> >>>>> There's a line in the instructions that may confuse some folks,<br>
> >>>>> specifically using a FirmwareUpdateX64.efi to flash a 32-bit firmware.<br>
> >>>>> This is because when you go to change the firmware you are running a<br>
> >>>>> 64-bit firmware, and therefore need a 64-bit EFI program to actually<br>
> >>>>>do<br>
> >>>>> the flashing.<br>
> >>>>><br>
> >>>>> If you want to switch back, you'll do the opposite, use<br>
> >>>>> FirmwareUpdateIA32.efi to flash a 64-bit firmware.<br>
> >>>>><br>
> >>>><br>
> >>>>Maybe it's possible to rename those updates (or add some renamed<br>
> >>>>updates) to something like FirmwareUpdateIA32to64 or something? That<br>
> >>>>would probably remove most of the cause for confusion here.<br>
> >>><br>
> >>> That isn't accurate unfortunately. The update tool doesn't care which<br>
> >>>bit<br>
> >>> length you are flashing to, you use the same tool to flash to 32b or to<br>
> >>> 64b, what matters is what firmware you are currently running, and that<br>
> >>>is<br>
> >>> what the tool name reflects.<br>
> >>><br>
> >>> --<br>
> >>> Darren Hart Open Source Technology<br>
> >>>Center<br>
> >>> <a href="mailto:darren.hart@intel.com">darren.hart@intel.com</a> Intel<br>
> >>>Corporation<br>
> >>><br>
> >>><br>
> >>><br>
> >>> _______________________________________________<br>
> >>> elinux-MinnowBoard mailing list<br>
> >>> <a href="mailto:elinux-MinnowBoard@lists.elinux.org">elinux-MinnowBoard@lists.elinux.org</a><br>
> >>> <a 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 href="mailto:elinux-MinnowBoard@lists.elinux.org">elinux-MinnowBoard@lists.elinux.org</a><br>
> >><a href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard" target="_blank">http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a><br>
> >><br>
> ><br>
> ><br>
> > --<br>
> > Darren Hart Open Source Technology Center<br>
> > <a href="mailto:darren.hart@intel.com">darren.hart@intel.com</a> Intel Corporation<br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > elinux-MinnowBoard mailing list<br>
> > <a href="mailto:elinux-MinnowBoard@lists.elinux.org">elinux-MinnowBoard@lists.elinux.org</a><br>
> > <a 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 href="mailto:elinux-MinnowBoard@lists.elinux.org">elinux-MinnowBoard@lists.elinux.org</a><br>
> <a href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard" target="_blank">http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a><br>
<br>
_______________________________________________<br>
elinux-MinnowBoard mailing list<br>
<a href="mailto:elinux-MinnowBoard@lists.elinux.org">elinux-MinnowBoard@lists.elinux.org</a><br>
<a href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard" target="_blank">http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a><br>
</div></div></blockquote></div><br></div>